XulRunner 1.8.1.3

[Andrew Gough]

In my ongoing battle tilting at Mozilla windmills...

Is it supposed to be theoretically possible to embed XulRunner 1.8.1.3
at all?

I am trying (once again) to make this work, so I downloaded the SDK &
runtime for xulrunner-1.8.1.3, and attempted to compile against it.

I cannot see how it can work. According to 'nsIWebBrowser.h':

* The chrome object associated with the browser instance. The embedder
* must create one chrome object for <I>each</I> browser object
* that is instantiated. The embedder must associate the two by setting
* this property to point to the chrome object before creating the
browser
* window via the browser's <CODE>nsIBaseWindow</CODE> interface.

...and yet there is _no_ corresponding nsIBaseWindow.h/nsIBaseWindow.idl
or any other defined reference to nsIBaseWindow anywhere.

Makes it pretty hard to link a call to it. The previous release I was
using (1.8.0.4) suffers exactly the same problem. Is this hard or am I
stupid? (dont answer that). All the examples I've seen use this
mechanism, I just don't understand how they do it in practice.

Would I be better off going way back to Gecko 1.7?

Goughy

[Benjamin Smedberg]

Andrew Gough wrote:

> Is it supposed to be theoretically possible to embed XulRunner 1.8.1.3
> at all?
>
> I am trying (once again) to make this work, so I downloaded the SDK &
> runtime for xulrunner-1.8.1.3, and attempted to compile against it.

The SDK only contains *frozen* interfaces and headers. It is currently not
possible to usefully embed gecko using only frozen interfaces: you will have
to use internal interfaces such as nsIBaseWindow as well.

So if the question is "Is it possible to embed XULRunner 1.8.1.3 by
compiling against the SDK?" the answer is no. If the question is "Is it
possible to embed XULRunner 1.8.1.3?" the answer is yes. But you'll need to
obtain the nonfrozen headers/interfaces from the source tarball.

--BDS

[martin3...@gmail.com]

Is there any information about when this will be (or is planned to be)
released? I'm in the same situation, I just realized I needed to
define MOZILLA_INTERNAL_API . If possible, I'd like to use the frozen
interface in the future.

-m3