|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | OpenOffice.org safe mode — for a more reliable Extension Manager | ||
|---|---|---|---|
| Product: | General | Reporter: | Graham Perrin <grahamperrin> |
| Component: | ui | Assignee: | AOO issues mailing list <issues> |
| Status: | CONFIRMED --- | QA Contact: | |
| Severity: | Trivial | ||
| Priority: | P3 | CC: | issues, Mathias_Bauer |
| Version: | DEV300m41 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://n2.nabble.com/OpenOffice.org-User-Feedback-Extension-tp2151578p2248450.html | ||
| Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
|
Description
Graham Perrin
2009-02-07 08:18:13 UTC
To clarify: an Extension Manager that can not manage extensions (for any reason) is not a manager. A safe mode should allow OpenOffice.org to run without extensions, so that Extension Manager can be more reliably used for management. — On Mac OS X: safe modes (of operating system, of applications) are sometimes (not always) achieved by holding the shift key when the OS or application is started. On other OSes: other routes to safe modes may be preferred. Sounds good but seems to be a complex problem to solve. Maybe we should rename the extension manager. It might also a solution to disable the extension that causes trouble. But checking the health of extensions costs perfomance. Set target. > a complex problem My primary motive (motives of others may vary) is to be able to disable and/or uninstall any extension. In the example given I found myself unable to use the Manager for a particular extension. > checking the health of extensions costs perfomance. Taking responsibility for the consequences of installing any exension, assuming imperfection of an extension, my main wish would be to disable or uninstall. I would treat health checking by OOo as a separate enhancement. Checks would be nice to have, but less important than the ability to uninstall. > It might also a solution to disable the extension that causes > trouble. Might that be less or more complex than a safe mode that (temporarily) disables all extensions, to allow uninstallation of any one extension? Thanks for comments/consideration. Setting target to 3.2, but keeping the "requirements" owner is a bad idea. If we want to have that in 3.2, we should form an iTeam for this feature. As I understood the original requirement, the user should be able to start OOo without his extensions. That should be easy. But I assume that a user also will be able to deinstall an extension so that she can restart OOo without "safe mode". And this might become more complicated. Anyway, I think we need input from all sides here, including development. And that means: we need an iTeam and an issue owner driving the feature. |