FreeLists / openbeos / [openbeos] Re: Javascript-capable Browser

["Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>]

> The downside however is that no matter how good port you make of it, 
> it 
> wont become a BeOS native app, and hence won't be using many of the 
> advanced features of the BeOS. That is, it wont be using the BeOS 
> mailing system, it wont be using translators for rendering images. It 
> wont be using add-ons the Be way. It wont be replicant-capable. It 
> wont 
> be using attributes in stored bookmarks. It won't store bookmarks in 
> a 
> folder. And so on.

Actually, even Net+ doesn't use the Translators for rendering images - 
that's mainly because of the lack of a progressive rendering API (and 
perhaps the age of Net+) - you have to wait until the Translator is 
ready to see the image.

Of course you are right, a Mozilla port couldn't be as integrated in 
BeOS as Net+ is, but it would be fine to have it.

Adios...
   Axel.