User talk:The Retro Gamer: Difference between revisions

m
Text replacement - "[Cc]haracter-infobox" to "character infobox"
m (Text replacement - "Special:WebChat" to "MarioWiki:Chat")
m (Text replacement - "[Cc]haracter-infobox" to "character infobox")
Line 181: Line 181:
:You seem concerned about the number of pages in my userspace. Reading through [[MarioWiki:Userspace]], I see nothing concerning about having multiple subpages as long as they're related to the wiki. If I wanted to I ''could'' move everything to the sandbox, but it's a personal demarcation: the sandbox is for testing things, and other subpages are for other organizational hierarchies. [[User:The Retro Gamer|<span style="color:red;">--The</span>]] [[User talk:The Retro Gamer|<span style="color:green;">Retro</span>]] [[Special:Contributions/The Retro Gamer|<span style="color:blue;">Gamer</span>]] 23:13, 22 April 2018 (EDT)
:You seem concerned about the number of pages in my userspace. Reading through [[MarioWiki:Userspace]], I see nothing concerning about having multiple subpages as long as they're related to the wiki. If I wanted to I ''could'' move everything to the sandbox, but it's a personal demarcation: the sandbox is for testing things, and other subpages are for other organizational hierarchies. [[User:The Retro Gamer|<span style="color:red;">--The</span>]] [[User talk:The Retro Gamer|<span style="color:green;">Retro</span>]] [[Special:Contributions/The Retro Gamer|<span style="color:blue;">Gamer</span>]] 23:13, 22 April 2018 (EDT)
::Thing with para needed is that it's an error call, which is something editors usually try to ''avoid''. How we usually have it set up, like in cases with infoboxes and other tables, if a parameter is ignored, it is excluded from the transclusion.  
::Thing with para needed is that it's an error call, which is something editors usually try to ''avoid''. How we usually have it set up, like in cases with infoboxes and other tables, if a parameter is ignored, it is excluded from the transclusion.  
::Take [[Template:Character-infobox]] for example; if "|full name=" is not used on a page, the parameter is ignored. Adding an error call and causing a large <span class="error">full name= is required</span> where the parameter should be is not only space-consuming, but it looks terrible, and if there is something to include there, it would've been included in the first place. Or the parameter can be added later, fully coded and ready to use. This template does not seem necessary.
::Take [[Template:character infobox]] for example; if "|full name=" is not used on a page, the parameter is ignored. Adding an error call and causing a large <span class="error">full name= is required</span> where the parameter should be is not only space-consuming, but it looks terrible, and if there is something to include there, it would've been included in the first place. Or the parameter can be added later, fully coded and ready to use. This template does not seem necessary.
::And you're right, there is no limit to userspace pages as long as they are helpful to the mainspace or are meant to be transcluded onto several pages, like a talk archive or status page. But if it's something like a simple table, it doesn't really need a page of its own, unless you're planning on transcluding just it somewhere else (which is something you don't usually do with a table). {{User:Alex95/sig}} 23:26, 22 April 2018 (EDT)
::And you're right, there is no limit to userspace pages as long as they are helpful to the mainspace or are meant to be transcluded onto several pages, like a talk archive or status page. But if it's something like a simple table, it doesn't really need a page of its own, unless you're planning on transcluding just it somewhere else (which is something you don't usually do with a table). {{User:Alex95/sig}} 23:26, 22 April 2018 (EDT)
:::It does look terrible, and that's on purpose. These templates are meant for a very specific purpose, and diverging from that purpose is ''always'' wrong. A table can't skip a cell; it should always be filled with ''something''. An error could alert the current editor or any future editor that the template needs to be modified. I could have set it so that it would display "n/a" if a table cell is not filled, but I want the editor to make the conscious choice to format it that way, rather than have any risk of accidentally missing a cell. It's a bit different from a navbox, because a navbox can be expanded to add more information, while a table needs all of the cells in a row filled when a row is created.  
:::It does look terrible, and that's on purpose. These templates are meant for a very specific purpose, and diverging from that purpose is ''always'' wrong. A table can't skip a cell; it should always be filled with ''something''. An error could alert the current editor or any future editor that the template needs to be modified. I could have set it so that it would display "n/a" if a table cell is not filled, but I want the editor to make the conscious choice to format it that way, rather than have any risk of accidentally missing a cell. It's a bit different from a navbox, because a navbox can be expanded to add more information, while a table needs all of the cells in a row filled when a row is created.