I think it would significantly change the result if the new registry
key was searched for. Then, the users who have multiple versions
installed and have installed OOo 1.x without the -net flag would be
able to use a client.

I don't think you should expect an end user who want's to use a
client app to know anything about these issues, or even know what a
remote connection to OOo is. You would definitely expect this of OOo
client app developers, but it should be seamless for a user.

I'm thinking a bug should be opened on this. Would you be opposed?

thanks,
mike

--- Mathias Bauer <[EMAIL PROTECTED]> wrote:
> Mike Traum wrote:
> > Ahh yes, I now see the -net flag in the SETUP_GUIDE.pdf that's
> > distributed with the package. But, I guarantee that 99% of people
> > installing on windows haven't done that. A command line argument
> to
> > an installer in windows is quite uncommon.
> > 
> > Anyway, I still think this is a bug. If the Bootstrap isn't
> supported
> > by OOo 1.x, shouldn't it ignore 1.x installations?
> 
> I think that it might have been better to use a new registry key
> for the
> bootstrap mechanism, but OTOH I don't know exactly why this wasn't
> done.
> Maybe there was a reason for this. And at the end it wouldn't
> change the
> result largely, would it?
> 
> The "-net" installation in OOo1.x or - more precicely - the fact
> that it
> isn't the default installation procedure is really a pain, I'm
> really
> lucky that we got rid of that.
> 
> Besides that I think that it is acceptable that people who want to
> use a
> remote connection to OOo should study some documentation. ;-)
> 
> Best regards,
> Mathias
> 
> -- 
> Mathias Bauer - OpenOffice.org Application Framework Project Lead
> Please reply to the list only, [EMAIL PROTECTED] is a spam sink.
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


                
__________________________________ 
Yahoo! Messenger 
Show us what our next emoticon should look like. Join the fun. 
http://www.advision.webevents.yahoo.com/emoticontest

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to