TommyBee wrote:
> Yeah, it wouldn't make much sense to have a Mozilla-based composer
> without actually being able to see what the pages would look like in
> Mozilla.
No, you're STILL missing the point. The reason the browser is integral to
Composer is because composer is little more than a different way of feeding HTML
to the browser. Rather than using the Necko library to feed HTML to the
renderer, composer feeds it to the renderer. Composer is nothing more than the
browser, with YOU as the origination point of the code (via a pretty GUI).
Without the browser, Composed wouldn't work, it'd be nothing but some Javascript
code with nothing to work with. Like Asa said, Composer is some XUL, some
Javascript code, and some graphics. You can delete it with no repercussions on
the browser, saving a few hundred kilobytes, most of which will be graphic
files.
--
jesus X [ Booze-fueled paragon of pointless cruelty and wanton sadism. ]
email [ jesusx @ who.net ]
web [ http://burntelectrons.com ] [ Updated April 29, 2001 ]
tag [ The Universe: It's everywhere you want to be. ]
warning [ All your base are belong to us. ]
