MozillaZine

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.


#310 Re:MozillaZine's ChromeZone Now Open!

by petejc <pete@mozdev.org>

Saturday June 5th, 1999 10:06 AM

You are replying to this message

Anon,

I think everyone is missing the whole point of XUL.

The default UI will be very standard, and speed will not be a problem.

The idea is that a web developer, who writes a web app, say a search engine, a script editor, spread shed, whatever, will have access to the UI. The idea being, if you are going to write an app and are cut off from the UI then this is a big problem.

Thus, this is where we currently stand with the state of web apps.

So say I write an database driven web app for a client using XUL and say PHP on the server side. The end result is an Icon the user will keep on their desktop (and yes we can create our own icons) that will open the remote web app as an application not as a browser. This is a separate entity. Their default UI has nothing to do with this new app. The user is now using a web application and not a web browser.

This is where XUL will be primarily utilized.

So you might say well what good is it if you have to force the user to use mozilla and they can't use IE instead.

Well first of all the user will probably be a client that has come to you for some kind of web based solution or migration. They are asking you to "build an app that will need to be accessible to their employees, 20 are using NT, 10 mac, 40 win 95 and 5 are unix admins. We need this to be able to work on on all of these platforms be developed quickly and cost efficiently." The answer is simple, I would write it in XUL, javascript, and PHP.

Have a look at all the apps you use. You had to first buy the version that will run on your platform (if there is one) install it on your local drive where it takes up space, has its own Icon and UI environment.

Where with a XUL based app very little space is taken up. The Icon is just a link to the file. Think about how easy it is to upgrade the app. The next time they open the link it could be a new version. An new developing environment that is extremely malleable.

I think this can revolutionize web development.

Something to think about.

Pete