On 04/05/06, Pete Bartlett <pcb21(a)yahoo.com> wrote:
Theoretically,
yes. I thought about having a similar system, only the
entire code would be written back to the monobook.js, because it's
protected from other users. However, I'm not sure that it would be
/practical/ to implement it without something like XUL to get the UI
setup - ie. it would be a Mozilla extension.
This is all very sexy. But wouldn't an easy first step just to be gather
the code in one set of pages first? Then users can do "manual" transclusion
to begin with, and the neat interface could come later?
Well, the French page given before does just that. But copying and
pasting becomes very quickly unmanageable. What do you do when you
have 30 extensions and your monobook.js doesn't compile? How do you
remove one extension without breaking others? I do it by embedding big
///////////////// comments around them, but it's still a bit dicey.
Steve