Re: oaf plugin patch



>
>> A concrete example of trouble : what if you wanted a Java plugin?
>
>"plugin" meaning shared library that gets loaded into the address space
>and has to adhere to a specific C API and use the same ORB.

I don't see why a bonobo component has to use the same ORB as its container.  That's 
the kind of 'plugin' I am thinking about.   On reflection I can see how the API you 
are discussing might not occur in such a case, I'll ask Mark for clarification.

>So, this is pretty irrelevant to Java plugins (however those would work,
>they would most likely use a different mechanism).

I would hope that they would use the bonobo container/component mechanism.  There are 
some issues to do with allowing the JVM to draw its visuals into the 'correct' X 
window but I think that the basic control interfaces could be implemented using bonobo 
as for other embedded components.  Or does bonobo component embedding not work for 
out-of-process components?  (Apologies for my confusion if this is a FAQ).

-Bill

>-- Elliot


------
Bill Haneman x19279
Gnome Accessibility / Batik SVG Toolkit
Sun Microsystems Ireland 





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]