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 Wed Jun 30 10:54:36 +0000 2010 ------- > It should be easy to understand that a company is > putting development resources it pays for first (if not, only?) on the > tasks the company has demand for. And it should be easy to understand that > a company does not employ new developers if the number of current > developers is able to implement the things the company needs. As a matter > of fact, Oracle currently has no demand for this feature and Oracle OOo > developers currently have not enough "spare" time to implement it. Do you > really think that your "arguments" will change this behavior and raise > Oracles priority for the restart feature? Of course not, but I would be very interested to know how Oracle determines whether there is demand for a feature or not. If everybody thought like Oracle, there would be no Linux, no KDE, no Gnome, etc. Aren't you worried that Oracle/Sun failed to build a strong developer community around OOo? How can you ask people to work for free on OOo, while Oracle doesn't show a strong eagerness to make it a better product? You can't ignore that OOo is affected by a lot of bugs that reduce the usability of the software and that could be fixed more quickly if Oracle accepted to spend a little more money. > Again if you need this feature now, go ahead and implement it. If not, > wait until somebody else (Oracle?) implements it. Even if I did it myself, it would take quite some time (aka money), and it would be released to users only in several months (at best). So, I'll continue to use workarounds. > >> 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. > > > >I'm affected by this problem too. > > What *exactly* is your problem? The fact that new UI elements aren't added immediately to existing windows. > >> 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. > > > >Maybe, but the solution would be partial (if it ever worked). > > I'm convinced that this will work to get rid off OnStartApp event > dependency and global variables. I have no idea why the solution would only > be partial. What else is missing? The UI thing you mentioned above, I > guess? Anything else? Even if I did it, I wouldn't be able to test it completely, because OOo crashes when I try to update my extension (I tested on two different Windows systems). --------------------------------------------------------------------- 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
