On Sun, Apr 3, 2011 at 12:14 PM, Amir E. Aharoni <
amir.aharoni(a)mail.huji.ac.il> wrote:
2011/4/3 Brion Vibber <brion(a)pobox.com>om>:
In particular, I think there's some
low-hanging fruit in the Gadgets
system.
Right now it's honestly pretty awkward to
create a Gadget in the first
place, and sharing code modules between wikis requires a lot of
cut-and-pasting (which leads to divergent code bases, which makes
maintenance nigh-impossible in the face of MediaWiki framework changes).
I'm not a real MediaWiki developer, so it may be a silly question: How
hard it is to convert a gadget into an extension? If it's not too
hard, wouldn't it be better to redo useful gadgets as extensions?
Unless i miss something very basic, this will make them easier to
maintain, install, update and localize.
In principle, making an extension based on an existing Gadget should be
pretty straightforward, especially with ResourceLoader taking care of more
of the details of JS & CSS fetching.
Might be fun to whip up a how-to guide and post it on the tech blog...
-- brion