MozillaZine

New Sample UI Posted

Monday March 22nd, 1999

We at Mozillazine have been playing around with XUL/CSS, and have created our own UI. It is similar to the old configurable chrome in mozillaclassic. To try it, simply rename the navigator.xul file to navigator.xu~, which is in the res/samples/ directory of the m3/nightly builds, download the new navigator.xul (*shift-click!*) file and place it in the same directory. This will download all the chrome and other UI elements when you load apprunner. Note, this will not change any UI except for the browser window.

In the UI, we killed the second/personal toolbar, added our own menu, changed the colors and buttons, and added some functionality. You can now load a new window, Messenger, or Composer from the bottom toolbar/component bar.


#51 Re:New Sample UI Posted

by SomeSmartAss <improv@magma.ca>

Wednesday March 24th, 1999 6:10 PM

You are replying to this message

As for my opinion on page specific "skin" replacment (and I know how much my opinion realy counts), it should be a link off the main page [Hey, download our Netscape Skin here!!] instead of a warning dialog popping out of no where telling you its about to be downloaded unless you say "NO". this would mean two things; a) it would be less obtrusive (I HATE that dialog that pops up asking if I want to download custom cursors all the time) b) it would also make these sites have a "Choose Netscape/Mozilla" button right around the Skin link (Free press is good press).

As for the actual downloadability, it should be built in to the end design with a section in the Preferences Dialog, allowing you to change to one of the installed "skins" (a la the highly over-rated NeoPlanet) and a seemless install front end. (I don't see my Grandpa renaming and replacing files and other such fiddling around)

Ideally, Netscape should put out a Skin design utility, or an extention of the composer app, that would allow WYSIWYG design without the need for people to learn XUL. This would create a proliferation of Skins, and minimize bad code. (course, the real code jockeys would be up to their arses in it, to make it do weird and wonderful new "features")