Recommended Posts

The only reason I can come up with is that they're lazy and slow. :p

In all seriousness, you're right, and to be quite honest most of the basic theming should have only taken a few days to complete.There's no reason to skin elements in a half-assed manner, just as they've been doing simply to get it out the door. Especially when it only takes a few minutes to skin something with CSS properly if you're familiar with the language.

Coding for a major project is not as simple as banging out some CSS and bam you're done. Themers might be able to do that, but you can't do that to the core product. Everyone has priority lists. Everything has to work with everything else. Everything needs to be doublechecked and refined.

If you're finding it slow, offer to help. It is an open source project, after all.

Coding for a major project is not as simple as banging out some CSS and bam you're done. Themers might be able to do that, but you can't do that to the core product. Everyone has priority lists. Everything has to work with everything else. Everything needs to be doublechecked and refined.

If you're finding it slow, offer to help. It is an open source project, after all.

When it comes to coding the default theme itself, it really isn't much different then developing one separately. I understand them taking their time integrating new features, don't misunderstand that. It's their usual method of throwing in a tacky looking element and leaving it that way for months before deciding to skin it properly to reflect the mockups that makes no sense.

Here's a perfect example. Rather than spending 3 minutes to skin this quick, "draft" version of the App Button, it would have made far more sense to spend 5 minutes to do it properly.

firefox4-about-addons.png

This is all my personal opinion, which you're more than welcome to disagree with.

When it comes to coding the default theme itself, it really isn't much different then developing one separately. I understand them taking their time integrating new features, don't misunderstand that. It's their usual method of throwing in a tacky looking element and leaving it that way for months before deciding to skin it properly to reflect the mockups that makes no sense.

Here's a perfect example. Rather than spending 3 minutes to skin this quick, "draft" version of the App Button, it would have made far more sense to spend 5 minutes to do it properly.

firefox4-about-addons.png

This is all my personal opinion, which you're more than welcome to disagree with.

I'm not trying to counter your point, but I am curious if it might be they want to get the core functionality down first before making it look right?

Beta 9 is out NOW:

ftp://ftp.mozilla.org/pub/firefox/releases/4.0b9/win32/en-US/Firefox Setup 4.0 Beta 9.exe

other languages: ftp://ftp.mozilla.org/pub/firefox/releases/4.0b9/win32/

mods: update the thread title please.

Dated the same as build 1. Are they the same?

Suppose I'll give this a spin again but I've found every previous beta to be really unpolished and quite disappointing.

That and the terrible font rendering, although I've heard one of the recent Windows 7 hotfixes was suppose to help that.

edit: Font rendering still looks crap compared to Chrome on my system :(

Suppose I'll give this a spin again but I've found every previous beta to be really unpolished and quite disappointing.

That and the terrible font rendering, although I've heard one of the recent Windows 7 hotfixes was suppose to help that.

That's why it's called a "beta" ;)

That's why it's called a "beta" ;)

Well the release is apparently about a month away!

Anyway, still can't use this beta until MS fix the font rendering, it's just terrible. I know I can turn off hardware rendering, but it works fine in Chrome so I'd be going backwards not using it.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.