MozillaZine

Full Article Attached Open XUL Alliance Site Goes Live

Sunday May 25th, 2003

Gerald Bauer writes in with news that the Open XUL Alliance site has launched. The site aims promote XUL and encourage interoperability with a collection of XUL news articles, mailing lists and links.


#51 W3C

by dhyatt

Wednesday May 28th, 2003 12:56 PM

You are replying to this message

"Ask yourself why does the W3C show no interest in XUL (XML UI Language)?"

The point of the W3C is to create frameworks that can then be used by organizations like Mozilla to describe markup languages (like the XUL language). XUL fundamentally breaks down into several pieces:

(1) Layout primitives - These are all defined using CSS and are completely independent of the XUL markup. You can make divs or spans into boxes, grids or popups right now in Mozilla today. These layout primitives are designed to integrate with the rest of the CSS layout primitives. You can't view the new primitives in a vacuum, since you need block and line layout in order to do simple wrapping markup even in XUL dialogs. (2) Widgets - The widgets in Mozilla largely (with a few exceptions) fall out of having the layout primitives + XBL. You could of course map the XUL markup to native widgets or any widgets you want to. (3) XUL Templates - For dynamic building of markup from back-end data. (4) Infrastructure - Commands, keys, etc. The rest of the markup.

The point of W3C technologies like CSS, DOM, XSLT, etc. is to create a framework that enables you to define your own markup languages. Most of the XUL implementation is independent of the markup used to describe it. This behavior, therefore, is outside the province of any one particular markup language design.

How the XUL box model should behave is therefore a question best decided by the CSS WG, since you have to consider its integration with the rest of CSS, e.g., how does it work with overflow, z-index, when a child of a block, with min and max width, etc. etc.