Kay is right,
A remote bridge can be implemented purely in C#. An inprocess bridge is needed when one also want to write extension components for the office. The current CLI-UNO bridge is the latter. However, components are not supported yet.
Even for a remote bridge you still need to solve the climaker problem. But if it is possible to use the already available cli_types.dll, then the remote bridge seems to be an "easier" approach (in that you only need C#).
Joachim
Kay Ramme - Sun Germany - Hamburg wrote:
Hi,
Joachim Lingner wrote:
Hi,
Martin Kretzschmar wrote:
Hi,
[snip]
If I read the code correctly, a pure C# version of UNO-CLI is not possible, because the bridge has to have C linkage.
The binary UNO interface is defined in C. That means, that a CLI runtime must be accessable through a C interface. For example, the Java bridge uses the Java Native Interface.
That code would
not quite correct, an implementation of the UnoRemoteProtocol (URP) would do it as well. Actually decoupling any two bridges on an ABI level.
[snap]
Kay
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
