Hi Rony,
see some comments inline
On 1/27/10 4:50 PM, Rony G. Flatscher wrote:
Hi there,
if this is not the right list, please advise. [This e-mail is directed
at [email protected] and [email protected], and the Reply-To-field
set to [email protected].]
After peeking around the documentation (mainly developer's guide)
currently one is able to create componenents in C++ and Java (and also
in Python).
C++, Java and Python we have real language bindings, for all other we
have bridges only. That is the main difference.
The question: how would one create and implement UNO components in
scripting languages that can be deployed via the OOo (Java-based)
scripting framework (e.g. JavaScript/Rhino, BeanShell, but also ooRexx
or other BSF-scripting languages)?
Some of the questions that may be needed to be addressed would be:
* How can one dynamically add IDL kind of type information to the
registry, such that the new types become reflectable?
do we want this because we wouldn't have any documentation for this new
types. Don't get me wrong it's just a question, we also have thought in
this direction in the past as well.
* How can one register a component dynamically ?
that is already possible i think. You add an appropriate factory
implementation for a new service implementation.
* How can one supply a service manager object to be used for
instantiating instances?
that would be one of the more interesting parts. All language bindings
provide some kind of bootstrap mechanism to get started, prepare a
connection etc. That would be necessary
* How can one take advantage of helper classes (XWeak, XComponent) ?
you have to provide similar helper for the scripting language of choice
Are there any links/hints to postings, definitions, sketches of such a
functionality? Is there some experimental implementation available
somewhere (or is it even available already)?
i don't think so, maybe you can take a look in the implementation of the
Python binding
Short of that, how is the Python support implemented? Is there a
documentation about the architecture and the UNO APIs it uses? What
are/were the problems there, are there any shortcomings?
as far as i know it is not really documented, no chapter in the DevGuide
etc. And i would say it is still not really maintained.
---
Maybe to rephrase this question differently: I would like to come up
with a solution for OOo disptachable scripting languages, in which
script programmers have no need for the OOo SDK, if they wish to create
UNO components in their scripting language of choice. (The necessary
complexity involved in creating UNO components, should be reduced to an
absolute minimum, where this minimum should be to have no need for
installing the OOo SDK.)
i agree to the statement "The necessary complexity involved in creating
UNO components, should be reduced to an absolute minimum" but the SDK
doesn't provide too much i would say.
New APIs have to be defined in IDL -> so at least idlc is necessary. The
other tools can be useful for C++ and Java. The header files for C++.
What else is there, the IDL reference, some docu and examples.
Ok for IDL we can think of an integrated idl compiler ...
In general i like the idea but i would focus more on better tooling
around scripting languages. I still have in mind to provide a better
integration for scripting languages in NB.
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
