Difference between revisions of "Extensions feature ideas"

From Apache OpenOffice Wiki
Jump to: navigation, search
(some items are obsolete)
(separate folder for shared extensions)
Line 4: Line 4:
 
This page is intended to collect ideas for future features of the Extensions Manager and Extensions.
 
This page is intended to collect ideas for future features of the Extensions Manager and Extensions.
  
 
+
#[[#shared_extensions|Separate Shared Extensions Folder]]
 
#[[#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]]
Line 14: Line 14:
  
 
<ol>
 
<ol>
 +
<li><span id="shared_extensions">Separate Shared Extensions Folder</span>
 +
<p>The shared extensions are saved in the office installation. By installing a new office in a folder, with a different name than the previous version, the old shared extensions are lost. The new office cannot use them. With OOo 3.0 this happens exactly for every minor version. That is, when installing 3.1, 3.2, etc. Therefore shared extensions should be installed in a folder outside of the office installation, similar to user extensions. One should also take into account to offer a migration between major versions, in case the extension manager has changed incompatibly.
 +
</p>
 
<li><span id="safemode">Running OOo in safe mode</span>
 
<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)  

Revision as of 09:59, 31 July 2008

OOo Extensions project

Please view the wiki usage guidelines
before contributing.

Categories:

Pages:

Extensions on the main site

Extensions in other languages:
ES - FR - IT - JA - NL - OC -

This page is intended to collect ideas for future features of the Extensions Manager and Extensions.

  1. Separate Shared Extensions Folder
  2. Running OOo in safe mode
  3. Support of licenses for extensions when they are installed together with OOo
  4. Enhance system integration
  5. Solving dependencies when running the online update



  1. Separate Shared Extensions Folder

    The shared extensions are saved in the office installation. By installing a new office in a folder, with a different name than the previous version, the old shared extensions are lost. The new office cannot use them. With OOo 3.0 this happens exactly for every minor version. That is, when installing 3.1, 3.2, etc. Therefore shared extensions should be installed in a folder outside of the office installation, similar to user extensions. One should also take into account to offer a migration between major versions, in case the extension manager has changed incompatibly.

  2. 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.

  3. 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.

  4. Enhance system integration
  5. It should be possible to install an extension by double clicking them. This should even be possible in these scenarios:

    • another instance of unopkg gui is running
    • another instance of unopkg is running

    This would probably mean some interprocess communication between two unopkg instances.

  6. Solving dependencies when running the online update

    The "Extension Update" dialog should make sure that dependencies are resolved. That is, an extension A version 2 depends on extension B version 2. The user selects extension A v.2 but does not have B v.2 installed. If B v.2 is also available as update, then the user should not be allowed to unselect B v.2. Or in case the user used the context menu for A to invoke the "Extensions Update" dialog then the dialog should automatically offer B v.2 rather then showing that A v.2 cannot be installed because of an incompatibility.

Personal tools