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.
#126 Re:MozillaZine's ChromeZone Now Open!
Wednesday May 26th, 1999 4:51 PM
You are replying to this message
Well, my next question would be, if XUL is going to be improved by caching results of tree traversals in Hashtables, what is the predicted increase in memory usage predicted to me? TANSTAAFL.
I guess it is no higher than the memory hogged by viewing a web page (building DOM, build flow objects, ...)
Still, there is the cost of STARTUP time. I'm a Java programmer, and this is a big deal. I think the major reason people don't like Java apps is that they take *way too long* to load, and JIT's make it worse.
So the question is, what is being done to optimize XUL's startup cost?
Where is the bottleneck? is it opening up all those gif files?
Is there any chance that after the first time a new chrome is encounted, some state is saved so that launching the same chrome against doesn't take as long? Kinda like saving the output of a JIT?
My beef with XUL right now isn't the sluggish UI, just that it takes Mozilla longer to launch.