diff --git a/offapi/com/sun/star/configuration/ConfigurationAccess.idl b/offapi/com/sun/star/configuration/ConfigurationAccess.idl index e6e672b86b4b..06d0fdbcecf5 100644 --- a/offapi/com/sun/star/configuration/ConfigurationAccess.idl +++ b/offapi/com/sun/star/configuration/ConfigurationAccess.idl @@ -2,9 +2,9 @@ * * $RCSfile: ConfigurationAccess.idl,v $ * - * $Revision: 1.8 $ + * $Revision: 1.9 $ * - * last change: $Author: jb $ $Date: 2001-02-05 14:39:42 $ + * last change: $Author: arellano $ $Date: 2001-02-27 00:38:55 $ * * The Contents of this file are made available subject to the terms of * either of the following licenses @@ -96,6 +96,8 @@ module com { module sun { module star { module configuration { //============================================================================= /** provides (read) access to a fragment of the configuration hierarchy. + +

Values that are direct or indirect descendants of a root element can be retrieved and, if themselves objects, navigated. Other interfaces provide access to information about this element and its context. @@ -106,10 +108,13 @@ module com { module sun { module star { module configuration { (and so on recursively).

+ +

Ultimately the configuration holds values. These values are organized into a hierarchy using structural elements. The structure is defined in advance in a schema. Necessary information from the schema is stored in the configuration - repository itself, and is accessible through an implementation of this service. + repository itself and is accessible through an implementation of this service.

Two different kinds of structural elements are used in the configuration @@ -118,29 +123,31 @@ module com { module sun { module star { module configuration {

Sets
are dynamic containers of homogeneous elements. Which elements - a set contains can vary; their names are defined by the - clients that insert them. On the other hand the type of + a set contains can vary. Their names are defined by the + clients that insert them. On the other hand, the type of the elements is the same for all elements. In the case of elements that are themselves hierarchy objects, the type includes the structure of the hierarchy fragment they contain. Such types are defined in the configuration schema as

templates

.
+ +
Groups
are static collections of heterogeneous elements. The names and - types of the elements a group are completely defined in the - configuration schema. But here each element may be of a different - type, allowing even groups that contain a mix of + types of the elements of a group are completely defined in the + configuration schema. Here each element may be of a different + type, allowing groups that contain a mix of subobjects and simple values.
-

Objects in the configuration hierarchy (i.e. implementations of this service) +

Objects in the configuration hierarchy, for example, implementations of this service, can thus be classified in the following ways: