"Sean Echevarria" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> On Wed, 13 Jun 2001 18:50:15 -0700, "Peter Sorotokin"
> <[EMAIL PROTECTED]> wrote:
> >
> >Note that only handful of Mozilla interfaces are frozen right now.
>
> correct.
>
>
> >Does anyone has (or anticipates) this problem?
>
> YES. Beatnik Player runs fine in N6.0 and N6.01 but crashes hard in
> N6.1 due to a situation arising out of the use of an unfrozen
> interface.
>
>
> >Would it be feasible for Mozila to change IID of *any* interface every
> >time its vtable layout is changed (this would not seem to require
anything
> >but IID string change in the same IDL file)?
>
> Unlikely to happen before an interface is declared frozen. But all is
> not lost - the best thing is for interfaces to be modified in a
> backwards-compatible way when at all possible, when the interface
> isn't frozen. That does require a certain amount of vigilance on the
> part of third party developers.
>
> Most interfaces that you'd need to use as a plugin developer are
> pretty solid (few changes in the last several months) and changes to
> them have been in backwards-compatible ways (nsIModule,
> nsIComponentManager, nsIMemory, nsIXPConnect, etc).
Well, SVG plug-in is almost like a separate browser in the browser.
It has its own DOM, CSS, layout, etc. and it all should work in the
browser environment. It needs much higher level of integration; I might
need things like Mozilla DOM interfaces or nsISecurityManager
(that most plug-ins won't need). It all works in Windows IE, by the
way.
Peter
>
>
