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.
#158 Re:MozillaZine's ChromeZone Now Open!
Thursday May 27th, 1999 12:02 PM
You are replying to this message
Microsoft changes/adds functionality to their products' user-interface constantly. For example, in Win98, if you hold down the mouse button while moving around the start menu, you end up *dragging* items in the menu, instead of just passing over them, as was the case in Win95. This is a horrible breach as far as usability goes.
The only thing that Windows users have in common is a desire for their operating system to stay up long enough to get even the simplest tasks done.
MS keeps pulling the rug out from under their users, when it comes to user interface concerns. I have no worries that people will "get" Mozilla's new interface. Except for its load time - which I believe will be a moot point at release time, the XUL interface behaves just like the current Communicator interface, only it will be customizable to a much greater extent.
What problems *exactly* would you think people will have? And you can't say "load time" or "slowness" because, again, we have no idea what the finished product will be like.