Re: Is there an example for packaging macros as an extension somewh

Hi Paolo,
>> 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?)
>>     
You definitely are "someone in the know"!


> All these information are accessible through the
singleton:
>
"com.sun.star.script.browse.theBrowseNodeFactory"
>
> I've put a basic example at the end of this post.
> Copy the source in your StarBasic IDE and run the first
macro.
> It should create a spreadsheet with a hierarchical list
of the macros for all 
> supported languages. (it may take some time...)
>   
Thank you *very* much! I was also able to transcribe it to
ooRexx and
run the macro from the commandline (from outside of OOo).

Will have to look further into the node-interfaces as it is
probable
that one can get at the content of the nodes (it is just too
late for me
to go on). But I think that from the knowledge gained from
your macro
alone, I will get some sort of a "jump start", so
again: thank you very
much!

>> 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)?
>>     
>
>
> All the necessary code is (more or less) already in the
BasicAddonBuilder, but 
> I've deliberately limited the choice to Starbasic only.
Not only, I've used 
> the old style macro URL's in the generated addons.xcu.
("macro:" protocol 
> instead of the new and language agnostic
"vnd.sun.star.script:" protocol)
>
> This is because in my first experiments I got errors
trying to install an 
> addons.xcu with commands specified with the
"vnd.sun.star.script:" protocol.
>
> Anyway I think that it would be possibile (even if not
so trivial) to make the 
> BasicAddonBuilder language agnostic, removing
limitations to basic only that 
> I've introduced, but this would work only in the
scripting domain, and not 
> for deployng UNO components.
> A more generic solution was suggested from Mathias
Bauer in this post:
> http://extensions.openoffice.org/servlet
s/ReadMsg?list=dev&msgNo=513
>
> Until now I was oriented in this direction, but I'm
open to any suggestions 
> and contributions.
> But, before to add new features I would like to finish
my todo list:
> - Localization of UI items in the generated Addons.xcu

> - Versioning support
> - Licensing support
> - Dependances support
>
> and I really need help for the first entry! 
>   
Well, for the first entry I can volunteer for the German
language,
should you have a need for it.

> I've posted my question here some days ago but I didn't
receive any reply 
> http://api.openoffice.org/servlets/ReadMsg?li
st=dev&msgNo=17858
>
> Perhaps my question was not well explained?
>   
Not being able to help myself, maybe rephrasing your
question from the
above URL may yield an answer by someone in the know by
luck:"Where all
that localized language names are stored? Are they
accessible via the
com.sun.star.resource.OfficeResourceLoader singleton
?"

Regards,

---rony