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.

#27 Re:MozillaZine's ChromeZone Now Open!

by kidzi

Tuesday May 25th, 1999 4:54 PM

You are replying to this message


I see what you are saying, but there are two short term probs which XUL addresses, for one, it is something that non-coders can do and feel good about. That may sound kinda cheesy, but it allows those who can program to work their butts off on the core program and focus on making gecko feature complete by the time it is ready. I'm sure if XUL, as you say, turns out to suck, then when we have a version one out, we can begin to work on something else. But by then the core functionality for the program will be more/less ironed out and we will have a bunch of developers who can create something.

Plus, the benefits of that is that at the end, if, for shits and giggles, they decide to dump xul and make it all proprietory for the platform, they will HAVE the mockups, the exact layouts most popular with the users to work with. They will KNOW what they need, and they will also already have the hooks to implement this in no time. Whereas otherwise you go back and forth with the code to add a button here or there. The XUL allows them to 'prototype' the environment, or i should say, allows the USERS to prototype THEIR environment.

Now of course Mozilla probably won't dump XUL, but i hope you can see the benefits for it at this stage especially. If it does come down to a major performance degredation, then I hope they can make a compiled form of XUL perhaps, a way to natively read it in instead of parsing it, maybe in some sort of bytecode of .class type of format, as well as .xul to help the speed. Or they could have the program come compiled with an XUL builtin, and allow the user to easily override the default, at their own performance expense.