Hi Ariel, >> And brings me to: Did you already play with making this an extension? As >> I understand it, you should be able to create an .oxt which contains the >> JAR, and thus adds the functions to any OOo installation. > > Yes, and added some things: > ...
Hey, all those sound terrific - I want to have this extension when it's finished ;) > * Unfortunatelly, I've tried to get the locale for the date formatting > functions from OOo configuration node; but I've experienced some > crashes, so I get the default/system locale of the JVM, what isn't > really a "prytty thing", because OOoLocale and the JVM default locale > CAN BE DIFFERENT. > My hypothesis: we have to proccesses, HSQLDB and OOo. When my Java > methods are invoked from OOo, it's HSQLDB that invokes them. In order to > get the locale from the configuration, I must bootstrap the Office, > because I don't get any XComponentContext or any other OOo API interface > to get the Service manager as I would have if my extension component was > called from the ProtocolHandler or the Job environment: it's HSQLDB who > is invoking them, NOT OOo. > I guess it crashes when I try to bootstrap because HSQLDB can't > find/load the API JARs. > So, I should ship the required JARS with my extension OXT file, as if > it was a client application (?), I should include in my JAR ALL the > classes required for a client app. (?), and should also > include the dymanics libraries for the diferent OSs (?) :-( . The latter definitely doesn't sounds like a good idea. I am not sure what your functions can access - is there any kind of context, such as the Database object? If so, there would be a Database.collation.locale member, which could serve as a substitute. Other than that, I don't have an idea, I know too little about the architecture of Java components in OOo. Perhaps [EMAIL PROTECTED] is worth a try. > * as in my testing with a database containing some binary files (some > pics == script.length()= 1,565,309) I discovered that the edit control > has some length limits, I added the posibility to directlly open the > script in a Writer doc. instead of the dialog. > The problem here is that the actual length limit > isn't documented in the API refrence, IIRC, it's the usual 64K limit. In every case, the limit strictly implementation driven, there has been no design decision whatsoever, so you won't find this document. Perhaps you should use 32K to be on the safe side (perhaps there are some signed instead of unsigned values involved somewhere). > When I finish my reserch, I will ship it as an extension I'm, looking forward to this! Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
