FreeLists / openbeos / [openbeos] Re: OpenBeOS Applications

["Stuart Rocks" <stuart@xxxxxxxxxxxxxxxxxxxxxxxxx>]

> Other than being fast, this was always always crap (IMO - I know there
> are people who loved it). I would suggest settling on BeZilla as our
> default browser (like we have much  choice anyway). Perhaps we can make
> a OpenBeOS distribution of it,  packaging it up nicely and give it a
> BeOS theme? I really don't think that now is the time to be making
> another web-rendering engine.
>
> If people object to the whole BeZilla, why don't we use the Mozilla
> rendering engine and create a simple browser like Gaelon does?

I think we should take the Gaelon / K-Meleon route. Skins are generally a
bad idea, the imply functionality which may not there be there, and are
confusing.
More skin criticism here:
http://www.suck.com/daily/2000/04/10/daily.html


> PoorMan
> =====
>
> This was actually OK... but is it really worth writing a web server
> when Apache 1.3x and Apache 2.x have been ported.
>
> I would suggest getting the Apache 2.x port up to date, and creating a
> GUI to httpd.conf instead of PoorMan. (Heh - ApacheMan) - much like
> MacOS X does, we could even bundle PHP with it.

I think RobinHood is a more adequete replacement. Apache always seemed a
little heavy for me.

> BeMail
> ====
>
> I don't know what to do about this either, I *really* like BeMail, but
> if we are going to bundle BeZilla, do we need to rewrite BeMail?  I
> have a feeling that the answer will be yes here :)

BeMail does indeed rule.

tlhf
xxx