In article <[EMAIL PROTECTED]>,
Asa Dotzler <[EMAIL PROTECTED]> wrote:
> TommyBee wrote:
>
> > In article <[EMAIL PROTECTED]>, Alex <[EMAIL PROTECTED]>
> > wrote:
> >
> >>TommyBee wrote:
> >>
> >>>- Why isn't Composer a separate module? I have a feeling that very few
> >>>people are going to use Mozilla / Netscape for page editing, and even if
> >>>separating Composer doesn't offer much in RAM or hard disk usage
> >>>savings, doing so would at least make Mozilla that much less cluttered
> >>>for those who choose not to install Composer.
> >>>
> >>Composer gives both the browser component and the Mail/News
> >>component the ability to use forms, so it's needed for that.
> >
> > I don't recall Netscape 3.x Standard having a problem with forms, and it
> > certainly didn't have a full-fledged web page composer built-in.
>
> This is not Netscape 3.x
Wasn't saying that. Just saying that at the time it was (or at least
seemed) possible to have forms work without a web page composer.
> At any rate, it should be possible to strip at
> > least the Composer interface out and leave the underlying code to
> > remain.
>
> It is possible. There isn't much in this universe which isn't. And
> guess what? It's even easy to do. In about 5 minutes anyone familiar
> with web development could remove the menu items associated with composer.
>
> Like I said above, it has more to do with interface
> > simplification than with performance gains.
>
> So get a build and hack it. The UI isn't compiled, you edit a few text
> files and the interface is whatever you want it to be.
Maybe sometime over the summer. Right now my knowledge of programming
is rather surface (I made a crappy little Battleship program with MFC
classes in my first sophomore CS class last fall, but other than that
it's been text I/O), but hopefully what you say is true.
--
TommyBee
http://www.tommybee.com/
