Difference between revisions of "Extensions feature ideas"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 21: Line 21:
 
<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.
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 the agree to the license.
+
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.
 
</p>
 
</p>
 
</li>
 
</li>
  
 
<li><span id="configure">Configuring extensions.</span></li>
 
<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>
 
</ol>
 
</ol>
  

Revision as of 12:57, 16 October 2006

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


  1. Running OOo in safe mode.
  2. Support of licenses for extensions when they are installed together with OOo.
  3. Configuring extensions.



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

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

  3. Configuring extensions.
  4. 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.

Personal tools