Re: XPackageManagerManager.removePackage changes

Tobias Krais wrote:
> Hi Juergen,
> 
>>> Is it planned to make it public one day ?
>> It doesn't matter because it's always possible to
have unpublished API's
>>    that are primary intended for private usage and
that remain
>> unpublished. General recommendation is to publish
API's after 1-2
>> releases, especially when they provide some new
typical service provider
>> functionality.
> 
> That is very interesting. Let me ask, which OOo version
offered the
> XPackageManager first? Is it 2.2 or 2.2.1?
> 
> That would mean this functionality is close to be
published!?
no, as i mentioned before it is intended for private usage
 I
am not 
sure if  it will be published. I don't see really demand for
it. for 
what exactly do you need it where you can't use the
extensions manager 
or unopkg directly?

and of course it's a recommendation -> no must

Juergen

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

Hi Juergen

>> That would mean this functionality is close to be
published!?
> no, as i mentioned before it is intended for private
usage  I am not

> sure if  it will be published. I don't see really
demand for it. for 
> what exactly do you need it where you can't use the
extensions manager 
> or unopkg directly?
>

the use case would be an intelligent extension that updates
itself
using XPackageManagerManager

a consequent use, a monitoring extension that monitors new
versions of 
all installed ones

Laurent

-- 
Laurent Godard <lgodardindesko.com> -
Ingénierie OpenOffice.org - 
http://www.indesko.com
Nuxeo Enterprise Content Management >> http://www.nuxeo.com - 
http://www.nuxeo.org
Livre "Programmation OpenOffice.org", Eyrolles
2004-2006

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

Hi Juergen,

>> That would mean this functionality is close to be
published!?

> no, as i mentioned before it is intended for private
usage  I am
not
> sure if  it will be published. I don't see really
demand for it. for
> what exactly do you need it where you can't use the
extensions manager
> or unopkg directly?

All our clients with an Windows XP system have admin access.
They will
install a new OpenOffice version as soon as OpenOffice tells
them about
the new version. Thus the path to the Extension Manager
changes and is
out of my scope.

Currently we use a little batch file installing the
extension or
updating it with the extension manager. But the paths in the
batch file
are hard coded.

We would prefer the solution of checking (updating or
installing) an
extension from within Java, because we start OpenOffice from
a little
Java programm. Thus we can check whether the correct
Extension version
is installed and install a different if necessary.

And there is an other reason. Our clients use OpenOffice on
different
platforms. The paths on these platforms are different. Using
the API to
manage packages is the only platform independent solution.

For us, publishing the api would be very useful.

Greetings, Tobias

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org