FYI ...
- XUL within XHTML doesn't work properly. Or better said, _I_ couldn't
make it work properly ;) One of the main ideas of BXE was and still is
to provide easy integration in existing projects/CMS/you-name-it. And
therefore it has to work with simple HTML documents. It's too much pain
to have the implementators force to deliver XUL, IMHO.
Are BXE loaded documents XML or XHTML?
http://bugzilla.mozilla.org/show_bug.cgi?id=183641
http://bugzilla.mozilla.org/show_bug.cgi?id=70049
- remote xul is also one of those not much used features out there. You
get a lot of tutorials/help etc, if you serve XUL from your chrome
directory, but leaving that, you're mostly on you own (maybe that
improved). Furthermore you have a lot of security restrictions if you
serve XUL remotely. This is another goal of BXE: It should work
remotely, meaning you don't have to install anything to get it work
(this will change a little in the future, if you want some of the more
advanced stuff, which you only can make work, if it's installed locally,
like really-native-clipboard access, saving to local files, etc..)
http://bugzilla.mozilla.org/show_bug.cgi?id=133695
More details for the interested here:
http://www.oreillynet.com/pub/a/mozilla/2002/12/17/app_dev.html
http://www.oreillynet.com/pub/a/mozilla/2003/05/02/casestudy2.html
Having said that, i'd like to point out, that there are implementations
for mozile, which use XUL, and AFAIK the xpi version of mozile does have
a seperate tool bar as well.
I have not looked at mozile, but their XPI must be installing the
toolbar into chrome. This would be one option for BXE ... though would
not be cross-browser. You could have an optional XUL toolbar, but this
would mean maintaining 2 toolbars, the HTML one and this one.
--
Brian King
www.mozdev.org
www.mozdevgroup.com
--
bx-editor-dev mailing list
bx-editor-dev@xxxxxxxxxxxxxxxx
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev
|
