Hi Mike,
We decided to go for a) and I don't really see any problems
with it. You mentioned the problem with OOo 1.1.x which
always writes to HKEY_CURRENT_USER. This is a bug and very
unfortunate. I think this bug cannot be fixed in OOo 1.1.x
but probably I'm wrong. Therefore I only see two
Thomas,
That's for the workaround, but I've been having these discussions
because I'm developing some client apps and am forseeing the problems
people are going to have as well as trying to prompt discussion to
enable a better OOo design for the future.
mike
--- Thomas Benisch [EMAIL PROTECTED]
Hi,
Mike Traum wrote:
Thomas,
I'm not sure what you mean by the user or administrator defining the
default installation.
They can make the registry entries point to the desired installation.
The administrator can set the HKLM one as default, the user can override
this in HKCU.
Maybe we should
Thomas,
For option (b), I wasn't proposing an automatic selection, unless, of
course, the Bootstrap was extended to be able to tell you what
services are available with each installation, or to be able to find
an installation which provides a certain service. This, in my opinon,
would be the best
Mike,
Mike Traum wrote:
Kay,
I understand what you're saying about the Bootsrap, but right now,
the Loader is completely dependant on OOo.
As far as the error reporting to the user, this could be done. But,
maybe I wasn't clear because I made some points in previous emails.
If a user has an
Kay Ramme - Sun Germany - Hamburg wrote:
Mike,
Mike Traum wrote:
Kay,
I understand what you're saying about the Bootsrap, but right now,
the Loader is completely dependant on OOo.
As far as the error reporting to the user, this could be done. But,
maybe I wasn't clear because I made some points in
Thomas,
forgot about that. You are certainly right, there is _no_ way to find
out which the latest/newest office is on a system.
Mike, I suggest to follow my other suggestion to just provide a
reasonable error message in case a service is not available or does not
work as expected.
The
Thomas,
forgot about that. You are certainly right, there is _no_ way to find
out which the latest/newest office is on a system.
Mike, I suggest to follow my other suggestion to just provide a
reasonable error message in case a service is not available or does not
work as expected.
The
Thomas,
forgot about that. You are certainly right, there is _no_ way to find
out which the latest/newest office is on a system.
Mike, I suggest to follow my other suggestion to just provide a
reasonable error message in case a service is not available or does not
work as expected.
The
Thomas,
I'm not sure what you mean by the user or administrator defining the
default installation. This would be possible in linux/unix, but, from
what I've gathered, there's no way to do this in Windows. OOo 1.1.x
will always trump all other installations (unless there's something I
don't know).
Mike Traum wrote:
Kay,
I understand what you're saying about the Bootsrap, but right now,
the Loader is completely dependant on OOo.
As far as the error reporting to the user, this could be done. But,
maybe I wasn't clear because I made some points in previous emails.
If a user has an
The SDK 1.9m77 is not intended to be used for OO 1.1.4.
That said I don't know if it is incompatible to OO 1.1.x, but since
bootstrapping has changed a lot over the last months it is not
surprising to me that problems occur in your case.
On Apr 7, 2005 4:27 PM, Mike Traum [EMAIL PROTECTED] wrote:
I'm using the 1.9.m77 sdk to write a java client. I've been having
other problems, but along the way, I was told that OOo 1.1.4 supports
the Bootstrap, but there is currently a bug when having a space in
the path name of the installation.
So, I removed the installation, installed without the
13 matches
Mail list logo
