And I've found a discussion about this on this list, which talks about
an effort within the OOo project:
http://api.openoffice.org/servlets/ReadMsg?list=dev&msgNo=8083
Has this lead to the kind of API we have now? Or is there some code in
development to be looked at?
See my repsponse from back then at
<http://api.openoffice.org/servlets/ReadMsg?list=dev&msgNo=8224>. This
has been introduced as "shiny new UNO" a long while ago (see
<http://marketing.openoffice.org/ooocon2004/presentations/friday/shinyhappyuno.pdf>)
and is the foundational work by which new UNO entities (interfaces,
services, etc.) can be designed that are easier to work with in the
various UNO language bindings; however, the vast majority of existing
OOo UNO API has not (yet?) been improved to make use of those new features.
@Tobias&Stephan: Thank's for your helpful feedback.
Looks as if it still would be useful to use an additional abstraction
layer for a lot of things. So I only have to decide on whether to use an
existing solution or whether to write one myself and how it should look
like... :)
Regards
Arthur
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
