To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111837
------- Additional comments from k...@openoffice.org Tue Jun 29 17:56:48 +0000 2010 ------- >> >What is the problem with requiring the user to restart OOo to use a newly >> >installed extension ? >> >> No problem with this feature in general. >In your previous comment, you said you wanted to achieve that all extensions >are >usable immediately and later, in you last comment, you said restarting is PITA >for the user. Exactly. Because it is PITA for the user I want to achieve that all extensions are life-deployable and do not need a restart. Nothing wrong or contradictorily with this, IMO - just consistent. >I may be wrong, but it doesn't seem so complex to implement : >- add a new element in description.xml to require restarting OOo >- when the extension is installed, warn that it requires OOo to be restarted to >be used >- wait until OOo is restarted to activate the files in the extension As you are so far with this - you know C++, you know OOo UNO API concepts, you have practice coding for OOo, you even have an idea how to implement the feature: Thus, do you volunteer to implement this feature? At the moment, we don't have the resources for this, because currently we have no demand for this feature. If you need the feature urgently, go ahead and implement it. Just make yourself the owner of this issue and start. This is the true spirit of open source. Otherwise you will have to be just patient... >It seem to me easier to implement correctly than the ability to use extensions >without restarting OOo. Many many features in OOo are already life deployment ready and we are working hard to get better and better. It is not the case that nothing works. Its more the other way round. >The current situation is convenient neither for the developers (because it is >impossible to do the job correctly), nor for the users (because a newly >installed extension doesn't update the UI immediately). First, please don't claim two certain problems as "nothings works for both developers and users". That really hurts. Second, you can do your job correctly(!) by doing lazy initialization. Implement a UNO singleton (an XPropertySet impl. maybe) and fill it with your global data during your lazy init. Once instantiated, the singleton will be alive until OOo exits and can be obtained from Service Manager at any time. No real need for the restart feature here. Just don't be too lazy and even today (OOo 3.2) your users can be happy - without restarting their offices after installation of your extension. Restart feature can make it into 3.4, earliest. Third, the problem with some(! not all) UI parts not updated live is a different story, unrelated to your problem, and must be tackled by fixing the actual problem, not worked around with an office restart. --------------------------------------------------------------------- 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...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
