PropertyValue
rdfs:label
  • GuildWars Wikia talk:Style and formatting/Archive 2
rdfs:comment
  • I am strongly in favor of expanding the use of icons throughout this wiki. Icons are the best way to display information at a glance. Like I said in some other talk: You can't overdose icons. This goes for profession icons as well as icons for items and skills. To allow for easier use of icons I have done two things for the start: What do you think? --Tetris L 03:46, 15 Oct 2005 (EST)
dbkwik:guildwars/property/wikiPageUsesTemplate
abstract
  • I am strongly in favor of expanding the use of icons throughout this wiki. Icons are the best way to display information at a glance. Like I said in some other talk: You can't overdose icons. This goes for profession icons as well as icons for items and skills. To allow for easier use of icons I have done two things for the start: 1. * I suggest a very simple template that allows for very quick and easy insert of profession icons: {{W}} will display as a warrior icon: Image:Warrior-icon-small.png 2. * I suggest a more general template for icons, that displays the icon of an article next to the link. {{Icon|Hamstring.png|Hamstring}} will display as: Image:Hamstring.png.jpg Hamstring.png. For this to work we would have to stick to a certain naming convention for icon files. See Template talk:Icon. What do you think? --Tetris L 03:46, 15 Oct 2005 (EST) (Edit: the original Template talk:Icon has moved to Template talk:Skill icon) -User:PanSola (talk to the Image:Follower of Lyssa.png) 05:42, 27 June 2006 (CDT) Icons are cool. The shortcuts for the profession icons would be a GREAT plus.. I suggest something intuitive though, like {{{W icon}}} so that editing contributors can recognize what that is. As I mentioned in the Template talk, I find no difference between the Template:Icon and the actual format used right now. I also think talking away the user's ability to SCALE the image (by placing it in the template) is a bad thing. --Karlos 08:43, 15 Oct 2005 (EST) For the profession icons I would want the minimum amount of code. And I think the code is pretty intuitive if we use the official acronyms (W for Warrior, Mo for Monk, etc). If a contributor sees the code and sees the result he should get the idea very quickly. The use of the icon template is questionable, indeed. My original idea was to simplify the code a lot, but that would only have worked if all icon files were following the name convention. But most of them don't. Plus, there is the problem about the apostroph. This "breaks" the code of the template. If we have to type the file name in the template too, then we might as well forget about the template and type the full code instead. It isn't much longer. And it allows to scale the icon. --Tetris L 19:00, 15 Oct 2005 (EST) I'm not going to argue over 4 letters. Suffice to say, I am the kind of programmer who prefers FunctionThatDoesGreatThings(GreatIdea, GreatThingDesired, PointerToGreatObject) over func(a,b,c). If you get my drift. --Karlos 20:24, 15 Oct 2005 (EST)