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.
  • Posts

    • LOL. Can't even quote and edit a comment correctly. Figures you're a Linux user.
    • I have disabled it, but the app is still taking space. I have a Mac and it is only possible to disable Ai on that, but I think that bit does get rid of the AI components after a while. What we are told is that we agree to all this when we use the devices as it is in the end user agreements, their software, they can do what they like. I doubt that any bill will happen in the U.S, the government there are in league with big tech firms. The E.U maybe, they seem to have some guts when it comes to tech companies. The U.K is not in the E.U, but some things still affect us. Our government is as gutless when it comes to tech companies as the U.s government.
    • WebChangeMonitor 26.06 by Razvan Serea Monitors allows you to quickly check a number of web pages and tracks changes based on the content of the web pages. Allows to monitor several protocols, including HTTP and HTTPS. Allows to view and record differences. Available for Win7/10, Linux and others. WebChangeMonitor features: Allows monitoring of web pages and informs about content changes Indication of states of currently monitored items in the tool and taskbar Reporting as sound and/or email as well as log file or HTML log Several configuration / filter options Support all protocols, e.g. http, https Multi-threaded, running in the background Bulk-import and bulk-export of items (from/to CSV) to monitor Export of results to CSV file for further processing Allows running command on items states and/or showing diff (changes) of content with preferred diff-tool ...and many more! Open Source (C++, wxWidgets) Cross platform for Windows (7/10), Linux, RPi and Mac (if self-compiled) WebChangeMonitor 26.06 release notes: Release 26.06 brings mostly s but updates the underlying core infrastructure. A major compiler is used for both x86/x64 and WoA64 architectures. This also means that all core libraries are re-compiled accordingly which required some changes in the build scripts. One of the core libraries (cURL) has been updated to address vulnerabilities and a nasty linker error that was causing the need for a dedicated patch which could now be eliminated. Download: WebChangeMonitor 64-bit | Setup 64-bit | ~10.0 MB (Open Source) Download: WebChangeMonitor 32-bit | Setup 32-bit View: WebChangeMonitor Website | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
    • Rising Star
      olavinto went up a rank
      Rising Star
    • One Month Later
      lamborghiniv10 earned a badge
      One Month Later
    • Week One Done
      lamborghiniv10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      PsYcHoKiLLa
      257
    3. 3
      Steven P.
      74
    4. 4
      +Edouard
      69
    5. 5
      Skyfrog
      68
  • Tell a friend

    Love Neowin? Tell a friend!