Hi Matthias,
> I don't know in what context you hit this issue but just in case it
> helps you I'd like to mention that the scripting framework provides
> another way to invoke macros besides dispatches. If you're interested,
> you can find ready to use functions for invoking macros via the
> scripting framework in the file UNO.java (a self-contained UNO Wrapper
> and support library) which you can find inside the wollmux_*.tar.gz
> archive downloadable from
>
> http://forge.osor.eu/frs/?group_id=11
>
thank you very much for this interesting link (path to UNO.java:
<\wollmux_5.1.0.tar\wollmux-5.1.0\UNOHelper\src\de\muenchen\allg\afid\UNO.java>)
!
[This is a *very* interesting solution for invoking scripts using the
OOo scripting framework, bypassing the
XDispatchHelper.executeDispatch(). It also demonstrates how to use an
XBrowseNode to traverse the tree of script nodes in executeMacro().]
---
For the current use-case in question, the user of any programming
language should be able to invoke a script written in ooRexx (by a
student, Nicole Scholz). The script takes either an UNO object or an IDL
string and creates a writer document that lists all available
definitions in various forms and links to the official OOo
documentation, such that one can easily get an overview of all the
functionality and structures available and being able to link from each
chunk to the OOo documentation.
This script can be invoked via the dispatch interface and therefore
programmers should be able to take advantage of it with the means
available to them. The easier the better. For this group of
programmers/people it is currently out of the question to use the
interesting solution you pointed to, as they are used to
executeDispatch(...) which is demonstrated in numerous snippets/examples.
There are up to nine (!) arguments possible that drive the production of
the "just-in-time" documentation, where only the first one is mandatory.
Hence, getting an additional argument, appended by OOo somewhere causes
a problem. In order to demonstrate some renderings (and then just click
to navigate the embedded links), I just created the following ones,
which may be interesting to look at as they demonstrate (and document)
what a writer document implements:
* <http://wi.wu-wien.ac.at/rgf/tmp/OOo/IDL-Definitions-writerComponent.pdf>
*
<http://wi.wu-wien.ac.at/rgf/tmp/OOo/IDL-Definitions-writerComponent-two-levels.pdf>
As you can see this might be really quite useful for OOo programmers of
all levels, and therefore I would like the ooRexx script to be easily
dispatched by anyone from any language using the OOo built-in dispatch
functionality for it. This intention is the motivation to ask for
help/infos w.r.t. the argument problem, but also the problem encountered
with OOo Basic, which can invoke the script, but once the script uses
the bootstrap mechanism to get at a new context to create the writer
document containing the rendered documentation, but goes out to lunch
(which is not the case if doing the same thing from a Java program).
---rony
