FreeLists / openbeos / [openbeos] OpenBeOS Applications

["Andrew Edward McCall" <mccall@xxxxxxxxxxxxxxxxxxxxx>]

Hi all,

I have been talking to Geoffrey Longo regarding the re-implementation 
of the OpenBeOS Applications, the ones you see after a new install when 
you go BeOS Menu->Applications.

Most of them are going to be fine to be re-implemented, but some I have 
doubts on why we should actually do it. Below are the applications I am 
questioning.

I also know that a fair few of the applications have their source code 
available with BeOS anyway, what happens about these? Can we use the 
code, or do we have to re-write them still?

N+
==

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?

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.


Terminal
=====

Why don't we just port the latest version of Bash, and use that 
instead?


BeIDE
====

I don't know what to do about this - discussions welcome!

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 :)

Thanks

Andrew Edward McCall
mccall@xxxxxxxxxxxxxxxxxxxxx
--
OpenBeOS! - Join the revolution now!
http://www.openbeos.org/