Paul Everitt wrote:
>  I tried one of the samples from the pyxpcom CVS and got an error 
>  trying to grab the sample component.  I blew away the profile for the 
>  xulrunner sample application (to make sure the registries weren't 
>  interfering), to no avail.  I tried going back to the drawing board, 
>  which means running xpidl...and wow, it's quite a chore trying to get 
>  xpidl on OS X.

The cvs problems is likely due to mozdev host, I've noticed they are 
sometimes a little flakey. This was working for me this morning:
$ cvs -d :pserver:guest@mozdev.org:/cvs login
# the password is guest
$ cvs -z3 -d :pserver:guest@mozdev.org:/cvs co pyxpcomext/src/samples


I have not tried to get xpidl built on the mac, so I don't know the joys 
there. An alternative is to download Komodo, it includes xpidl already 
built and also provides some nice tools to build an extension, i.e. for 
the pyxpcom_samples I do the following:
$ cd pyxpcomext/src/samples/pyxpcom_examples
$ <komodo_install> /lib/sdk/bin/koext build
and the idl files get compiled, the xpi is generated and built for me.

> 
>  I then tried doing something using pydom, meaning, <script 
>  type="application/x-python">.  That didn't work...is PyDOM not part of 
>  the equation?

No, the PyDOM is not a part of the pyxpcomext moz1.9 packages. It is on 
my TODO list, but I had been running into a few issues with getting it 
to build and run correctly (due to changes in the Mozilla 1.9 tree). 
Most of these problems are now resolved so I will be starting to look 
into this again.

Cheers,
Todd

_______________________________________________
pyxpcom mailing list
pyxpcom@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs