Difference between revisions of "Extension Deployment"

From Apache OpenOffice Wiki
Jump to: navigation, search
 
Line 1: Line 1:
−
 
 
== First considerations ==
 
== First considerations ==
  
 
Extension deployement should not be considered as an independent task.
 
Extension deployement should not be considered as an independent task.
−
Indeed, when you need to deploy extensions on a number of workstations, you'll need also to deploy models, shortcuts, gallery themes, and so on, because you'll need to preserve a relative homogeneity. In fact, you'll often need de deploy extensions in the same time you need to deploy models, shortcuts and gallery themes.
+
Indeed, when you need to deploy extensions on a number of workstations, you'll need also to deploy templates, autotexts, gallery themes, and so on, because you'll need to preserve a relative homogeneity. In fact, you'll often need to deploy extensions in the same time you need to deploy templates, autotexts and gallery themes.
  
 
That's why it is suggested here to consider the following approach:
 
That's why it is suggested here to consider the following approach:
−
1 - to define the structure of a package which aims to deploy in one operation extensions, includind macro and toolbars, models, shortcuts and gallery themes;
+
 
−
2 - to define the user interface of an administration tools whose goal is to create such a package;
+
1 - to define the structure of a package which aims to deploy in one operation extensions, including macro and toolbars, templates, autotexts and gallery themes;
−
3 - to define the user interface of a user tools which would enable the end user to install the package on her workstation, or the administrator in the shared installation tree.
+
 
 +
2 - to define the user interface of an administration tool whose goal is to create such a package;
 +
 
 +
3 - to define the user interface of a user tool which would enable the end user to install the package on her workstation, or the administrator to install it in the shared installation tree.
  
  
 
== Technical constraints ==
 
== Technical constraints ==
 
Before specifying the content of the package, we must keep in mind some technical contraints induced by the implementations of the configuration objects, and the rules for specifying their location.
 
Before specifying the content of the package, we must keep in mind some technical contraints induced by the implementations of the configuration objects, and the rules for specifying their location.
 +
 +
 +
=== Default locations ===
 +
Default locations of the objects seem to be specifyed in the file
 +
<code>$(insturl)/share/registry/schema/org/openoffice/Office/Common.xcs</code>
 +
 +
In most configuration files, some frequently used location are referenced via variables:
 +
 +
$(insturl) represents the installation directory, eg. /opt/openoffice.org2.0
 +
 +
$(userurl) represents the user configuration directory, eg. /home/smith/.openoffice.org2/user
 +
 +
$(work) stands for the user work directory.
 +
 +
=== Templates ===
 +
The default locations of templates are specifyed in the following XML part:
 +
<code><pre>
 +
<prop oor:name="Template" oor:type="oor:string-list">
 +
    <info>
 +
      <desc>Specifies the templates originate from these folders and sub-folders.</desc>
 +
    </info>
 +
    <value oor:separator=":">$(insturl)/share/template/$(vlang):$(userurl)/template</value>
 +
</prop>
 +
</pre></code>
 +
 +
Templates are objects very similar of other objects produced with the suite. The only differences stand in the 't' in place of 'd' in the second place of the suffix, and in the virtual tree for accessing to them, built from the set of pathes declared in the configuration files.
 +
 +
If the user changes this set of pathes, these ones are from this time stored in the file
 +
registry/data/org/openoffice/Office/Common.xcu
 +
=== Autotexts ===
 +
The default location of autotexts  is specifyed in the following XML part:
 +
<code><pre>
 +
<prop oor:name="AutoText" oor:type="oor:string-list">
 +
  <info>
 +
      <desc>Contains the directory which contains the AutoText modules.</desc>
 +
  </info>
 +
  <value oor:separator=":">$(insturl)/share/autotext/$(vlang):$(userurl)/autotext</value>
 +
</prop>
 +
</pre></code>
 +
The user interface of OOo doesn't seems to provide a way for changing these locations.
 +
$(userurl)/registry/data/org/openoffice/Office/Common.xcu
 +
 +
 +
=== Macros ===
 +
 +
=== Toolbars ===
 +
 +
=== Gallery's themes ===

Revision as of 14:02, 31 March 2006

First considerations

Extension deployement should not be considered as an independent task. Indeed, when you need to deploy extensions on a number of workstations, you'll need also to deploy templates, autotexts, gallery themes, and so on, because you'll need to preserve a relative homogeneity. In fact, you'll often need to deploy extensions in the same time you need to deploy templates, autotexts and gallery themes.

That's why it is suggested here to consider the following approach:

1 - to define the structure of a package which aims to deploy in one operation extensions, including macro and toolbars, templates, autotexts and gallery themes;

2 - to define the user interface of an administration tool whose goal is to create such a package;

3 - to define the user interface of a user tool which would enable the end user to install the package on her workstation, or the administrator to install it in the shared installation tree.


Technical constraints

Before specifying the content of the package, we must keep in mind some technical contraints induced by the implementations of the configuration objects, and the rules for specifying their location.


Default locations

Default locations of the objects seem to be specifyed in the file $(insturl)/share/registry/schema/org/openoffice/Office/Common.xcs

In most configuration files, some frequently used location are referenced via variables:

$(insturl) represents the installation directory, eg. /opt/openoffice.org2.0

$(userurl) represents the user configuration directory, eg. /home/smith/.openoffice.org2/user

$(work) stands for the user work directory.

Templates

The default locations of templates are specifyed in the following XML part: 

<prop oor:name="Template" oor:type="oor:string-list">
    <info>
       <desc>Specifies the templates originate from these folders and sub-folders.</desc>
    </info>
    <value oor:separator=":">$(insturl)/share/template/$(vlang):$(userurl)/template</value>
</prop>

Templates are objects very similar of other objects produced with the suite. The only differences stand in the 't' in place of 'd' in the second place of the suffix, and in the virtual tree for accessing to them, built from the set of pathes declared in the configuration files.

If the user changes this set of pathes, these ones are from this time stored in the file registry/data/org/openoffice/Office/Common.xcu

Autotexts

The default location of autotexts is specifyed in the following XML part: 

<prop oor:name="AutoText" oor:type="oor:string-list">
   <info>
       <desc>Contains the directory which contains the AutoText modules.</desc>
   </info>
   <value oor:separator=":">$(insturl)/share/autotext/$(vlang):$(userurl)/autotext</value>
</prop>

The user interface of OOo doesn't seems to provide a way for changing these locations. $(userurl)/registry/data/org/openoffice/Office/Common.xcu


Macros

Toolbars

Gallery's themes

Retrieved from "https://wiki.openoffice.org/w/index.php?title=Extension_Deployment&oldid=7194"
Personal tools