[Maf] Alternative way of running the maf compressor programs with nsIProcess

[Christopher Ottley]

Allister Beharry wrote:

>1. InfoZip's command-line tools return exit status codes that can be trapped by nsIProcess.run() and are available in the nsIProcess.exitValue property. 
>  
>
I committed to CVS this morning error checking code that uses the status 
codes of the process. The exitValue is included in an array of data that 
is sent to the observers. If it's non-zero you should see an archive 
failed message with the code. I thought about this and figure added FAQ 
entries for error codes would save me a bunch of hassle. :). Now just to 
update the website...

>If people on Windows are using invis.vbs then here's an alternative that will cause the wscript.exe script host to return the status code of the zip.exe process:
>  
>
I added your new invis.vbs to CVS. Thanks. :).

>The XPCOM zlib wrapper is on my New Year's Resolutions List...
>
Mine too. Just so much stuff to do. I have the infozip zip source here 
somewhere and the XPCOM C++ framework with the idls and everything. 
Getting it to compile using the Gecko SDK and more importantly cross 
compiling so I can make a DLL for Windows users are what's stumping me 
right now. If you want to collaborate on this I can request a separate 
mozdev hosting account for a XPCOM Zlib wrapper (xpzip say) and upload 
what I've done so far to CVS. I won't be able to work on this for a 
while (after February next year probably) but it might save you some time.

Regards,
Christopher.