On 2/22/07, timeless <[EMAIL PROTECTED]> wrote:
You can deploy extensions and components to a profile directory, it's something like:~/.mozilla/{app}/components/{here} I'm sure you can find documentation on this.
Actually, I had considered deploying the extension to to a local app-specific user profile, but had difficulties making it work, and in finding documentation. I'll investigate this option further.
> Deployment is also complicated by the fact that they may have > different GtkMozEmbeds on their system, and consistently sniffing them > out and handling change in the environment can be hard. it shouldn't be. write proper code using frozen interfaces and always QI to verify that the objects you have behave as necessary. if you know that a given object needs to be present and won't be present in certain versions, you can make your factory search for it and refuse to create its objects when it doesn't find the necessary object.
Unfortunately my code is somewhat more simplistic than that -- I'm using Gecko# (i.e. GTKMozEmbed) with some C++/XPCOM glue code to access the DOM. The app my code is embedded in (MonoDevelop) sniffs out a Mozilla in the launch script in order to set LD_LIBRARY_DIR, and I have to hope that it's still the same one into which the installer installed the extension. Thanks for your advice. I've been looking at this for a while hoping that there's an easy and elegant answer, but not come up with anything workable yet. -- Michael Hutchinson http://mjhutchinson.com _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
