5,391
edits
Template talk:BSLjunc: Difference between revisions
reply
No edit summary |
(reply) |
||
| Line 10: | Line 10: | ||
:All right, I've simplified the format for listing variables (functions will be more complicated, so I'm leaving them aside until we can agree on variables). How does look to you? Note the hovertext. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 16:58, 20 February 2018 (CET) | :All right, I've simplified the format for listing variables (functions will be more complicated, so I'm leaving them aside until we can agree on variables). How does look to you? Note the hovertext. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 16:58, 20 February 2018 (CET) | ||
::The hovertext for the variable name seems redundant, so I'd change it to display the default value instead (it's a bit counter-intuitive if the default value is displayed only when you hover over the type). So there can be not two hovertexts but one, for the whole field (only the variable name would work as a link to the variable's redirect page). | |||
::Also, I'd make the type listing optional (either with two templates, "verbose" and "minimal", or with a parameter that gives "minimal" display by default). The lack of brackets is enough to identify the variable as a variable and not a function, and the hovertext in the "minimal" case can include the type, something like: "boolean; default value at game start: false". | |||
::There can probably be a second line of hovertext as a reminder of a variable's effect or an indication of the "group" it belongs to - either picked from the database or supplied in the page's context through a parameter. Other than that, it's OK. --[[User:Geyser|geyser]] ([[User talk:Geyser|talk]]) 21:13, 20 February 2018 (CET) | |||