Hi Jürgen, On 15.02.2010 13:07, Juergen Schmidt wrote: > On 2/15/10 12:40 PM, Rony G. Flatscher wrote: >> Hi there, >> >> where could one find the specs or the code (Java/C/++) for creating the >> registry file-structure from IDL files, such that one can create >> registry files oneself? > i would like to ask again for what reason you want to create it on > your own. You should or have to provide the IDL files anyway.
in order to make it as easy as possible for script language users to create UNO components, they should not be forced to install anything else than OOo (and possibly an external scripting language). Especially "end-user-programmers" (who may have no clues about C++ or Java at all!) should not be forced to install and setting up the SDK or NetBeans (Eclipse). It seems that in order to deploy a component one must supply a physical registry file that will get honored at installation time. This file should therefore be created when creating the necessary infrastructure for packaging a component. The only means available at that point in time would be either the scripting language itself or Java. (If there was a means to register the new types with OOo at installation time programmatically that would be even preferable.) To boil it down: a script programmer (focusing on end-user programmers) should get a (script defined) assistant where s/he fills-in whatever is needed for successfully creating an extension package, without the user needing to know anything of the intimate details that need to be honored. If there are simpler means to achieve that (SDK-less, C++-less), the better. [Even though I am targeting the scripting language ooRexx which is deployed/uses the OOo-Java-scripting framework, I am interested in creating the support such, that at least the packaging - including the type definitions - could be used for any scripting language deployable via the OOo-Java-scripting framework. This way efforts can be reused, and users can pick any language that best fits their own needs.] > There is no formal spec available. But you can check the idlc and the > registry module. > > If you want to provide type descriptions on your own you should more > focus on an own implementation of an TypeDescriptionProvider > (http://api.openoffice.org/docs/common/ref/com/sun/star/reflection/TypeDescriptionProvider.html) > Thank you very much for these pointers. How could one then register new types with OOo (what other services, interfaces would need to be instrumentated, if any)? Regards, ---rony --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
