Tree Closes For 0.9.8
Wednesday January 16th, 2002
Mozilla.org has closed the tree to approved checkins only, starting as of 12am Wednesday, and will do so until 0.9.8 has branched. 0.9.8 will have a variety of new items including new natively drawn widgets on WindowsXP, Mac OS X, and GTK, when you are in the classic skin (We will have more on this later, including screenshots); the addressbook was rewritten, and now supports printing, a new "Get Map" button allowing you to query for a map based on a card address, and other stability fixes; Windows MAPI support; and a huge amount of performance and stability work.
Many believe this is one of the last milestones prior to 1.0, and that Mozilla.org will actually have 1.0 following 0.9.9. 0.9.8 should branch sometime next week, with a release two Mondays from now. We'll keep you updated on both the branching and the release.
#87 Re: Re: Your arguments
Saturday January 19th, 2002 8:30 PM
You are replying to this message
This is not the architectural "change" that you keep trying to make it out to be. This is an addition to existing functionality, not a change to existing functionality. There was a time when we didn't have -moz-border-radius and so we couldn't specify curved boorders in CSS. Then the Mozilla Module Owner (who is specifically tasked as the architectural lead for that module) Dave Hyatt, implemented this mozilla addition to CSS and it gave theme developers a great tool in CSS for making round buttons and whatnot. Modern theme uses this extensively. Border colors was a similar great addition that gives me the ability to specify multiple borders of different colors without having to use an additional XUL box or an image.
This probably doesn't have the negative impact on theme development that you speculate either. It's one more tool, like -moz-border-radius, that gives theme developers the ability to specify that some parts of their theme should pick up a native style, and in the case of OSes that have themes of their own, to pick up the changing OS theme. If anything, I suspect this additional feature will further encourage theme developers to experiment with making specific parts of the browser "better" than native while not having to spend time getting all the other parts as good as native.
I also dispute your assertion that users prefered a native theme. Classic is a darned good match for windows 95-NT users and the majority of people I've seen comment on the two default themes preferred Modern (not me, I've always been in the minority and use classic almost exclusively). I'll give you Mac users on this one but they are a minority of current Mozilla and Mozilla-based browsers users. There are definitely oportunities to do it better than the OS and I think that Microsoft's current shipping WMP theme demonstrates that even they think non-standard pieces of UI for 'flavor' are what the user wants. Another example of this is what the IE 6 sidebar media player looks like compared to the rest of IE and the rest of my win2K apps. MS is not the best example of quality UI but I think my point holds that it doesn't all have to look and feel the same.