Slashdot Mirror


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."

17 of 416 comments (clear)

  1. How about... by G-funk · · Score: 5, Insightful

    ...They leave everything as it is, and fix the resource leak in windows? It's hard to try and convince people to switch to my browser when I have to "end process tree" the thing once a day.

    --
    Send lawyers, guns, and money!
    1. Re:How about... by linuxci · · Score: 5, Insightful

      Well remember the people who design themes aren't the same sort of people who can fix resource leaks!

      Also have you got a bug number for this? I've not had any major problems with Mozilla or Firefox for ages.

    2. Re:How about... by hattig · · Score: 5, Insightful

      Definitely. It looks fine at the moment, but that resource leak is the biggest annoyance. Especially when everything stops responding because Firefox running as the only application starts paging on a 512MB machine.

  2. Definately a bad choice on the part of the devs by Xshare · · Score: 5, Insightful

    Qute was a great Default theme. It looked great as a default theme, and really made switchers from IE feel comfortable. This new theme just doesnt fit in Windows or Linux... it looks good for OSX, but just not in other OSes.

    1. Re:Definately a bad choice on the part of the devs by Xshare · · Score: 5, Insightful

      First off: That's not the new skin: This is. Second:Exactly. You have been using this skin. You know how to change a skin. Hell, you know what a skin is. You are also a reader of slashdot. That already means that you most likely are an advanced computer user, prolly use linux at times, and etc. Most people aren't. The people who we want to convert from MSIE don't like change. They don't want to go into the skinning thing and get a new skin. It's too complicated. First impressions are also crucial, and most "new users" would see this new skin as alien to them, and they won't want to go through the trouble of changing it, and will just slump back to IE. Just my take on things.

    2. Re:Definately a bad choice on the part of the devs by j7953 · · Score: 4, Insightful
      Qute was a great Default theme. It looked great as a default theme, and really made switchers from IE feel comfortable.

      I agree. Replacing this comfortable feeling with a uniform cross-platform look is a stupid idea. Who benefits from a uniform cross-platform look, anyway? Most computer users use only a single platform. They probably don't care at all how the browser looks on some other platform (hell, many don't even know that there are other platforms), but they do care if it looks like it was designed for the platform they use.

      People who use multiple platforms are likely to be experienced computer users anyway, so if they want a uniform look, they'll probably be able to install whatever theme they prefer on all the platforms they use.

      --
      Sig (appended to the end of comments I post, 54 chars)
  3. If you want to take market share by Anonymous Coward · · Score: 5, Insightful

    in the browser market, you'd be looking to take it from Internet Explorer (duh). That's Internet Explorer on Windows ... not the Mac. I think that it is important to have a default theme that makes it easy for the mums and dads to identify with (because they are not likely to change it). I think the current default theme does this and the proposed change is a mistake. But what do I know?

  4. Yay by W2k · · Score: 4, Insightful

    This is why I like open source software development. Just look at that forum thread. Inside a company like IBM or Microsoft, a debate like this would be kept covered up out of PR fears. Open source developers more often than not do not give a shit about PR (which is a good thing), they just want to make the best possible program. They also don't have to be afraid of losing their jobs, getting their salaries lowered, or whatnot. So we get to see the nitty gritty details of intra-project disputes and arguments from the front row, even silly things like what theme ships with Firefox as the default.

    Gotta love it.

    --
    Quality, performance, value; you get only two, and you don't always get to pick.
  5. Re:Fuck the Mozilla devs by linuxci · · Score: 4, Insightful
    The problem is when you debate every little detail to death you get a browser like the Mozilla suite which progressed relatively slowly because everything was a committee decision.

    Yes I do think this could have been handled a *lot* better because Arvid but a lot of work into this excellent theme and now is word will be getting a lot less attention as it'll now just be a downloadable theme on update.mozilla.org

    Also as you can see from the forum thread mentioned in the original article you can see the information process wasn't the best.

    However, ultimately difficult decisions have to be made and they can't satisfy everyone all of the time.

    If you look at the original charter for m/b, Phoenix, Firebird, Firefox you'll see that they intended from the very beginning to have only a small group of people making the decisions.

    To quote:
    The size of the team working on the trunk is one of the many reasons that development on the trunk is so slow. We feel that fewer dependencies (no marketing constraints), faster innovation (no UI committees), and more freedom to experiment (no backwards compatibility requirements) will lead to a better end product.

  6. Re:Fuck the Mozilla devs by Fnkmaster · · Score: 4, Insightful
    Those difficult decisions should not be made by Ben Goodger. I'm sure he's a great, stand-up guy. I've worked with engineers like him before - their code may be fabulous, but their sense of aesthetics is fundamentally broken. I support the idea of a small group *of artists and UI designers* making UI decisions, and a group with some marketing experience to make branding decisions.


    I've managed plenty of software development teams before, and you just don't assign any random engineer to make important UI decisions. Some people have the talent for this and some don't. It's part aesthetics, part usability, part style. Very important stuff, and not something you learn getting a computer science degree, hacking Unix, writing HTML rendering engines and so on.

  7. Theme choice... by Epistax · · Score: 4, Insightful

    Now I know you can just download themes to your heart's content. I'm using a tiny theme because that's the way I like it. However there's no reason not to have several default themes to choose from at install time. I would suggest the themes be "Default", "Internet Explorer", "Netscape", "Opera" and perhaps a Macish theme. As long as it is explained that this is simply the look and feel and has no real functionality differences (explained in a calm and simple manner), things should be less scary. Previous posters are absolutely right-- the more different it looks, the more scared the user will be, even if everything is in exactly the same place.

  8. From my reading of it by Chuck+Chunder · · Score: 4, Insightful

    The Mozilla devs did the right thing and asked about having Qute freely licenced 6 months ago. They were apparently told no and have therefore taken the only reasonable course left to them, sourcing another theme.

    The new theme might not be brilliant but it is a work in progress and rather importantly is freely licenced so other people will be able to tweak it over time.

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  9. You act like IE is stable... by gtaluvit · · Score: 4, Insightful

    I've seen IE barf on pages before. No browser is going to be perfect and I think explaining to people that you may have to close and restart a browser during the day (if they keep it open THAT long) is a lot easier than saying "ok, if you close those 5 pop ups and uninstall CometCursor, you'd see the page you're lookin for."

    --
    - gtaluvit (prnc. GOT-tuh-LUV-it)
    1. Re:You act like IE is stable... by Kyouryuu · · Score: 4, Insightful
      Just because IE isn't stable doesn't mean Firefox can't aspire to be. IE is an archaic browser as far as I'm concerned, and that's why Mozilla and Netscape are actually gaining momentum. Prior to Mozilla 1.0, IE dominated. Now, at least according to my statistic, it's more of a 90%-10% or 85%-15% distribution. And although that may seem small, in something as gigantic as the browser market, that's actually quite a lot of people.

      Why are they gaining? They offer technologies people want. Tabbed browsing, pop-up blocking, and are generally less crashy. They are also generally more immune to the various sorts of crap unscrupulous advertisers have been pulling that "infects" IE. To keep gaining, these browsers need to keep doing this. That means not allowing large and highly documented bugs like the memory leak in question to be ignored.

  10. Re:The new theme by chunkwhite86 · · Score: 4, Insightful

    And here is a complete screenshot of the new theme. I think this is a huge step backwards.

    Remember that to gain market share, you have to design the product for the average idiot. Yes, you know the one; the guy that thought his CDROM was a cup holder.

    To win the average idiot, you need simple layout, bright colors, and hand-holding wizards.

    --
    I'd rather be a conservative nutjob than a liberal with no nuts and no job.
  11. Re:Did they fix the Cancel/Ok buttons? by damiam · · Score: 4, Insightful
    No, the decision is because they did think about it. Cancel/OK makes more sense and is fundamentally easier to use than OK/Cancel. That's why Apple uses it.

    It'd be nice if Firefox could detect KDE and switch its button order. However, as Firefox is written in GTK and KDE already has its own non-Gecko browser, probably most of the Firefox developers aren't KDE users and don't care. If you do care, go ahead and code it.

    --
    It's hard to be religious when certain people are never incinerated by bolts of lightning.
  12. Re:Caution 0.9 will break ALL your extensions by Eil · · Score: 4, Insightful


    once again backwards compatibility has been sacrificed (and we are not even at 1.0 yet)

    Uh, hello? How did this get modded up?

    Rather than feeding this relatively obvious troll, I'll simply remind folks that the whole POINT of the pre-1.0 development cycle is to break things. And nobody's forcing anyone else to use Firefox, stable or not. End of story.