Hi guys,
I'm looking at: http://udk.openoffice.org/common/man/spec/remotebridge.html
... and sample code in: /bridges/test
... and the interfaces: XPlayer XPlayerWindow
... and on the helix side: https://player.helixcommunity.org/nonav/2004/developer/doc/hxclientkit/HXClient.htm
... and am generally thinking that it should be straight forward to come up with a c++ component for openoffice that runs out of process as step 1 to integrating helix properly.
Are these all the right pieces? Is doing this out-of-process a good idea?
Also, I have a question on sdk's.
With the out of process plan, there are two parts to helix integration: An OOo side, and a helix side, separated by a inter-process bridge.
There are two ways the helix-side component could get done:
1. In Helix cvs with an external OOo sdk, eg: http://openoffice.mirrors.tds.net/pub/openoffice/developer/680_m91_sdk/OOo_1.9.91_LinuxIntel_sdk.tar.gz
2. In the OpenOffice project.
I'm not sure how sdk's generally work in OOo. Eg, I see some mozilla/netscape stuff in np_sdk -- would helix get included in a similar way?
I'd tend to lean towards (1), as most of the changes the helix side would be tracking would be helix-related, and doing this part in hc.org would save some work (vs keeping a hxclientkit sdk up to date within ooo cvs). hc.org members would also probably be more familiar with the helix-style code.
Will the OOo sdk have everything I need in it to do out-of-process stuff?
-- Ryan Gammon [EMAIL PROTECTED] Developer for Helix Player https://player.helixcommunity.org
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
