Hallo Mike,
> After all of these discussions, I've come up with the following list
> of improvements that I think would make the Bootloader better.
>
> 1. Make it so that a you have a better chance at getting an instance
> of OOo that has the capabilities your client requires.
> ...
> 2. Make the searching for OOo more robust so that it may fulfill item
> 3. Give Bootstrap the optional capability to let the client app
> choose
> which installation among several to use
Good suggestions. You might want to consider reporting these to the UDK
project (which is more appripriate than the API project) to IssueZilla.
But keep in mind what Kay Ramme recently said: It os not a good idea to
specify the OOo version somebody wants. OOo is actually just a collection
of components. And it's the components capabilities you actually want.
Maybe even, almost nobody really want's to instanciate a OOo process, but
rather a text, drawing or calc document. Then of course it could happen
that with one request somebody is getting one OOo version and woth some
other request another version. It's also questionable wheter it makes
sense for external programs which call into OOo to really have access to
allopen documents etc, even those opened by other applications or the user
themselve via UI.
Thus something like a context needed to be implemented. And that would
again more an API issue, which would have to be implmented in the
framework component, at least partly.
Michael
--
Michael Hoennig <[EMAIL PROTECTED]>
project lead OpenOffice.org API
http://api.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
