two short remarks on
http://codesnippets.services.openoffice.org/snippet.dtd.
* ATTLIST for ELEMENT snippet:
o Starting with OOo 2.0 there are two officially supported
scripting languages missing from the valid values for the
language attribute:
Hi,
maybe I've missed something and but is ooRex a seperate scripting language
and if yes should we add it to our snippet collection.
Tom
--- Ursprüngliche Nachricht ---
Von: Rony G. Flatscher [EMAIL PROTECTED]
An: dev@api.openoffice.org
Betreff: Re: [api-dev] Returnvalues from Macros -
But I think if you are calling a OOBasic-Macro e.g. from Java
you need to invoke the ScriptingFramework don't you?
So maybe the snippet should deal with calling a Macro from some UNO-Binding
e.g. C++, Java, Python, ... and fetching its return value.
Tom
--- Ursprüngliche Nachricht ---
Von:
Hi,
I don't know if these exceptions are related to that but OO is not thread
save thus you have to serialize calls to it in your java-app.
Tom
Hi,
We have a multi-threaded Java environment. We are using OpenOffice.org
1.1.3. There are times when we make a series of UNO calls (mostly
Hi,
would it be easier to use SWT?
Tom
Hi Kohei,
no, they will probably not extended and i hope that we will find an
alternative (however it will look like) that it will be possible to
implement own dialogs for extensions with the same look and feel as
the rest of the office on
Hi,
How is the IDL created? Maybe we could switch to output format to XML and
then do the same the codesnippet page does?
XML = HTML
* once sorted alphabetically
* once grouped like it is now
According to the what the user desires? We could even create other output
formats from this point on
I thought about automatically linking all imports or includes when we are
talking C++. We could even link all com.sun to the IDL?
What do you think about it?
Tom
Hi Tom,
thanks for the extensison, i think it is very helpful to improve the
navigation to the IDL reference and implicit
