Re: [api-dev] external application getting OOo version number

2007-03-22 Thread Stephan Bergmann
Jorge Marques Pelizzoni wrote: Thing is: once I developed a UNO package that worked fine for version 1.5 but would crash 2.0. So it seems to me that OOo version numbers may come handy for installers/updaters. In theory, it should not happen that a well-behaved UNO application or component

Re: [api-dev] external application getting OOo version number

2007-03-22 Thread Mathias Bauer
Jorge Marques Pelizzoni wrote: Thank you very much for your reply, John! Anyway, I'm amazed that this must be so complicated. I mean, I wouldn't expect to have to dig into the UNO framework to get that. I thought something like a -v option should do the job :o) Thing is: once I developed a

Re: [api-dev] external application getting OOo version number

2007-03-22 Thread Stephan Bergmann
Mathias Bauer wrote: Jorge Marques Pelizzoni wrote: Thank you very much for your reply, John! Anyway, I'm amazed that this must be so complicated. I mean, I wouldn't expect to have to dig into the UNO framework to get that. I thought something like a -v option should do the job :o) Thing is:

Re: [api-dev] external application getting OOo version number

2007-03-22 Thread Laurent Godard
Hi I'd like to know what is the easiest way for an external application (say, an ebuild binary) to find out OOo's version number (e.g. 2.0.2). the information is stored in the ooo/share/registry/.../Setup.xcu file (Node Product/ooSetupVersion) here is a macro i usualy use from inside OOo

Re: [api-dev] external application getting OOo version number

2007-03-22 Thread Christian Lohmaier
On Thu, Mar 22, 2007 at 03:23:10PM +0100, Laurent Godard wrote: Hi I'd like to know what is the easiest way for an external application (say, an ebuild binary) to find out OOo's version number (e.g. 2.0.2). the information is stored in the ooo/share/registry/.../Setup.xcu file (Node

Re: [api-dev] external application getting OOo version number

2007-03-22 Thread Laurent Godard
Hi the information is stored in the ooo/share/registry/.../Setup.xcu file (Node Product/ooSetupVersion) That won't work if you want to detect the minor version. this a bug IMHO as it worked in the OOo 1.1.x branch could it be solved ? btw, you'll have the minor version but not the third

Re: [api-dev] external application getting OOo version number

2007-03-22 Thread Christian Lohmaier
On Thu, Mar 22, 2007 at 05:38:29PM +0100, Laurent Godard wrote: the information is stored in the ooo/share/registry/.../Setup.xcu file (Node Product/ooSetupVersion) That won't work if you want to detect the minor version. this a bug IMHO as it worked in the OOo 1.1.x branch could it be

RE: [api-dev] external application getting OOo version number

2007-03-21 Thread John Sisson
Hi The thread/subject 'How to get the Version?' has a way that a java client that has a hook to OO can do this. Previous posts on other similar threads have discussed how OO Basic can do the same. John Sisson -Original Message- From: Jorge Marques Pelizzoni [mailto:[EMAIL PROTECTED]

RE: [api-dev] external application getting OOo version number

2007-03-21 Thread Jorge Marques Pelizzoni
Thank you very much for your reply, John! Anyway, I'm amazed that this must be so complicated. I mean, I wouldn't expect to have to dig into the UNO framework to get that. I thought something like a -v option should do the job :o) Thing is: once I developed a UNO package that worked fine for

Re: [api-dev] external application getting OOo version number

2007-03-21 Thread Jim Watson
On 22/03/2007, at 11:08 AM, Jorge Marques Pelizzoni wrote: Thank you very much for your reply, John! Anyway, I'm amazed that this must be so complicated. I mean, I wouldn't expect to have to dig into the UNO framework to get that. I thought something like a -v option should do the job