We need to write documentation for Gadgets 2.0.
Specifically, flesh out the sections at https://www.mediawiki.org/wiki/Gadgets_2.0.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T34169 Action to join scripts and styles in one file | |||
| Open | None | T110014 Make gadgets easily customizable (merge Gadgets' branch "gadgetprefs" from GSoC 2011) | |||
| Open | None | T31272 Implement Gadgets 2.0 | |||
| Resolved | kaldari | T118224 Gadgets 2.0: Write documentation |
Event Timeline
Comment Actions
@Legoktm, @Krinkle: I imagine we want to encourage gadget writers to use some sort of namespacing for their translatable messages (so that they don't collide with other gadget messages or MediaWiki software messages). Any suggestions regarding that? Maybe MediaWiki:gadget-foo-message? (For example, MediaWiki:gadget-hotcat-submit-button.)
Comment Actions
@kaldari: Indeed. That should be the encouraged pattern. However I don't think we should enforce it by design since there is value in re-using core and extension messages as well. This is no different from other messages administrators can (and do) create for the sidebar and various other interface components.
In extensions we have conventions against re-use of messages but that's more viable there due to being backed by translatewiki.net. That isn't the case for gadgets.
Comment Actions
@Krinkle: Thanks for the feedback. Feel free to tweak the documentation further at https://www.mediawiki.org/wiki/Gadgets_2.0.
Comment Actions
The mw.Message constructor accepts an instance of mw.Map as argument. A separate mw.Map of messages could be provided to each gadget.