202
edits
Line 17: | Line 17: | ||
--[[User:Delve|Delve]] 02:42, 1 February 2009 (UTC) | --[[User:Delve|Delve]] 02:42, 1 February 2009 (UTC) | ||
:Where all would you be displaying them? Within the walkthrough as well, or just on the recipe pages (sorted in multiple ways)? You could make a table out of all the recipes, which can be sorted (see [[Kingdom Hearts II/Weapons]] for an example). You can add a "number" column so that people can sort by in game order. -- [[User:Prod|Prod]] ([[User talk:Prod|Talk]]) 04:11, 1 February 2009 (UTC) | :Where all would you be displaying them? Within the walkthrough as well, or just on the recipe pages (sorted in multiple ways)? You could make a table out of all the recipes, which can be sorted (see [[Kingdom Hearts II/Weapons]] for an example). You can add a "number" column so that people can sort by in game order. -- [[User:Prod|Prod]] ([[User talk:Prod|Talk]]) 04:11, 1 February 2009 (UTC) | ||
Displaying the full recipe info within the walkthrough would probably be disruptive so likely only in the recipe pages. However I don't think a table would work for a few reasons. | |||
#Too much data, I think the table would be too wide to display well. I can test this and see. | |||
#Uncertain number and type of effect. In order to be sure sorting will work properly each effect type would need a separate and unique column, which brings us back to #1. | |||
#Wouldn't that eliminate the ability to link directly to a recipe [[Aquaria/Soups#Hot Soup|like so]]? A direct link (rather than displaying the entire recipe info) is prefered within the walkthrough. | |||
I agree that one dynamic resortable table is better than many static lists, but I'm not sure it's feasible. What are your thoughts? Is there a particular reason to prioritize against extra pages? The individual recipes are not likely to change much over time. | |||
--[[User:Delve|Delve]] 04:40, 1 February 2009 (UTC) |
edits