Slashdot Mirror
Seamonkey 1.1 Released
stuuf writes "Version 1.1 of the Seamonkey Internet Application Suite is now available, with quite a few improvements over the 1.0 series. Some of the new features include spell checking in form text areas, a new tagging system to classify email, a better indicator for secure web sites and preview images for browser tabs. This release also includes many of the updates that have gone into the Firefox 2 and Thunderbird 2 branches. Check out the release notes and download page for more."
Seamonkey/Mozilla is much more customizable. I particularly like the ability to make key bindings, as well as define scroll ranges. Firefox tries way too hard to be minimal. Look at the preference page, there's barely anything there. Tons of features I found useful before Firefox came about were just cut. I don't want minimal, I like having lots of features.
I am writing a theme called SeaGnome for Seamonkey so it blends in nicely with GTK desktops. I have the Mail and Browser section but am still working on the remaining suite applications.n t=c_linuxseagnome.php
n t=c_linuxmonkeymenu.php
Try it out here:
http://markbokil.org/index.php?section=tech&conte
I also have written an extension for Seamonkey which allows you to collapse down the toolbars and provides a quick menu to often used features. Great to reclaim screen realestate while browsing.
http://markbokil.org/index.php?section=tech&conte
I think the FUD that the OP was referring to was not that Firefox and SeaMonkey do have some leaks, but that some people try to make "the memory leak" seem like a huge, obvious problem that is going unfixed. I've seen several posts lately saying something to the effect that "the memory leak" is not being addressed. The reality is that the leaks are being fixed. I also don't see any evidence that Firefox or SeaMonkey leak any more than other browsers. So there is FUD, and also you are not just imagining memory leaks.
What a fool believes, he sees, no wise man has the power to reason away.
MacOS X DOES provide an inline spell checker, though I believe it only works for Cocoa apps, not Carbon, and I think they leave it up to developers whether to implement it or not...
This is not quite correct. The OS X spellchecking service, like all the other services, works automatically in Cocoa apps without any work on the part of the developer (as I understand) and functions inline. Developers can integrate it in additional ways as well and it can be included in Carbon applications, but the developers have to do it specifically. For example, Firefox3 alpha 1 includes the native OS X spellchecking with the same dictionary as all the other applicatons, despite not being a cocoa application.
There's also a spell checker on the Services menu, though its more for checking the spelling of individual words.
This is the same spell checker and uses the same dictionary. It is just a different interface for getting to that function.