A New Look For Firefox

ben writes "Regular users of Mozilla Firefox may be interested to know a new default theme is planned for 0.9 in preparation for the road to 1.0. 0.9 will also feature new improved theme and extension management, which will make it easy to make Firefox look the way you want it to."

Comments

Re:I liked the old look

[Conor Turton]

The preferences importing from Opera works extremely well. In fact I wasn't aware it was there, installed FF 0.9 and fired it up for the first time to set it up just to find it loading up my homepage and my Opera bookmarks were all there.

A welcome suprise and it means I can get shut of my 3rd party bookmark convertor.

Re:The new theme

[linuxci]

This is not informative. That's not the new theme. The article at the top points to the thread with the discussion about the new theme.

This is a port of the Mac Pinstripe theme, although the new theme based on Pinstripe but called Winstripe (the GNOME version is called GNOMEstripe - not Linstripe!) I assume these names won't be used in the finished product though.

Anyway back on track, although Winstripe will be similar to Pinstripe the icons will look more Windows like and therefore not a total Mac lookalike.

Re:Did they fix the Cancel/Ok buttons?

[linuxci]

That order is only in Mac/Linux builds.

The reason for it in Mac is because all apps should be that way due to the UI guidelines.

As for Linux apparently it's in the GNOME UI guidelines. However, I rarely use any other GNOME apps in Linux, most things I do are either in browser or in a terminal window - therefore the button ordering is frustrating for me when I'm in Linux because I switch between Windows and Linux more than Linux and Mac.

But technically they're doing the right thing - although ideally it'd only display in that order if you're actually using GNOME.

Re:And what was Firefix was for, again ??

[linuxci]

Firefox was *supposed* to be a *fast* lean-and-mean browser. One reason was given that bundling IE with OS works because people are too lazy to download another browser. That gap WIDENS as the download size increases. Already Firefox is 10+ MB!!!!

Don't be such a troll. The download size for Firefox hasn't been anywhere near 10 meg (except perhaps before they stripped out all the app suite stuff).

If you look at the latest branch builds you'll see that the current download is below 5 meg on Windows.

Re:You need a bigger "but" next time

[Fnkmaster]

I've spent a lot of time on the Mozillazine forums and so have many others who've contributed code, artwork, testing and hundreds upon hundreds of hours of their time. I am talking here about the core developers from Mozilla.org who have actively displayed their arrogance repeatedly to the rest of the community. In particular, I think Ben Goodger has stood out as a tremendous prick. In fact, my original post said "Fuck Ben Goodger" in the title, but I decided it was too much of an ad hominem, when many of the others have stood up far too strongly for Goodger.

Ben Goodger is the strongest anti-advocate for Mozilla I have ever seen. There are hundreds of other developers who have contributed lots of code to the original Mozilla project and the Firefox codebase. Many of these are great people who have quietly contributed tens of thousands of hours of their work over the years to the community. And those people I respect immensely. The ones who insist on repeatedly driving rifts through and disrespecting the fabulous community of Mozilla supporters that have evangelized their product and fought for a better, more standards-compliant internet everywhere else have been done a tremendous disservice to the rest of the Internet, and I have simply lost my respect for them.

Re:Did they fix the Cancel/Ok buttons?

[marq00z]

It's not a bug, it's a feature. The Cancel|OK order appears only in Linux and Mac OS X and it's done this way to be compliant with Gnome and Apple Human Interface Guidelines. If you want to have the Windows-like OK|Cancel order, just add these lines to your userChrome.css in your .firefox//xxxxxx.slt/chrome directory:

.dialog-button-box {
-moz-box-direction: reverse;
-moz-box-pack: center;
}

.dialog-button-box spacer {
display: none !important;
}

Re:Why bother?

[linuxci]

I've just had a look at the bugs mentioned and they're both being worked on. Therefore it's unlikely you'll see them when 1.0 comes out. However, like I said previously, the type of person who can design a good theme is unlikely to be able to help with the other bugs

Caution 0.9 will break ALL your extensions

[Anonymous Coward]

do not install 0.9 until (if) the extensions have been updated as it will break

once again backwards compatibility has been sacrificed (and we are not even at 1.0 yet) we had now 200+ extensions have to be updated and some have been abandoned as they worked, now they will be broken and useless

i hope all this aggro was worth it, or you might find a lot of people just give up with it and go back to IE while its got a lot of failings at least you know where you are with it and it doesn't keep breaking every month

Re:Caution 0.9 will break ALL your extensions

[colinramsay]

0.9 will FIX the extension system in Firefox, which has been one of it's weakest points thus far. After 0.9 there will be no further major shifts in the way extensions are handled, and so this is the first and only time that extensions have been broken in this way.

It's a necessary change.

I reported the leak on October 17, 2003:

[Futurepower(R)]

I reported the memory leak on October 17, 2003:

Firefox 0.8: All instances crash. Memory leaks.
http://bugzilla.mozilla.org/show_bug.cgi?id=222660

(Copy and paste the link to view the bug report.)

Please add your experiences to the report.

I reported the same bug in Mozilla browser, a long time ago. Huge memory leaks have existed since Mozilla version 1.0.

A recent experience: After two days of opening and closing instances of FireFox, with two FireFox instances open and maybe 5 tabs total, the FireFox memory usage in Windows XP was 374,656 kilobytes. When I closed one of the instances, the memory usage went UP to 385,868 kilobytes.

When you reach the limit of installed memory, Windows XP has to do its terrible disk thrashing thing. If Bill Gates weren't so poor, he could fix that. The advantage of open source is that there is at least a chance that the FireFox bug will be fixed.

Re:I reported the leak on October 17, 2003:

[Alexis de Torquemada]

Blatant MS bashing gets you mod points aparently. When you reach the upper limit of memory, this "disk thrashing" you speak of is the cache being resised. All that you need to do to stop that is set your cache minimum size the same as the maximum. No more disk thrashing. Or you could just hate on M$, that might be even easier.

Poppycock. In order to shrink the cache, only dirty pages have to be flushed. However, dirty pages have to be written much earlier than that in order to reduce the damaging effects of system or power failures anyway, so most of the cache will very likely not be dirty at that time. Cache pages which are not dirty, i.e. identical to the version on disk do not need to be written out, but can simply be discarded. So shrinking the cache should typically involve little disk I/O. Exceptions would be times where you do write lots of data to harddisk (e.g. downloads over a fast connection).

Btw, Linux may write "anonymous" pages (e.g. application memory) that haven't been recently accessed into swapspace before it actually runs out of physical RAM, but keeps them in RAM as "not dirty". That way, it can also just discard them once memory conditions get critical, and thus avoid a lot of disk I/O delays.

Re:Slashdot Rendering

[marq00z]

This bug has been fixed recently. (bug 217527).

Screenshot of the New Default Theme

[sgarrity]

Here is a screenshot of the new theme.

Screenshot of the new theme

[Anonymous Coward]

The author of the new theme, Kevin Gerich, has posted a screenshot in his blog:
http://kmgerich.com/archive/000062.html

Re:Yay

[eyeye]

Firefox devs make their decisions (e.g name changes!) behind closed doors and the first you know about it is when they have already made the change.

I am glad he released this info.

Re:How about...

[xandroid]

A thread I stumbled upon at MozillaZine mentioned that these resource issues won't be fixed in 0.9, or even 1.0.

(Not sure if this is gospel truth, but I sure hope not... kill -9 firefox is getting old...)