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
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
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:
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
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
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
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
Hi Stephan,
There is only a min version, see
http://udk.openoffice.org/servlets/ReadMsg?list=featuresmsgNo=40.
The rationale for not having a max version is that OOo's UNO interface
should generally be backward compatible.
which implies that UNO extensions can/should not use unpublished
Hi,
Alle 20:20, giovedì 22 marzo 2007, Frank Schönheit - Sun Microsystems Germany
ha scritto:
Hi Stephan,
[...]
I suppose one can think of more things which contribute to an
extension's required environment, but are not guaranteed to be stable
over major OOo upgrades.
dispatch Url's are
Hi, all!
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).
Thanks in advance. Cheers,
Jorge M. Pelizzoni
ICMC - Universidade de São Paulo
]
Sent: Wednesday, March 21, 2007 3:12 PM
To: dev@api.openoffice.org
Subject: [api-dev] external application getting OOo version number
Hi, all!
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).
Thanks
threads
have discussed how OO Basic can do the same.
John Sisson
-Original Message-
From: Jorge Marques Pelizzoni [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 3:12 PM
To: dev@api.openoffice.org
Subject: [api-dev] external application getting OOo version number
Hi, all
: [api-dev] external application getting OOo version number
Hi, all!
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).
Thanks in advance. Cheers,
I went into OOo/program/ and did
grep -r Build
13 matches
Mail list logo
