Slashdot Mirror

Seeing that the Chimera project (Mozilla/Cocoa for OSX) had to change it's name to "Camino"; I would hazzard a guess that the Mozilla team is targeting gas-guzzling sports cars for new monikers, rather than fowl. Maybe they should name the next version of Mozilla Corvette?

Thunderbird has an option to junk everything from anyone who isn't in your address book. This might be something close to what you want. And if not, get the source and make it do it.

Thunderbird has an option to junk everything from anyone who isn't in your address book. This might be something close to what you want. And if not, get the source and make it do it.

This was a very interesting article. I natively speak Perl, C, and C++, know enough about PHP to get by, and still remember some Commodore 64 BASIC (10 ? CHR$(147)). I am also, as I believe I've said before, not afraid to learn things like Java, Python, Ruby, maybe even Visual Basic again (God forbid) should they prove exceedingly relevant to my case - in fact, I quite look forward to knowing (hopefully) all of them and then some. But never Pascal. (Just kidding.)

I've really found that the thing I hate most about programming in general is that no single language is the right one to use for any of my programs! I am very interested in any effort I ever come across to do functional merging of disparate environments. In addition to a couple of workarounds I've invented in the past for shoehorning Perl into PHP, I like reading about things like SWIG, the open CLR, and even COM (the concept more than the implementation), and a smile always comes to my face when I think about the Inline library written for Perl.

Now, the thing I really pine for is all of this interlanguage binding stuff being easy, fairly portable, more synactically simple, and less hacky. I know that these exist, but not quite completely together. If I write a program in Perl with use Inline C, I can never be sure that anyone else has all the development tools necessary to compile all the C on the fly. Writing a program in Visual Basic with a nice mouse-drawn GUI and an external component is really easy - but it's Visual Basic. Writing a component wrapper for Perl is fairly straightforward with SWIG, but some well-thought-out language features would make it easier. And COM... I'm going to have to try wrapping my head around that book again someday... I'm sure the ATL makes it all very simple, but can I use ATL from MinGW? From C? From Perl? And don't try to tell me that I need to learn yet another flavor of XML to make all of this work.

That's mis tus centavos.

(Note: I disclaim perfection. Don't hit me too hard; I admit I haven't done enough of my homework to claim this post isn't full of holes. Once I've looked this whole matter through, if ever, and if I still haven't come up with anything good, I may just have to take a deep breath, lay down a syntax, figure out how to use a lexer generator and a compiler compiler, and throw together some ghastly but very easy-to-use homogeneous aggregator system. Either that, or I wait for Parrot to interoperate with Mono...)

JavaScript is a really nice language. For starters, Waldemar Horwat sure knows his stuff. He seems to give a lot of thought to new features before introducing them (check out the project page) and has managed to write an interpreter that can be configured to accept varying language versions (as in language="JavaScriptXXX"). Then, the whole idea of a prototype-based object-oriented language becoming mainstream should have made the Self team green with envy. It supports very powerful constructs, like dynamically attaching behavior to built-in objects via __prototype.

Besides, JavaScript inconsistencies between browsers is mainly a DOM issue, not a language one. Chromatic should have blamed the browsers, not the language.

• 1.x.1 releases are not the norm, they hopefuly should not happen in 1.4. 1.2.1 and 1.3.1 were made to fix important bugs that were not found/fixed before the expected release dates. These extra releases drain resources from development on the main branch. Help out identifying the important bugs by using 1.4b and you will NOT have a 1.4.1 (and a better 1.4).
• 1.(x+1) release cycle starts BEFORE 1.x release is done. E.g. 1.4 will be frozen, then branched. When branching occurs, the main tree will be opened again for 1.5a checkins.

SVG support is still very much incomplete; the browser won't recognise SVG that is embedded into pages using the embed tag (which is pretty much all SVG on the net, since that's what the Adobe plugin supports best). It also doesn't have support for the entire spec, although for basic static graphics, it is pretty much there. The libart licensing issue to which you allude is a simple incompatibility between the MPL/LGPL/GPL trilicense that Mozilla is released under and the LGPL of the libart library. That pretty much prevents mozilla including SVG by default at the moment. In addition, a lot of the SVG had a rewrite quite recently and, because no one has had time to review thousands of lines of new code, it's still living on a branch. That's important if you decide to compile Mozilla with --enable-svg set - to get the new code you need to pull the branch from CVS, otherwise you'll get the older, somewhat buggier code. For more details, including quite detailed build instructions, see http://www.mozilla.org/projects/svg/ If you think that duplicating cpu effort by compiling everything yourself is a waste of time, then there are regular svg-enabled builds contributed to ftp://ftp.mozilla.org/pub/mozilla/nightly/latest These come in two flavors, GDI+ (windows only) and Libart (Linux and windows). All svg builds have mathml-svg in the filename. If you're not on one of those platforms or want something cool like Xft and SVG, you'll need to complie yourself, I'm afraid. For more information, see the netscape.public.mozilla.svg newsgroup.

SVG support is still very much incomplete; the browser won't recognise SVG that is embedded into pages using the embed tag (which is pretty much all SVG on the net, since that's what the Adobe plugin supports best). It also doesn't have support for the entire spec, although for basic static graphics, it is pretty much there. The libart licensing issue to which you allude is a simple incompatibility between the MPL/LGPL/GPL trilicense that Mozilla is released under and the LGPL of the libart library. That pretty much prevents mozilla including SVG by default at the moment. In addition, a lot of the SVG had a rewrite quite recently and, because no one has had time to review thousands of lines of new code, it's still living on a branch. That's important if you decide to compile Mozilla with --enable-svg set - to get the new code you need to pull the branch from CVS, otherwise you'll get the older, somewhat buggier code. For more details, including quite detailed build instructions, see http://www.mozilla.org/projects/svg/ If you think that duplicating cpu effort by compiling everything yourself is a waste of time, then there are regular svg-enabled builds contributed to ftp://ftp.mozilla.org/pub/mozilla/nightly/latest These come in two flavors, GDI+ (windows only) and Libart (Linux and windows). All svg builds have mathml-svg in the filename. If you're not on one of those platforms or want something cool like Xft and SVG, you'll need to complie yourself, I'm afraid. For more information, see the netscape.public.mozilla.svg newsgroup.

Careful if you work a lot with bookmarks, you might hit a bug where you can't delete or move bookmarks (in Linux) or the new bookmark folder setting doesn't work.

I'm looking forward to getting my bookmark functionality back in the next release...

Careful if you work a lot with bookmarks, you might hit a bug where you can't delete or move bookmarks (in Linux) or the new bookmark folder setting doesn't work.

I'm looking forward to getting my bookmark functionality back in the next release...

Right here.

No, firebird will package with minotaur to provide e-mail.
Look at the roadmap for more information.

Ryan

No, firebird will package with minotaur to provide e-mail.
Look at the roadmap for more information.

Ryan

1. 1. SeaMonkey: The SeaMonkey project is also called the Application Suite or "App Suite." It's largely the same as the old Netscape 4.x Communicator brand. It has more or less the same functionality and branding as that the old 4.x product and we've done little to counter that association.
   2. Firebird/Thunderbird: These are the basis for the second generation mozilla products. They split our application into two separate applications with separate identities: a web browser and an email program. In talking about these projects, we should allow them to have their own identities.

ftp://ftp.mozilla.org/pub/phoenix/nightly/latest-t runk

Also check out all of the extensions, most of which still work on the latest nightly build.

Mozilla 1.3.1 (bugfix update for 1.3) was released this week, too.

For People with an *nix Account:

• Spamassassin ruleset-based mail analizer. Detects spam quite well, especially if you enable access to Razor and Realtime-Blacklists. Newest release includes a bayesian filter.
• bogofilter My favourite bayesian spam filter. Pro: Very good detection rates after training properly. Con: Needs to be trained.

• Use Mozilla Mail The up-to-date Mozilla release includes a bayesian spam filter which can be easily trained by marking spam messages. Very good detection rate after resonable low training effort.
• Find your favourite bayesian filter here

It's been my experience that browser advocates come in one of two flavors. Those who worship Bill and constantly mutter under their breath "I hate netscape", and those (us) fringers that use an alternative browser (mozilla, phoenix, opera, icab, etc).

People that used to love Netscape have pretty much turned to IE due to the NS4 line's stagnation and the netscape branch of mozilla being inadequate (I'm highly looking forward to a branch of the 1.4 trunk). They don't complain or they'll get laughed at.

The last group of people I find are people who don't understand why some people's Internet is a big E and some people's is a wheel, and some are a lighthouse.

I work for a huge megacorp that you have heard of. We're worldwide. The official policy is Netscape 4.78 is the mandatory web browser. I only found that by digging for several hours on our Intranet. But our IT staff is to afraid to tell anybody which browser to run, and we've got the most ugly assortment of browsers you can imagine.

Think of any flaw available for IE and send it to my company and you're going to destroy most people here.

The problem I think is that to most people (especially those of us who remember the browser war vividly) browser choice has become one of those things like religion or politics. You've got one side that's rational, logical and informed about their choice, and the other who have the attitude "don't bother me with facts because I've made up my mind" (which in turn causes a heated response from the first group) and the whole thing gets ugly. Another major problem is that on all currently available versions of Windows there's no way to remove IE, even if you wanted to standardize on a non MS browser you can't, because the bugger will always be there.

The question isn't which browser to use it's how does one combat the demons of stupidity so that it actually does get used.

I wonder about this too.

I notice that Opera is listed as having 3 security vulnerabilities in the pivx.com link above. However, Opera's history is that the security vulnerabilities get fixed quickly.

I found a serious bug (204668) in a recent build of Mozilla (a stack overflow, not a security vulnerability), reported it using Mozilla Bugzilla, and they fixed it within a day.

I complained of another bug in Mozilla, and they had an answer in two hours. Those Mozilla people are seriously interested in getting the job done.

Maybe the world only has the intellectual resources to produce one or two good browsers.

I wonder about this too.

I notice that Opera is listed as having 3 security vulnerabilities in the pivx.com link above. However, Opera's history is that the security vulnerabilities get fixed quickly.

I found a serious bug (204668) in a recent build of Mozilla (a stack overflow, not a security vulnerability), reported it using Mozilla Bugzilla, and they fixed it within a day.

I complained of another bug in Mozilla, and they had an answer in two hours. Those Mozilla people are seriously interested in getting the job done.

Maybe the world only has the intellectual resources to produce one or two good browsers.

Get it before it's slashdotted!

Get it before it's /.'ed!

Documentation? You don't need it really do you? Do I need a manual for C#? SQL Server? Notepad? IE?

Get it before it's slashdotted!

Get it before it's slashdotted!

The move to "Mozilla Browser" and "Mozilla Mail" was always in the plan, and was in the branding document published last month. This change is scheduled to happen at some point after we release the currently-in-development 1.4 application suite.

But, before the change happens, there are likely to be one or more releases of the Mozilla Firebird Browser as a standalone application. That was also always in the plan.

Move along, no change, nothing to see here.

Gerv
(gerv at mozilla.org)

Please, everyone keep in mind that the naming situation wouldn't have been nearly as bad if Phoenix hadn't made such a big deal in the first place.

The big, bloated, everything-including-the-kitchen-sink Mozilla that you download from mozilla.org is called Seamonkey.
However, nobody ever refers to it as Seamonkey - it's just Mozilla. Phoenix/Firebird was just being referred to directly as Phoenix/Firebird until Seamonkey could be retired and the rest of the developers could move over to the new codebase. At that point it would've been "Mozilla Browser" and "Mozilla Mail & News" again (as far as we end-users are concerned).

If Phoenix hadn't flipped out and had just waited a few months the "Phoenix Browser" would probably have been forgotten.

It's not like Mozilla ever got sued by Exploratoy.

Please, everyone keep in mind that the naming situation wouldn't have been nearly as bad if Phoenix hadn't made such a big deal in the first place.

The big, bloated, everything-including-the-kitchen-sink Mozilla that you download from mozilla.org is called Seamonkey.
However, nobody ever refers to it as Seamonkey - it's just Mozilla. Phoenix/Firebird was just being referred to directly as Phoenix/Firebird until Seamonkey could be retired and the rest of the developers could move over to the new codebase. At that point it would've been "Mozilla Browser" and "Mozilla Mail & News" again (as far as we end-users are concerned).

If Phoenix hadn't flipped out and had just waited a few months the "Phoenix Browser" would probably have been forgotten.

It's not like Mozilla ever got sued by Exploratoy.

Use Phoenix/Firebird

The Browser Formerly Known as Phoenix people seem to be asserting that.

Perhaps it's just a glib reversal to save face?

You'll be interested in this bugzilla entry. They fixed it about a year ago, but since then holes have been punched through ...

mozilla lets you just turn them off.

when was the last time pr0n resulted in a turn off? Oh yeah -- that goat website.

God Bless Mozilla .. no more pop-ups. Hopefully it will still block those audio pop-ups "that can't be turned off."

Use Phoenix (FireBird):

Firebird home

New release coming soon =)

The GNU implementation of the ISO/C++ language has only recently (since gcc-3.0) been close enough to the standard to be really useful.

Before then C++ was difficult to work with. See the Mozilla recommended style guide that lists the features not to use to be portable. It starts with "do not use templates".

Working standard templates is the number one reason to use C++ these days, if you ask me. They are even more useful than all that OO stuff, and fantastic in combination with OO.

Combined with all that is the notion that C++ is a hard language to learn and that people (amateurs) will be productive much faster with C, although this point really is debatable. Learning C++ through the standard library (containers, algorithms, etc) is now the recommended way, and using this part of the language is relatively simple and safe.

Hopefully this GNU recommendation will be dropped one day.

http://msgs.securepoint.com/cgi-bin/get/bugtraq030 3/122.html
http://msgs.securepoint.com/cgi-bin/get/bugtraq030 4/98.html
http://msgs.securepoint.com/cgi-bin/get/bugtraq030 3/347.html

Not as pathetic as IE, although they are still unpatched and Mozilla Firebird(TM) does not feature them ;).

I've got a better fix.

It's a usual bug. All browsers have them.

No, not all browsers have this bug and so far I can't replicate similar sounding bugs in Mozilla producing a crash and loss of work. Also, not all browsers are so widely used and not all browsers integrate code with widely used e-mail clients (Outlook and Outlook express still use the same HTML renderer that is subject to so many problems). This leads to multiple paths to sabotage someone remotely, perhaps even anonymously. Let's not forget that any application that embeds MSIE/Windows' renderer is vulnerable. Considering how many people use MSIE on MS Windows and how many of them are affected by this bug, I'd hardly call revealing the bug a "joke".

This bug does *not* exist because MS is Evil.

I'm not encouraging anyone to think in the false dichotomy of good vs. evil and neither should you. Nobody is helped by glossing over relevant details of how this works or ignoring the wide scope of the bug. This is one of a long string of Microsoft bugs that directly adversely affects ordinary users. We are much better served by suggesting real-world fixes (such as switching to Mozilla to do most browsing, even under a proprietary operating system). We're also better off identifying this exemplar of the practical shortcomings of proprietary software. There's no workaround here--MSIE/Windows users must simply wait for a fix from the proprietor if they won't switch browsers (and any other app adversely affected by embedding the MSIE renderer).

And it's impossible to expect any software company to create a bug-free program. While I want this, I know that everything will have bugs. Even some other browsers have some ugs that crash it.

Note that I'm posting this using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030320 Phoenix/0.5, so it's not like I'm an IE evangelist, I just prefer to look at this things objectively.

And it's impossible to expect any software company to create a bug-free program. While I want this, I know that everything will have bugs. Even some other browsers have some ugs that crash it.

Note that I'm posting this using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030320 Phoenix/0.5, so it's not like I'm an IE evangelist, I just prefer to look at this things objectively.

And it's impossible to expect any software company to create a bug-free program. While I want this, I know that everything will have bugs. Even some other browsers have some ugs that crash it.

Note that I'm posting this using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030320 Phoenix/0.5, so it's not like I'm an IE evangelist, I just prefer to look at this things objectively.

And it's impossible to expect any software company to create a bug-free program. While I want this, I know that everything will have bugs. Even some other browsers have some ugs that crash it.

Note that I'm posting this using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030320 Phoenix/0.5, so it's not like I'm an IE evangelist, I just prefer to look at this things objectively.

And now... Shall we continue to post all the bugs that crash Mozilla, Netscape or Galeon?

Sure. It'd be appreciated, too.

Unfortunately, 0.5 is very old and there are only nightly releases since then. Try the nightly build from March 20th. It haven't managed to crash it once in those weeks.

A crash bug? Mozilla has none of those, right? Right? (seriously, if anything Microsoft should be proud that one pointless crash bug is such a big deal)

Here. Phoenix^H^H^H^H^H^H^HFirebird allows you to block certain Javascript functions (like popups, window resizing, status bar text, etc) without disabling Javascript entirely. On the other hand, if you do want to disable Javascript entirely, take a look at w3m.

I use a browser called Phoenix, which enables you to diable "pop-up ads"
It's a nice little feature....I believe Mozilla does this as well...
I have not seen a pop-up since I've been using Phoenix.....which you can download here peace/out!

1. Install Mozilla
2. Go to Edit, Prefrences, Advanced, Scripts and Plugins
3. Unselect "Change status bar text"
4. Click "OK"
5. Viola. The status bar is yours!

If you use Phoenix, which in my opinion kicks I.E./Netscape/whatever elses ass, you don't even think of this. One of the main points of Phoenix is that it gets rid of these stupid web "tricks".. Read this http://www.mozilla.org/projects/phoenix/why/ and weep IE users..

Pick your poison:

Phoenix/Firebird - blocked
Opera - blocked
Mozilla - blocked
Netscape - blocked
IE - oh thats a feature.