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 patrick12...@openoffice.org Tue Jun 29 17:11:01 +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. > The actual problem is that it is a feature OOo currently does not support > and someone must find the time to implement it. When it shall be done > right, lots of things need to be specified and implemented (extend > description.xml, user interface, how to deal with open documents, ...). But > hey, we're open source. Do you volunteer? ;-) 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 It seem to me easier to implement correctly than the ability to use extensions without restarting OOo. > >Issue 88692 seems to acknowledge that it isn't always possible to install > > an extension and use it without restarting OOo. > > I disagree with the conclusion in this issue. There, a concrete bug in OOo > is proposed to be worked around via the restart-feature. Right thing to do > about that is to fix the actual bug that new menu items will not appear > immediately after extension installation in already opened documents. And > there will be no more need for the inconvenient (from users point of view) > office restart for this scenario. Cool, one step ahead on the road of user > friendliness... Restarting the program is not so inconvenient when you just have to press a button, as is the case with firefox. > >Besides, forcing the extension developers to implement lazy initialization > >complicates their task unnecessarily. That's why it is necessary to > > guarantee that the code that initializes the extension is called before > > the user can use the extension. > > Again, I don't say that this feature is nonsense, just that it currently > has no high priority as we have only limited resources. > > But wait, why do you prefer developer convenience over user convenience? > And the need to restart office after extension installation is PITA for the > user, right? Developer convenience is necessary if you want developers to create extensions for OOo, which in turn increases user convenience. 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). > >If an extension has state, this state can't be stored in local variables. > > It must be stored globally (and the registry isn't always appropriate). > > So the problem with multithreading can't be avoided. The simplest way is > > to use global variables. > > Don't see your point here without knowing the actual use case, sorry. > > Out of curiosity: For what do you use global vars and what exactly are you > doing upon office startup? For example, if an extension can be used to translate words, it may need to store in the memory the words the user asked to translate. When OOo exits, the extension stores the words on disk, and when OOo starts, it loads the information from disk into the memory. > >Btw, are you sure OOo doesn't use global variables ? If it does, this > > means that it is badly designed. > > I know OOo uses global variables (mainly in code more then 15 years old, > though) and it is common agreement among OOo developers that this is bad > design, yes. Global variables are used to store global resources, and can't be avoided entirely. They must be used carefully and advisedly. --------------------------------------------------------------------- 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
