Planning For Mozilla 2.0
wikinerd writes "The MozillaWiki maintains a number of pages on Mozilla 2.0 which reveals lots of possible new features of the popular browser. What does your wishlist include about Mozilla 2.0, and how has the release of Firefox affected your use of Mozilla?"
It has ended it.
How about a new Theme? I personaly dispise the current theme and the way the various toolbars interact within mozilla.
Also how about a way to manage Mozilla using Windows group policies?
What about a MSI package?
Mine are pretty simple.
A graphical history record (i.e. one that keeps a stored image of places where I've been, rather than a mere text description, as most give very limited info of what that particular site was).
And, an RSS reader equivalent to FeedDemon.
So I always used Moz. Personally I think the best change for Moz would be to make it less bloated, and make it totally modular. Basically make it so you can strip away most of the program and turn it into something closely resembling Firefox if you so choose.
I would like to see something like what opera has with web page magnification. Its on firefox too but you cant make images any bigger then they already are like you can with opera. But i still like FF better.
When I read about the evils of drinking, I gave up... reading.-Henny Youngman
I would like to see a build in page validator.
There is a lot of badly coded web pages out there.
It might take a rewrite of gecko by I think it is wroth it.
The normal web based validators really don't cut it
when your developing dynamic cgi scripts.
A kick-ass feature I'd like to see in Mozilla and Firefox would be to automatically break up long words/numers/urls at the edge of the screen.
Since I have a TFT with 1280x1024 resolution, I often increase font sizes when browsing the web to reduce eye strain, but that often causes horizontal scroll bars to appear when long words or urls are in the text, making it much less convenient to read, e.g. in those ubiquitous phpBB based forums.
I still remember the day when I tried running two separate instances of Mozilla on the same Windows machine. Neither Google nor the forums helped. Luckily I can still read C++.
Open source should mean you can look into the source if you want to, not that you have to look into the source every time you try something non trivial.
Though its not directly related to the Mozilla Suite (sorry, I tried to RTFA, but its down) my biggest wish is to see the Gecko Rendering Engine (GRE) finally split from the Mozilla/Firefox/et al code base. This seems to have completely dropped off the road map despite being discussed for months (years?).
The idea of running the GRE as a service (started at boot) and then simply launching the frontends for the various Mozilla apps (in my case, Firefox and possibly Thunderbird) appeals to me immensely.
I value "snapiness" greatly when it comes to my web browser and email apps. Having to run multiple instances of the same rendering engine is a bit of a downer IMHO. (Yes, I realise there are some benefits. Yes, I realise we all tend to have ample computing power.)
Of course, some of the above may alreay be planned but as I can't get on mozilla's web site, I can't check.... Maybe it was slashdotted?
One of Mozilla's greatest strengths is not as just a web-browser but as a cross-platform application development platform.
Just try playing around with XUL a little. It's surprising what it can do. I'm just starting out with it, but having worked my way through MFC, QT, TCL/TK, WTL, GTK++, FLTK, wxWidgets etc. etc. in search of the One True UI Library, I'm liking what I've seen so far.
Talk about ancient history! When mozilla.org first decided to focus on Firefox, they were going to "replace" the suite with FIrefox/Thunderbird. They quickly junked that plan when they realized that many large organizations, including ones that support Mozilla with money or developers, preferred the suite. Dropping support for the suite would mean losing those companies' support for Mozilla.
What a fool believes, he sees, no wise man has the power to reason away.
- SVG
- A better client-side VM.
- Heavy duty form support, including the ability to create and use form "widgets"
- Client-side persistent store
Want to compete with MS's upcoming XAML platform? I believe this list will go a long way toward that.This will allow interactive graphic applications that are just not possible now with primarily text-oriented DHTML.
Like real compiled Javascript 2.0 or perhaps a Python VM. You can do some amazing and surprising things with client-side JS, but as web apps tackle what are now primarily the domain of "fat" installed apps, we're going to need some real client side power. The ability to create and call libraries of routines will prove to be important.
These issues are being addressed in both Ian Hickson's WHAT-WG and W3C's Xforms. Implementations of these in compiled code would be great.
From what I gather, Moz 2.0 will embed the small SQL engine SQLite to store it's configuration data, etc.. How about providing access to this engine for web apps? Think of it as maybe a cookie on some relational algebra radioactive steriods. Imagine being able to download chunks of data from your server-side store and work with them locally. You would effectively have web apps that continue to work when disconnected from the web.
For some reason the Firefox engine will not print from my Samsung ML1750 printer without skewing the text up. Everything else prints on it fine. This is a show stopper for me and I am using Opera (which works fine with the printer).
I want/prefer/like my email integrated into the browser. Firefox/Thunderbird works OK but not as well as Mozilla. But overall I prefer the Firefox browser for tabbing, speed and ease of user. It just feels good. It's nice to have choices again. I am a happy camper even with the problems.
I would like to see an extension to tabbed browsing where you could grab a tab and make a new window out of it and pull it out of the current window. And I guess the inverse transform would be handy - allow merging of windows into tabs.
Most of my boxen have virtual desktops, so it's handy sometimes to have different windows on each desktop each with several tabs on the same subject. For example, I'll have one desktop with slashdot and a few links alongside IRC and another desktop reading API documentation for a project.
Another reason this is useful is so that when you open links from the mail program in a new tab, it does not always put the tab in the window you want.
- You don't know how to maintain a station wagon either!