mozilla.org Branches for 1.0
Tuesday April 9th, 2002
mozilla.org today cut the MOZILLA_1_0_0_BRANCH for 1.0 to use. Expect to see an RC1 candidate sometime next week in order to see where the builds are as far as stability and usability. Work will continue on the branch up until the final 1.0 release, and beyond for point releases. An updated roadmap will be posted soon reflecting this. The trunk is now open to 1.1 alpha work, on the road to 2.0!
#61 Re: Two schools of thought here
by SubtleRebel <email@example.com>
Thursday April 11th, 2002 10:36 PM
You are replying to this message
I do not believe that the issue is divided exactly between Mozilla and Netscape. For example, many Mozilla.org people agreed that the context menus were too long and needed revised; also there were various Netscape people who were not completely happy with what did and did not end up as part of the context menus. Both organizations believe that the primary purpose of the right click popup menus is for access to context sensitive functions.
The debate seems to mostly be about which functions should not have been removed from the popup menus, which ones need revised, and which new items should possibly be added.
My personal view seems to be very much in the minority. I believe that almost all of the previous functions should have remained available in the popup menu and that there should be a preference panel to allow people to choose which ones are needed and which ones are not. I agree that too many items in the popup menu makes it unwieldy, but different people have different needs. It is not Mozilla's goal to be the most widely used browser; Mozilla's goal is to be the browser that the most widely used browsers are built from. In order to achieve this goal, Mozilla needs to have lots and lots of features available; developers like Netscape, Beonex, Galeon, K-Meleon, etc can then pick and choose which features and options that they want to include or not include in their browsers. Why should Mozilla reduce access to any features? Items were added to the context menu because someone thought it would be handy to have the item there; for me that is enough reason for it to stay there in Mozilla. If Netscape wants to reduce the number of items in their context menu, then they can do so as they see fit. If Mozilla's context menu is too big then context menu items should be configurable via preferences.
I realize that a lot of UI people are opposed to an abundance of prefs, especially when those prefs can greatly change the placement of menu items and such, but I much prefer to customize my UI to my specific needs rather than try to conform to using the standard options made available.