Template talk:Sandbox: Difference between revisions
Jump to navigation
Jump to search
m (update + eliminating deprecate refs) |
|||
| Line 11: | Line 11: | ||
::I agree that people might not recognize that they ''can'' use all the fields, but I think we can assume that users of this template are at least a little more wiki savvy than most, by virtue of the fact that they're involved in creating some sort of technical thing. |
::I agree that people might not recognize that they ''can'' use all the fields, but I think we can assume that users of this template are at least a little more wiki savvy than most, by virtue of the fact that they're involved in creating some sort of technical thing. |
||
::: Yes, the ''optionallity'' was basically my intent (didn't like all those ''missing/unknown'' fields). Another possible solution (that just popped into my head) is something similar to |
::: Yes, the ''optionallity'' was basically my intent (didn't like all those ''missing/unknown'' fields). Another possible solution (that just popped into my head) is something similar to {{tl|Babel-X}} but instead of User languages and preferences (as implemented in Wikipedia) we could have the ''Component xxx'' (Component Python, Component Game, Component l10n, etc) and the activity page would just a 'add them'... I was thinking polishing the {{tl|Babel-X}} for users, and use that as a the starting framework for the ''Software Component Babel''... --[[User:Xavi|Xavi]] 13:56, 3 July 2007 (EDT) |
||
:::: Update, we should soon be in condition of using general [[:Category:Userbox templates]] (for user attributes) and [[:Category:OBX templates]] for all others. We need to build the appropriate boxes, but hopefully a small set that cover those aspects in the {{tl|Status box}} will soon be up and running :) --[[User:Xavi|Xavi]] 16:02, 5 July 2007 (EDT) |
|||
Revision as of 20:02, 5 July 2007
Template:Status box re-working starting on 2007-06-01
I really like this, btw. --Lauren 11:30, 3 July 2007 (EDT)
- Thanks! It was not easy (I'm learning about the Parser Functions—quite tricky as all the tweaking saves proves ;) I concentrated myself on getting it to work, with caring for (structural) cosmetics (ie: table layout and whitespaces) but not other cosmetics.
- My doubts about the usability of this template are two-fold:
- people actually using it — since most parameters are optional, many users will probably not bother checking for the available fields to fill in (ie: l10n).
- maintenance and evolution — the source code IS tricky, and a simple enter in the wrong place can create some havoc in the layout :(
- The other bleeding edge in this template is the dynamic categorization... I like it, but should be tested further and decided upon. Again thanks, and if you (or anybody else) has ideas, comments, suggestions, the merrier I'll be! --Xavi 12:01, 3 July 2007 (EDT)
- I liked that most of the fields were optional.
- I agree that people might not recognize that they can use all the fields, but I think we can assume that users of this template are at least a little more wiki savvy than most, by virtue of the fact that they're involved in creating some sort of technical thing.
- Yes, the optionallity was basically my intent (didn't like all those missing/unknown fields). Another possible solution (that just popped into my head) is something similar to {{Babel-X}} but instead of User languages and preferences (as implemented in Wikipedia) we could have the Component xxx (Component Python, Component Game, Component l10n, etc) and the activity page would just a 'add them'... I was thinking polishing the {{Babel-X}} for users, and use that as a the starting framework for the Software Component Babel... --Xavi 13:56, 3 July 2007 (EDT)
- Update, we should soon be in condition of using general Category:Userbox templates (for user attributes) and Category:OBX templates for all others. We need to build the appropriate boxes, but hopefully a small set that cover those aspects in the {{Status box}} will soon be up and running :) --Xavi 16:02, 5 July 2007 (EDT)