Re: [pyxpcom] Building PYXPCOM XPI with embedded user Python
by Mark Hammond other posts by this author
Jan 23 2008 4:25PM messages near this date
view in the new Beta List Site
Re: [pyxpcom] roll-call for pyxpcom users
|
[pyxpcom] XULRunner + PyXPCOM
> 3) Installed XPI on client and added attached pyabout.py* to
> "Program Files\Mozilla Firefox\components" and tested using about:python
> in url bar - After deleting compreg.dat and xpti.dat** from profile
> dir ("Documents And Settings\User\Application Data")Â component was
> loaded and about:python worked (brought me to python.org)
...
> **note - getting components to register has always seemed like
> voodoo to me.. Hopefully someone here can help explain how this
> should actually work..
I *think* that in debug builds, all you need is to have a component file
dated later than compreg.dat - the equivilent of 'regxpcom' is run each time
the app is started. In release build, I believe regxpcom must be executed
manually - although in release builds, the most common way of getting
installed is via a .xpi, and I believe the JS code there can force
registration at install time.
Or something like that :) Hopefully one the ActiveState guys can correct me
if their memory doesn't match mine.
Cheers,
Mark
_______________________________________________
pyxpcom mailing list
pyxpcom@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
|