MozillaZine's ChromeZone Now Open!

Monday May 24th, 1999

Steve Morrison, creator of the XULTool, has joined MozillaZine (as some of you may already know). He has been hard at work getting the XULTool working on our site, and we're pleased to announce that the ChromeZone is now online.

Now, with a simple form, you can change the look and feel of Mozilla, and create your own themes! You can also choose from some ready-made themes we have available. You can also send your own themes to ChromeZone for addition to our site.

So, fire up apprunner and head over to the chromeZone.

We got a lot of great entries for our little "name our new chrome area" contest, but in our final vote, "ChromeZone" came out on top. A number of people submitted the name "ChromeZone" or a variation for our contest. Clayton Scott was the first, however, and his prize is a stuffed Mozilla doll from Netscape. I know we didn't promise any prizes for the contest, but we wanted to give something to the winner.

Thanks to everyone for you contributions, and if you have any suggestions for the chromeZone, let us know.

#28 Re:MozillaZine's ChromeZone Now Open!

by mozineAdmin

Tuesday May 25th, 1999 5:00 PM

You are replying to this message


I don't think you understand the nature of XUL and the definable chrome. The mozilla group is enabling a cross-platform web application platform. The idea is this: Web-based applications are, by their nature, cross platform. They utilize HTML for their display and interaction with the user. However, the applications are always restricted by the notion that their user interface and content all must share the same content space. The major benefit of the new UI model is that web application developers can alter the interface of the browser itself.

Why is this useful? First, the web applications that run in the browser can actually perform behaviour modifications to their UI (instead of downloading the altered navbar every time, you only send the change down). For example, in the example of our article administration application, let's say we're displaying an article in our browser window. Instead of downloading the navbar with the addition of a "delete this article" button, we download an XUL fragment for the "delete" button, which pulls the images from the chrome cache and displays the button in our "chrome" toolbar. A few lines of text and no images to download (after their initial download), instead of an entire navbar specification and images (because, remember, images in the browser window may have expired from cache).

Second, through Mozilla's source, XUL makes it easier to develop whole new Internet-based, cross-platform and *localizable* applications. By providing the structure for localization and the cross-platform compatibility of a common UI interface, markets for applications open up considerably. Someone who would develop strictly for Windows now finds that it's just as easy to develop for multiple platforms at once.