Mozilla 1.2 Beta Released
nberardi writes "Mozilla 1.2 Beta is out. Typeahead now works on Mac and Java now works on Jaguar. On Linux, the classic theme now picks up GTK native theme. See the release notes for more info."
← Back to Stories (view on slashdot.org)
If only there was a theme that used the OS native widgets, without the ugly 'classic' icons...
-- Sometimes you have to turn the lights off in order to see.
seems to mean that if you're reading page 1 of a multi-page article, page 2 will be loaded in the background. nice!
Type ahead find is great. Been using it since Moz 1.2 alpha. The neat thing is that you can type a search phrase, and you can search again with ctrl-G. My only suggestion would be to have type ahead and find searches appear in a history combobox in the find window.
Get the latest nightly build here!
Strange women lying in ponds distributing swords is no basis for a system of government.
With the two rapid releases of Phoenix and Mozilla, with Netscape (the browser) being pushed by AOL, and with Chimera popular on the Mac, IE may have more users, but aside from being more stable and configurable, Moz is now steadily heading for a 1-1 user:browser ratio. Hopefully, this will result in an extremely customized browsing experience.
May we never see th
It's something mozilla is missing, blocking based off of filters. It'd be nice if I can say, fine, take everything on this server except .swf files.
-
ping -f 255.255.255.255 # if only
I really have to say that I find the recent development of Mozilla very inspiring as it brings completely new, unique features to the users. First came integrated popup and advertisement blocking. A simple but effective feature. Then came Type Ahead. Then came link prefetching. Now, in what time span?
:-)
I don't know about you, but at least my opinion is that the browser software has suffered from some serious stagnation during the past years. Since Internet Explorer 4.0 and its CSS and "DHTML" (mostly Javascript+CSS) support, I haven't seen much development in the browsers at all. Opera was innovative with mouse gestures, but I think the browser that truly turns this stagnation of browser features that's often limited to things like "slightly better CSS support", etc is Mozilla. I'm not even sure how it's possible for the team to bring so many new features in such a short time. Is it a side effect from being open source with browser enthusiasts working on it day and night? Is it "just" because a very flexible and well written code base? An efficient organization of the mozilla developers? A combination?
IMHO, the changes in Mozilla from a late version such as 1.0 are surely larger (at least more useful) than the changes since Internet Explorer 4.0. Each new version is right now bringing lots of new features. Perhaps that will change in the future, but I'll enjoy it while it lasts for sure.
Beware: In C++, your friends can see your privates!
Maybe delaying a release and all new features for a short time to fix existing bugs would be worth it. My $.02.
If you don't believe GUI innovation happens, imagine if X had an enforced toolkit. It would be Athena, in black and white, with this 1-bit color so written into it that it would be impossible to remove, and everybody would marvel at the fact that you could set it to inverse video and all applications would agree. And defenders would claim that the fact that only the middle mouse button makes the scrollbars move was a *feature*. And any intelligent people would be laughing X off the planet!
Meanwhile, despite it's problems and pretty stupid design even for when it was invented, X is able to replicate interfaces designed 15 or more years after it was invented. This is because of the one intelligent decision they made, which was to keep the GUI widgets out of it!
Now X has problems. There really should be high-level graphics, at least similar to PostScript. Though also complex, it is far less complex than toolkit interfaces, and perhaps more importantly the set of graphics calls needed has been pretty stable for about 20 years. It may even make sense to add calls to "draw a nice raised box" or "clear this to the flat background color" which would do about 99% of what people want "themes" to do.
Also there is a bit of "toolkit" inside X: the "window manager" (even though a seperate process, but the communication protocols are there, and I know for a fact that it takes more code to communicate with the window manager than it would take to draw the window borders and handle moving and raising the windows myself). This also needs to be removed.
But I am serious that putting any kind of "toolkit" interface into the system in a very very bad idea.
I installed XUL Planet's Preferences Toolbar on Mozilla, but the next time I installed a new version, it was gone and I had to reinstall it. I know that you can install plugins into your ~/.mozilla directory so that upgrading the browser doesn't require reinstalling the plugins, but is it possible to do this for chrome-like things (like the aforementioned Preferences Toolbar)? I've highly customized the toolbar, as well, and I don't even know where that configuration gets saved. Thanks.
"Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
they still stubbornly refuse to use CSS stylesheets that aren't served with a mime type of text/css ... I still can't see the information on a vast number of web sites out there
You visit sites that include the "information" in stylesheets? That's completely lame. The whole purpose of CSS is to separate the information from the style. If they're including the content in their style sheets then they're doing a lot more wrong than just serving the incorrect mime type.
--Asa