Arnulf Wiedemann wrote:
[...]
I have an additional question in that area:
did anyone think about making an urp interface which uses only nested string
lists instead of the "bit fiddling" and all the other value types used in the
current implementation of bridges/remote/urp which make it sometimes hard to
connect to ooo. The interfaces can be unchanged, its only the the stuff read
from and written to the socket which would have been added for that kind of
interface.
My idea is:
using a name/value pair for all the parameters, types etc. in the interface.
For example a PropertyValue structure could be sent as:
{{struct PropertyValue} {{Name Filtername} {Handle -1} {Value MSExcel97}
{State 0}}}
I think a lot of people using scripting languages could get easier access to
ooo.
Cheers,
Arnulf
You mean a "text-based front end" to the URP bridge, so you can talk URP
"by hand?" No, I am not aware anybody already did anything in that
direction. But go ahead if you like... :)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
