Rony G. Flatscher wrote: > 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)!
Honestly speaking I think that it was a mistake to offer the macro recorder as it is today. IMHO we would be better off without one. Recording only "dispatch" calls is not what people expect and something else is impossible to achieve with reasonable effort. IMHO we should have offered a pure automation recorder that doesn't generate source code but binary code only. So I hesitate to support any further development in this area. If you want you can "overwrite" the service "com.sun.star.frame.DispatchRecorder" with your service (by implementing this service with your Python recorder) so it will be used automatically instead of the built-in one when you call "Tools-Macro-Record" from the menu. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
