TommyBee wrote:

> 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.



Then think of it like this.  It isn't the forms that depend on the 
composer code, it is the composer which is a byproduct of having decent 
html forms.  The browser requires code for making text fields. That code 
was designed as a general purpose editing module which could alos be 
used in an html composer or a mailnews compose window.

--Asa


Reply via email to