mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-07 15:22:31 +01:00
Code Issues Packages Projects Releases Wiki Activity

Replace occurrences of ..' by ..` (backtick+text+quote replaced by backtick+text+backtick).

Browse Source 
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1597 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
eiffel-org
2016-07-01 10:32:39 +00:00
parent 067d834eba
commit 10e39cfb40
68 changed files with 452 additions and 453 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/trunk/solutions/preferences/eiffelpreferences/eiffelpreferences-tutorial/initialization.wiki
View File

@@ -19,7 +19,7 @@ The current supported underlying storages are ''XML file'' (<eiffel>PREFERENCES_
''Note:'' that you can build your own custom storage, by implementing the class <eiffel>PREFERENCES_STORAGE_I</eiffel>, and use such object as storage in the associated creation routine.
The option <eiffel>make_with_defaults_and_storage</eiffel> is similar to <eiffel>make_with_storage</eiffel> except an additional parameter is given to retrieve one or more default file locations. This will be one or more XML files on disk containing the default values to use for some or all of your preferences. It is a convenient way to initialize your application with all the default values required `out of the box' for correct or preferred functioning. Those files also contain additional attributes for preference configuration such as more detailed descriptions of the preference. If two files list the same preference, the last one to mention it takes precedence.
The option <eiffel>make_with_defaults_and_storage</eiffel> is similar to <eiffel>make_with_storage</eiffel> except an additional parameter is given to retrieve one or more default file locations. This will be one or more XML files on disk containing the default values to use for some or all of your preferences. It is a convenient way to initialize your application with all the default values required `out of the box` for correct or preferred functioning. Those files also contain additional attributes for preference configuration such as more detailed descriptions of the preference. If two files list the same preference, the last one to mention it takes precedence.
The format of the XML default file is very simple:
<xml><EIFFEL_DOCUMENT>

2
documentation/trunk/solutions/preferences/eiffelpreferences/eiffelpreferences-tutorial/overview.wiki
View File

@@ -5,7 +5,7 @@ This document gives a brief overview of the EiffelPreferences library.
==Introduction==
Simply, preferences are name-value pairs. All preferences are descendants of the deferred class <eiffel>PREFERENCE</eiffel>, and therefore all inherit the common properties of name, value, default values and string representations. Common to all <eiffel>PREFERENCE</eiffel> objects is the notion of `manager'. All preferences belong to a manager, which is a helper class used for organizational and hierarchical management of your applications preferences.
Simply, preferences are name-value pairs. All preferences are descendants of the deferred class <eiffel>PREFERENCE</eiffel>, and therefore all inherit the common properties of name, value, default values and string representations. Common to all <eiffel>PREFERENCE</eiffel> objects is the notion of `manager`. All preferences belong to a manager, which is a helper class used for organizational and hierarchical management of your applications preferences.
So, all preferences belong to a <eiffel>PREFERENCE_MANAGER</eiffel>. The manager itself belongs to a set of related <eiffel>PREFERENCES</eiffel>. In fact, when you create a new manager for a group of preferences you must provide a <eiffel>PREFERENCES</eiffel> object to the creation routine to indicate which set of preferences the new manager will be associated:
<code>