Greetings,
I am attempting to estimate the level of effort it would take to
create a Swing "lightweight" implementation of the Java OpenOffice
interface. We have a project that would like to integrate OpenOffice
functionality, but it is based on an internally-developed graphics
engine. We can embed lightweight Swing but not heavyweight AWT.
Searches of the mailing list archives turned up a few inquiries
about this but no answers. I am looking for someone who knows something
about OOo's graphics internals to help point the way. I've spent some
time digging through UNO and the Java interface and have come up with
some candidate courses of action and would appreciate some pointers as
to where some of the appropriate code might live within the large OOo
codebase.
Some approaches I can imagine:
* Create a Java BufferedImage in RAM and use it as the drawing
surface upon which OOo renders its contents, and use it as the
back-buffer to a Swing JComponent.
* Use JOGL to create a texture on the graphics card and use that
as the "hardware" peer and render it out to a JComponent through a
GLJPanel.
* Draw the OOo work off-screen then copy it to a lightweight
buffer on-screen.
I have experience hacking at Swing and was a C++ expert in a
past life, but haven't even glanced at CORBA in over a decade so am
having trouble tracing the flow of execution through UNO. Is there
anyone out there who can point the way to the right code?
--Sam Kass
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
