Thank you very much.
Effectively, this is the situation that I feared.
So now let me say the whole story :-)
I'm implementing (in Python) a DispatchRecorder for the Python language.
The service itself is far from being complete but I don't see big difficulties
at implementation level.
After your answer I see a big problem at ui integration level...
Initially, I have thought to implement my service as an alternative
Dispatchrecorder.
At integration level, I would have supplied a toolbox with two buttons in
order to start/stop the recording, with the usual Addons.xcu file.
After your answer the only way I see is to implement my PytonDispatchRecorder
as a replacement for the original one.
This means that In the XDispatchRecorder.getRecordedMacro() method I must
supply a way (let's say a dialog) to let the user select the language for the
macro.
In case the user select "python" I must also find some dirty hack to avoid the
"save macro" dialog and launch instead my alternative "save python" dialog
Any comments or ideas will be greatly appreciated
Hmm, since OOo 2.0 there are even more scripting languages (BeanShell,
JavaScript, and in addition all those scripting languages which can be
plugged in via the OOo scripting framework).
So it would make a lot of sense to have a generic solution for this
problem: allow the user to pick any of the available/installed scripting
languages to be used for macro recording.
Actually, this functionality is the paramount one that I feel is missing
from the new scirpting framework (unless I oversaw the obvious)!
Regards,
---rony
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
