Subj : Re: A plea to the Open Sourcerors To : netscape.public.mozilla.jseng From : ajmayo@my-deja.com (Andrew Mayo) Date : Fri Jan 23 2004 05:22 am Martin Honnen wrote in message news:... > Andrew Mayo wrote: > > > > In my case, all I want to do is have a JSSHELL with support for the > > intrinsic objects, particularly the File, Environment and System > > objects that supposedly exist, so I can deploy platform-independent > > scripts for various purposes that have a pretty lightweight framework > > (i.e runtime support) around them. > > Download a Mozilla build as a .zip (or the compression format for your > platform), it comes with some executable called > xpcshell.exe > the XPCOM shell, then check > http://www.xulplanet.com/references/xpcomref/creatingcomps.html > on how to create XPCOM components with JavaScript and check the > reference docs at > http://www.xulplanet.com/references/xpcomref/ > [snip] Thanks, that's good advice. But doesn't this require me to have the entire Mozilla infrastructure on each target machine?. The advantage of Seamonkey standalone was the very small runtime. I want to be able to distribute scripts and the associated runtime over very low bandwidth dialup links to a bunch of machines, some of which are quite old and run Win95. Originally we tried installing Internet Explorer 6 on these machines but this caused *big* problems so we are now looking at a lightweight Javascript engine we can use instead. Can I use this approach and slim down Mozilla considerably? (I could live with, say, a 3 meg runtime environment but the full Mozilla is a bit much, I think. If I could do this, how would I go about determining which components I'd need out of Mozilla as a runtime support environment for the Javascript engine? .