Hi Samuel,
>>
>> > It is even packaged as an extension
>> >
>> > http://wiki.services.openoffice.org/wiki/Extensions_Packager
>> >
>> > So, imho, it is the way to go. Just enhance it
>>
>> Thank you for this hint. I did install the extension, but do not see any
>> add-on-entry, nor an entry on the export drop-down (neither in the OOo
>> Basic IDE, nor in the document's file menu). So I assume that I am
>> overseeing the obvious.
>
> If you installed the extension there should be a new button somewhere
> on the toolbar. i think for me it was top left-hand corner near the
> new document button.
Yes, thank you!

After reading the text you pointed me to and looking once more to the
BasicAddonBuilder I finally looked through the "View -> Toolbars" and
saw there was a Basic Addon Toolbar, which I found afterwards, and as
you write, consists of one entry.

In the meantime I looked over the code which is really impressive ans
shows the high command Paolo has gained over that area of OOo!

Unfortunately, at the moment it would be a little bit too much time
consuming research effort to try to extend it to cater generically for
all macro languages that happen to be installed on the system.

Things like:

    * how to get a list of the installed macro languages,
          o what is the exact spelling of a macro language (E.g. "java"
            vs. "Java"),
          o what is the URL to indicate a specific macro from a specific
            macro language should be used (with or without arguments),
    * how to get a list of existing macro libraries
          o "user-home"/user/Scripts
          o "shared-hoome"/shared/Scripts
    * how to get a list of
          o existing macro files (in the Python case there are macros
            right in "./Scripts/python", i.e., the home of macro
            language directory contains already scripts.

These questions are probably easy to answer by those in the know, which
would help save quite some research time. (Maybe someone who knows could
just give hints/pointers where to look into?)

Once this knowledge is available, one could start to try to generalize
the current BasicAddonBuilder to become a true "MacroAddonBuilder" (like
having a choice for the desired macro language initially, and maybe even
allow to pick any macro from any macro language to execute, if a toolbar
button or menu option got chosen)?

Regards,

---rony

Reply via email to