Difference between revisions of "Extensions feature ideas"
| Line 2: | Line 2: | ||
| − | #[[#safemode|Running OOo in safe mode | + | #[[#safemode|Running OOo in safe mode]] |
| − | #[[#license_ooo_install|Support of licenses for extensions when they are installed together with OOo | + | #[[#license_ooo_install|Support of licenses for extensions when they are installed together with OOo]] |
| − | #[[#configure|Configuring extensions | + | #[[#configure|Configuring extensions]] |
| − | #[[#systemintegration|Enhance system integration | + | #[[#systemintegration|Enhance system integration]] |
| − | #[[#file_open_installation|Installing extensions by opening extensions in the office's file dialog | + | #[[#file_open_installation|Installing extensions by opening extensions in the office's file dialog]] |
| + | #[[#language_pack|Language Packs for extensions]] | ||
| Line 13: | Line 14: | ||
<ol> | <ol> | ||
| − | <li><span id="safemode">Running OOo in safe mode | + | <li><span id="safemode">Running OOo in safe mode</span> |
<p>A faulty extension may cause OOo to crash. When this happens for example at startup (or shortly after) | <p>A faulty extension may cause OOo to crash. When this happens for example at startup (or shortly after) | ||
it is difficult for the user to remove the extension. That is, the Extension Manager cannot be invoked anymore. | it is difficult for the user to remove the extension. That is, the Extension Manager cannot be invoked anymore. | ||
| Line 20: | Line 21: | ||
</p> | </p> | ||
</li> | </li> | ||
| − | <li><span id="license_ooo_install">Support of licenses for extensions when they are installed together with OOo | + | <li><span id="license_ooo_install">Support of licenses for extensions when they are installed together with OOo</span> |
<p>Extensions support a simple mechanism for showing a license to the user. This happens during installation. The user must | <p>Extensions support a simple mechanism for showing a license to the user. This happens during installation. The user must | ||
agree to the license before the extension is installed. This works well when the extension is installed by the Extension Manager. | agree to the license before the extension is installed. This works well when the extension is installed by the Extension Manager. | ||
| Line 26: | Line 27: | ||
</p> | </p> | ||
</li> | </li> | ||
| − | <li><span id="configure">Configuring extensions | + | <li><span id="configure">Configuring extensions</span></li> |
<p>An extension may need to be configured. In this case it could bring a dialog through which all necessary settings could be done. This dialog could for example be started after installation of an extension. It could also be integrated in the options dialog of OOo. | <p>An extension may need to be configured. In this case it could bring a dialog through which all necessary settings could be done. This dialog could for example be started after installation of an extension. It could also be integrated in the options dialog of OOo. | ||
</p> | </p> | ||
| − | <li><span id="systemintegration">Enhance system integration | + | <li><span id="systemintegration">Enhance system integration</span></li> |
<p> | <p> | ||
It should be possible to install an extension by double clicking them. This should even be possible in these scenarios: | It should be possible to install an extension by double clicking them. This should even be possible in these scenarios: | ||
| Line 41: | Line 42: | ||
This would probably mean some interprocess communication between two unopkg instances. | This would probably mean some interprocess communication between two unopkg instances. | ||
</p> | </p> | ||
| − | <li><span id="file_open_installation">Installing extensions by opening extensions in the office's file dialog | + | <li><span id="file_open_installation">Installing extensions by opening extensions in the office's file dialog</span> |
<p> | <p> | ||
For more user friendlyness it should be possible to install extensions by using the file open dialog of OOo. That is, the user need not open the Extension Manager to install an extension. | For more user friendlyness it should be possible to install extensions by using the file open dialog of OOo. That is, the user need not open the Extension Manager to install an extension. | ||
</p> | </p> | ||
</li> | </li> | ||
| + | <li><span id="language_pack">Language Packs for extensions</span> | ||
| + | <p> | ||
| + | </p> | ||
| + | |||
</ol> | </ol> | ||
[[Category:Extensions]] | [[Category:Extensions]] | ||
Revision as of 13:04, 23 October 2006
This page is intended to collect ideas for future features of the Extensions Manager and Extensions.
- Running OOo in safe mode
- Support of licenses for extensions when they are installed together with OOo
- Configuring extensions
- Enhance system integration
- Installing extensions by opening extensions in the office's file dialog
- Language Packs for extensions
- Running OOo in safe mode
A faulty extension may cause OOo to crash. When this happens for example at startup (or shortly after) it is difficult for the user to remove the extension. That is, the Extension Manager cannot be invoked anymore. By starting OOo in safe mode, all extensions would be disabled. Then the user could remove the faulty extension in the Extension Manager.
- Support of licenses for extensions when they are installed together with OOo
Extensions support a simple mechanism for showing a license to the user. This happens during installation. The user must agree to the license before the extension is installed. This works well when the extension is installed by the Extension Manager. However, when an extension is part of the installation set, that is, it is installed along with the office, then this mechanism does not work or integrates well. For example, when installing the rpms every extension with a license would require a user interaction on the console. When developing a solution one should bear in mind, that one has to make sure that an extension is not usable, does not leave any marks in the GUI, and best is not copied at all to the office installation when the user refuses to agree to the license.
- Configuring extensions
- Enhance system integration
- OOo is running, no extension manager running
- OOo and its extension manager are running
- another instance of unopkg gui is running
- another instance of unopkg is running
- Installing extensions by opening extensions in the office's file dialog
For more user friendlyness it should be possible to install extensions by using the file open dialog of OOo. That is, the user need not open the Extension Manager to install an extension.
- Language Packs for extensions
An extension may need to be configured. In this case it could bring a dialog through which all necessary settings could be done. This dialog could for example be started after installation of an extension. It could also be integrated in the options dialog of OOo.
It should be possible to install an extension by double clicking them. This should even be possible in these scenarios:
This would probably mean some interprocess communication between two unopkg instances.
