> I was wondering what people thought of how XBL should be python-ified.
XBL "1.0" (what's implemented in cvs.mozilla.org under
mozilla/content/xbl) should not be.
XBL 2 is under discussion among major browser vendors (except MS) and in
the w3c (where it may not end up being called that, or implemented in a
usable way except for SVG). Mozilla could claim the trademark, and may,
but aside from standards politics and related train-wrecks, our plan is
to work quickly to prototype XBL 2, or perhaps XBL 1.5, in the next few
months, in a language-neutral fashion. That means *no* intermingled JS
and XML, with method formals and name in the XML but bodies in CDATA
marked sections full of JS.
The idea is to completely separate implementation from interface and
generic data. That way, you could implement in Python or JS, and the
caller would be no wiser.