To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=97633
User jsc changed the following: What |Old value |New value ================================================================================ Status|UNCONFIRMED |RESOLVED -------------------------------------------------------------------------------- Resolution| |INVALID -------------------------------------------------------------------------------- ------- Additional comments from j...@openoffice.org Mon Dec 29 08:47:10 +0000 2008 ------- This API is not really intended to be used directly but i can understand your needs but ... 1. we don't want that single extensions do it on their own. We want a well defined workflow. It's also for security. That means the office checks for updates of any installed extensions automatically or when the users request it explicitly. Extension developers can easy update their extension in the extension repository or can provide an own update url (own repository). The official repository is recommended. 2. This can be easy achieved by using the unopkg command line tool as well. Well using the API is of course easier here because you don't have to search the office if you use the simple bootstrap. We haven't published the API because we are working on improvements in this area and we want to keep the flexibility of easy changes. But we are thinking about a way to become more flexible with published API's in the future. That means API's might be change with new major versions. Not defined yet but i think we need this flexibility in the future ... I set this request on invalid because it's the normal process to publish API's over time. We don't need requests for that -> too much overhead. Use the current API, i don't expect big changes in the near future. Check it early with new versions and adapt your code if necessary. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@api.openoffice.org For additional commands, e-mail: issues-h...@api.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org