diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/console-tool.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/console-tool.wiki
index 56b97d86..a5ba9e84 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/console-tool.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/console-tool.wiki
@@ -62,7 +62,7 @@ Auto-complete feature name: [[Image:console-auto3|Auto-complete feature name]]
You can also pick and drop a group/class/feature into the command area to have related name/path inserted.
-{{seealso| '''See Also'''
+{{seealso|
[[External commands editor dialog|External commands Editor dialog]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-editing.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-editing.wiki
index 3326f633..2f10e300 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-editing.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-editing.wiki
@@ -53,7 +53,7 @@ Note that any existing breakpoint can be referenced by an implicit tag with ''"'
[[Image:breakpoint-dialog-when-hits]]
-{{seealso| '''See Also'''
+{{seealso|
[[Breakpoint commands|Breakpoint commands]]
[[Breakpoint information command|Breakpoint information command]]
}}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-information-command.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-information-command.wiki
index 2f073013..6f602a1c 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-information-command.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-information-command.wiki
@@ -17,7 +17,7 @@ Note: you can sort by clicking the column, especially the first column which pro
Display all breakpoints in a list filtered by a tag using button [[Image:breakpoints-list-filter-button]]
[[Image:breakpoints-list-filter]]
-{{seealso| '''See Also'''
+{{seealso|
[[Breakpoint commands|Breakpoints commands]]
[[Breakpoint information command|Breakpoint information command]]
}}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-menu.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-menu.wiki
index ff64f743..62f739f1 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-menu.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/breakpoints/breakpoint-menu.wiki
@@ -14,7 +14,7 @@ The condition is a Boolean expression that follows the same rule as the expressi
{{warning|'''Caution''': if you enter an expression that is not supported or which raises an error during evaluation, by default the condition is considered as True (then the debugger will stop) }}
-{{seealso| '''See Also'''
+{{seealso|
[[Breakpoint editing|Breakpoint menu]]
[[Breakpoint commands|Breakpoints commands]]
[[Breakpoint information command|Breakpoint information command]]
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/execute-one-line-time.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/execute-one-line-time.wiki
index df4d8cdd..b3dd7f84 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/execute-one-line-time.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/execute-one-line-time.wiki
@@ -7,7 +7,7 @@ If an application was stopped, it attempts to execute the instruction located on
It is accessible through the '''project''' toolbar ( [[Image:debug-step-over-icon]] ) or through the '''debug''' menu.
-{{seealso| '''See Also'''
+{{seealso|
[[Eiffel Debugger Execution: Introduction|Execution commands]]
[[Generating executables|Compiling in Workbench mode]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/pause-application.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/pause-application.wiki
index c1460268..6c0b001e 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/pause-application.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/pause-application.wiki
@@ -7,7 +7,7 @@ This gives access to dynamic information concerning the application, such as the
It is accessible through the '''project''' toolbar ( [[Image:debug-pause-icon]] ) or through the '''debug''' menu.
-{{seealso| '''See Also'''
+{{seealso|
[[Eiffel Debugger Execution: Introduction|Execution commands]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-and-stop-breakpoints.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-and-stop-breakpoints.wiki
index 09cbf068..9299ddc2 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-and-stop-breakpoints.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-and-stop-breakpoints.wiki
@@ -5,7 +5,7 @@ This command launches an application compiled in Work Bench mode. The applicatio
It is accessible through the '''project''' toolbar ( [[Image:debug-run-icon]] ) or through the '''debug''' menu.
-{{seealso| '''See Also'''
+{{seealso|
[[Eiffel Debugger Execution: Introduction|Execution commands]]
[[Generating executables|Compiling in Workbench mode]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-finalized-executable.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-finalized-executable.wiki
index d399bede..14838ec2 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-finalized-executable.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-finalized-executable.wiki
@@ -7,7 +7,7 @@ No debugging is possible with this command, but it lets you test the real speed
It is accessible through the '''project''' toolbar ( [[Image:debug-run-finalized-icon]] ) or through the '''project''' menu.
-{{seealso| '''See Also'''
+{{seealso|
[[Eiffel Debugger Execution: Introduction|Execution commands]]
[[Generating executables|Compiling in finalized mode]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-without-breakpoints.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-without-breakpoints.wiki
index 87950c94..91ac7e06 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-without-breakpoints.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/run-without-breakpoints.wiki
@@ -5,7 +5,7 @@ This command launches an application compiled in Workbench mode. The application
It is accessible through the '''project''' toolbar ( [[Image:debug-run-without-breakpoint-icon]] ) or through the '''debug''' menu.
-{{seealso| '''See Also'''
+{{seealso|
[[Eiffel Debugger Execution: Introduction|Execution commands]]
[[Generating executables|Compiling in Workbench mode]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/step-feature.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/step-feature.wiki
index 53a72e65..8827a4dc 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/step-feature.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/step-feature.wiki
@@ -7,7 +7,7 @@ If an application was stopped, it attempts to enter the feature located on the e
It is accessible through the '''project''' toolbar ( [[Image:debug-step-into-icon]] ) or through the '''debug''' menu.
-{{seealso| '''See Also'''
+{{seealso|
[[Eiffel Debugger Execution: Introduction|Execution commands]]
[[Generating executables|Compiling in Workbench mode]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/step-out-feature.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/step-out-feature.wiki
index 2545bef6..09774032 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/step-out-feature.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/step-out-feature.wiki
@@ -7,7 +7,7 @@ If an application was stopped, it attempts to exit the feature where the applica
It is accessible through the '''project''' toolbar ( [[Image:debug-step-out-icon]] ) or through the '''debug''' menu.
-{{seealso| '''See Also'''
+{{seealso|
[[Eiffel Debugger Execution: Introduction|Execution commands]]
[[Generating executables|Compiling in Workbench mode]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/stop-debugged-application.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/stop-debugged-application.wiki
index f1c310d6..93340ac9 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/stop-debugged-application.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/execution-commands/stop-debugged-application.wiki
@@ -5,7 +5,7 @@ This command kills the debugged application, if any. This stops the debugging se
It is accessible through the '''project''' toolbar ( [[Image:debug-stop-icon]] ) or through the '''debug''' menu.
-{{seealso| '''See Also'''
+{{seealso|
[[Eiffel Debugger Execution: Introduction|Execution commands]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/expression-evaluation/evaluation-tool-or-watch-tool.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/expression-evaluation/evaluation-tool-or-watch-tool.wiki
index 28a5e9e4..e3f675e7 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/expression-evaluation/evaluation-tool-or-watch-tool.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/expression-evaluation/evaluation-tool-or-watch-tool.wiki
@@ -11,9 +11,9 @@ In the screenshot, you can see various expressions, the 4th one, is a dropped ob
The 5th expression has an error, the icon is different, and the 'value' shows there is an error, double click on it for more details
-{{tip| '''Tip''': If the expression returns a non-Void (and non basic type) object, then the corresponding row in the list is pickable, and can be dropped for example in the Watch tool to evaluate expression on it, or even to keep the object over the steppings. }}
+{{tip|If the expression returns a non-Void (and non basic type) object, then the corresponding row in the list is pickable, and can be dropped for example in the Watch tool to evaluate expression on it, or even to keep the object over the steppings. }}
-{{tip| '''Tip''': holding the mouse pointer over the expression's cell will popup a tooltip with details on the pointed expression }}
+{{tip|holding the mouse pointer over the expression's cell will popup a tooltip with details on the pointed expression }}
On top of the list, four buttons can be found.
* the button [[Image:toolbar-dropdown-icon]] is used to create/close watch tools via a menu popup
@@ -35,7 +35,7 @@ The associated key shortcut is F2.
The associated key shortcut is Del.
* And the last two buttons are used to move up and down the expressions. You can also move the expressions up and down using [CONTROL] + [-] or [CONTROL] + [+].
-{{tip| '''Tip''': Dropping an object onto this list lets you define quickly an expression whose context is the dropped object. This avoids having to type object addresses manually.
+{{tip|Dropping an object onto this list lets you define quickly an expression whose context is the dropped object. This avoids having to type object addresses manually.
If you press the [Control] key during the dropping, you will add the dropped object as itself. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/object-tool/debug-output.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/object-tool/debug-output.wiki
index 113a56c1..dcd6c0cb 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/object-tool/debug-output.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/object-tool/debug-output.wiki
@@ -5,9 +5,9 @@ In both grids of the [[Objects tool: Introduction|object tool]] , objects are di
To do so, inherit from the class
DEBUG_OUTPUT in the classes that should let their objects display a string value, and implement the `debug_output' feature. At run-time, the debugger will automatically query the result of this feature on all objects that define it and display it in the object tool and the [[Expression evaluation|evaluation tool]] .
-{{sample| '''Sample''': The
NUMERIC class inherits from the
DEBUG_OUTPUT one so that it is possible to see the value of *_REF objects without expanding them. }}
+{{sample|The
NUMERIC class inherits from the
DEBUG_OUTPUT one so that it is possible to see the value of *_REF objects without expanding them. }}
-{{tip| '''Tip''': If an object has a long string output or an output with carriage returns, for instance, pick-and-drop it to the expanded display command [[Image:debugger-expand-info-icon]] in the object tool. }}
+{{tip|If an object has a long string output or an output with carriage returns, for instance, pick-and-drop it to the expanded display command [[Image:debugger-expand-info-icon]] in the object tool. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/object-tool/object-viewer-also-known-expanded-display.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/object-tool/object-viewer-also-known-expanded-display.wiki
index 60765f76..a8576e8b 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/object-tool/object-viewer-also-known-expanded-display.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/object-tool/object-viewer-also-known-expanded-display.wiki
@@ -11,7 +11,7 @@ Depending the nature of the dropped object, you can view it with several viewers
* '''Object browse''': browse the object, as you would do in objects or watch tools
* '''Object internal''': display a few internal data such as
class_name,
type_name,
dynamic_type,
field_count,
deep_physicial_size, and
physical_size
-{{note|Note that the "string display" viewer is available for object with a string representation, for instance object conformed to [[ref:/libraries/base/reference/string_8_chart]] or conform to [[ref:/libraries/base/reference/debug_output_chart]] (see [[Debug output|Debug Output]] )}}
+{{note|that the "string display" viewer is available for object with a string representation, for instance object conformed to [[ref:/libraries/base/reference/string_8_chart]] or conform to [[ref:/libraries/base/reference/debug_output_chart]] (see [[Debug output|Debug Output]] )}}
{{note|And the "XML display" is available for object eligible to "String display", and whose string representation has XML content. The viewer is display XML in a basic tree enabled grid.}}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/stack-overflow-prevention.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/stack-overflow-prevention.wiki
index 85095b39..9e1579d6 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/stack-overflow-prevention.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/debugger/stack-overflow-prevention.wiki
@@ -7,7 +7,7 @@ Accessible via the '''Debug/Overflow prevention...''' menu, this command makes i
By default a warning is issued when the debugged program reaches a stack depth of 1,000 elements.
-{{note| '''Note''': Once an application has stopped at the selected level, it will not stop again until its stack depth goes below the critical stack depth again. }}
+{{note|Once an application has stopped at the selected level, it will not stop again until its stack depth goes below the critical stack depth again. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/diagram-tool/notation.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/diagram-tool/notation.wiki
index a63df831..4c909524 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/diagram-tool/notation.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/diagram-tool/notation.wiki
@@ -25,7 +25,7 @@ The diagram tool uses the [http://bon-method.com BON] (Business Object Notation
[[Image:bon-class-root]]
-{{seealso| '''See also'''
+{{seealso|
[[Rename class|Changing class names]] }}
==Cluster==
@@ -33,7 +33,7 @@ The diagram tool uses the [http://bon-method.com BON] (Business Object Notation
A cluster is a collection of classes and sub-clusters. It is represented by a stippled, rounded rectangle. The cluster name is in a similar rectangle, by default located at the top of the cluster just outside of it. A cluster can be iconified, which means it is minimized to take up as less space as possible.
[[Image:bon-cluster-iconified]] [[Image:bon-cluster]]
-{{seealso| '''See also'''
+{{seealso|
[[Iconifying and restoring a cluster|Iconifying a cluster]] }}
==Inheritance links==
@@ -42,7 +42,7 @@ Inheritance between classes is represented by an arrow from a class to its paren
[[Image:bon-inheritance]]
-{{seealso| '''See also'''
+{{seealso|
[[Creating inheritance links|Creating inheritance links]] }}
==Client/supplier links==
@@ -51,7 +51,7 @@ Client relationships between classes are represented by an arrow with a double l
[[Image:bon-client]] [[Image:bon-agg-client]]
-{{seealso| '''See also'''
+{{seealso|
[[Creating client/supplier links|Creating client/supplier links]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-incoming/eiffel-scheme-syntax.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-incoming/eiffel-scheme-syntax.wiki
index a4805c9a..c30e8d1c 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-incoming/eiffel-scheme-syntax.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-incoming/eiffel-scheme-syntax.wiki
@@ -11,9 +11,9 @@
* <''classe''>, in the form of class=to_be_replaced, '''to_be_replaced''' is the name of the class.
* <''featuree''>, in the form of feature=to_be_replaced, '''to_be_replaced''' is the name of the feature.
-{{note| '''Note: '''All parts above are unordered. }}
+{{note|All parts above are unordered. }}
-{{seealso| '''See Also'''
+{{seealso|
[[EIS incoming Examples|Examples]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/index.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/index.wiki
index 0356cfbe..7e819f08 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/index.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/index.wiki
@@ -6,7 +6,7 @@
Annotations may be applicable to:
* An individual class or feature. In this case the annotation figures in the class text, as part of an Eiffel "note" clause ("indexing" is still supported, it depends on which syntax level users choose).
* A target, library or cluster. In this case the annotation figures in the associated ECF file; EiffelStudio provides support for entering it through a Information (EIS) Tool.
-{{seealso| '''See Also'''
+{{seealso|
[[Information Tool|Information Tool]] }}
@@ -24,7 +24,7 @@ The following example illustrates the basic form of an EIS note entry:
The label (Node_entry as called in the ECMA/ISO Eiffel Standard syntax) is '''EIS'''. '''EIS''' Note_value tells the Eiffel Information System that this Note_entry is of interest to EIS, as distinct from any other information that might be expressed through a Note_entry. The file name (src) includes '''$PROJ''', referring to a variable, defining the project location. The protocol is PDF. The '''nameddest''' property (name destination) is a specific property of PDF documents. The tag '''requirement''' indicating that this entry links the enclosing Eiffel class or feature with some parts of the requirement documents.
-{{seealso| '''See Also'''
+{{seealso|
[[Variable Definition|Variable Definition]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/information-tool/annotation-management.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/information-tool/annotation-management.wiki
index 8e33571d..bfe99471 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/information-tool/annotation-management.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/information-tool/annotation-management.wiki
@@ -2,7 +2,7 @@
[[Property:weight|1]]
[[Property:uuid|696457ef-ac1f-40c1-a0da-54900d9cccf8]]
Information Tool provides information management functions: adding, modifying and removing.
-{{note| '''Note: '''Annotation management is only available in lists coresponding to nodes rather than tag nodes - all tags and "Items without tag". }}
+{{note|Annotation management is only available in lists coresponding to nodes rather than tag nodes - all tags and "Items without tag". }}
==Adding==
@@ -13,7 +13,7 @@ For each kind of nodes in the information tree, related annotations are listed i
To modify an annotation, one can use Information Tool or do it by code.
* By Information Tool, a line in the annotation list should be selected, then click into columns and activate editing/choosing mode. Once the editing area/drop down list is deactivated, the modification is done and synchronized into code automatically.
* By code, one simply modifies code in the editor, or .ecf files in external editor (not recommented).
-{{seealso| '''See Also'''
+{{seealso|
[[EIS: Outgoing|Syntax for Annotations]] }}
@@ -21,7 +21,7 @@ To modify an annotation, one can use Information Tool or do it by code.
By pressing '''Delete''', or clicking the third button on the bottom toolbar deletes all selected annotations in the list. And corresponding code is synchronized.
-{{note| '''Note: '''Annotation list can be multi-selected. }}
+{{note|Annotation list can be multi-selected. }}
{{note| All means to manage annotations via the tool are inreversible, except that the location - class or feature - has been opened in the editor, thus undo can be achieved via the editor. Removing is prompted on user demands. The tag tree is automatically updated when annotations are added/modified/removed or through system sweeping. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/information-tool/variable-definition.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/information-tool/variable-definition.wiki
index 7245b780..884ceef3 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/information-tool/variable-definition.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/information-tool/variable-definition.wiki
@@ -12,7 +12,7 @@ EIS supports following types of variables which can be used in '''Source''' of a
** group_name
** target_name
-{{note|'''Note: '''This kind of variables can only be used in components that are enclosed in those the variable name refers to. For example, '''feature_name''' has no effect if used in a target component.}}
+{{note|This kind of variables can only be used in components that are enclosed in those the variable name refers to. For example, '''feature_name''' has no effect if used in a target component.}}
* Individual system or library preferences. This kind of variables are defined in .ecf files, can be accessed via Project Setting dialog.
{{note|System -> Target -> Advanced -> Variables}}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/automatic-completion/feature-call-auto-complete.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/automatic-completion/feature-call-auto-complete.wiki
index 059bc5f5..0baddc7a 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/automatic-completion/feature-call-auto-complete.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/automatic-completion/feature-call-auto-complete.wiki
@@ -11,13 +11,13 @@ To complete your code with the selected item, press "Enter" or "Ctrl+Space".
To cancel the auto-complete, press "Esc" at any time.
-{{tip| '''Tips''': }}
+{{tip|s''': }}
* If the selected feature is a query, you can call the auto-complete again right after the previous completion. There is no need to type a dot.
* You can call the auto-complete without an identifier. The auto-complete window will then show the features of the current class.
* The keyboard shortcut for automatic completion can be changed in the [[Keyboard shortcuts preferences|editor preferences]] .
* Typing a non-alphanumeric character in the completion window automatically closes it. You can therefore type '.', ' ' or '(' to close the completion window and start typing the next token straight away.
-{{note| '''Notes''': }}
+{{note|s''': }}
* Only identifiers that were already defined when the class was compiled for the last time can be completed, except for local entity names that can always be completed.
* Only compiled features will appear in the auto-complete window.
* By default, features from class ANY will be ignored by the auto-complete window. This can be changed in the [[General Editor Preferences|editor preferences]] .
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/automatic-completion/syntax-auto-complete.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/automatic-completion/syntax-auto-complete.wiki
index 95de92f8..47192cbb 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/automatic-completion/syntax-auto-complete.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/automatic-completion/syntax-auto-complete.wiki
@@ -61,7 +61,7 @@ The editor can complete syntactic structures or part of them. The auto-complete
The way these reserved words are completed is fully [[Syntax automatic completion preferences|customizable]] .
-{{seealso| '''See Also'''
+{{seealso|
To see how the editor completes by default and how it can be changed, please read the following pages: [[Syntax automatic completion preferences|Syntax auto-complete preferences]]
}}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/cursor-moves.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/cursor-moves.wiki
index c07b83f0..5ccf9f6c 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/cursor-moves.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/cursor-moves.wiki
@@ -8,7 +8,7 @@ If you choose to use the mouse, just click in the text where you want the cursor
The keys that you may use to move the cursor in EiffelStudio editor are "Home", "End", "Page up", "Page Down" and the four arrows. Pressing "Home" will make the cursor go to the beginning of the line. Pressing "End" will move the cursor to the end of the line. You can use "Page Up" to move the cursor one page closer to the beginning of the text. Pressing "Page down" will position the cursor one page further.
Left and Right arrows can be used to move respectively to the character on the left or on the right of current position. Up and Down arrows allow you to move the cursor to the previous and next lines.
-{{tip| '''Tip''': By maintaining "Ctrl" pressed as you use Left and Right arrows, you will move the cursor to the next or previous word instead of the next or previous character. }}
+{{tip|By maintaining "Ctrl" pressed as you use Left and Right arrows, you will move the cursor to the next or previous word instead of the next or previous character. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/comment-and-uncomment-lines.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/comment-and-uncomment-lines.wiki
index 140a36a1..e1843c83 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/comment-and-uncomment-lines.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/comment-and-uncomment-lines.wiki
@@ -10,7 +10,7 @@ The "Uncomment" command corresponds to the '''Uncomment''' entry in the '''Advan
-{{note| '''Note''': If there is no selection, these commands will be applied to the current line. }}
+{{note|If there is no selection, these commands will be applied to the current line. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/embed-lines-if-thenend-or-debugend.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/embed-lines-if-thenend-or-debugend.wiki
index 1f414d2d..5209ef1a 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/embed-lines-if-thenend-or-debugend.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/embed-lines-if-thenend-or-debugend.wiki
@@ -7,7 +7,7 @@ EiffelStudio editor offers the possibility to embed several lines in "if then...
* The first command corresponds to the '''Embed in if''' entry in the '''Advanced''' submenu of the [[Edit menu commands]] [[Edit menu commands| Menu]] . It may be called by using the keyboard shortcut "Ctrl+I" too. Its action is to insert a line with "if then" before the [[Selection|selected]] lines and a line with "end" after those lines. The lines will be indented and the cursor positioned between "if" and "then".
* The second command corresponds to the '''Embed in debug''' entry in the '''Advanced''' submenu of the [[Edit menu commands]] [[Edit menu commands| Menu]] . It may be called by using the keyboard shortcut "Ctrl+D" too. Its action is to insert a line with "debug" before the [[Selection|selected]] lines and a line with "end" after those lines. The lines will be indented and the cursor positioned after "debug" and "then".
-{{note| '''Note''': If there is no selection, these commands will be applied to the current line. }}
+{{note|If there is no selection, these commands will be applied to the current line. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/indent-and-unindent-selection.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/indent-and-unindent-selection.wiki
index 730bd209..933f1b9f 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/indent-and-unindent-selection.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/operations-text-blocks/indent-and-unindent-selection.wiki
@@ -11,7 +11,7 @@ The "Unindent" command corresponds to the '''Unindent selection''' entry in the
-{{note| '''Note''': If there is no selection, you may still use the unindent shortcut "Shift+Tab". The command will be applied to the current line.
+{{note|If there is no selection, you may still use the unindent shortcut "Shift+Tab". The command will be applied to the current line.
}}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/search-functionality.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/search-functionality.wiki
index ef4d07ef..2d6ab459 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/search-functionality.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/search-functionality.wiki
@@ -19,7 +19,7 @@ Search the previous occurrence of the current selected pattern.
To do so, press "Ctrl+Shift+F3". You can change this key binding in [[Keyboard shortcuts preferences|the preferences]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Search tool|Search tool]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/selection.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/selection.wiki
index 1a9dbf04..ad9b578c 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/selection.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/selection.wiki
@@ -5,7 +5,7 @@ In EiffelStudio editor, you can select text by using either the mouse or the key
To select a text zone with the keyboard, [[Cursor moves|move the cursor]] to one end of the zone. Then press "Shift" and maintain the key pressed until you moved the cursor to the other end of the zone. The selected zone will appear in reverse video. If you want to select the entire text, press "Ctrl" and "A".
-{{tip| '''Tip''': You can combine "Ctrl" and "Shift" when using Left and Right arrows to select text word by word }}
+{{tip|You can combine "Ctrl" and "Shift" when using Left and Right arrows to select text word by word }}
If you choose to use the mouse, first [[Cursor moves|position the cursor]] to one end of the text zone you want to select, and click there without releasing the mouse button. Then move the mouse pointer to the other end of the zone and release the button. The selected text is shown in reverse video. If the other end of the zone is not visible, move the mouse pointer out of the edition area as you select text in the direction where the end is. EiffelStudio Editor will start scrolling automatically and will stop as soon as the mouse pointer enters the edition area again.
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/pick-and-drop-mechanism.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/pick-and-drop-mechanism.wiki
index d856fb5a..767d7bc9 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/pick-and-drop-mechanism.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/pick-and-drop-mechanism.wiki
@@ -13,7 +13,7 @@ Right-clicking when the pebble is crossed will only stop the pick-and-drop becau
* If, for any reason, you change your mind, you can cancel the pick-and-drop by left-clicking anywhere or by pressing the Escape key.
-{{seealso| '''See Also'''
+{{seealso|
[[Pick-and-drop shortcut|Pick-and-drop shortcut]]
}}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/pick-and-drop-shortcut.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/pick-and-drop-shortcut.wiki
index 2030f329..85aae403 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/pick-and-drop-shortcut.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/pick-and-drop-shortcut.wiki
@@ -3,9 +3,9 @@
[[Property:uuid|2cb70fcf-913c-0b74-d2a9-5928caa5904a]]
In the [[EiffelStudio Editor Introduction|editor]] and the [[EiffelStudio window overview|context tool]] , pressing the '''control''' key while right-clicking on a development object opens a new development window which is centered on the clicked object.
-{{tip| '''Tip''': The effect of control-picking is now configurable in the [[Preferences Reference|preferences]] . }}
+{{tip|The effect of control-picking is now configurable in the [[Preferences Reference|preferences]] . }}
-{{seealso| '''See Also'''
+{{seealso|
[[Pick-and-drop mechanism|Pick-and-drop mechanism]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/toolbar-customization.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/toolbar-customization.wiki
index 6e5c4c30..e6afcf05 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/toolbar-customization.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-interface-mechanisms/toolbar-customization.wiki
@@ -14,13 +14,13 @@ To remove an icon, click on it in the right list and click on '''<- Remove'''.
The order of the icons in the right list is the same as in the toolbar. If you want to move an icon in the list, select it and use '''Up''' and '''Down''' buttons. '''Up''' will move it to the top, i.e. to the left of the toolbar. '''Down''' will move it in the opposite direction.
-{{tip| '''Tip''': You can also pick-and-drop icons to organize them. }}
+{{tip|You can also pick-and-drop icons to organize them. }}
Lastly, some icons can be displayed with an explanatory text. A menu at the bottom of the window will allow you to choose if the text should be displayed. The tables below present the list of these icons for both toolbars and what they look like with and without text.
Once you made the changes you wanted, validate them by clicking on '''OK'''. You can also go back to the initial toolbar layout by clicking on '''C ancel'''.
-{{seealso| '''See Also'''
+{{seealso|
[[Main toolbars|Toolbars Reference]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-key-shortcuts.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-key-shortcuts.wiki
index 1614c273..cb1fdbd4 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-key-shortcuts.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-key-shortcuts.wiki
@@ -128,7 +128,7 @@ This shortcut may be customized.
|}
-{{note| '''Note''': These shortcuts are not available everywhere. All operations that do not imply changes in the text are available both in the editor and in the class and feature tabs of the context tool. Other operations are available only in the editor. }}
+{{note|These shortcuts are not available everywhere. All operations that do not imply changes in the text are available both in the editor and in the class and feature tabs of the context tool. Other operations are available only in the editor. }}
==Compiler==
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-window-overview.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-window-overview.wiki
index ab1f1a15..a5f2614c 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-window-overview.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/eiffelstudio-window-overview.wiki
@@ -60,7 +60,7 @@ The context tool, located in the right panel, is a major part of EiffelStudio. I
By default, the context tool is unlinked from the rest of the window, which means all left tools refer to the object that is in the editor and the main toolbar, while the context tool (and the debug tools if they are present) displays information concerning a different object. It is possible to link the context tool, so that the whole development window displays information relative to the same development object.
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelStudio: A Guided Tour|EiffelStudio Guided Tour]]
[[Browsing tools: Introduction|Browsing tools]]
[[Main toolbars|Toolbar customization]]
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/main-toolbars.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/main-toolbars.wiki
index d299c968..c3348438 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/main-toolbars.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-general-interface-description/main-toolbars.wiki
@@ -9,7 +9,7 @@ You can hide toolbars (or the address bar) by unselecting them in the '''Toolbar
In the standard toolbar, you will find buttons to manage [[Browsing tools: Introduction|tools]] and windows or that are related to the [[EiffelStudio Editor Introduction|editor]] .
-{{note| '''Note''': For both toolbars, it is possible to choose which buttons are displayed and which ones are not. See the [[Toolbar customization|Toolbars customization page]] for more information. }}
+{{note|For both toolbars, it is possible to choose which buttons are displayed and which ones are not. See the [[Toolbar customization|Toolbars customization page]] for more information. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preference-window-overview.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preference-window-overview.wiki
index 78c9ad28..f486f67c 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preference-window-overview.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preference-window-overview.wiki
@@ -13,10 +13,10 @@ There are several kinds of preferences:
* Shortcut preferences : edit the value cell, and press the wanted shortcuts..
* Other preferences : They will be modified by typing their value directly into an editable text field.
If there is no message stating you need to restart EiffelStudio, changes will be taken into account immediately.
-{{tip| '''Tip''': below the table, you will find a text field with the internal name of the preference (for instance: ''editor.eiffel.auto-complete_...''). }}
+{{tip|below the table, you will find a text field with the internal name of the preference (for instance: ''editor.eiffel.auto-complete_...''). }}
-{{tip| '''Tip''': you can export preferences to xml file, and import from xml file, this can be convenient when reinstalling EiffelStudio). }}
+{{tip|you can export preferences to xml file, and import from xml file, this can be convenient when reinstalling EiffelStudio). }}
{{warning| '''Caution''': You can restore preferences default values by clicking on the "Restore Default" button. ALL preferences will be reset. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/editor-preferences/eiffel-editor-preferences/syntax-automatic-completion-preferences/default-values-keyword-completion-preferences.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/editor-preferences/eiffel-editor-preferences/syntax-automatic-completion-preferences/default-values-keyword-completion-preferences.wiki
index 846d96a2..8db00f99 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/editor-preferences/eiffel-editor-preferences/syntax-automatic-completion-preferences/default-values-keyword-completion-preferences.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/editor-preferences/eiffel-editor-preferences/syntax-automatic-completion-preferences/default-values-keyword-completion-preferences.wiki
@@ -500,7 +500,7 @@ Default value for [[Keywords automatic completion preferences|"Customized autoco
-{{seealso| '''See Also'''
+{{seealso|
[[Keywords automatic completion preferences|Keywords automatic completion preferences]]
[[Keyword completion customization|Keyword completion customization]]
}}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/editor-preferences/eiffel-editor-preferences/syntax-automatic-completion-preferences/keyword-completion-customization.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/editor-preferences/eiffel-editor-preferences/syntax-automatic-completion-preferences/keyword-completion-customization.wiki
index 8d1c5b04..4a9f3ae5 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/editor-preferences/eiffel-editor-preferences/syntax-automatic-completion-preferences/keyword-completion-customization.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/editor-preferences/eiffel-editor-preferences/syntax-automatic-completion-preferences/keyword-completion-customization.wiki
@@ -66,10 +66,10 @@ The four ''%B'' will remove ''end'' plus one character before ''end'' (the tabul
''$indent$%B$cursor$'' means that the cursor will be moved to the end of the line where one less blank space than before the original ''end'' will have been inserted.
-{{note| '''Note''': EiffelStudio editor can insert spaces instead of tabulation when you use special character ''%T''. This is set in [[General Editor Preferences|another section of the preferences]] .
+{{note|EiffelStudio editor can insert spaces instead of tabulation when you use special character ''%T''. This is set in [[General Editor Preferences|another section of the preferences]] .
}}
-{{seealso| '''See Also'''
+{{seealso|
[[Keywords automatic completion preferences|Keywords automatic completion preferences]]
[[Default values for keyword completion preferences|Default values for keyword completion preferences]]
}}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/eiffelstudio-tools-preferences/context-tools.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/eiffelstudio-tools-preferences/context-tools.wiki
index 086b8354..7647ba89 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/eiffelstudio-tools-preferences/context-tools.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/eiffelstudio-tools-preferences/context-tools.wiki
@@ -102,7 +102,7 @@ Feature views indices:
|}
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelStudio Tools Preferences|Preferences for other tools]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/eiffelstudio-tools-preferences/eiffelstudio-diagram-tool-preferences.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/eiffelstudio-tools-preferences/eiffelstudio-diagram-tool-preferences.wiki
index 928772d4..0326ee7d 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/eiffelstudio-tools-preferences/eiffelstudio-diagram-tool-preferences.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-preferences/preferences-reference/eiffelstudio-tools-preferences/eiffelstudio-diagram-tool-preferences.wiki
@@ -167,7 +167,7 @@ This category gathers the preferences related to the EiffelStudio BON Diagram to
| Color for UML inheritance links.
|}
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelStudio Tools Preferences|Preferences for other tools]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-project-settings-window/general-target-options/advanced-options/index.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-project-settings-window/general-target-options/advanced-options/index.wiki
index 1a2d533c..c3890370 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-project-settings-window/general-target-options/advanced-options/index.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-project-settings-window/general-target-options/advanced-options/index.wiki
@@ -9,7 +9,7 @@
* Dead Code Removal: should unused code be removed? (C code generation mode only)
* Dynamic Runtime: makes the generated executable use a shared library version of the runtime on both Windows (DLL) and Unix platforms (.so) that supports shared libraries.(C code generation mode only)
-{{note| '''Note''': On Windows, the dynamic run-time is available only if you compile with the Microsoft Visual compiler. }}
+{{note|On Windows, the dynamic run-time is available only if you compile with the Microsoft Visual compiler. }}
* Enforce unique class names: enforce all class names to be system wide unique?
* Exception Trace: makes it possible to see a complete exception trace in a finalized application. Because it is adding some code to remember where the application was during the crash it can slow down the performance of your application by a factor of 5% to 30% depending of your platform. (C code generation mode only)
* Inlining, Inlining Size: enables inlining on Eiffel features that can be inlined, i.e. whose size is less or equal to the specified size in the combo box. The size value given in parameter corresponds to the number of instructions as seen by the Eiffel compiler (for example a := b.f corresponds to 2 instructions). The inlining is very powerful since it can inline a function in all your Eiffel code, without scope limitation as found in C or C++ compilers. (C code generation mode only)
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/ancestors.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/ancestors.wiki
index 4dd41840..95c2e36b 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/ancestors.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/ancestors.wiki
@@ -4,7 +4,7 @@
The ancestors view [[Image:class-ancestors-icon]] displays all the classes from which the current class inherits, directly or not, using a tree-like indented layout.
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Descendants|Descendants]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/attributes.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/attributes.wiki
index fcfc7156..fc98630e 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/attributes.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/attributes.wiki
@@ -4,7 +4,7 @@
The attributes view [[Image:class-features-attribute-icon]] displays all the attributes of the current class, including inherited attributes.
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Routines|Routines]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/class-formatters-basic-text-view.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/class-formatters-basic-text-view.wiki
index ed549c0e..69e49631 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/class-formatters-basic-text-view.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/class-formatters-basic-text-view.wiki
@@ -9,7 +9,7 @@ In this view, most of the development objects are [[Pick-and-drop mechanism|clic
'''Note''': The generated text is not editable, but it is compilable. This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View.
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelStudio Editor|Editor]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/class-formatters-flat-view.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/class-formatters-flat-view.wiki
index 9cb94973..3f4919b5 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/class-formatters-flat-view.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/class-formatters-flat-view.wiki
@@ -5,9 +5,9 @@ The flat view [[Image:view-flat-icon]] displays all the features for the curren
{{warning| '''Caution''': For classes with many [[Ancestors|ancestors]] , computation of the flat view may require a few seconds. }}
-{{note| '''Note''': This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View. }}
+{{note|This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View. }}
-{{seealso| '''See Also'''
+{{seealso|
[[Flat Contract view|Flat Contract view]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/clickable-view.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/clickable-view.wiki
index 2aadee46..d39c04c3 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/clickable-view.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/clickable-view.wiki
@@ -3,7 +3,7 @@
[[Property:uuid|8ddd0d2a-d4db-b0b6-8ee1-63e205a53dcc]]
The clickable view [[Image:view-clickable-icon]] allows to [[Pick-and-drop mechanism|pick]] every class or feature name in the class text and is available either through the [[EiffelStudio Editor|editor]] or through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
-{{note| '''Note''': This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View. }}
+{{note|This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/clients.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/clients.wiki
index 9f222edc..c3f7fbe8 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/clients.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/clients.wiki
@@ -4,7 +4,7 @@
The clients view [[Image:class-clients-icon]] displays all the classes which are using features of the current class, and thus rely on its [[Flat Contract view|interface]] .
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Suppliers|Suppliers]]
[[Callers|Feature callers]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/contract-view.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/contract-view.wiki
index 5cfaf39b..a768bd1a 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/contract-view.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/contract-view.wiki
@@ -3,7 +3,7 @@
[[Property:uuid|e8bbc475-d7f8-baa6-aba8-021c0e05c4b6]]
The contract view [[Image:view-contracts-icon]] displays the contracts of all written-in features of the current class. It is available either through the [[EiffelStudio Editor|editor]] or through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Flat Contract view|Flat contract view]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/descendants.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/descendants.wiki
index 97af0fe2..4276be78 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/descendants.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/descendants.wiki
@@ -4,7 +4,7 @@
The descendants view [[Image:class-descendents-icon]] displays all the classes which inherit from the current class,directly or not, using a tree-like indented layout.
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Ancestors|Ancestors]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/flat-contract-view.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/flat-contract-view.wiki
index 8647e425..7f66490f 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/flat-contract-view.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/flat-contract-view.wiki
@@ -5,7 +5,7 @@ The Flat Contract view [[Image:view-flat-contracts-icon]] displays the contract
{{warning| '''Caution''': For classes with many [[Ancestors|ancestors]] , computation of the Flat Contract view may require a few seconds. }}
-{{seealso| '''See Also'''
+{{seealso|
[[Class formatters: Flat view|Flat view]]
[[Contract view|Contract view]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/routines.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/routines.wiki
index 0ebdb36c..547651cd 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/routines.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/routines.wiki
@@ -4,7 +4,7 @@
The routines view [[Image:class-features-routine-icon]] displays all the routine signatures of the current class, including inherited routines.
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Attributes|Attributes]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/suppliers.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/suppliers.wiki
index 653118c3..782999d1 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/suppliers.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/class-views/suppliers.wiki
@@ -4,7 +4,7 @@
The suppliers view [[Image:class-supliers-icon]] displays all the classes from which the current class is calling features.
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Clients|Clients]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-ancestor-versions.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-ancestor-versions.wiki
index f68c84f7..cb08a7c6 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-ancestor-versions.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-ancestor-versions.wiki
@@ -4,7 +4,7 @@
[[Property:uuid|ca7f840d-30fb-c1cb-8f2f-6b45aa244f95]]
The ancestor view [[Image:feature-ancestors-icon]] displays all the features which the current feature is redefining.
-{{seealso| '''See Also'''
+{{seealso|
[[Descendant versions|Descendant versions]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-basic-text-view.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-basic-text-view.wiki
index 8d65aef2..2987875a 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-basic-text-view.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-basic-text-view.wiki
@@ -6,7 +6,7 @@ It does not work with [[Breakpoints|breakpoints]] ; in order to do this the [[Fe
'''Note''': This view is not available to .NET features which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no feature implementation to display. The feature interface may be viewed, in a clickable format using the Flat View.
-{{seealso| '''See Also'''
+{{seealso|
[[Class formatters: Basic text view|Class basic text view]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-callers.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-callers.wiki
index 6369c874..141ea675 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-callers.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-callers.wiki
@@ -4,7 +4,7 @@
[[Property:uuid|63b7a88c-86ff-7aef-bf31-05d0ed850e4e]]
The callers view [[Image:feature-callers-icon]] display all the features which are calling the current feature. It is possible to choose in the preferences if callers of the descendants should be displayed too (they are by default).
-{{seealso| '''See Also'''
+{{seealso|
[[Clients|Class clients view]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-descendant-versions.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-descendant-versions.wiki
index 3423477f..bd67965c 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-descendant-versions.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-descendant-versions.wiki
@@ -4,7 +4,7 @@
[[Property:uuid|c232a74a-7264-c8e1-4613-a65d75302602]]
The descendant view [[Image:feature-descendents-icon]] displays all the features that redefine the current feature.
-{{seealso| '''See Also'''
+{{seealso|
[[Ancestor versions|Ancestor versions]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-flat-view.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-flat-view.wiki
index 37cd2615..8693e4ca 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-flat-view.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-flat-view.wiki
@@ -3,7 +3,7 @@
[[Property:uuid|b325d97c-772d-8207-a901-a401c6a61376]]
The clickable view [[Image:view-clickable-feature-icon]] displays the feature body as it is seen at run-time (according to ancestor versions, if any). This is why it is possible to add or remove [[Breakpoints|breakpoints]] in this view.
-{{seealso| '''See Also'''
+{{seealso|
[[Class formatters: Flat view|Class flat view]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-homonyms.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-homonyms.wiki
index 20848013..19bc82b0 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-homonyms.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-homonyms.wiki
@@ -6,7 +6,7 @@ The homonyms view [[Image:feature-homonyms-icon]] displays all the features in
{{warning| '''Caution''': This operation may take a long time if the system has a lot of classes. }}
-{{seealso| '''See Also'''
+{{seealso|
[[Implementers|Implementers]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-implementers.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-implementers.wiki
index 58553f24..3ccd5bfd 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-implementers.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/formatted-information-about-compiled-classes-and-features/feature-views/feature-formatters-implementers.wiki
@@ -4,7 +4,7 @@
[[Property:uuid|4032bef0-39e5-5fa6-0ffe-156392c0234e]]
The implementers view [[Image:feature-implementers-icon]] displays all the different versions of the current feature by exploring the [[Ancestor versions|ancestor versions]] and the [[Descendant versions|descendant versions]] , and selecting among those the ones which are not inherited.
-{{seealso| '''See Also'''
+{{seealso|
[[Ancestor versions|Ancestor versions]]
[[Descendant versions|Descendant versions]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/domains.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/domains.wiki
index 311e80fa..1bbdbcd7 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/domains.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/domains.wiki
@@ -25,7 +25,7 @@ After running the metric, you should see the following result in the Detailed Re
[[Image:domain-example2|Metric detailed result]]
-{{note|Note: an element can appear more than one time in a domain, but the detailed result list show only distinct items, so it is possible that the calculated metric value is not equal to the number of items in the detailed result list.}}
+{{note|an element can appear more than one time in a domain, but the detailed result list show only distinct items, so it is possible that the calculated metric value is not equal to the number of items in the detailed result list.}}
A domain can be used as an argument of a relation criterion, see the following example:
@@ -52,10 +52,10 @@ And when this metric is calculated over input domain {
APPLICATION
+{{seealso|
[[Units|Units]]
[[Scopes|Scopes]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/elementary-and-composite-metrics.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/elementary-and-composite-metrics.wiki
index df250a1f..324ca7f2 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/elementary-and-composite-metrics.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/elementary-and-composite-metrics.wiki
@@ -25,7 +25,7 @@ By convention, this definition treats as process metric as a composite metric in
The classification introduced for metrics extends to measures, so that we may talk about an elementary product measure, a composite process measure and so on.
-{{seealso| '''See Also'''
+{{seealso|
[[Attributes, metrics and measures|Metrics]]
[[Scopes|Scopes]]
[[Domains|Domains]]
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/metric-framework-and-theory.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/metric-framework-and-theory.wiki
index 3ff6a1af..09667e48 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/metric-framework-and-theory.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/metric-framework-and-theory.wiki
@@ -18,7 +18,7 @@ This note does not introduce a metric theory, but defines a metric framework by
-{{seealso| '''See Also'''
+{{seealso|
[[Attributes, metrics and measures|Attributes, metrics and measures]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/raw-metrics-and-selection-criteria.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/raw-metrics-and-selection-criteria.wiki
index 178ea361..d5d49bd5 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/raw-metrics-and-selection-criteria.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/raw-metrics-and-selection-criteria.wiki
@@ -37,7 +37,7 @@ This criterion independence principle is not absolute, however, and in some case
A metric is either elementary or composite. An elementary metric is either a raw metric, such as "number of features", or a derived metric obtained from slicing a raw metric by selection criteria. Composite metrics are obtained from existing metrics (elementary, or previously defined composite metrics) by applying some mathematical formula.
-{{seealso| '''See Also'''
+{{seealso|
[[Elementary and composite metrics|Elementary metrics]]
[[Selection Criteria|Selection Criteria]]
[[Criterion References|Selection criterion reference]]
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/selection-criteria.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/selection-criteria.wiki
index ccd9030d..94520cae 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/selection-criteria.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/metrics-tool/definitions/selection-criteria.wiki
@@ -111,7 +111,7 @@ There are three criterion connectors: and, or, not. They are self-explanatory. J
[[Image:selection-cri8|Relation criterion]]
-{{seealso| '''See Also'''
+{{seealso|
[[Domains|Domains]]
[[Criterion References|Selection criterion reference]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/argument-list.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/argument-list.wiki
index c81cdcc2..4fb89ccb 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/argument-list.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/argument-list.wiki
@@ -3,9 +3,9 @@
[[Property:uuid|f2d63c29-6be2-b3d9-a735-b18e08c5a678]]
For functions and procedures, you can build a formal argument list. You can do this by clicking on the '''New argument''' button as many times as you need arguments.
-{{note| '''Note''': Even though this dialog always shows parentheses, they are not generated if the list is empty (Eiffel's command-query separation (CQS) principle). }}
+{{note|Even though this dialog always shows parentheses, they are not generated if the list is empty (Eiffel's command-query separation (CQS) principle). }}
[[Image:feature-wizard-3-arguments]]
-{{note| '''Note''': If you add arguments to a routine, it is not possible anymore to select routine type '''once'''. }}
+{{note|If you add arguments to a routine, it is not possible anymore to select routine type '''once'''. }}
For every attribute you selected, enter a name in the text box and a type using the [[Type selection|type selection]] .
[[Image:feature-wizard-1-argument]]
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/feature-clauses.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/feature-clauses.wiki
index 9ad35d20..a6d192cb 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/feature-clauses.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/feature-clauses.wiki
@@ -6,7 +6,7 @@ The feature you create will be inserted in the feature clause you specified. If
The export status is the class the feature is accessible for. Usually, this is ANY for public features, or NONE for implementation features, but you can specify any class here.
[[Image:feature-wizard-export]]
-{{note| '''Note''': In the class text, you can export a feature to more than one class but (for simplicity) not with this dialog. }}
+{{note|In the class text, you can export a feature to more than one class but (for simplicity) not with this dialog. }}
==Feature clause names==
For feature clause names it is recommended that you pick one from the standard ones, but it is also possible to create a new one. If you have introduced a special feature clause name in your project, add it to the feature clause order list in the [[Preferences Reference|preferences]] and it will also appear in this dialog.
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/name-field.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/name-field.wiki
index 97debd05..4919f5f6 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/name-field.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/name-field.wiki
@@ -3,7 +3,7 @@
[[Property:uuid|850bd867-5cbf-34d0-f94c-97a75bfa244b]]
The feature name field is a text box that lets you enter a name for the feature. For help on how to choose the right name for a feature, see: [http://www.eiffel.com/doc/oosc/ Object-Oriented Software Construction, Second Edition] , paragraph 26.2.
-{{warning| '''Warning''': EiffelStudio performs no validation on the name you choose. For example if you type a space in it, it will generate the code, and detect a syntax error only when compiling. }}
+{{warning|EiffelStudio performs no validation on the name you choose. For example if you type a space in it, it will generate the code, and detect a syntax error only when compiling. }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/type-selection.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/type-selection.wiki
index 10a229de..0456418d 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/type-selection.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/dialogs/new-feature-dialog/new-feature-dialog-feature-properties-modification/type-selection.wiki
@@ -5,14 +5,14 @@ Whenever you need to give a type of something in the dialog, the type selection
[[Image:feature-wizard-typeselection]]
When you select a class that is in the system and has formal generic parameters, the type selection component lets you specify an actual generic parameter in another type selection.
[[Image:feature-wizard-generictype]]
-{{note| '''Note''': the window might grow in size because of the added component. }}
+{{note|the window might grow in size because of the added component. }}
Since the actual generic type selection is also a type selection, you can select another class with generic parameters and nest them as deep as you need.
[[Image:feature-wizard-generictyperec]]
You can also select the type TUPLE, which is a special class that can have zero or more generic parameters. When you select it, it has no parameters, but you can add one by clicking on the '''Add parameter''' button. Click it as often as the number of generic parameters that you need.
[[Image:feature-wizard-tupletype2]]
-{{warning| '''Warning''': if you need a very complex type, it is better not to use the dialog, as the window might grow bigger than your screen. After you completed the feature, edit it manually in the class text. }}
+{{warning|if you need a very complex type, it is better not to use the dialog, as the window might grow bigger than your screen. After you completed the feature, edit it manually in the class text. }}
The code generated for the selected type is quite straightforward, an example:
[[Image:feature-wizard-complextype]]
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-how-tos/how-set-profiler-configuration-file.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-how-tos/how-set-profiler-configuration-file.wiki
index 8f9c4c50..4dc8625e 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-how-tos/how-set-profiler-configuration-file.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-how-tos/how-set-profiler-configuration-file.wiki
@@ -43,7 +43,7 @@ As in Eiffel, -- introduces a comment, which has no effect on the specification.
-{{seealso| '''See Also'''
+{{seealso|
[[Select a Run-time information record to generate the Execution Profile|Select a Run-time information record to generate the Execution Profile]]
[[Profiling|How to profile a system]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/index.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/index.wiki
index 96711463..9e3be818 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/index.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/index.wiki
@@ -7,7 +7,7 @@
# [[Select the information you need and formulate your query|'''Final step''': Select the information you need and formulate your query.]]
# [[Profile query window|Profile query window]]
-{{seealso| '''See Also'''
+{{seealso|
[[Profiler wizard: Introduction|How the Profiler wizard works]]
[[Profiling|How to profile a system]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/profile-query-window.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/profile-query-window.wiki
index 0fb09d74..71e1f11a 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/profile-query-window.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/profile-query-window.wiki
@@ -13,11 +13,11 @@ To change the operator affecting an existing sub query, select it in either the
Click on the '''Save''' button to save the currently displayed results in a text file.
-{{tip| '''Tip''': To visualize the result in Microsoft Excel or any other spreadsheet, select the entire text (except the first three lines where the Execution Profile file is specified), copy it and then paste it into Excel. }}
+{{tip|To visualize the result in Microsoft Excel or any other spreadsheet, select the entire text (except the first three lines where the Execution Profile file is specified), copy it and then paste it into Excel. }}
[[Image:profiler-query-window]]
-{{seealso| '''See Also'''
+{{seealso|
[[Profiler wizard: Introduction|How the Profiler wizard works]]
[[Profiling|How to profile a system]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/reuse-or-generate-execution-profile.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/reuse-or-generate-execution-profile.wiki
index 291fb13a..177a95ac 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/reuse-or-generate-execution-profile.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/reuse-or-generate-execution-profile.wiki
@@ -5,12 +5,12 @@ The second screen of the wizard lets you reuse a previously generated ''Executio
The profiler wizard has detected that one or more ''Execution Profiles'' have already been generated for this system in this compilation mode. If you have executed your system after the generation of the existing profile, select '''Generate a profile from Run-time information record''' to create a new ''Execution Profile'' for the newly produced ''Run-time information record''.
-{{note| '''Note''': If you choose '''Generate a profile from Run-time information record''' the generated ''Execution Profile'' will be written into ''
/EIFGENa/target_name/W_CODE/profinfo.pfi'' if you have selected '''Workbench mode''' in the first step, or ''/EIFGENs/target_name/F_CODE/profinfo.pfi'' if you have selected '''Finalized mode'''. If a file with the same name already exists its content will be destroyed and replaced. }}
+{{note|If you choose '''Generate a profile from Run-time information record''' the generated ''Execution Profile'' will be written into ''/EIFGENa/target_name/W_CODE/profinfo.pfi'' if you have selected '''Workbench mode''' in the first step, or ''/EIFGENs/target_name/F_CODE/profinfo.pfi'' if you have selected '''Finalized mode'''. If a file with the same name already exists its content will be destroyed and replaced. }}
However, if you have not executed your system since the generation of the last ''Execution Profile'', there is no need to generate a new ''Execution Profile''. If you are in the latter case, select '''Use existing profile''' and choose the last ''Execution Profile'' you have generated.
-{{tip| '''Tip''': If you want to archive different ''Execution Profiles'' (to compare them for example), rename the ''profinfo.pfi'' file into a new name but keep the .pfi extension. The profiler wizard detects existing Execution Profiles by checking the file extensions. }}
+{{tip|If you want to archive different ''Execution Profiles'' (to compare them for example), rename the ''profinfo.pfi'' file into a new name but keep the .pfi extension. The profiler wizard detects existing Execution Profiles by checking the file extensions. }}
[[Image:profiler-wizard-second-state]]
@@ -18,7 +18,7 @@ However, if you have not executed your system since the generation of the last '
Clicking '''Next''' will lead you to the [[Select a Run-time information record to generate the Execution Profile|Third state]] if you have selected '''Generate a profile from Run-time information record'''. On the other hand if you have selected '''Use existing profile''' you will go to the [[Select the information you need and formulate your query|Final state]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Profiler wizard: Introduction|How the Profiler wizard works]]
[[Profiling|How to profile a system]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-compilation-mode.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-compilation-mode.wiki
index 1cd849d8..5bd4f1a9 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-compilation-mode.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-compilation-mode.wiki
@@ -11,7 +11,7 @@ If you have run a finalized system under the control of the profiler then select
Clicking '''Next''' will lead you to the [[Reuse or Generate an Execution Profile|Second state]] or to the [[Select a Run-time information record to generate the Execution Profile|Third state]] depending on whether an ''Execution Profile'' has already been generated for this compilation mode or not. If no ''Execution Profile'' has been generated so far (which happens the first time you execute this wizard for a specified project in a given compilation mode) you will go to the [[Select a Run-time information record to generate the Execution Profile|Third state]] , otherwise you will go to the [[Reuse or Generate an Execution Profile|Second state]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Profiler wizard: Introduction|How the profiler wizard works]] [[Profiling|How to profile a system]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-information-you-need-and-formulate-your-query.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-information-you-need-and-formulate-your-query.wiki
index 47376514..45b21e09 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-information-you-need-and-formulate-your-query.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-information-you-need-and-formulate-your-query.wiki
@@ -50,7 +50,7 @@ Each sub-query must have the following syntax 'attribute operator value' where:
Clicking '''Next''' will open the [[Profile query window|Profile query window]] and display the results of the formulated query.
-{{seealso| '''See Also'''
+{{seealso|
[[Profiler wizard: Introduction|How the Profiler wizard works]]
[[Profiling|How to profile a system]] }}
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-run-time-information-record-generate-execution-profile.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-run-time-information-record-generate-execution-profile.wiki
index e7d38893..761c8ead 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-run-time-information-record-generate-execution-profile.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/wizards-and-dialogs/profiler-wizard/profiler-wizard-guided-tour/select-run-time-information-record-generate-execution-profile.wiki
@@ -5,7 +5,7 @@ The third screen of the wizard lets you generate an ''Execution Profile'' from a
Then, in the combo box labeled '''Profiler used to produce the above record''', select the profiler that has been used to produce the ''Run-time information record'' you have entered. If the profiler used to execute the system does not appear in the combo box, you have to add it. See [[How to set up a Profiler Configuration File|How to set up a Profiler Configuration File]] for more details on how to do so.
-{{note| '''Note''': ''The Run-time information record'' has to be located in the ''EIFGENs/target_name/W_code'' directory of your project. }}
+{{note|The Run-time information record'' has to be located in the ''EIFGENs/target_name/W_code'' directory of your project. }}
[[Image:profiler-wizard-third-state]]
@@ -17,7 +17,7 @@ Clicking '''Next''' will lead you to the [[Select the information you need and f
[[Image:profiler-wizard-rtir-error-state]]
-{{seealso| '''See Also'''
+{{seealso|
[[Profiler wizard: Introduction|How the Profiler wizard works]]
[[Profiling|How to profile a system]]
[[How to set up a Profiler Configuration File|How to set up a Profiler Configuration File]] }}
diff --git a/documentation/current/method/eiffel-tutorial-et/et-other-mechanisms.wiki b/documentation/current/method/eiffel-tutorial-et/et-other-mechanisms.wiki
index 4d1163e2..a932ecd6 100644
--- a/documentation/current/method/eiffel-tutorial-et/et-other-mechanisms.wiki
+++ b/documentation/current/method/eiffel-tutorial-et/et-other-mechanisms.wiki
@@ -143,7 +143,7 @@ end
a.r (x)
-{{note|Note the recommended convention: extra indentation of the check part to separate it from the algorithm proper; and inclusion of a comment listing the rationale behind the developer's decision not to check explicitly for the precondition. }}
+{{note|the recommended convention: extra indentation of the check part to separate it from the algorithm proper; and inclusion of a comment listing the rationale behind the developer's decision not to check explicitly for the precondition. }}
In production mode with assertion monitoring turned off, this instruction will have no effect. But it will be precious for a maintainer of the software who is trying to figure out what it does, and in the process to reconstruct the original developer's reasoning. (The maintainer might of course be the same person as the developer, six months later.) And if the rationale is wrong somewhere, turning assertion checking on will immediately uncover the bug.
diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/accessing-com-component.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/accessing-com-component.wiki
index 361693a7..ddefd0fd 100644
--- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/accessing-com-component.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/accessing-com-component.wiki
@@ -17,11 +17,11 @@ The third tutorial describes how to access a COM component. It will build a clie
==First look at the generated code==
At the end of the processing the '''EiffelStudio''' button becomes enabled. Click on it. This will automatically start EiffelStudio with the generated project so you can more easily navigate through the created Eiffel classes.
-{{note| '''Note''': When accessing a COM component the EiffelCOM Wizard will generate a precompiled library which includes all the generated classes. This allows for easy browsing of the generated classes, however a precompilation project is read-only, so you need to start another EiffelStudio to reuse the generated classes. The interesting classes are all related to the coclass proxy STRING_MANIPULATOR_PROXY. The proxy is the Eiffel class that gives access to the component. Each feature on the proxy calls the corresponding interface function on the component. You can use the EiffelStudio opened by the wizard to browse through the generated classes and study the class hierarchy.}}
+{{note|When accessing a COM component the EiffelCOM Wizard will generate a precompiled library which includes all the generated classes. This allows for easy browsing of the generated classes, however a precompilation project is read-only, so you need to start another EiffelStudio to reuse the generated classes. The interesting classes are all related to the coclass proxy STRING_MANIPULATOR_PROXY. The proxy is the Eiffel class that gives access to the component. Each feature on the proxy calls the corresponding interface function on the component. You can use the EiffelStudio opened by the wizard to browse through the generated classes and study the class hierarchy.}}
==Implementing a client==
To implement a client of the StringManipulator component open a new EiffelStudio. Create the project in ''$ISE_EIFFEL\examples\com\wizard\string_manipulator\client'' using the ecf file found in that directory. Freeze and run the project. You are now accessing the previously built component and calling functions on its interfaces! The class MY_STRING_MANIPULATOR inherits from the generated STRING_MANIPULATOR_PROXY and redefines the feature ''replace_substring_user_precondition''. The generated interfaces include contracts for each exposed function. You can redefine the ''user_precondition'' features to implement your own preconditions.
-{{note| '''Note''': If a COM component should be added to an existing client, the generated ecf file can be added as a library. }}
+{{note|If a COM component should be added to an existing client, the generated ecf file can be added as a library. }}
==Contracts==
Contracts can be broken directly on the proxy in which case you will get a standard contract violation in the client. If contracts are broken on the server then the exception will be forwarded by the EiffelCOM runtime to the client. The feature replace_substring_user_precondition in MY_STRING_MANIPULATOR includes has some assertions.: Comment them out. Now the contract of the [[ref:libraries/base/reference/string_8_chart|replace_substring ]] feature is wrong and erroneous calls can be made. Quick melt the changes and run the client. Enter some invalid numbers in the fields used to call this feature. After you click '''Replace''' you will see an error message box warning you that a precondition was violated on the server side. This demonstrates contracts `over the wire'. The precondition was violated in the server; this exception was caught by the EiffelCOM runtime and sent back to the client.
diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-component-eiffel-project.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-component-eiffel-project.wiki
index c77e7ac4..252e7174 100644
--- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-component-eiffel-project.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-guided-tour/creating-new-component-eiffel-project.wiki
@@ -30,7 +30,7 @@ The generated Eiffel classes include:
* ECOM_STRING_REGISTRATION: This class contains the code required to register the component.
You do not need to modify or implement any classes. The wizard produces a ready-to-use component.
-{{tip| '''Tip''':
+{{tip|
In most Eiffel systems functionality is spread out throughout the system. No single class exposes the full functionality of the system and can serve as a Facade to the outside world. Running the wizard on any such class would not be practical. Before starting the wizard write an Eiffel class that acts as a Facade and forwards client calls to the appropriate subsystems. Enter the Facade class name into '''Name of Eiffel facade class''' field. The wizard generates an IDL file from this class. }}
{{seealso| '''See Also'''
diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/building-com-component.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/building-com-component.wiki
index 769858d4..5c9e85d9 100644
--- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/building-com-component.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/building-com-component.wiki
@@ -9,7 +9,7 @@ If the project consists of adding a COM interface to an existing Eiffel project
If the project uses a COM definition file (either an IDL file or a type library), the EiffelCOM Wizard generates empty features in the classes corresponding to the component's coclasses. The implementation can then be added into these empty features.
-{{warning| '''Warning''': Depending on the project settings, the EiffelCOM Wizard may overwrite the files containing the classes corresponding to the component's colasses if the project is re-generated thereby replacing the implemented features with empty ones. Make sure the destination folder is different from the folder where the classes have been implemented prior to re-generating the project. }}
+{{warning|Depending on the project settings, the EiffelCOM Wizard may overwrite the files containing the classes corresponding to the component's colasses if the project is re-generated thereby replacing the implemented features with empty ones. Make sure the destination folder is different from the folder where the classes have been implemented prior to re-generating the project. }}
Unlike the code generated to access an existing component, the code generated to implement a new COM component will differ for an in-process or an out-of-process component. The difference lies in the component activation code in the class ECOM__REGISTRATION. If the component is in-process then this class includes the four functions that need to be exported from an in-process COM component ( DllRegisterServer, DllUnregisterServer, DllGetClassObject, and DllCanUnloadNow). If the component is out-of-process then the registration class includes a feature initializing the component and its graphical user interface.
diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/how-eiffelcom-wizard-works.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/how-eiffelcom-wizard-works.wiki
index 99b28b58..12fc4f6b 100644
--- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/how-eiffelcom-wizard-works.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/eiffelcom-wizard-reference/how-eiffelcom-wizard-works.wiki
@@ -11,7 +11,7 @@ Depending on the project settings there are between 2 and 6 major steps involved
Optionally, EiffelStudio can be opened on the generated system by clicking the corresponding button after the system has been compiled.
-{{note| '''Note''': The EiffelStudio button will only be enabled if the Eiffel code was compiled. }}
+{{note|The EiffelStudio button will only be enabled if the Eiffel code was compiled. }}
{{seealso| '''See Also''': [[Generated Files|Generated Files]] , [[Class Hierarchy|Class Hierarchy]] , [[Eiffel Project Processing|Adding a COM Interface to an Eiffel Project]] , [[Reusing a COM Component|Accessing a COM Component]] , [[Building a COM Component|Building a COM Component]] , [[Wizards: Command Line Options|Command Line Options]] }}
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/eiffel-codedom-provider-manager.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/eiffel-codedom-provider-manager.wiki
index b2e1e467..eaebb75c 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/eiffel-codedom-provider-manager.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/eiffel-codedom-provider-manager.wiki
@@ -2,7 +2,7 @@
[[Property:weight|-1]]
[[Property:uuid|089e658f-4bd8-df8f-5647-0c176c00359b]]
The Eiffel Codedom Provider Manager allows to graphically configure the Eiffel CodeDom Provider. There can be multiple configurations, each of them being associated with at least one application.
-{{note| '''Note:''' The Eiffel for ASP.NET installation program will add a shortcut in the start menu to the Eiffel CodeDom Provider Manager. }}
+{{note|The Eiffel for ASP.NET installation program will add a shortcut in the start menu to the Eiffel CodeDom Provider Manager. }}
The main dialog of the Eiffel CodeDom Provider Manager is divided into two vertical panes. The left pane contains a list of available configurations while the right pane contains the settings corresponding to the currently selected configuration. Initially the only available configuration is the '''default''' configuration which applies to all applications. The configurable settings are listed below.
==General Settings==
* '''Fail on error''': Checking this box will force the Eiffel Codedom Provider to fail when an error occurs. By default the provider rescues the failure and logs an error but it might be easier for debugging to have the Eiffel CodeDom Provider stop and raise an exception.
@@ -12,12 +12,12 @@ The main dialog of the Eiffel CodeDom Provider Manager is divided into two verti
==Compiler Settings==
* '''Default root class''': In the event where the CodeDom tree does not define an entry point, there still needs to be a root class for the Eiffel system to compile properly. If there is an entry point defined in the Codedom tree then this setting is ignored.
* '''Precompile ace file''': This setting, if set, gives the path to the ACE file of the precompile that the CodeDom compiler should use when compiling systems with this configuration. The CodeDom compiler will first check whether the precompile for that ACE file already exists in the precompile cache (See Precompile cache below). If it finds one then it will check whether the ACE file was modified since the precompile was created. If there isn't a corresponding precompile or if the ACE file was modified then the CodeDom compiler will create a new precompile in the precompile cache using the specified ace file. It will then compile the system using the precompile in the cache corresponding to the specified ACE file.
-{{note| '''Note:''' If for any reason the precompilation fails then the CodeDom compiler will still compile the system but without using any precompile. }}
+{{note|If for any reason the precompilation fails then the CodeDom compiler will still compile the system but without using any precompile. }}
* '''Metadata cache''': Both the Eiffel CodeDom Provider and the Eiffel compiler require reading from and writing to an Eiffel Metadata Cache. These caches contain information about mapping the .NET types and members names to valid Eiffel identifiers. Because read and write access are required, the application that uses the CodeDom Provider must have write access rights to the Eiffel Metadata Cache folder.
-{{note| '''Note:''' The Eiffel for ASP.NET installation program will grant write access rights to the Eiffel Metadata Cache folder to the ASPNET user and IIS_WPG group if they exist. ASPNET is the default user account used by the ASP.NET process (aspnet_wp.exe) under Windows XP while IIS_WPG is the default user account used by the ASP.NET process (w3wp.exe) under Windows 2003 Server. }}
+{{note|The Eiffel for ASP.NET installation program will grant write access rights to the Eiffel Metadata Cache folder to the ASPNET user and IIS_WPG group if they exist. ASPNET is the default user account used by the ASP.NET process (aspnet_wp.exe) under Windows XP while IIS_WPG is the default user account used by the ASP.NET process (w3wp.exe) under Windows 2003 Server. }}
-{{warning| '''Warning:''' Changing the Eiffel Metadata Cache folder path will force the Eiffel CodeDom Provider to regenerate the cache content during the next code generation or compilation. This process can take a long time and in particular can take more time than the default timeout for an ASP.NET page. If the Eiffel CodeDom Provider is used together with ASP.NET and if the Eiffel Metadata Cache path has been modified, it is recommended to change the default timeout for the first ASP.NET page containing Eiffel code to be loaded (this can be done by setting the ''HttpServerUtility.ScriptTimeout'' property). }}
+{{warning|Changing the Eiffel Metadata Cache folder path will force the Eiffel CodeDom Provider to regenerate the cache content during the next code generation or compilation. This process can take a long time and in particular can take more time than the default timeout for an ASP.NET page. If the Eiffel CodeDom Provider is used together with ASP.NET and if the Eiffel Metadata Cache path has been modified, it is recommended to change the default timeout for the first ASP.NET page containing Eiffel code to be loaded (this can be done by setting the ''HttpServerUtility.ScriptTimeout'' property). }}
* '''Compiler metadata cache''': This cache is used by the Eiffel Codedom Provider Compiler to map .NET types and members names to valid Eiffel identifiers. Please consult '''Metadata cache''' for additional information (the same note and warning apply).
* '''Precompile cache''': If the configuration defines a precompile ace file then the Eiffel CodeDom Provider will create the precompile in the directory specified in this setting. Changing this value will force the Eiffel CodeDom Provider compiler to recreate the precompile in the new directory.
@@ -26,7 +26,7 @@ The main dialog of the Eiffel CodeDom Provider Manager is divided into two verti
This list associates .NET assemblies with the prefix that will be used for Eiffel class names corresponding to .NET types belonging to the assembly. For example the prefix for the assembly ''System.Xml.dll'' is ''XML_'', this means that the Eiffel class names of all the types in the assembly ''System.Xml.dll'' will all begin with ''XML_''. This is necessary because Eiffel doesn't have a notion of namespace. The default assembly prefixes cannot be modified but new assembly/prefix pairs can be added if necessary.
==Applications==
This last setting will only appear for configurations other than the default configuration. It lists the applications that will use the configuration when they load the Eiffel CodeDom Provider assembly. If an application is not listed in any configuration then it will use the default configuration.
-{{note| '''Note:''' For a change in an existing configuration to take effect, the process that uses the modified configuration must be restarted. }}
+{{note|For a change in an existing configuration to take effect, the process that uses the modified configuration must be restarted. }}
==New Configuration==
New configurations may be created by clicking the ''New'' button or the ''New'' entry in the ''File'' menu. The New Configuration dialog box asks for the name and the path of the configuration. It will create a file with the extension '''.ecd''' ('''E'''iffel '''C'''ode'''D'''om) with the specified name in the directory located at the specified path. Whenever one of the applications listed at the bottom of the New Configuration dialog loads the Eiffel CodeDom Provider, it will use this new configuration.
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/name-mapper.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/name-mapper.wiki
index 1cf70950..ce2276be 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/name-mapper.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-aspnet-tools-and-administration/name-mapper.wiki
@@ -3,9 +3,9 @@
[[Property:uuid|82691c82-50a5-ed7f-b138-90946d094dae]]
The Name Mapper utility allows retrieving the Eiffel identifier corresponding to a .NET type name or a .NET member name. There are only two input fields in the interface: the .NET type name should be entered in the first one while the .NET member name should be entered in the second one. Once a valid .NET type name is entered in the type name input field, the tool starts searching for the corresponding Eiffel identifier. When the Name Mapper finds the corresponding Eiffel identifier, it automatically fills the .NET member name input combo box with all the member names of the corresponding type. This means that the .NET member type name can be chosen from the combo box entries or typed in (if it's typed in then the tool will autocomplete the member name).
The assemblies the tool will look into for the .NET type whose name was given in the .NET type name input field are listed below the input fields. It is possible to add new assemblies to the list by clicking the ''Add'' button. Assemblies that were added this way can be removed by clicking the ''Remove'' button after selecting the assembly from the list.
-{{note| '''Note:''' Assemblies that are listed by default cannot be removed. }}
+{{note|Assemblies that are listed by default cannot be removed. }}
-{{note| '''Note:''' When adding an assembly and if the assembly has not been consumed (i.e. the XML names mapping files have not been generated in the Eiffel Metadata Cache) then the Name Mapper will consume the assembly, this may take a while. }}
+{{note|When adding an assembly and if the assembly has not been consumed (i.e. the XML names mapping files have not been generated in the Eiffel Metadata Cache) then the Name Mapper will consume the assembly, this may take a while. }}
{{seealso| '''See also:''' [[Names Mappings|Names Mapping]] }}
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/configuration.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/configuration.wiki
index 47748b89..804c6c96 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/configuration.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/configuration.wiki
@@ -4,7 +4,7 @@
The Eiffel Codedom Provider uses XML configuration files that define additional settings specific to Eiffel. Such settings include whether to fail on error, what events to log, where to log them etc... Each application can define its own configuration to be used when it loads the Eiffel CodeDom Provider. If an application is not associated with a configuration file then a default configuration is used.
The association between applications and configurations as well as the actual settings the configuration defines can be set in the [[Eiffel CodeDom Provider Manager|Eiffel CodeDom Provider Manager]] . Run ''ecdpman.exe'' to start the manager.
-{{note| '''Note:''' The Eiffel for ASP.NET installation program will add a shortcut in the start menu to the Eiffel CodeDom Provider Manager. }}
+{{note|The Eiffel for ASP.NET installation program will add a shortcut in the start menu to the Eiffel CodeDom Provider Manager. }}
{{seealso| '''See also:''' [[Eiffel CodeDom Provider Manager|Eiffel CodeDom Provider Manager]] , [[Logging|Logging]] , [[Required Permissions|Required permissions]] }}
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/eiffel-implementation.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/eiffel-implementation.wiki
index 30d2f61d..5a58bc07 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/eiffel-implementation.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/eiffel-implementation.wiki
@@ -4,15 +4,15 @@
There are a few topics specific to the implementation of the Eiffel CodeDom Provider that are worth mentioning.
==Multiple Classes File==
The Eiffel compiler expects that there is only one class per source file (file with extension '''.e'''), however the CodeDom interface specification requires multiple classes to be generated in the same file (actually in the same ''stream''). The Eiffel CodeDom Provider code generator generates files with the extension '''.es''' which may contain multiple class definitions. Each class definition is separated with a special marker that the Eiffel CodeDom Provider compiler will parse to create multiple '''.e''' files - each containing a single class definition - prior to calling the command line Eiffel compiler.
-{{note| '''Note:''' Only the Eiffel CodeDom Provider compiler knows how to handle '''.es''' files. The standard Eiffel compilers can only parse '''.e''' files. }}
+{{note|Only the Eiffel CodeDom Provider compiler knows how to handle '''.es''' files. The standard Eiffel compilers can only parse '''.e''' files. }}
Eiffel for ASP.NET includes the [[eSplitter|eSplitter]] utility which can 'split' Eiffel multi-class files ('''.es''' files) into single class files ('''.e''' files).
==Inheritance Snippet==
Any type defined in a CodeDom tree to be consumed by the Eiffel CodeDom Provider may include one (and only one) snippet member that includes an inheritance clause declaration. This ''inheritance snippet'' must start with the keyword '''inherit''' and follows the Eiffel syntax for inheritance clauses. All the feature adaptations available in the Eiffel language may be used in such a snippet ('''rename''', '''export''', '''undefine''', '''redefine''', '''select''').
-{{note| '''Note:''' The CodeDom tree itself might define additional inheritance clauses in which case the Eiffel CodeDom Provider will merge the snippet and the implicit clauses in the generated source file. }}
+{{note|The CodeDom tree itself might define additional inheritance clauses in which case the Eiffel CodeDom Provider will merge the snippet and the implicit clauses in the generated source file. }}
==Indexing Snippet and Precompiled Libraries==
Another interesting snippet member is the ''indexing clause snippet'' which must start with the '''indexing''' keyword and follows the Eiffel syntax for indexing clauses. This snippet may include the indexing clause '''precompile_definition_file''' which can be used to specify the path to the precompiled library ACE file to be used by the Eiffel CodeDom Compiler. This is specially useful in ASP.NET pages where each page can specify which precompiled ACE file to use when compiling it. This path will be used instead of the path defined in the [[Configuration|configuration file]] .
-{{note| '''Note:''' Only one class per compile unit should define a path to the precompiled library ACE file. If more than one class contain a '''precompile_definition_file''' indexing clause then there is no guarentee on which one the Eiffel CodeDom Compiler will use. }}
+{{note|Only one class per compile unit should define a path to the precompiled library ACE file. If more than one class contain a '''precompile_definition_file''' indexing clause then there is no guarentee on which one the Eiffel CodeDom Compiler will use. }}
==Eiffel Configuration==
There are several Eiffel specific settings that can be set in the Eiffel CodeDom Provider which will affect the generated code as well as the CodeDom compiler behavior. These settings are covered in the [[Configuration|Configuration]] section.
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/installation.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/installation.wiki
index 8f1bf72e..11662e69 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/installation.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/eiffel-codedom-provider/installation.wiki
@@ -8,7 +8,7 @@ For certain tools (including ASP.NET) to detect the availability of a CodeDom Pr
Conversely, should the Eiffel Codedom Provider not be required anymore, running the following command line will remove it from the ''machine.config'' file:
InstallUtil /u EiffelSoftware.Codedom.dll
-{{note| '''Note''': The '''Eiffel for ASP.NET''' installation program will take care of registering and unregistering the Eiffel CodeDom Provider properly. }}
+{{note|The '''Eiffel for ASP.NET''' installation program will take care of registering and unregistering the Eiffel CodeDom Provider properly. }}
{{seealso| '''See also''': [[Supported Constructs|Supported constructs]] }}
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/codedom-getting-started.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/codedom-getting-started.wiki
index 2ba5c2d3..c6fea704 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/codedom-getting-started.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/codedom-getting-started.wiki
@@ -7,7 +7,7 @@ Writing ASP.NET pages in Eiffel also requires to be familiar with the Eiffel lan
==Samples==
The '''Samples''' folder of the Eiffel for ASP.NET delivery includes ASP.NET pages written in Eiffel. To run the samples you can either click on the corresponding link in the ''Start'' menu or open the page [http://localhost/EiffelSample http://localhost/EiffelSample] in your internet browser. Each sample comes with an extensively commented source code.
-{{note| '''Note''': The samples will only be available if IIS was installed prior to installing Eiffel for ASP.NET. }}
+{{note|The samples will only be available if IIS was installed prior to installing Eiffel for ASP.NET. }}
{{seealso| '''See also:''' [[Using Eiffel (to write ASP.NET pages)|Using Eiffel]] }}
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/names-mappings.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/names-mappings.wiki
index 67f630dc..34144336 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/names-mappings.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-aspnet-documentation/writing-aspnet-pages-eiffel/names-mappings.wiki
@@ -2,7 +2,7 @@
[[Property:weight|4]]
[[Property:uuid|fa212869-ffb0-0a6a-cbd0-7a184b11491d]]
Maybe the most striking difference when writing pages in Eiffel comes from the name of the .NET types and methods. Because of different naming conventions, overloading and differences in identifier validity rules, .NET identifiers cannot be mapped directly to Eiffel identifiers. As a consequence, the Eiffel compiler creates XML mapping files in the ''Eiffel Metadata Cache''. These files are created only once for each referenced assembly.
-{{note| '''Note:''' The ASP.NET installation program pre-generates the Eiffel Metadata Cache for all assemblies required by ASP.NET by default. }}
+{{note|The ASP.NET installation program pre-generates the Eiffel Metadata Cache for all assemblies required by ASP.NET by default. }}
The name mapping algorithm is quite complex but it is possible to guess the Eiffel identifier from the .NET identifier in most cases. The following simple steps can be followed to retrieve the Eiffel identifier corresponding to a .NET type:
# Only the simple type name is used, the namespace isn't used by the Eiffel identifier:
System.Xml.NameTable -> NameTable
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/adding-class-features.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/adding-class-features.wiki
index f89bb7bc..ff37c2f0 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/adding-class-features.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/adding-class-features.wiki
@@ -176,7 +176,7 @@ end -- Class SOME_CLASS
When you write a feature in a class, you typically will include some of the following:
* The feature's name
-{{note| '''Note:''' In Eiffel every feature of a class must have a name that is unique within that class. }}
+{{note|In Eiffel every feature of a class must have a name that is unique within that class. }}
* The feature's type (in the case of an attribute or a function)
* The feature's formal argument list (in the case of a function or procedure that has arguments)
@@ -275,7 +275,7 @@ The precondition part of a feature is introduced by the keyword " require
This part contains the declarations for any "local entities" used by the feature. Sometimes the computation accomplished in a feature requires the use of entities which are only temporary. It would not be appropriate to make these attributes of the class. So, instead we can use local entities, which have scope only within the feature in which they are declared. In the example, hd_item is available as type WEL_HD_ITEM during the computation of feature insert_text_header_item .
-{{note| '''Note:''' A local entity name must not be the same as any feature of the class in which its feature occurs or the same as any argument name of the feature in which it occurs. }}
+{{note|A local entity name must not be the same as any feature of the class in which its feature occurs or the same as any argument name of the feature in which it occurs. }}
===Routine Body===
@@ -303,7 +303,7 @@ There are other forms that a routine body can take. Here are some examples of so
The routine body above is for an "external" routine. External routines are used to represent within Eiffel classes, routines that are written in other languages.
-{{tip| '''Tip:''' Because of the high degree of language interaction provided by Microsoft.NET, it is not necessary in Eiffel for.NET to use externals to use software components from.NET assemblies. Instead, these components are presented to the Eiffel programmer as if they were Eiffel classes. Read more about this in [[Conventions|Conventions]] . }}
+{{tip|Because of the high degree of language interaction provided by Microsoft.NET, it is not necessary in Eiffel for.NET to use externals to use software components from.NET assemblies. Instead, these components are presented to the Eiffel programmer as if they were Eiffel classes. Read more about this in [[Conventions|Conventions]] . }}
====Once Routines====
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-classes.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-classes.wiki
index 5dfa72cb..6c26c6f5 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-classes.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-classes.wiki
@@ -209,7 +209,7 @@ You may declare multiple feature statements. This helps you group
Although the words " Initialization " and " Access " are actually in comments after the feature keyword, some language processing tools apply some significance to these, for example, ordering the groups in "pretty-printed" views of a class. Also, some tools allow you to build templates for creating new classes which have feature clauses already in place for predetermined groups.
-{{tip| '''Tip:''' There is not a technical requirement governing the grouping or ordering of features in a class. It is the option of the producer of a class to group and order the features in some fashion that has some meaning. Many years of Eiffel development experience are reflected in the classes in the Eiffel Base Library. This is a good place to look for examples of well constructed classes. }}
+{{tip|There is not a technical requirement governing the grouping or ordering of features in a class. It is the option of the producer of a class to group and order the features in some fashion that has some meaning. Many years of Eiffel development experience are reflected in the classes in the Eiffel Base Library. This is a good place to look for examples of well constructed classes. }}
===Invariant===
diff --git a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-net-compliance.wiki b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-net-compliance.wiki
index b34ff391..8b5f9933 100644
--- a/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-net-compliance.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/net/eiffel-net-language/eiffel-net/eiffel-net-compliance.wiki
@@ -3,7 +3,7 @@
[[Property:uuid|1e19c2f0-995e-02c1-0588-c134a11e0003]]
As of EiffelEnvision 2.6, Eiffel for ASP.NET 5.6 and EiffelStudio 5.7; Eiffel for .NET introduces the notion of '''Eiffel-Compliance'''. .NET specifies a number of language interopability rules in a [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwhatiscommonlanguagespecification.asp Common Language Specification-Compliance] specification. Eiffel for .NET supports all CLS-Compliant type and features in .NET but now additionally supports a number of non-CLS-compliant types and features. This is the purpose of the Eiffel-Compliant notion.
-{{note| '''Note''': The information contained within this page does not go into any depth on the Common Language Specification (CLS) or CLS-Compliance. For this information please see Microsoft's on-line documentation [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwhatiscommonlanguagespecification.asp What is the Common Language Specification?] }}
+{{note|The information contained within this page does not go into any depth on the Common Language Specification (CLS) or CLS-Compliance. For this information please see Microsoft's on-line documentation [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwhatiscommonlanguagespecification.asp What is the Common Language Specification?] }}
==Applicability==
diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/hello-world.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/hello-world.wiki
index 4279e37f..afd64bea 100644
--- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/hello-world.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-samples/hello-world.wiki
@@ -30,7 +30,7 @@ on_paint (paint_dc: WEL_PAINT_DC; invalid_rect: WEL_RECT) is
end
-{{note| '''Note:''' If you look at MAIN_WINDOW, you will see that it contains many features. However, nearly all of these are features are inherited from WEL_FRAME_WINDOW. }}
+{{note|If you look at MAIN_WINDOW, you will see that it contains many features. However, nearly all of these are features are inherited from WEL_FRAME_WINDOW. }}
This sample contains the following classes:
* HELLO_DEMO
diff --git a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-1.wiki b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-1.wiki
index 425a41c1..a636b5dc 100644
--- a/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-1.wiki
+++ b/documentation/current/platform-specifics/microsoft-windows/wel/wel-tutorial/tutorial-step-1.wiki
@@ -19,7 +19,7 @@ This sample shows you how to set up your first [[ref:/libraries/wel/reference/we
After you launch the sample, You should see the window displayed in the screen as illustrated above. You will have full control over the window, and the program will quit when you close the window.
-{{note| '''Note:''' The size and shape of the window may be different on your machine. }}
+{{note|The size and shape of the window may be different on your machine. }}
==Under the Hood==
diff --git a/documentation/current/solutions/basic-computing/eiffelbase/eiffelbase-samples/eiffelbase-sample-calculator.wiki b/documentation/current/solutions/basic-computing/eiffelbase/eiffelbase-samples/eiffelbase-sample-calculator.wiki
index 133611ea..f562930e 100644
--- a/documentation/current/solutions/basic-computing/eiffelbase/eiffelbase-samples/eiffelbase-sample-calculator.wiki
+++ b/documentation/current/solutions/basic-computing/eiffelbase/eiffelbase-samples/eiffelbase-sample-calculator.wiki
@@ -3,7 +3,10 @@
[[Property:uuid|12c3409d-165b-b1df-e26a-b05d49969661]]
This sample consists of a command line reverse Polish notation (RPN) calculator.
-{{note| '''Note:''' A RPN calculator works slightly differently from standard calculators. It consists of a stack of numbers. Operations are applied to the two numbers on top of the stack. The result is then put on top of the stack so that it can be used in the next operation. This sample refers to the top of the stack as ''Accumulator''.
+{{note|A RPN calculator works slightly differently from standard calculators. It consists of a stack of numbers. Operations are applied to the two numbers on top of the stack. The result is then put on top of the stack so that it can be used in the next operation. This sample refers to the top of the stack as ''Accumulator''.This sample consists of a command line reverse Polish notation (RPN) calculator. }}
+
+{{note|A RPN calculator works slightly differently from standard calculators. It consists of a stack of numbers. Operations are applied to the two numbers on top of the stack. The result is then put on top of the stack so that it can be used in the next operation. This sample refers to the top of the stack as ''Accumulator''. }}
+
==Compiling==
To compile the example:
@@ -36,7 +39,7 @@ Enter a number, followed by :
Enter the first number to be put onto the stack, for example 3.
-{{note| '''Note:''' Failing to enter a number at this stage will cause the sample to stop. This sample was designed to showcase the use of EiffelBase data structures and is not protected against unexpected entries. }}
+{{note|Failing to enter a number at this stage will cause the sample to stop. This sample was designed to showcase the use of EiffelBase data structures and is not protected against unexpected entries. }}
You may then add another number on the stack by entering the character a:
@@ -77,7 +80,7 @@ Next operation?
You may use the operation 0 to clear the stack at any time. You may use q to quit the program.
-{{tip| '''Tip:''' You can use the command ? to display the list of available operations. }}
+{{tip|You can use the command ? to display the list of available operations. }}
==Under the Hood==
@@ -94,7 +97,7 @@ Each of these classes implement the feature do_one_state from STATE which perfor
Every descendant of STATE implement the feature operation which performs the corresponding stack transformation.
See the reference for the class interfaces.
-}}
+
diff --git a/documentation/current/solutions/concurrent-computing/eiffelthread/eiffelthread-tutorial/thread-library-overview.wiki b/documentation/current/solutions/concurrent-computing/eiffelthread/eiffelthread-tutorial/thread-library-overview.wiki
index 87c384f3..7da511a9 100644
--- a/documentation/current/solutions/concurrent-computing/eiffelthread/eiffelthread-tutorial/thread-library-overview.wiki
+++ b/documentation/current/solutions/concurrent-computing/eiffelthread/eiffelthread-tutorial/thread-library-overview.wiki
@@ -36,7 +36,7 @@ Creating a thread is like creating an Eiffel object:
create my_thread
-{{note| '''Note''': You have created a thread object but have not started the thread itself yet.
+{{note|You have created a thread object but have not started the thread itself yet.
To run the thread, use the feature launch from THREAD. }}
my_thread.launch
On the Eiffel side, the procedure execute will be launched. This procedures deferred in class THREAD, you have to define it in MY_THREAD.
@@ -65,7 +65,7 @@ The implementation of the class MUTEX is mapped on the C standa
my_mutex.is_set
-{{note| '''Note''': on Windows: The MUTEX objects on Windows are recursive while they are not on Unix. A recursive mutex can be locked twice by the same thread. }}
+{{note|on Windows: The MUTEX objects on Windows are recursive while they are not on Unix. A recursive mutex can be locked twice by the same thread. }}
{{warning| '''Caution''': be sure that a mutex is unlocked when it is disposed. }}
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/esql-sample.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/esql-sample.wiki
index 9e94e06f..4e5a041f 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/esql-sample.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/esql-sample.wiki
@@ -27,7 +27,7 @@ Name: smith
Password: mypass
-{{note| '''Note:''' '' Name'' and ''Password'' are no required with ODBC. If you don't need ''Name'' and ''Password'', you can simply hit '''Return''' when prompted ''.'' }}
+{{note|Name'' and ''Password'' are no required with ODBC. If you don't need ''Name'' and ''Password'', you can simply hit '''Return''' when prompted ''.'' }}
* For Oracle:
@@ -36,7 +36,7 @@ Name: smith@HANDSON
Password: mypass
-{{note| '''Note:''' you have to specify the Oracle User Name and Net Service Name with the syntax ''@ ''where '''' stands for the User Name and '''' stands for the Net Service Name. }}
+{{note|you have to specify the Oracle User Name and Net Service Name with the syntax ''@ ''where '''' stands for the User Name and '''' stands for the Net Service Name. }}
Then you can enter standard SQL queries to interact with your database, for instance:
@@ -46,7 +46,7 @@ John Smith
SQL>
-{{note| '''Note:''' enter ''exit'' to quit the application. }}
+{{note|enter ''exit'' to quit the application. }}
==Under the Hood==
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/inserter-sample.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/inserter-sample.wiki
index 288270ab..dadd2ada 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/inserter-sample.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/inserter-sample.wiki
@@ -31,7 +31,7 @@ Name: smith
Password: mypass
-{{note| '''Note:''' '' Name'' and ''Password'' are no required with ODBC. If you don't need ''Name'' and ''Password'', you can simply hit '''Return''' when prompted ''.'' }}
+{{note|Name'' and ''Password'' are no required with ODBC. If you don't need ''Name'' and ''Password'', you can simply hit '''Return''' when prompted ''.'' }}
* For Oracle:
@@ -42,7 +42,7 @@ Name: smith@HANDSON
Password: mypass
-{{note| '''Note:''' you have to specify the Oracle User Name and Net Service Name with the syntax ''@ ''where '''' stands for the User Name and '''' stands for the Net Service Name. }}
+{{note|you have to specify the Oracle User Name and Net Service Name with the syntax ''@ ''where '''' stands for the User Name and '''' stands for the Net Service Name. }}
Then you can insert a book in the database, for instance:
@@ -64,7 +64,7 @@ Double value? 12.675
Object inserted
-{{note| '''Note:''' if your database does not contain a DB_BOOK table, this example will create it. }}
+{{note|if your database does not contain a DB_BOOK table, this example will create it. }}
==Under the Hood==
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/selector-sample.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/selector-sample.wiki
index 591bd8c9..85504b90 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/selector-sample.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-samples/selector-sample.wiki
@@ -40,7 +40,7 @@ Name: smith
Password: mypass
-{{note| '''Note:''' '' Name'' and ''Password'' are no required with ODBC. If you don't need ''Name'' and ''Password'', you can simply hit '''Return''' when prompted. }}
+{{note|Name'' and ''Password'' are no required with ODBC. If you don't need ''Name'' and ''Password'', you can simply hit '''Return''' when prompted. }}
* For Oracle:
@@ -49,7 +49,7 @@ Name: smith@HANDSON
Password: mypass
-{{note| '''Note:''' you have to specify the Oracle User Name and Net Service Name with the syntax ''@ ''where '''' stands for the User Name and '''' stands for the Net Service Name. }}
+{{note|you have to specify the Oracle User Name and Net Service Name with the syntax ''@ ''where '''' stands for the User Name and '''' stands for the Net Service Name. }}
Then you can select rows from this table with author's name, for instance:
@@ -77,7 +77,7 @@ First publication:07/01/1992 12:00:00.0 AM
Author? ('exit' to terminate):
-{{note| '''Note:''' enter ''exit'' to quit the application. }}
+{{note|enter ''exit'' to quit the application. }}
==Under the Hood==
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-dataview-cluster.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-dataview-cluster.wiki
index 10ab2db9..5c66e9e8 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-dataview-cluster.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-dataview-cluster.wiki
@@ -179,7 +179,7 @@ Table components can be associated to reflect relation of database tables repres
* 1 master component enables to manually select database table rows.
* Slave components automatically select table rows that are associated to the current table row of the master component.
-{{note| '''Note''': Notice that table associations can be '''nested'''. }}
+{{note|Notice that table associations can be '''nested'''. }}
2 types of associations are possible to reflect table relations:
* The slave table is dependent on the master table (1:N relationship)
@@ -265,7 +265,7 @@ Basic relationship between table component class and navigation class
DV_TABLEROWS_NAVIGATOR clients
-{{note| '''Note''': DV_TABLEROWS_COMPONENT class merely carries a set of table rows and enables to select one table row. }}
+{{note|DV_TABLEROWS_COMPONENT class merely carries a set of table rows and enables to select one table row. }}
DV_CONTROL_NAVIGATOR affords a way to navigate among searched table rows.
@@ -275,7 +275,7 @@ This class enables 2 navigation systems:
* Navigating among table rows with "previous" and "next" controllers.
* Navigating among table rows through a display list.
-{{tip| '''Tip''': Notice that both systems can be used. }}
+{{tip|Notice that both systems can be used. }}
You can directly set [[#dv_s_control| controllers]] for "previous" and"next" actions. A 3rd controller, "edit list", enables to show or raise the display list.
@@ -384,9 +384,9 @@ This cluster provides the model with an interface to input or output data on the
The [[ref:libraries/store/reference/dv_sensitive_control_chart|DV_SENSITIVE_CONTROL]] class lets a model class trigger a specific action on a determined user event. Furthermore, the model class lets the user know when its state enables to trigger the action, by setting the controller sensitivity (i.e. if the controller is insensitive, the action cannot be triggered).
-{{note| '''Note''': sensitivity excepted, these controllers could have been implemented by Eiffel ''agents''. }}
+{{note|sensitivity excepted, these controllers could have been implemented by Eiffel ''agents''. }}
-{{note| '''Note''': sensitivity enables to let the user know ''before''triggering an action if this is possible or not. The other possibility is to let the user know ''after'' trying to trigger the action that it was not possible(with a warning for instance): this is often less convenient. }}
+{{note|sensitivity enables to let the user know ''before''triggering an action if this is possible or not. The other possibility is to let the user know ''after'' trying to trigger the action that it was not possible(with a warning for instance): this is often less convenient. }}
The standard controllers are buttons or menu items: the specific action is triggered when button is clicked or menu item selected.
@@ -400,7 +400,7 @@ The standard graphical widgets to perform this are text fields, but several othe
* A combo-box so that the interface can suggest different values.
* A label if the text only need to be output.
-{{note| '''Note''': customized, specific widgets can be defined, you can for instance take a look at the DV_STRING_LIST class. }}
+{{note|customized, specific widgets can be defined, you can for instance take a look at the DV_STRING_LIST class. }}
===5.3. DV_SENSITIVE_INTEGER class===
@@ -425,7 +425,7 @@ The [[ref:libraries/store/reference/dv_tablerow_list_chart|DV_TABLEROW_LIST]] c
[[ref:libraries/store/reference/dv_tablerow_multilist_chart|DV_TABLEROW_MULTILIST]] implements DV_TABLEROW_LIST with an EiffelVision2 multi-column list.
-{{note| '''Note''': This class is used for the [[#dv_control_navigator|standard implementation]] of [[ref:libraries/store/reference/dv_tablerows_navigator_chart|DV_TABLEROW_NAVIGATOR]] to [[#dv_tablerow_navigator|navigate among table rows]] selected from the database. }}
+{{note|This class is used for the [[#dv_control_navigator|standard implementation]] of [[ref:libraries/store/reference/dv_tablerows_navigator_chart|DV_TABLEROW_NAVIGATOR]] to [[#dv_tablerow_navigator|navigate among table rows]] selected from the database. }}
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-generation-cluster/data-structures-use.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-generation-cluster/data-structures-use.wiki
index 23fc45bf..4c5f76eb 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-generation-cluster/data-structures-use.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-generation-cluster/data-structures-use.wiki
@@ -45,7 +45,7 @@ You can then access or modify [[ref:libraries/store/reference/db_table_flatshort
end
-{{note| '''Note:''' to access attributes data with ''code'', you need to use the [[ref:/libraries/store/reference/db_table_description_flatshort|DB_TABLE_DESCRIPTION]] object associated to your [[ref:libraries/store/reference/db_table_flatshort|DB_TABLE]] object. }}
+{{note|to access attributes data with ''code'', you need to use the [[ref:/libraries/store/reference/db_table_description_flatshort|DB_TABLE_DESCRIPTION]] object associated to your [[ref:libraries/store/reference/db_table_flatshort|DB_TABLE]] object. }}
===2.3. Getting objects metadata===
@@ -168,7 +168,7 @@ As seen in the previous section, to manipulate abstract table/view rows content,
As descriptions are unique, this means that description objects are also associated to a specific table object to deal with it (i.e. access or modify its content). Actually, the table_description feature associates the description with the current object and then returns this description.
-{{note| '''Note:''' The table_description feature is still a query as the association part should not be visible at the interface level. }}
+{{note|The table_description feature is still a query as the association part should not be visible at the interface level. }}
On the whole, you have to pay attention to always execute table_descriptionon your table/view row to get the appropriate description.
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-implementation-layer.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-implementation-layer.wiki
index f9c5e013..cb68ab7d 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-implementation-layer.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-implementation-layer.wiki
@@ -64,7 +64,7 @@ Let us give some details about the set_base feature:
** Login information.
** Status information.
-{{note| '''Note''': When database is inactive, its information is stored in the DATABASE_APPL object. }}
+{{note|When database is inactive, its information is stored in the DATABASE_APPL object. }}
The corresponding code looks like:
@@ -82,7 +82,7 @@ The corresponding code looks like:
...
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelStore Interface Layer|The interface layer]]
}}
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/data-modification.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/data-modification.wiki
index 1cdb03d4..cfa87848 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/data-modification.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/data-modification.wiki
@@ -3,7 +3,7 @@
[[Property:uuid|ef5568ff-dc7c-4c85-0174-335fdab1bd84]]
Use the [[ref:/libraries/store/reference/db_change_flatshort|DB_CHANGE]] class to perform any operation on your database that does not require access to a result. You can for instance modify table row content, drop table rows, create and delete tables.
-{{note| '''Note''': Take a look at the [[Data Object Coupling|Data Storing]] capability if you want to '''insert''' table rows. }}
+{{note|Take a look at the [[Data Object Coupling|Data Storing]] capability if you want to '''insert''' table rows. }}
[[ref:/libraries/store/reference/db_change_flatshort|DB_CHANGE]] allows you to modify the database data using the SQL language:
* Prepare your SQL query and use modify:
@@ -23,10 +23,10 @@ Use the [[ref:/libraries/store/reference/db_change_flatshort|DB_CHANGE]] class
session_control.commit
-{{tip| '''Tip''': It is always better to check the database status for errors before committing changes. }}
+{{tip|It is always better to check the database status for errors before committing changes. }}
-{{seealso| '''See Also'''
+{{seealso|
[[Data Object Coupling|Data storing]]
[[Stored Procedures|Stored procedures]]
[[EiffelStore Implementation Layer|Implementation]]
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/data-object-coupling.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/data-object-coupling.wiki
index fe42f04e..ee0ce15a 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/data-object-coupling.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/data-object-coupling.wiki
@@ -19,7 +19,7 @@ A [[ref:/libraries/store/reference/db_repository_flatshort|DB_REPOSITORY]] obje
end
-{{tip| '''Tip''': Loading a table description is often a costly operation: table has to be fetched among existing tables then every table column description must be loaded. Hence it is better to store and reuse a repository (maybe with a HASH_TABLE) once it has been loaded. }}
+{{tip|Loading a table description is often a costly operation: table has to be fetched among existing tables then every table column description must be loaded. Hence it is better to store and reuse a repository (maybe with a HASH_TABLE) once it has been loaded. }}
Using the table information, [[ref:/libraries/store/reference/db_repository_flatshort|DB_REPOSITORY]] then helps generating Eiffel classes mapping relational tables:
* You can directly use {[[ref:/libraries/store/reference/db_repository_flatshort|DB_REPOSITORY]] }.generate_class. Generated class may look like:
@@ -40,7 +40,7 @@ Using the table information, [[ref:/libraries/store/reference/db_repository_flat
...
-{{note| '''Note''': The EiffelStore Wizard uses the generation.generator cluster to generate the classes mapped to your database. }}
+{{note|The EiffelStore Wizard uses the generation.generator cluster to generate the classes mapped to your database. }}
==Inserting data in the database==
@@ -79,10 +79,10 @@ This is straight-forward since you only have to give [[ref:/libraries/store/refe
end
-{{note| '''Note''': You can see how actions are used in [[ref:/libraries/store/reference/db_selection_flatshort|DB_SELECTION]] . }}
+{{note|You can see how actions are used in [[ref:/libraries/store/reference/db_selection_flatshort|DB_SELECTION]] . }}
-{{seealso| '''See Also'''
+{{seealso|
[[Database Selection|Performing a database selection.]]
[[Data structures use|Database-specific structures use.]]
}}
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-connection.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-connection.wiki
index d432a37e..a2bf9b71 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-connection.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-connection.wiki
@@ -11,11 +11,11 @@
-{{note| '''Note''': Calling set_base links the EiffelStore interface to this specific handle. }}
+{{note|Calling set_base links the EiffelStore interface to this specific handle. }}
-{{tip| '''Tip''': You can manage handles to many databases: as an instance of DATABASE_APPL stands for a specific database handle, you only have to create one instance of DATABASE_APPL for every DBMS handle you wish to create. Do not forget to call set_base to activate appropriate handle. }}
+{{tip|You can manage handles to many databases: as an instance of DATABASE_APPL stands for a specific database handle, you only have to create one instance of DATABASE_APPL for every DBMS handle you wish to create. Do not forget to call set_base to activate appropriate handle. }}
-{{note| '''Note''': The generic parameter of DATABASE_APPL specifies the actual DBMS used. }}
+{{note|The generic parameter of DATABASE_APPL specifies the actual DBMS used. }}
# Once your handle is created, you have to create a session manager which will allow you to manage your database, specifically to establish connection, disconnect and also handle errors. The class DB_CONTROL enables your application to plainly control the functioning and status of your database and to request any information about it.
@@ -26,10 +26,10 @@
session_control.connect
-{{note| '''Note''': Take a look at the [[Database control|database control]] part to see how to use DB_CONTROL capabilities. }}
+{{note|Take a look at the [[Database control|database control]] part to see how to use DB_CONTROL capabilities. }}
-{{seealso| '''See Also'''
+{{seealso|
[[Database control|Database control and error handling]]
[[EiffelStore Implementation Layer|Implementation]]
}}
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-control.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-control.wiki
index 200e218e..6bc86bd8 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-control.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-control.wiki
@@ -59,7 +59,7 @@ The loop performs a multi-step transaction. If transaction is not carried out en
{{warning| '''Caution''': Some databases can be in an auto-commit mode. Furthermore, some special database commands can automatically commit database changes. }}
-{{seealso| '''See Also'''
+{{seealso|
[[Database Connection|Database connection]]
[[EiffelStore Implementation Layer|Implementation]]
}}
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-selection.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-selection.wiki
index 5e44eb12..f2c2e99e 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-selection.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/database-selection.wiki
@@ -3,7 +3,7 @@
[[Property:uuid|de759a74-b3e1-c937-e620-67526c116925]]
Use the [[ref:/libraries/store/reference/db_selection_flatshort|DB_SELECTION]] class to select data from the database. Once you have selected the data, you can [[Selection Access|access]] it with convenience using adaptative EiffelStore structures.
-{{note| '''Note''': Take a look at the [[Data Object Coupling|Database/Eiffel objects Coupling]] if you need information about your database structure. }}
+{{note|Take a look at the [[Data Object Coupling|Database/Eiffel objects Coupling]] if you need information about your database structure. }}
[[ref:/libraries/store/reference/db_selection_flatshort|DB_SELECTION]] enables your application to get database content using SQL 'select' queries:
* You can carry out 'select' queries in an intuitive way using directly the SQL language:
@@ -15,11 +15,11 @@ Use the [[ref:/libraries/store/reference/db_selection_flatshort|DB_SELECTION]]
selection.execute
-{{tip| '''Tip''': Always check the database status for errors after your 'select' query. }}
+{{tip|Always check the database status for errors after your 'select' query. }}
* You can also customize your selection using [[Query variables|bind variables]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Query variables|Binding variables in a database query.]]
[[Data Object Coupling|Coupling database objects with Eiffel objects.]]
[[Selection Access|Accessing selected data from the database.]]
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/index.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/index.wiki
index c13c4a01..37915b9a 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/index.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/index.wiki
@@ -13,9 +13,9 @@ The interface affords these main capabilities:
* Using [[Stored Procedures|stored procedures]] .
* Dealing with database [[Database control|status and behavior]] .
-{{note| '''Note''': In general, each of these capabilities corresponds to one EiffelStore class. }}
+{{note|In general, each of these capabilities corresponds to one EiffelStore class. }}
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelStore Implementation Layer|The implementation layer]] }}
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/query-variables.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/query-variables.wiki
index 2df11a5f..06074243 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/query-variables.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/query-variables.wiki
@@ -22,7 +22,7 @@ Variables syntax is simple: the ':' special character followed by the variable n
selection.set_query ("Select * from CONTACTS where Firstname = ':" + Bind_var + "'")
-{{note| '''Note''': The code example shows how to bind variables to a [[ref:/libraries/store/reference/db_selection_chart|DB_SELECTION]] object but the mechanism is exactly the same for [[ref:/libraries/store/reference/db_change_chart|DB_CHANGE]] objects. }}
+{{note|The code example shows how to bind variables to a [[ref:/libraries/store/reference/db_selection_chart|DB_SELECTION]] object but the mechanism is exactly the same for [[ref:/libraries/store/reference/db_change_chart|DB_CHANGE]] objects. }}
==Binding variables to a query==
@@ -40,7 +40,7 @@ Once you have created your query, you can map variable names to values and execu
end
-{{seealso| '''See Also'''
+{{seealso|
[[Database Selection|Performing a database selection.]]
[[Data Modification|Modifying database content.]]
}}
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/selection-access.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/selection-access.wiki
index 083a8f91..119b35ba 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/selection-access.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/selection-access.wiki
@@ -3,7 +3,7 @@
[[Property:uuid|3b4fdde3-d903-55c8-0068-cee2407db280]]
Once you have [[Database Selection|selected data]] from the database, it returns a set of rows containing queried columns values. Each row loaded with DB_SELECTION is stored in a DB_RESULT object. The easiest way to access the data is thus to refer to DB_RESULT objects themselves.
-{{note| '''Note''': Take a look at the [[Data Object Coupling|Database/Eiffel objects Coupling]] to learn advanced data handling features. }}
+{{note|Take a look at the [[Data Object Coupling|Database/Eiffel objects Coupling]] to learn advanced data handling features. }}
To use DB_RESULT, process in 2 steps:
* [[#retrieve|retrieve]] DB_RESULT objects.
@@ -41,7 +41,7 @@ To use DB_RESULT, process in 2 steps:
end
-{{tip| '''Tip''': Provide [[ref:/libraries/store/reference/db_selection_flatshort|DB_SELECTION]] with the LIST structure convenient for what you need to do with the results. }}
+{{tip|Provide [[ref:/libraries/store/reference/db_selection_flatshort|DB_SELECTION]] with the LIST structure convenient for what you need to do with the results. }}
* You want to '''select part''' of the result set: you can set an action in [[ref:/libraries/store/reference/db_selection_flatshort|DB_SELECTION]] that will be executed each time a row is loaded. This action can for instance manipulate current row and define a stop condition.
** You need to define a descendant of class ACTION and set it to [[ref:/libraries/store/reference/db_selection_flatshort|DB_SELECTION]] :
@@ -93,7 +93,7 @@ A DB_RESULT object merely carries data retrieved from the database. You have to
end
-{{seealso| '''See Also'''
+{{seealso|
[[Database Selection|Performing a database selection.]]
[[Data Object Coupling|Coupling database data and Eiffel objects.]]
}}
diff --git a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/stored-procedures.wiki b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/stored-procedures.wiki
index 09c54eb0..6efddc97 100644
--- a/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/stored-procedures.wiki
+++ b/documentation/current/solutions/database-access/eiffelstore/eiffelstore-tutorial/eiffelstore-interface-layer/stored-procedures.wiki
@@ -22,11 +22,11 @@ To execute a stored procedure:
* Execute the procedure through a [[ref:/libraries/store/reference/db_selection_chart|DB_SELECTION]] (if a result is expected) or a [[ref:/libraries/store/reference/db_change_chart|DB_CHANGE ]] object (otherwise).
-{{note| '''Note''': Requests with a result ([[ref:/libraries/store/reference/db_selection_chart|DB_SELECTION]] ) or without ([[ref:/libraries/store/reference/db_change_chart|DB_CHANGE]] ) are both abstract '''expressions'''. DB_PROC executes an abstract expression using an object of [[ref:/libraries/store/reference/db_expression_chart|DB_EXPRESSION]] type, which corresponds to an abstract expression. [[ref:/libraries/store/reference/db_selection_chart|DB_SELECTION]] and [[ref:/libraries/store/reference/db_change_chart|DB_CHANGE]] inherits from [[ref:/libraries/store/reference/db_expression_chart|DB_EXPRESSION]] . }}
+{{note|Requests with a result ([[ref:/libraries/store/reference/db_selection_chart|DB_SELECTION]] ) or without ([[ref:/libraries/store/reference/db_change_chart|DB_CHANGE]] ) are both abstract '''expressions'''. DB_PROC executes an abstract expression using an object of [[ref:/libraries/store/reference/db_expression_chart|DB_EXPRESSION]] type, which corresponds to an abstract expression. [[ref:/libraries/store/reference/db_selection_chart|DB_SELECTION]] and [[ref:/libraries/store/reference/db_change_chart|DB_CHANGE]] inherits from [[ref:/libraries/store/reference/db_expression_chart|DB_EXPRESSION]] . }}
You can execute your request mostly like a basic one:
** Create your request.
** Bind request variables. Variables are stored procedure arguments.
-{{note| '''Note''': Take a look at how to [[Query variables|bind variables]] to a query. }}
+{{note|Take a look at how to [[Query variables|bind variables]] to a query. }}
** Execute the query through the DB_PROC object.
@@ -62,7 +62,7 @@ The following example shows how to overwrite a procedure in the database:
end
-{{seealso| '''See Also'''
+{{seealso|
[[Database Selection|Performing a database selection.]]
[[Data Object Coupling|Coupling database data and Eiffel objects.]]
}}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/create-object.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/create-object.wiki
index 0e09520f..30818120 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/create-object.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/create-object.wiki
@@ -5,19 +5,19 @@ An EiffelBuild [[EiffelBuild Notation|object]] is a representation of a Vision2
To create a new instance of an object, [[EiffelBuild Notation|pick]] a type from the [[Type selector|type selector]] and [[EiffelBuild Notation|drop]] onto an existing [[EiffelBuild Notation|object]] (Accessible from the [[Layout constructor|layout constructor]] or [[Builder window|builder window]] ). You will only be able to complete the [[EiffelBuild Notation|drop]] if the targeted [[EiffelBuild Notation|object]] will accept a new object of the transported type.
-{{note| '''Note''': Once an [[EiffelBuild Notation|object]] has been [[Create an object|created]] , it will always be contained in a parent [[EiffelBuild Notation|object]] until [[Delete an object|deleted]] . }}
+{{note|Once an [[EiffelBuild Notation|object]] has been [[Create an object|created]] , it will always be contained in a parent [[EiffelBuild Notation|object]] until [[Delete an object|deleted]] . }}
==Creating Window and Dialog Objects==
Window and dialog objects are created by picking a type from the [[Type selector|type selector]] and dropping into the [[Widget selector|widget selector]] . If the target of the drop is a directory within the widget selector, the new object is created within that directory, otherwise in the root of the project location. Window and dialog objects are generated as individual classes by EiffelBuild.
-{{note|'''Note''' If there are no other windows or directories in the project, the newly created object is set as the root window.}}
+{{note|If there are no other windows or directories in the project, the newly created object is set as the root window.}}
==Creating objects for re-use==
If you wish to create an object that may be re-used in multiple locations within your EiffelBuild project, pick the type from the [[Type selector|type selector]] and drop into the [[Widget selector|widget selector]] . This ensures that at generation time, the object is generated as a seperate class (as with all objects in the [[Widget selector|widget selector]] ). Objects within the [[Widget selector|widget selector]] may be used in a client fashion within other object structures as required, and any changes made to these objects are reflected at all locations in which they are used.
-{{seealso| '''See Also'''
+{{seealso|
[[Type selector|Type selector]]
[[Reparent an Object|Reparent an object]]
[[Delete an object|Delete an object]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/delete-object.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/delete-object.wiki
index aaf8366a..6315531f 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/delete-object.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/delete-object.wiki
@@ -5,9 +5,9 @@ To remove an [[EiffelBuild Notation|object]] from your EiffelBuild system, [[Ei
You may also delete via the keyboard by pressing the delete key while the tool containing the objects representation has the focus. Whichever [[EiffelBuild Notation|object]] has the selection is deleted.
-{{note| '''Note''': To restore a deleted object, you may use the [[History|History]] }}
+{{note|To restore a deleted object, you may use the [[History|History]] }}
-{{seealso| '''See Also'''
+{{seealso|
[[History|History]]
[[Type selector|Type selector]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/eiffelbuild-starting-project/eiffelbuild-creating-new-project.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/eiffelbuild-starting-project/eiffelbuild-creating-new-project.wiki
index 02e919d7..619b26a1 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/eiffelbuild-starting-project/eiffelbuild-creating-new-project.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/eiffelbuild-starting-project/eiffelbuild-creating-new-project.wiki
@@ -15,7 +15,7 @@ Selecting 'Ok' will create a new project, overwriting the existing project, and
Selecting 'Cancel' will return you to the directory selection dialog, from which you can select the directory in which you wish to create the new Build project.
-{{seealso| '''See Also'''
+{{seealso|
[[Retrieving a project from a Build project file|Retrieving a project from a Build project file]]
}}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/eiffelbuild-starting-project/retrieving-project-build-project-file.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/eiffelbuild-starting-project/retrieving-project-build-project-file.wiki
index 004036a5..efada97a 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/eiffelbuild-starting-project/retrieving-project-build-project-file.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/eiffelbuild-starting-project/retrieving-project-build-project-file.wiki
@@ -13,7 +13,7 @@ You may also open a recent EiffelBuild project via the 'Recent Projects' entry o
This list contains the most recent projects that have been used within EiffelBuild, and if none are available, this list is empty and the menu option disabled.
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelBuild: Creating a new project|Creating a new project]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/import-project.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/import-project.wiki
index 4dec57ae..fb87c315 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/import-project.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/import-project.wiki
@@ -14,7 +14,7 @@ Upon completion of the import, there are two possible outcomes:
* One or more name clashes occurred: One or more objects or constants from the imported project had names that matched that of objects in the open project. As the names are used directly in the generated code, they must be unique within their scope (accessible within the code), and therefore EiffelBuild must resolve these clashes. A dialog is displayed on screen showing all the names that were resolved by EiffelBuild:
[[Image:import-project-clashes]]
-{{note| '''Note''': If a name clash occurs, the names of the imported project are modified, not the open project. }}
+{{note|If a name clash occurs, the names of the imported project are modified, not the open project. }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/reparent-object.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/reparent-object.wiki
index f9cc0480..5879618e 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/reparent-object.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/reparent-object.wiki
@@ -7,11 +7,11 @@ When an [[EiffelBuild Notation|object]] is inserted into a parent, it is always
You can access [[EiffelBuild Notation|objects]] from both the [[Builder window|builder window]] and [[Layout constructor|layout constructor]] .
-{{note|'''Note''' Although window and dialog objects may be accessed within the [[Widget selector|widget selector]] , it is not possible to build into these objects, you should use the [[Layout constructor|layout constructor]] or [[Builder window|builder window]] directly in this situation. }}
+{{note|Although window and dialog objects may be accessed within the [[Widget selector|widget selector]] , it is not possible to build into these objects, you should use the [[Layout constructor|layout constructor]] or [[Builder window|builder window]] directly in this situation. }}
For more information about an [[EiffelBuild Notation|objects]] capacity and permitted children, see the [[EiffelVision Introduction|EiffelVision2]] documentation.
-{{seealso| '''See Also'''
+{{seealso|
[[Create an object|Create an object]]
[[Delete an object|Delete an object]]
[[Builder window|Builder window]]
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/save-project.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/save-project.wiki
index b9f520b3..dd7b9f81 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/save-project.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-how-tos/save-project.wiki
@@ -5,9 +5,9 @@ To save the project that is currently open, select '''Save''' from the '''File''
Alternatively, you may use the keyboard shortcut - '''Ctrl+S'''
-{{note| '''Note''': If no changes have been made to the system, the save command will be disabled. }}
+{{note|If no changes have been made to the system, the save command will be disabled. }}
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelBuild: Key shortcuts|Key shortcuts]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/builder-window.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/builder-window.wiki
index e5e509a0..b40a1f60 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/builder-window.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/builder-window.wiki
@@ -10,7 +10,7 @@ This window may either be shown or hidden (default). To change between these two
The content of this window is a representation of the [[EiffelBuild Notation|objects]] you have defined in your project. Each [[EiffelBuild Notation|object]] is represented by the [[EiffelVision Introduction|EiffelVision2]] control matching its type. For example, an [[EiffelBuild Notation|object]] representing an EV_BUTTON will be displayed in here using an EV_BUTTON. As this view provides direct access to the objects ( [[EiffelBuild Notation|Pick]] any of the controls in this window), it enables you to build your interface within a view which provides rich visual feedback.
Because this window is just a view of the [[EiffelBuild Notation|objects]] , it will be always synchronized with the [[Layout constructor| layout constructor]] . This means you can [[Reparent an Object| re-parent objects]] , using the [[EiffelBuild Notation|pick and drop]] transport method, seamlessly between the two views.
-{{note|'''Note:''' Holding Ctrl while right clicking on an [[EiffelBuild Notation|object]] in the Builder Window creates a new [[Object editor|object editor]] targeted to the [[EiffelBuild Notation|object]] . Holding Ctrl and Shift while right clicking on an [[EiffelBuild Notation|object]] , highlights it within the [[Layout constructor|layout constructor]] .}}
+{{note|Holding Ctrl while right clicking on an [[EiffelBuild Notation|object]] in the Builder Window creates a new [[Object editor|object editor]] targeted to the [[EiffelBuild Notation|object]] . Holding Ctrl and Shift while right clicking on an [[EiffelBuild Notation|object]] , highlights it within the [[Layout constructor|layout constructor]] .}}
==Visual Differences==
@@ -24,7 +24,7 @@ The properties of the [[EiffelBuild Notation|objects]] in you system are always
* 'user_can_resize', 'maximum_width', 'maximum_height' and 'title_string' are not reflected in this window.
* 'minimum_width' and `minimum_height' are not reflected in any of the controls representing [[EiffelBuild Notation|objects]] within this window.
-{{seealso| '''See also'''
+{{seealso|
[[Display window|Display window]]
[[Layout constructor| Layout constructor]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/component-selector.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/component-selector.wiki
index 4d46a4b5..d68dd816 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/component-selector.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/component-selector.wiki
@@ -24,13 +24,13 @@ If the [[EiffelBuild Notation|pick and drop]] completed successfully, then you
To remove a [[EiffelBuild Notation|component]] from your EiffelBuild system, [[EiffelBuild Notation|pick]] it, and then [[EiffelBuild Notation|drop]] it on [[Image:icon-delete-small-color]] in the [[Main toolbar| main toolbar]] .
-{{note| '''Note''': The deletion of a [[EiffelBuild Notation|component]] cannot be undone. }}
+{{note|The deletion of a [[EiffelBuild Notation|component]] cannot be undone. }}
==Viewing a component==
To view an existing component, use the [[Component viewer|component_viewer]] .
-{{seealso| '''See also'''
+{{seealso|
[[Component viewer|Component_viewer]]
[[Builder window|Builder window]]
[[Layout constructor| Layout Constructor]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/component-viewer.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/component-viewer.wiki
index aaad1e5f..03588556 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/component-viewer.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/component-viewer.wiki
@@ -19,9 +19,9 @@ Looking at the left-hand screenshot above, you can see that the [[Image:icon-co
* '''Builder view''' - This view is similar to the view used by the [[Display window|display window]] . i.e. the [[EiffelVision Introduction|EiffelVision2]] controls are displayed exactly as is defined in the [[EiffelBuild Notation|component]] .
* '''Display view''' - This view is similar to the view used by the [[Builder window|builder window]] . i.e. all [[EiffelVision Introduction|EiffelVision2]] containers are represented by frames so they are immediately visible. This makes the actual structure represented by the [[EiffelBuild Notation|component]] completely visible.
-{{note| '''Note''': The type of the "root_object" within the component is displayed in the toolbar of the component viewer. }}
+{{note|The type of the "root_object" within the component is displayed in the toolbar of the component viewer. }}
-{{seealso| '''See also'''
+{{seealso|
[[Builder window|Builder window]]
[[Layout constructor| Layout constructor]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/constants.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/constants.wiki
index 1e17d9b6..49a83bda 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/constants.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/constants.wiki
@@ -30,7 +30,7 @@ To add a new constant to your project, select the type of the constant that you
* '''Font''' - Enter a name in the "Name" field, and then select "New" which displays a font dialog. Selecting a font from this dialog and pressing "OK" adds the new font constant to the project.
* '''Color''' - Enter a name in the "Name" field, and then select "New" which displays a color dialog. Selecting a color from this dialog and pressing "OK" adds the new color constant to the project.
-{{note| '''Note''': After adding a new constant, it is immediately displayed with all constants in the dialog. }}
+{{note|After adding a new constant, it is immediately displayed with all constants in the dialog. }}
===Modifying an existing constant===
@@ -50,7 +50,7 @@ To remove a constant from the project, select it in the multi column list, and s
As objects are reliant on the constant you are removing, you must confirm that you really wish to remove it from the system. If you select "OK", the constant is removed, and the object property relying on that constant is converted to a manifest value. For example, if you are using an Integer constant with a value of 100, and you remove the constant, the property no longer references the constant, but is set explicitly to 100.
-{{note| '''Note''': You may sort the constants displayed in the dialog, by clicking the associated column header. }}
+{{note|You may sort the constants displayed in the dialog, by clicking the associated column header. }}
==String constant==
@@ -148,7 +148,7 @@ The Pixmap Constant dialog is used to select pixmaps for addition to an EiffelBu
[[Image:pixmap-selection-dialog]]
An individual pixmap may be selected, or a whole directory of pixmaps may be selected from this dialog for addition. In the screenshot above, a directory containing two pixmaps was selected. The "Build from" option at the bottom of the dialog permits you to select if you wish to add an absolute or relative pixmap, and if multiple pixmaps are being added, the currently selected pixmap from the list above is active. The relative "DIRECTORY" for relative pixmaps is filled in automatically if EiffelBuild finds a directory constant in the system that matches the path chosen. If not, you may enter a name in this field to create a new directory matching the required path. If you do not enter a directory name for one or more relative pixmaps, upon closing the dialog, you will be prompted to enter a name for a directory constant used for these pixmaps.
-{{note| '''Note''': If you are selecting new pixmaps, and they appear in the dialog as unchecked, it means that an equivalent pixmap already exists in the project. }}
+{{note|If you are selecting new pixmaps, and they appear in the dialog as unchecked, it means that an equivalent pixmap already exists in the project. }}
==Loading constants==
@@ -162,9 +162,9 @@ By default, all constant values are hard coded into the implementation class, bu
Constants may be associated to properties of your [[EiffelBuild Notation|objects]] via an [[Object editor|object editor]] targeted to that [[EiffelBuild Notation|object]] . The [[Image:icon-format-onces-color]] button denotes the use of a constant value. For more information regarding using constants, in [[Object editor|object editors]] , see [[Object editor|object editor]] .
When an EiffelBuild project is generated, all constants are added to a class, inherited by each window class. There is an "_IMP" and interface versions of these classes as with each window. For more information regarding the generation of constants, see [[EiffelBuild: Code Generation|code generation]] .
-{{note| '''Note''': To modify pixmap constants based on the current installation of an EiffelBuild generated interface, simply redefine the Directory constant used to access the pixmaps within the interface constants class (not "_IMP"), which is not re-generated if it already exists. }}
+{{note|To modify pixmap constants based on the current installation of an EiffelBuild generated interface, simply redefine the Directory constant used to access the pixmaps within the interface constants class (not "_IMP"), which is not re-generated if it already exists. }}
-{{seealso| '''See also''':
+{{seealso|
[[EiffelBuild: Code Generation|Code generation]]
[[Object editor|Object editor]]
[[EiffelBuild: Project settings window|Project settings]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/display-window.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/display-window.wiki
index fc94cd5d..f5d57c8d 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/display-window.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/display-window.wiki
@@ -11,7 +11,7 @@ This view is provided so that you can really see what your project will look lik
All properties that have been set on the [[EiffelBuild Notation|objects]] in your project are set in the [[EiffelVision Introduction|EiffelVision2]] control matching its type.
-{{seealso| '''See Also'''
+{{seealso|
[[Builder window|Builder window]]
[[Layout constructor|Layout constructor]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-code-generation.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-code-generation.wiki
index 6af4f64a..a8627f53 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-code-generation.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-code-generation.wiki
@@ -21,7 +21,7 @@ If the "generate as client" option is selected for a particular object (changeab
[[Image:class-project-diagram-client]]
-{{note| '''Note''': All other diagrams on this page show only the non client version of the settings, where the generated widget inherits from the EiffelVision class. }}
+{{note|All other diagrams on this page show only the non client version of the settings, where the generated widget inherits from the EiffelVision class. }}
==Project build type==
@@ -40,11 +40,11 @@ The choice to generate an interface and an implementation class for the windows
Using this mechanism, you can generate your initial system using EiffelBuild, and implement any event features that have been generated (in the interface) by EiffelBuild. If you then decide that you wish to modify the look and the feel of the interface, you can return to EiffelBuild, make the necessary adjustments and then re-generate the system.
-{{note| '''Note''': When returning to EiffelBuild to modify the interface, if you delete or rename controls, then it is quite possible that you will break your existing code. Care should be taken with all changes of this type. }}
+{{note|When returning to EiffelBuild to modify the interface, if you delete or rename controls, then it is quite possible that you will break your existing code. Care should be taken with all changes of this type. }}
Looking at a generated system, you will see that the [[Object editor|events]] connected to your controls are defined as deferred in the implementation and actually implemented in the interface class. This means that if you return to EiffelBuild with a previously generated system, and add a new event to a control, then you will have to implement the definition in the interface class yourself (as the class interface class is not re-generated).
-{{seealso| '''See also''':
+{{seealso|
[[EiffelBuild: Project settings window|Project settings]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/docking.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/docking.wiki
index 3918c969..b0cb3f98 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/docking.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/docking.wiki
@@ -16,7 +16,7 @@ The tool may now be freely moved to any location on screen, in the same fashion
** '''Closing the window''' - Clicking the cross displayed to the right hand side of the windows title bar causes the window to be destroyed, and the tool contained to be restored back to its original position within the main window.
-{{note| '''Note''': The position of tools that have been docked, is maintained automatically between EiffelBuild sessions. When a new project is opened, they are restored to the positions that they had during the last use. }}
+{{note|The position of tools that have been docked, is maintained automatically between EiffelBuild sessions. When a new project is opened, they are restored to the positions that they had during the last use. }}
==Main window with externally docked tools==
@@ -24,7 +24,7 @@ The following screenshot illustrates the appearance of the main window with all
[[Image:main-window-with-docked-tools]]
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelBuild: General interface description|General interface description]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/eiffelbuild-key-shortcuts.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/eiffelbuild-key-shortcuts.wiki
index fa137a8f..0837e1cd 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/eiffelbuild-key-shortcuts.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/eiffelbuild-key-shortcuts.wiki
@@ -38,7 +38,7 @@ This page gathers all the keyboard shortcuts available in the environment.
'''Note''': These shortcuts are not always available and are dependent on the state of EiffelBuild. For example, Ctrl+S does nothing if there is no modified project open.
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelBuild: General interface description|General interface description]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/eiffelbuild-window-overview.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/eiffelbuild-window-overview.wiki
index 5db773cf..1845578a 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/eiffelbuild-window-overview.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-general-interface-description/eiffelbuild-window-overview.wiki
@@ -16,7 +16,7 @@ The window contains several different tools, highlighted below:
The [[Type selector|type selector]] , [[Component selector|component selector]] and [[Widget selector|widget selector]] may all be docked from their original position, permitting re-ordering and customization of the main window. Each of these may be docked external to the main window, permitting each to be displayed in their own movable window. For more information regarding the docking mechanism, see [[Docking|docking]] .
-{{seealso| '''See Also'''
+{{seealso|
[[Main toolbar| Main toolbar]]
[[Layout constructor| Layout constructor]]
[[Type selector|Type selector]]
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-preferences.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-preferences.wiki
index 3c46e202..e1256223 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-preferences.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-preferences.wiki
@@ -13,9 +13,9 @@ The button marked "Restore Defaults" in the lower left hand corner of the dialog
When you have finished modifying the preferences, select the "Close" button to close the dialog.
-{{note| '''Note''': The preferences are saved automatically by EiffelBuild, even if the open project is not saved, the preferences are saved whenever a property changes. }}
+{{note|The preferences are saved automatically by EiffelBuild, even if the open project is not saved, the preferences are saved whenever a property changes. }}
-{{seealso| '''See also''':
+{{seealso|
[[EiffelBuild: General interface description|General interface description]]
[[EiffelBuild Reference|EiffelBuild reference]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-project-settings-window/build-tab.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-project-settings-window/build-tab.wiki
index d5c43bd1..2f5a90fb 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-project-settings-window/build-tab.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-project-settings-window/build-tab.wiki
@@ -31,7 +31,7 @@ This entry is used as the name of the constants class generated by EiffelBuild t
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelBuild: Code Generation|Code generation]]
[[EiffelBuild: Project settings window|Project settings window]]
[[Generation Tab|Generation tab]]
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-project-settings-window/index.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-project-settings-window/index.wiki
index 3839cd5a..854c8c09 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-project-settings-window/index.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/eiffelbuild-project-settings-window/index.wiki
@@ -15,7 +15,7 @@ The window is organized as two tabs:
All options are enabled and saved into the project settings file, 'build_project.bpr' as soon as the window is closed.
-{{seealso| '''See Also'''
+{{seealso|
[[EiffelBuild: Code Generation|Code generation]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/history.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/history.wiki
index e76c55b2..517534fc 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/history.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/history.wiki
@@ -25,9 +25,9 @@ Looking at the screenshot above, you will see that the last action in the histor
If you execute an action which will be added to the history while the history is not at the final position, all history events after this current position will be removed, and the history will be up to date again.
-{{note| '''Note''': If you use the history list to move through many recorded actions at once, there may be a slight delay dependent on the systems complexity and steps moved. }}
+{{note|If you use the history list to move through many recorded actions at once, there may be a slight delay dependent on the systems complexity and steps moved. }}
-{{seealso| '''See also'''
+{{seealso|
[[Builder window|Builder window]]
[[Layout constructor| Layout constructor]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/layout-constructor.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/layout-constructor.wiki
index 25ba6540..b30c1e24 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/layout-constructor.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/layout-constructor.wiki
@@ -41,7 +41,7 @@ You may convert an existing widget structure into a locked instance of a widget
{{note|Double clicking on a locked object within the Layout Constructor, targets the object of which it is an instance to the Layout Constructor. }}
-{{seealso| '''See Also'''
+{{seealso|
[[Builder window|Builder window]]
[[Object editor|Object editor]]
[[Display window|Layout window]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/index.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/index.wiki
index 46ca6059..396ef945 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/index.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/index.wiki
@@ -19,7 +19,7 @@ These object editors appear in their own window, and you may open as many of the
To open a new floating object editor, [[EiffelBuild Notation|drop]] an [[EiffelBuild Notation|object]] on [[Image:icon-object-editor-color]] , displayed in the [[Main toolbar| main toolbar]] and also in each existing object editor. The new object editor will then be targeted to the [[EiffelBuild Notation|object]] that was [[EiffelBuild Notation|dropped]] .
-{{note| '''Note''': If the [[EiffelBuild Notation|object]] targeted to floating object editor is deleted, then the editor will be destroyed. This helps stop the screen becoming cluttered with empty editors. }}
+{{note|If the [[EiffelBuild Notation|object]] targeted to floating object editor is deleted, then the editor will be destroyed. This helps stop the screen becoming cluttered with empty editors. }}
As a shortcut to a complete [[EiffelBuild Notation|pick and drop]] transport, you may hold down the Ctrl key while starting the [[EiffelBuild Notation|pick]] , which will immediately open a new floating object editor targeted to the [[EiffelBuild Notation|object]] you clicked.
@@ -33,7 +33,7 @@ When an object editor is targeted to an [[EiffelBuild Notation|object]] , you wi
All properties that may be manipulated in an object editor correspond directly to a property of the [[EiffelVision Introduction|EiffelVision2]] control that is represented by the [[EiffelBuild Notation|object]] (Displayed in an object editor as '''type'''). There is one exception to that rule though, and that is the '''Name''' field which is specific to EiffelBuild. This field is used for your identification of the [[EiffelBuild Notation|object]] and as the attribute name in the generated code. For example, when EiffelBuild generates code corresponding to the [[EiffelBuild Notation|object]] targeted in the editor shown above, it would declare the vision2 component as - button1: EV_BUTTON
-{{note| '''Note''': You may have as many object editors targeted to the same [[EiffelBuild Notation|object]] as you wish. Whenever a change is made to the [[EiffelBuild Notation|object]] through one of the editors, all other editors targeted to that [[EiffelBuild Notation|object]] are synchronized. }}
+{{note|You may have as many object editors targeted to the same [[EiffelBuild Notation|object]] as you wish. Whenever a change is made to the [[EiffelBuild Notation|object]] through one of the editors, all other editors targeted to that [[EiffelBuild Notation|object]] are synchronized. }}
==Using Constants==
@@ -52,7 +52,7 @@ For all "top level" objects (those contained within the [[Widget selector|widget
As well as being able to manipulate the standard properties of an [[EiffelBuild Notation|object]] , facilities are provided for connecting to the events of an [[EiffelBuild Notation|object]] . Looking at the object editor screenshot above, you will see that there is a button marked '''Select events''' which is also available in all targeted editors.
-{{note| '''Note''': The button will be marked '''Modify events''' when one or more events are already selected for the current [[EiffelBuild Notation|object]] . }}
+{{note|The button will be marked '''Modify events''' when one or more events are already selected for the current [[EiffelBuild Notation|object]] . }}
Clicking this button will cause the following dialog to be displayed:
@@ -62,9 +62,9 @@ Looking at the screenshot above, you will see that this dialog contains all the
If you check a button connected with one of the action sequences, you will be then able to enter the name of a feature that you wish to connect to the action sequence. The screenshot above shows the user has connected a feature named `button_pressed' to the `select_actions'. When [[EiffelBuild: Code Generation|code is generated]] , this will cause EiffelBuild to generate an empty feature named `button_pressed' already connected to the `select_actions' of the button.
-{{note| '''Note''': You will only be allowed to enter valid and unique Eiffel feature names. If a name is invalid, it will be highlighted in red, and a dialog will warn you when you attempt to close the dialog. }}
+{{note|You will only be allowed to enter valid and unique Eiffel feature names. If a name is invalid, it will be highlighted in red, and a dialog will warn you when you attempt to close the dialog. }}
-{{seealso| '''See Also'''
+{{seealso|
[[Create an object|Create an object]]
[[Delete an object|Delete an object]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/merging-radio-button-groups.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/merging-radio-button-groups.wiki
index 08ee061a..3873bebb 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/merging-radio-button-groups.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/merging-radio-button-groups.wiki
@@ -10,7 +10,7 @@ With this control, you can merge two or more instances of EV_CONTAINEREV_CONTAINER, and [[EiffelBuild Notation|drop]] it anywhere on the control. This will merge the radio button group of the EV_CONTAINER referenced in the object editor, to the transported one. Each merge, will show up as a new item in the control.
-{{note| '''Note''': Container objects may only be grouped once, and as such, you will not be permitted to add an [[EiffelBuild Notation|object]] that is already contained in the list. }}
+{{note|Container objects may only be grouped once, and as such, you will not be permitted to add an [[EiffelBuild Notation|object]] that is already contained in the list. }}
==Unmerging==
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/positioning-fixed-children.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/positioning-fixed-children.wiki
index 4b3b7174..3c452604 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/positioning-fixed-children.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/positioning-fixed-children.wiki
@@ -7,7 +7,7 @@ If the current [[EiffelBuild Notation|object]] in the object editor is of type
* '''Moving''' - Press and hold the left mouse button within the selected child, and move the mouse.
* '''Resizing''' - Move the mouse over the border of the child, until the cursor changes to a resize cursor, then press and hold the left mouse button to re-size the child.
-{{note| '''Note''': As placing a child in an EV_FIXED does not modify the size of the child, it is possible that some children have a size of 0x0 pixels, and hence do not show up in the diagram. In this case, there will be the following displayed in the status bar "Widget is 0x0 pixels, click HERE to enlarge". If you subsequently click on the status bar, then the widget will be enlarged to a more useful size. }}
+{{note|As placing a child in an EV_FIXED does not modify the size of the child, it is possible that some children have a size of 0x0 pixels, and hence do not show up in the diagram. In this case, there will be the following displayed in the status bar "Widget is 0x0 pixels, click HERE to enlarge". If you subsequently click on the status bar, then the widget will be enlarged to a more useful size. }}
==Grid Properties==
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/positioning-table-children.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/positioning-table-children.wiki
index b95e1aba..46460729 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/positioning-table-children.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/object-editor/positioning-table-children.wiki
@@ -9,7 +9,7 @@ Each of the children are displayed on a grid representing the table cells that e
* '''Moving''' - Press and hold the left mouse button within the selected child, and move the mouse.
* '''Resizing''' - Move the mouse over the border of the child, until the cursor changes to a resize cursor, then press and hold the left mouse button to re-size the child.
-{{note| '''Note''': Each child, may only occupy a unique set of cells within the table, and if you attempt to move or re-size a child to an invalid position, it will be displayed in gray. }}
+{{note|Each child, may only occupy a unique set of cells within the table, and if you attempt to move or re-size a child to an invalid position, it will be displayed in gray. }}
When you have finished manipulating the children of the table, click the button marked "Done" to close the dialog.
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/type-selector.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/type-selector.wiki
index 23cac0a2..8dfd9b3e 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/type-selector.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/type-selector.wiki
@@ -7,7 +7,7 @@ The type selector contains all the available Vision2 types supported by EiffelBu
The types are organized into three groups - Primitives, Containers and Items. All types that may be used in EiffelBuild have a text in uppercase, corresponding to their type in [[EiffelVision Introduction|EiffelVision2]] . For example, looking at the screenshot above, the BUTTON item represents an EV_BUTTON, and the EV_COMBO_BOX item represents EV_COMBO_BOX.
-{{note| '''Note''': The types available in the type selector are fixed, and cannot be modified. Almost all [[EiffelVision Introduction|EiffelVision2]] components are available. }}
+{{note|The types available in the type selector are fixed, and cannot be modified. Almost all [[EiffelVision Introduction|EiffelVision2]] components are available. }}
==Creating a new object==
[[EiffelBuild Notation|Objects]] are the building blocks used in EiffelBuild to construct your interface. To create a new [[EiffelBuild Notation|object]] for use in your system, [[EiffelBuild Notation|pick]] the type corresponding to the type of object you wish to create,and [[EiffelBuild Notation|drop]] onto an [[EiffelBuild Notation|object]] representation. If an object is full, or does not allow other objects of the new type to be contained, then you will not be able to [[EiffelBuild Notation|drop]] on it.
@@ -18,7 +18,7 @@ This shows how simple it is to Build new [[EiffelBuild Notation|objects]] in Ei
You may drop an object directly from the Type Selector into the [[Widget selector|widget selector]] which creates the object as a "top level object" ensuring that upon generation, it is represented by an individual set of classes. These top level objects may then be re-used within your interface as desired.
-{{note| '''Note''': To understand the types accepted, and the capacity of objects, you should consult the [[EiffelVision Introduction|EiffelVision2]] library reference. }}
+{{note|To understand the types accepted, and the capacity of objects, you should consult the [[EiffelVision Introduction|EiffelVision2]] library reference. }}
==Changing the type of an existing object==
@@ -32,7 +32,7 @@ The following rules govern if the type of an existing object may be changed to a
* The parent of the existing [[EiffelBuild Notation|object]] must accept children of type corresponding to the new type.
* The new type must be able to accept all of the existing [[EiffelBuild Notation|objects]] children.
-{{seealso| '''See Also'''
+{{seealso|
[[Layout constructor|Layout constructor]]
}}
diff --git a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/widget-selector.wiki b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/widget-selector.wiki
index 0871159b..dc58dc1e 100644
--- a/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/widget-selector.wiki
+++ b/documentation/current/solutions/gui-building/eiffelbuild/eiffelbuild-reference/widget-selector.wiki
@@ -11,7 +11,7 @@ To add an Object to your project, [[EiffelBuild Notation|pick]] the object type
* '''The Widget Selector itself''' - The newly created object is added to the root directory of the project.
* '''A Directory node''' - The newly created object is added to the directory that was the target of the drop.
Both of these outcomes create a new object in your project that is to be generated as an individual class during code generation.
-{{note| '''Note''': The selected object in the Widget Selector is automatically targeted as the root window of the [[Layout constructor|layout constructor]] , permitting building. You may not build directly into the representation of an object within the Widget Selector, as this must be performed within the [[Layout constructor|layout constructor]] or [[Builder window|builder window]] . }}
+{{note|The selected object in the Widget Selector is automatically targeted as the root window of the [[Layout constructor|layout constructor]] , permitting building. You may not build directly into the representation of an object within the Widget Selector, as this must be performed within the [[Layout constructor|layout constructor]] or [[Builder window|builder window]] . }}
==Root Window==
@@ -27,10 +27,10 @@ The ability to add directories to your project permit organization of objects in
Enter a unique name that is not already in use, and select "OK" to add the directory to your project. The newly added directory is then visible, as a node in the Widget Selector.
-{{note| '''Note''': Creating a new directory in the Widget Selector causes the actual directory on the disk to be created immediately. }}
+{{note|Creating a new directory in the Widget Selector causes the actual directory on the disk to be created immediately. }}
You may insert objects into a directory, or move an object between directories by [[EiffelBuild Notation|picking]] the object from its representation in the Widget Selector, and [[EiffelBuild Notation|dropping]] on the desired directory. Each object contained in the Widget Selector is generated as a seperate class and the parent directory is used as the generated location on disk.
-{{note| '''Note''': If you move an object between directories within an EiffelBuild project that has already generated the Eiffel code for that object, the code files are moved immediately on the disk. }}
+{{note|If you move an object between directories within an EiffelBuild project that has already generated the Eiffel code for that object, the code files are moved immediately on the disk. }}
Directories may be nested as deeply as required, and the following buttons are available to help with directory nesting:
* [[Image:directory-search-small]] Selecting this button recursively adds all directories from the current project location to the project.
@@ -50,7 +50,7 @@ The OK_CANCEL_BUTTONS object is used is used in two different places within the
To use an instance of a widget contained within the Widget Selector as a client, simply pick the representation of the object and drop into the desired parent object within the [[Type selector|type selector]]
-{{seealso| '''See also''':
+{{seealso|
[[Layout constructor|Layout constructor]] }}
diff --git a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/accelerator-sample.wiki b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/accelerator-sample.wiki
index 47ef3581..d876f8bb 100644
--- a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/accelerator-sample.wiki
+++ b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/accelerator-sample.wiki
@@ -22,7 +22,7 @@ This sample contains the following class:
* ACCELERATOR
-{{seealso| '''See Also'''
+{{seealso|
[[ref:/libraries/vision2/reference/ev_accelerator_chart|EV_ACCELERATOR]]
[[ref:/libraries/vision2/reference/ev_key_chart|EV_KEY]]
}}
diff --git a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/gauges-sample.wiki b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/gauges-sample.wiki
index 5c3a37a5..d2416942 100644
--- a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/gauges-sample.wiki
+++ b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/gauges-sample.wiki
@@ -26,7 +26,7 @@ This sample contains the following class:
* GAUGES
-{{seealso| '''See Also'''
+{{seealso|
EV_GAUGE
EV_SCROLL_BAR
EV_RANGE
diff --git a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/viewport-sample.wiki b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/viewport-sample.wiki
index 85cfa415..e13a4c1d 100644
--- a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/viewport-sample.wiki
+++ b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-2-samples/viewport-sample.wiki
@@ -26,7 +26,7 @@ This sample contains the following class:
* VIEWPORT
-{{seealso| '''See Also'''
+{{seealso|
EV_VIEWPORT
EV_SPIN_BUTTON
[[ref:/libraries/vision2/reference/ev_button_chart|EV_BUTTON]]
diff --git a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/kernel.wiki b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/kernel.wiki
index 1fee8dda..2bbcaab9 100644
--- a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/kernel.wiki
+++ b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/kernel.wiki
@@ -7,7 +7,7 @@ The kernel cluster contains classes that provide functionality that are common t
[[ref:libraries/vision2/reference/ev_application_chart|EV_APPLICATION]] is the basis for every Vision2 application and is considered the most important class in the library. It is responsible for initializing the underlying toolkit that is driving the windowing system on the platform that you decide to compile your system on. It also also where the main event loop that drives your application is executed.
-{{note| '''Note:''' It is ''' not''' possible to create a Vision2 component unless an application exists (query [[ref:/libraries/vision2/reference/ev_environment_chart|EV_ENVIRONMENT]] ). }}
+{{note|It is ''' not''' possible to create a Vision2 component unless an application exists (query [[ref:/libraries/vision2/reference/ev_environment_chart|EV_ENVIRONMENT]] ). }}
You may inherit [[ref:libraries/vision2/reference/ev_application_chart|EV_APPLICATION]] or use it as a client in order to create your vision2 application. A simple method of using EV_APPLICATION is as follows:
# Create an instance of EV_APPLICATION.
# Create one or more windows for your application.
@@ -71,7 +71,7 @@ This is the same Vision2 application but instead using [/libraries/visio
==What does Launch actually do?==
In Vision2, to launch an application means to pass control to the underlying graphical toolkit. Simply creating an application does not launch it. An explicit call to launch is required for the event processing to begin.
-{{note| '''Note: '''A Vision2 system is event based. This means that you do not have control of the execution within a Vision2 system, but must respond appropriately to [[Events|events]] as they occur. Therefore, if you call launch on an [[ref:libraries/vision2/reference/ev_application_chart|EV_APPLICATION]] , the processing for the application will continue indefinitely unless you have provided a way to exit the application. It is essential to initialize your components correctly, so your application can be exited (call destroy on the application). }}
+{{note|A Vision2 system is event based. This means that you do not have control of the execution within a Vision2 system, but must respond appropriately to [[Events|events]] as they occur. Therefore, if you call launch on an [[ref:libraries/vision2/reference/ev_application_chart|EV_APPLICATION]] , the processing for the application will continue indefinitely unless you have provided a way to exit the application. It is essential to initialize your components correctly, so your application can be exited (call destroy on the application). }}
==Building your application skeleton==
diff --git a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/properties/eiffelvision-pick-and-drop.wiki b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/properties/eiffelvision-pick-and-drop.wiki
index da57ff60..0d635cb4 100644
--- a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/properties/eiffelvision-pick-and-drop.wiki
+++ b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/properties/eiffelvision-pick-and-drop.wiki
@@ -19,7 +19,7 @@ A simple example of this is demonstrated here:
As print takes an argument of type [[ref:/libraries/base/reference/string_8_chart|STRING_8]] , button2 becomes a valid target for the pebble contained in button1. Right clicking the mouse pointer over the '''source''' will start the transport, and right clicking with the mouse pointer over a valid '''target''' will end the transport. The transport can be canceled anytime with a simple left click, just as you would do in EiffelStudio.
-{{note| '''Note''': When a transport completes, the '''pebble''' that was transported is passed as an argument to all features in the '''targets'''drop_actions whose argument type matches the '''pebble''' }}
+{{note|When a transport completes, the '''pebble''' that was transported is passed as an argument to all features in the '''targets'''drop_actions whose argument type matches the '''pebble''' }}
==Three different modes of transport==
diff --git a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/properties/index.wiki b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/properties/index.wiki
index e304a95f..23f0b25c 100644
--- a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/properties/index.wiki
+++ b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/properties/index.wiki
@@ -30,7 +30,7 @@ Use minimum_width and minimum_height to find i
-{{note| '''Note:''' [[ref:libraries/vision2/reference/ev_containable_chart|EV_CONTAINABLE]] has no features for setting the parent. In Vision2, a child has no features for setting its parent, while a parent such as ev_container contains routines for adding children (one example is extend). }}
+{{note|[[ref:libraries/vision2/reference/ev_containable_chart|EV_CONTAINABLE]] has no features for setting the parent. In Vision2, a child has no features for setting its parent, while a parent such as ev_container contains routines for adding children (one example is extend). }}
The following properties are also used within Vision2:
* [[ref:libraries/vision2/reference/ev_deselectable_chart|EV_DESELECTABLE]]
diff --git a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/widgets/containers.wiki b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/widgets/containers.wiki
index 83d22c34..5f61ee0e 100644
--- a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/widgets/containers.wiki
+++ b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/widgets/containers.wiki
@@ -7,7 +7,7 @@ All Vision2 containers inherit [[ref:libraries/vision2/reference/ev_container_ch
A container is a Vision2 widget that may contain other widgets. Some containers such as [[ref:libraries/vision2/reference/ev_cell_chart|EV_CELL]] may only hold one widget while containers such as [[ref:libraries/vision2/reference/ev_box_chart|EV_BOX]] may hold multiple widgets. As a container is of type [[ref:libraries/vision2/reference/ev_widget_chart|EV_WIDGET]] , this means that a container may be placed within a container. Windows inherit from [[ref:libraries/vision2/reference/ev_cell_chart|EV_CELL]] and are therefore classed as containers also.
-{{note| '''Note: '''Containers may only contain other widgets. Items may only be placed in certain primitives. For example, an [[ref:libraries/vision2/reference/ev_list_item_chart| EV_LIST_ITEM]] may be contained in an [[ref:libraries/vision2/reference/ev_list_chart| EV_LIST]] . }}
+{{note|Containers may only contain other widgets. Items may only be placed in certain primitives. For example, an [[ref:libraries/vision2/reference/ev_list_item_chart| EV_LIST_ITEM]] may be contained in an [[ref:libraries/vision2/reference/ev_list_chart| EV_LIST]] . }}
==Inheritance from Base==
@@ -47,7 +47,7 @@ The mapping of a Vision2 container interface is very close to that of containers
* To empty a container call `wipe_out'.
* To traverse the container, you can use features such as start, forth, item and off.
-{{note| '''Note''': When a widget is added to a container, the container is the parent of the widget. }}
+{{note|When a widget is added to a container, the container is the parent of the widget. }}
==Size of widget within a container==
@@ -55,7 +55,7 @@ The size of a widget in a container is always at least its minimum size. By defa
==Sizing of containers==
As [[ref:libraries/vision2/reference/ev_container_chart|EV_CONTAINER]] is of type [[ref:libraries/vision2/reference/ev_widget_chart|EV_WIDGET]] , the following facilities are provided for setting the minimum size: set_minimum_width, set_minimum_height and set_minimum_size. It is important to remember that as a general rule, '''the current size of a container is always at least the minimum size of all its contents.'''
-{{note| '''Note: '''The exception to this is: [[ref:libraries/vision2/reference/ev_fixed_chart|EV_FIXED]] , [[ref:libraries/vision2/reference/ev_viewport_chart|EV_VIEWPORT]] and [[ref:libraries/vision2/reference/ev_scrollable_area_chart|EV_SCROLLABLE_AREA]] which do actually allow their contents to be larger than their current size.
+{{note|The exception to this is: [[ref:libraries/vision2/reference/ev_fixed_chart|EV_FIXED]] , [[ref:libraries/vision2/reference/ev_viewport_chart|EV_VIEWPORT]] and [[ref:libraries/vision2/reference/ev_scrollable_area_chart|EV_SCROLLABLE_AREA]] which do actually allow their contents to be larger than their current size.
}}
diff --git a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/widgets/index.wiki b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/widgets/index.wiki
index a8d5c32a..f3d1e367 100644
--- a/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/widgets/index.wiki
+++ b/documentation/current/solutions/gui-building/eiffelvision-2/eiffelvision-library-reference-manual/widgets/index.wiki
@@ -30,7 +30,7 @@ This would be in place of
a_button.set_text ("Click Me")
-{{note|Note: When a widget is created no extra initialization has to be performed. '''The only exception is for a window where you have to call show in order for it to be displayed on screen'''. }}
+{{note|When a widget is created no extra initialization has to be performed. '''The only exception is for a window where you have to call show in order for it to be displayed on screen'''. }}
==Sizing==
@@ -38,7 +38,7 @@ As [[ref:libraries/vision2/reference/ev_primitive_chart|EV_PRIMITIVE]] is of ty
The minimum size of a widget is the smallest possible size that it can possibly be inside its parent container. If an [[ref:libraries/vision2/reference/ev_button_chart|EV_BUTTON]] was created and set with a minimum_size of width/height (100, 100), if this button was inserted in to an [[ref:libraries/vision2/reference/ev_horizontal_box_chart| EV_HORIZONTAL_BOX]] , then the box's size could never be below (100, 100) or it would break the minimum size of the button. '''The size of a container must always be greater or equal to the minimum sizes of its children.'''
-{{note| '''Note: '''In Vision2, there is no way to set the current size of the primitive. The current size is dependent on the size of the parent or the minimum_size. }}
+{{note|In Vision2, there is no way to set the current size of the primitive. The current size is dependent on the size of the parent or the minimum_size. }}
==Now what do I do?==
Now that you can create a widget, you will need to actually make it usable to your intended user. This will usually involve these three steps.
diff --git a/documentation/current/solutions/other-languages/cecil/cecil-interface-overview.wiki b/documentation/current/solutions/other-languages/cecil/cecil-interface-overview.wiki
index 68660124..b67f11be 100644
--- a/documentation/current/solutions/other-languages/cecil/cecil-interface-overview.wiki
+++ b/documentation/current/solutions/other-languages/cecil/cecil-interface-overview.wiki
@@ -14,9 +14,9 @@ The EIFFEL include files define types for every EIFFEL types:
Generally, you should use these types when implementing external C functions bound to be used from Eiffel or when you want to manipulate Eiffel objects from the C side. EIF_REFERENCE, EIF_OBJECT, EIF_POINTER all correspond in C to a (char *), but their semantic remains different in Eiffel.
-{{note|'''Note:''' In the following code samples, the class OBJECT is a placeholder for one of your type that you wish to use via CECIL.}}
+{{note|In the following code samples, the class OBJECT is a placeholder for one of your type that you wish to use via CECIL.}}
-{{sample| '''Sample''': Calling C external `foo' from Eiffel, which takes a pointer and an eiffel object of type OBJECT as arguments and returns an INTEGER. }}
+{{sample|Calling C external `foo' from Eiffel, which takes a pointer and an eiffel object of type OBJECT as arguments and returns an INTEGER. }}
c_foo (ptr: POINTER; obj: OBJECT): INTEGER is
@@ -118,7 +118,7 @@ EIF_INTEGER foo (EIF_POINTER ptr, EIF_OBJECT obj);
'''Important rules when using eif_access:'''
-{{note| '''Note''': The first argument of ''(ep)'' is the target of the function (the eiffel object to which you want to apply the Eiffel feature ''(ep)'') and the second argument corresponds to the first argument of ` ''print'''. Any Eiffel object could have been the 1st argument of ''(ep)'' since all of them inherit ''ANY''. }}
+{{note|The first argument of ''(ep)'' is the target of the function (the eiffel object to which you want to apply the Eiffel feature ''(ep)'') and the second argument corresponds to the first argument of ` ''print'''. Any Eiffel object could have been the 1st argument of ''(ep)'' since all of them inherit ''ANY''. }}
* '''Never pre compute the value returned by eif_access. '''
@@ -262,7 +262,7 @@ main (int argc,char **argv,char **envp)
-{{note| '''Note''': `eif_create' does not call any creation procedure. It just allocates memory and initializes an object. }}
+{{note|`eif_create' does not call any creation procedure. It just allocates memory and initializes an object. }}
===Protecting the objects returned by Eiffel functions.===
@@ -309,7 +309,7 @@ main (int argc,char **argv,char **envp)
-{{note| '''Note''': Although you must protect Eiffel references returned by eif_attribute, you do not have to protect attributes of basic types - they are not Eiffel references and not supposed to move. }}
+{{note|Although you must protect Eiffel references returned by eif_attribute, you do not have to protect attributes of basic types - they are not Eiffel references and not supposed to move. }}
===Getting the type id of an Eiffel type: eif_type_id===
'''# include "eif_gen_conf. h"''' # include "eif_gen_conf. h"
@@ -375,7 +375,7 @@ EIF_REFERENCE eif_wean(EIF_OBJECT object)
Tell the GC to remove the artificial reference to the nested Eiffel reference returned by eif_access (object). Then, the GC will be able to collect this nested object, as soon as it is not referenced from Eiffel any longer.
-{{note| '''Note:''' Object must have been previously created with eif_adopt, eif_protect or eif_create. }}
+{{note|Object must have been previously created with eif_adopt, eif_protect or eif_create. }}
eif_wean (object) returns an Eiffel reference, which corresponds to eif_access (object). After a call to eif_wean (object), eif_access (object) is NULL, which does not mean that the nested Eiffel object is Void, but that the indirection pointer does not reference it any longer. It is possible to reuse object later on.
Calling eif_wean (external_argument) where external_argument is an Eiffel object given by a C external can cause erratic behaviors. Indeed, external_argument is an indirection pointer, which is automatically deleted after the external call (not the nested Eiffel object), deleting it prematurely can corrupt the indirection pointers stack.
See also
eif_access.
@@ -423,7 +423,7 @@ RETURN VALUE:
upon failure, it returns (EIFFEL_TYPE) 0, otherwise, the attribute is returned. If the return value is not a basic type, you must protect it with eif_protect
COMPATIBILITY:
eif_attribute (object, name, type, NULL) is equivalent to eif_field (object, name, type)
-{{tip| '''Tips''': You cannot access a constant attribute, or the result of a function (once or not) with eif_attribute. Use eif_procedure or eif_xx_function instead.
+{{tip|s''': You cannot access a constant attribute, or the result of a function (once or not) with eif_attribute. Use eif_procedure or eif_xx_function instead.
EIF_BOOLEAN attribute_exists (EIF_REFERENCE object, char *name) returns EIF_TRUE or EIF_FALSE depending if the attribute exists or not, is visible or not. }}
@@ -443,7 +443,7 @@ Return the address of the Eiffel routine by giving its name rout_name and the ty
The Eiffel object returned by an Eiffel function must be protected afterwards with 'eif_protect' (this only applies for functions whose addresses are returned by `eif_reference_function', since the other function types returns basic types, which are not Eiffel objects).
-{{note| '''Note''': The address returned by these functions must be called between parenthesis. }}
+{{note|The address returned by these functions must be called between parenthesis. }}
{{warning| '''Caution''': Be sure that the Eiffel routine is not a C External. In this case, you should call directly the C external instead of its Eiffel wrapper. }}
@@ -461,7 +461,7 @@ EIF_REFERENCE eif_string (char *string) /* Macro */
Return the direct reference to an Eiffel string by giving the corresponding C string . The result of eif_string does not reference the C string passed as argument: it copies it, before creating the Eiffel string.
-{{note| '''Notes''': The return value must be protected with eif_protect for later use.
+{{note|s''': The return value must be protected with eif_protect for later use.
The C string must be manually freed by the user, if it has been dynamically allocated. }}
@@ -494,7 +494,7 @@ printf ("type is %d\n"); /* Should be EIF_INTEGER_TYPE since it returns an Ei
-{{tip| '''Tip''': *(EIFFEL_TYPE *) eif_attribute_safe (EIF_REFERENCE object, char *name, int type_int, int *status) can be used for debugging or type checking. It returns the attribute reference of name from the object of type type_int. status contains the status of the function call: it can be EIF_CECIL_OK, EIF_CECIL_ERROR, EIF_NO_ATTRIBUTE or EIF_WRONG_TYPE (type_int does not match with real type of object). }}
+{{tip|*(EIFFEL_TYPE *) eif_attribute_safe (EIF_REFERENCE object, char *name, int type_int, int *status) can be used for debugging or type checking. It returns the attribute reference of name from the object of type type_int. status contains the status of the function call: it can be EIF_CECIL_OK, EIF_CECIL_ERROR, EIF_NO_ATTRIBUTE or EIF_WRONG_TYPE (type_int does not match with real type of object). }}
===Getting the class name corresponding to a type id: eif_name===
''' #include "eif_cecil. h"'''
diff --git a/documentation/current/solutions/other-languages/cecil/compiling-eiffel-system-cecil.wiki b/documentation/current/solutions/other-languages/cecil/compiling-eiffel-system-cecil.wiki
index 98d97731..e8b61b6b 100644
--- a/documentation/current/solutions/other-languages/cecil/compiling-eiffel-system-cecil.wiki
+++ b/documentation/current/solutions/other-languages/cecil/compiling-eiffel-system-cecil.wiki
@@ -21,7 +21,7 @@ Note that through CECIL you can use an Eiffel system compiled in any of the Eiff
* Finalized C code.
* Workbench (melted/frozen) code, usually for development purposes. In this case you must copy the ''
.melted'' file ( where '''' is the name of your system) located in EIFGENs\\W_code to the directory where you intend to execute your C application from.
-{{note| '''Note''': each time you melt the Eiffel system, the ''. melted'' file is updated. }}
+{{note|each time you melt the Eiffel system, the ''. melted'' file is updated. }}
{{warning| '''Caution''': in the second case (workbench mode), it is not possible to call through the CECIL interface any routine that has been melted in the last compilation; this would raise the run-time exception:
''' $ applied to melted routine'''
diff --git a/documentation/current/solutions/other-languages/cecil/using-cecil-archive.wiki b/documentation/current/solutions/other-languages/cecil/using-cecil-archive.wiki
index 090d7f68..664dfefd 100644
--- a/documentation/current/solutions/other-languages/cecil/using-cecil-archive.wiki
+++ b/documentation/current/solutions/other-languages/cecil/using-cecil-archive.wiki
@@ -6,7 +6,7 @@ The CECIL archive already incorporates the Eiffel run-time. To use the functions
on Unix/linux:
ld -o [name of your CECIL executable] [your C object files and archives]lib.a -lm
-{{note| '''Note''': On Unix, linking with "-lm" is required since the Eiffel run-time uses the standard math libraries. You may need to link with other libraries (for example, on linux: with "-lbsd", in MT mode with "-lpthread" (posix threads) or "-lthread" (solaris)). }}
+{{note|On Unix, linking with "-lm" is required since the Eiffel run-time uses the standard math libraries. You may need to link with other libraries (for example, on linux: with "-lbsd", in MT mode with "-lpthread" (posix threads) or "-lthread" (solaris)). }}
@@ -33,7 +33,7 @@ or , if you are on Windows using MS VC++:
or, if you are on Windows using Borland:
bcc32 -c -I$ISE_EIFFEL\studio\spec\windows\include -I -D your_file.c
-{{sample| '''Sample''': if you want to use the multithreaded facilities of Eiffel, you should define the EIFFEL MT flags by adding "-DEIF_THREADS" to the command line and follow the instructions of your C compiler and platform to find out which additional flags you may need '''. For example:''' on Solaris you need to add "-DSOLARIS_THREADS -D_REENTRANT". }}
+{{sample|if you want to use the multithreaded facilities of Eiffel, you should define the EIFFEL MT flags by adding "-DEIF_THREADS" to the command line and follow the instructions of your C compiler and platform to find out which additional flags you may need '''. For example:''' on Solaris you need to add "-DSOLARIS_THREADS -D_REENTRANT". }}
You can specify a Makefile in your configuration file, so that your C files will be compiled automatically after the Eiffel compilation and before the final linking. See [[Externals Options|the manipulation of external]] in the project settings to add $PATH_TO_MAKEFILE/your_makefile.
@@ -61,7 +61,7 @@ int main(int argc, char **argv, char **envp)
EIF_DISPOSE_ALL
}
-{{note| '''Notes''':
+{{note|s''':
The above mentioned macros must imperatively be in the body of the "main" function for the Eiffel exception handling mechanism to work correctly. You also need to add the Eiffel run time directory to the list of directories in which the C compiler searches for include files. You can do so by using the "-I" option of your C compiler. You can only link one CECIL library into your C applications at a time. }}
{{warning| '''Caution''': Even though external object files and archives are correctly specified in the "object" clause of the configuration file, you will need to explicitly link them to your C application. }}
diff --git a/documentation/current/solutions/other-languages/eiffel-external-mechanism/obsolete-external-interfaces/c-externals.wiki b/documentation/current/solutions/other-languages/eiffel-external-mechanism/obsolete-external-interfaces/c-externals.wiki
index b7ade45d..4ac4decc 100644
--- a/documentation/current/solutions/other-languages/eiffel-external-mechanism/obsolete-external-interfaces/c-externals.wiki
+++ b/documentation/current/solutions/other-languages/eiffel-external-mechanism/obsolete-external-interfaces/c-externals.wiki
@@ -190,7 +190,7 @@ In WEL, the encapsulation is written as:
"SendMessage"
end
-{{seealso| '''See also'''
+{{seealso|
[[C++ Externals|C++ externals]] }}
diff --git a/documentation/current/solutions/other-languages/eiffel2java/eiffel2java-tutorial.wiki b/documentation/current/solutions/other-languages/eiffel2java/eiffel2java-tutorial.wiki
index 759475cd..6f09c162 100644
--- a/documentation/current/solutions/other-languages/eiffel2java/eiffel2java-tutorial.wiki
+++ b/documentation/current/solutions/other-languages/eiffel2java/eiffel2java-tutorial.wiki
@@ -51,7 +51,7 @@ Access to Java classes. Static methods and attributes are accessed via this clas
This class gives Eiffel access to Java objects. You can use it directly or inherit from to and create a more convenient Eiffel class that makes the Java object look like an Eiffel object. The Eiffel representation of a Java Object.
-{{warning| '''Warning:''' to access the static fields or routines of a Java Class, you have to use the features of a JAVA_CLASS instance!! }}
+{{warning|to access the static fields or routines of a Java Class, you have to use the features of a JAVA_CLASS instance!! }}
===JAVA_EXTERNALS===
diff --git a/documentation/current/solutions/text-processing/eiffellex/eiffellex-tutorial.wiki b/documentation/current/solutions/text-processing/eiffellex/eiffellex-tutorial.wiki
index a22b68e1..3b4fe42f 100644
--- a/documentation/current/solutions/text-processing/eiffellex/eiffellex-tutorial.wiki
+++ b/documentation/current/solutions/text-processing/eiffellex/eiffellex-tutorial.wiki
@@ -171,7 +171,7 @@ If you do not want to make the class a descendant of [[ref:/libraries/base/refer
To analyze a text, call set_file or set_string to specify the document to be parsed. With the first call, the analysis will be applied to a file; with the second, to a string.
-{{note| '''Note''': if you use procedure analyze of [[ref:/libraries/lex/reference/scanning_chart|SCANNING]] , you do not need any such call, since analyze calls set_file on the file name passed as argument. }}
+{{note|if you use procedure analyze of [[ref:/libraries/lex/reference/scanning_chart|SCANNING]] , you do not need any such call, since analyze calls set_file on the file name passed as argument. }}
===Obtaining the tokens===
@@ -354,7 +354,7 @@ You may freely combine the various construction mechanisms to describe complex r
===Dealing with keywords===
Many languages to be analyzed have keywords - or, more generally, "reserved words". Eiffel, for example, has reserved words such as class and Result .
-{{note| '''Note''': in Eiffel terminology reserved words include keywords; a keyword is a marker playing a purely syntactical role, such as class . Predefined entities and expressions such as Result and Current , which have an associated value, are considered reserved words but not keywords. The present discussion uses the term "keyword" although it can be applied to all reserved words. }}
+{{note|in Eiffel terminology reserved words include keywords; a keyword is a marker playing a purely syntactical role, such as class . Predefined entities and expressions such as Result and Current , which have an associated value, are considered reserved words but not keywords. The present discussion uses the term "keyword" although it can be applied to all reserved words. }}
In principle, keywords could be handled just as other token types. In Eiffel, for example, one might treat each reserved words as a token type with only one specimen; these token types would have names such as Class or Then and would be defined in the lexical grammar file:
@@ -386,7 +386,7 @@ BOOLEAN
{{warning| '''Caution''': every keyword in the keyword section must be a specimen of one of the token types defined for the grammar, and that token type must be the last one defined in the lexical grammar file, just before the '''Keywords''' line. So in Eiffel where the keywords have the same lexical structure as identifiers, the last line before the keywords must be the definition of the token type ''Identifier'', as shown above. }}
-{{note| '''Note''': the rule that all keywords must be specimens of one token type is a matter of convenience and simplicity, and only applies if you are using SCANNING and lexical grammar files. There is no such restriction if you rely directly on the more general facilities provided by [[ref:/libraries/lex/reference/metalex_chart|METALEX]] or [[ref:/libraries/lex/reference/lex_builder_chart|LEX_BUILDER]] . Then different keywords may be specimens of different regular expressions; you will have to specify the token type of every keyword, as explained later in this chapter. }}
+{{note|the rule that all keywords must be specimens of one token type is a matter of convenience and simplicity, and only applies if you are using SCANNING and lexical grammar files. There is no such restriction if you rely directly on the more general facilities provided by [[ref:/libraries/lex/reference/metalex_chart|METALEX]] or [[ref:/libraries/lex/reference/lex_builder_chart|LEX_BUILDER]] . Then different keywords may be specimens of different regular expressions; you will have to specify the token type of every keyword, as explained later in this chapter. }}
===Case sensitivity===
@@ -467,7 +467,7 @@ The calls seen so far record a number of regular expressions and keywords, but d
make_analyzer
After that call, you may not record any new regular expression or keyword. The analyzer is usable through attribute analyzer.
-{{note| '''Note''': for readers knowledgeable in the theory of lexical analysis: one of the most important effects of the call to make_analyzer is to transform the non-deterministic finite automaton resulting from calls such as the ones above into a deterministic finite automaton. }}
+{{note|for readers knowledgeable in the theory of lexical analysis: one of the most important effects of the call to make_analyzer is to transform the non-deterministic finite automaton resulting from calls such as the ones above into a deterministic finite automaton. }}
Remember that if you use procedure read_grammar, you need not worry about make_analyzer, as the former procedure calls the latter.
Another important feature of class [[ref:/libraries/lex/reference/metalex_chart|METALEX]] is procedure store_analyzer, which stores the analyzer into a file whose name is passed as argument, for use by later lexical analysis sessions. To retrieve the analyzer, simply use procedure retrieve_analyzer, again with a file name as argument.
diff --git a/documentation/current/solutions/text-processing/eiffelparse/eiffelparse-tutorial.wiki b/documentation/current/solutions/text-processing/eiffelparse/eiffelparse-tutorial.wiki
index 69abae06..b69f6b44 100644
--- a/documentation/current/solutions/text-processing/eiffelparse/eiffelparse-tutorial.wiki
+++ b/documentation/current/solutions/text-processing/eiffelparse/eiffelparse-tutorial.wiki
@@ -53,7 +53,7 @@ Parsing is seldom an end in itself; rather, it serves as an intermediate step fo
Parsing takes care of one of the basic tasks of a document processor: reconstructing the logical organization of a document, which must conform to a certain '''syntax''' (or structure), defined by a '''grammar'''.
-{{note| '''Note''': the more complete name '''syntactic grammar''' avoids any confusion with the ''lexical'' grammars discussed in the [[EiffelLex Tutorial]]. By default, "grammar" with no further qualification will always denote a syntactic grammar. A syntactic grammar normally relies on a lexical grammar, which gives the form of the most elementary components - the tokens - appearing in the syntactic structure. }}
+{{note|the more complete name '''syntactic grammar''' avoids any confusion with the ''lexical'' grammars discussed in the [[EiffelLex Tutorial]]. By default, "grammar" with no further qualification will always denote a syntactic grammar. A syntactic grammar normally relies on a lexical grammar, which gives the form of the most elementary components - the tokens - appearing in the syntactic structure. }}
Once parsing has reconstructed the structure of a document, the document processor will perform various operations on the basis of that structure. For example a compiler will generate target code corresponding to the original text; a command language interpreter will execute the operations requested in the commands; and a documentation tool such as the short and flat-short commands for Eiffel will produce some information on the parsed document. Such operations are called '''semantic actions'''. One of the principal requirements on a good parsing mechanism is that it should make it easy to graft semantics onto syntax, by adding semantic actions of many possible kinds to the grammar.
@@ -109,7 +109,7 @@ An aggregate production defines a construct whose specimens are obtained by conc
This means that a specimen of Conditional (a conditional instruction) is made of the keyword if , followed by a specimen of Then_part_list, followed by zero or one specimen of Else_part (the square brackets represent an optional component), followed by the keyword end .
-{{note| '''Note''': this notation for productions uses conventions similar to those of the book Eiffel: The Language. Keywords are written in '''boldface italics''' and stand for themselves. Special symbols, such as the semicolon, are written in double quotes, as in ";". The [=] symbol means "is defined as" and is more accurate mathematically than plain =, which, however, is often used for this purpose (see "Introduction to the Theory of Programming Languages", Prentice Hall, 1991, for a more complete discussion of this issue). }}
+{{note|this notation for productions uses conventions similar to those of the book Eiffel: The Language. Keywords are written in '''boldface italics''' and stand for themselves. Special symbols, such as the semicolon, are written in double quotes, as in ";". The [=] symbol means "is defined as" and is more accurate mathematically than plain =, which, however, is often used for this purpose (see "Introduction to the Theory of Programming Languages", Prentice Hall, 1991, for a more complete discussion of this issue). }}
A choice production defines a construct whose specimens are specimens of one among a number of specified constructs. For example, the production for construct Type in an Eiffel grammar may read:
Type [=] Class_type | Class_type_expanded | Formal_generic_name | Anchored | Bit_type
@@ -469,7 +469,7 @@ For TERMINAL, only one semantic action makes sense. To avoid an
Often, the semantic procedures need to compute various elements of information. These may be recorded using appropriate attributes of the corresponding construct classes.
-{{note| '''Note''': readers familiar with the theory of parsing and compiling will see that this scheme, using the attributes of Eiffel classes, provides a direct implementation of the "attribute grammar" mechanism. }}
+{{note|readers familiar with the theory of parsing and compiling will see that this scheme, using the attributes of Eiffel classes, provides a direct implementation of the "attribute grammar" mechanism. }}
===Polynomial semantics===
@@ -499,7 +499,7 @@ As an example let us examine the semantics of the Product construct for the poly
Here each relevant construct class has an attribute info used to record the semantic information associated with polynomials and their components, such as child_value, an INTEGER. The post_action takes care of computing the product of all child_values for the children. First, of course, post_action must recursively be applied to each child, to compute its own child_value.
-{{note| '''Note''': recall that an instance of CONSTRUCT is also a node of the abstract syntax tree, so that all the TWO_WAY_TREE features such as child_value, child_start, child_after and many others are automatically available to access the syntactical structure. }}
+{{note|recall that an instance of CONSTRUCT is also a node of the abstract syntax tree, so that all the TWO_WAY_TREE features such as child_value, child_start, child_after and many others are automatically available to access the syntactical structure. }}
===Keeping syntax and semantics separate===
@@ -591,7 +591,7 @@ specimens could begin with an opening parenthesis "(".
Because of this property, if the parser goes so far as to recognize an opening parenthesis as part of parsing any construct C for which NESTED is an alternative, but further tokens do not match the structure of NESTED specimens, then we will have failed to recognize not only a NESTED but also a C.
-{{note| '''Note''': some readers will have recognized commit as being close to the Prolog "cut" mechanism. }}
+{{note|some readers will have recognized commit as being close to the Prolog "cut" mechanism. }}
In this example, NESTED is used in only one right-hand side production: the choice production for TERM, for which the other alternatives are SIMPLE_VAR and POLY_INTEGER, none of whose specimens can include an opening parenthesis.
@@ -611,7 +611,7 @@ Different processors for the same grammar may use different top constructs. }}
A document processor will be a particular system made of construct classes, complemented by semantic classes, and usually by other auxiliary classes. One of the construct classes corresponds to the top construct and is called the '''top construct class'''.
-{{note| '''Note''': this notion of top construct class has a natural connection to the notion of root class of a system, as needed to get executable software. The top construct class could indeed be used as root of the processor system. In line with the previous discussion, however, it appears preferable to keep the top construct class (which only depends on the syntax and remains independent of any particular processor) separate from the system's root class. With this approach the root class will often be a descendant of the top construct class.
+{{note|this notion of top construct class has a natural connection to the notion of root class of a system, as needed to get executable software. The top construct class could indeed be used as root of the processor system. In line with the previous discussion, however, it appears preferable to keep the top construct class (which only depends on the syntax and remains independent of any particular processor) separate from the system's root class. With this approach the root class will often be a descendant of the top construct class.
This policy was adopted for the Polynomial language example as it appears in the delivery: the processor defined for this example uses LINE as the top construct class; the root of the processor system is a class PROCESS, which inherits from LINE. }}
===Steps in the execution of a document processor===
diff --git a/documentation/current/solutions/web-technology/eiffelweb/eiffelweb-sample/eiffelweb-basic-sample.wiki b/documentation/current/solutions/web-technology/eiffelweb/eiffelweb-sample/eiffelweb-basic-sample.wiki
index 2249ade8..fd098330 100644
--- a/documentation/current/solutions/web-technology/eiffelweb/eiffelweb-sample/eiffelweb-basic-sample.wiki
+++ b/documentation/current/solutions/web-technology/eiffelweb/eiffelweb-sample/eiffelweb-basic-sample.wiki
@@ -3,7 +3,7 @@
[[Property:uuid|da8f72cb-0ecd-464a-a558-cbf7d24301e3]]
This sample shows how to retrieve and display information from a basic form on a web page.
-{{note| '''Note:''' This sample requires a web server supporting CGI in order to be run. Both the Internet Information Services web server from Microsoft and the GNU Apache server may be used.
+{{note|This sample requires a web server supporting CGI in order to be run. Both the Internet Information Services web server from Microsoft and the GNU Apache server may be used.
==Compiling==
To compile the example:
diff --git a/documentation/current/solutions/web-technology/eiffelweb/eiffelweb-tutorial/processing-requests.wiki b/documentation/current/solutions/web-technology/eiffelweb/eiffelweb-tutorial/processing-requests.wiki
index 1f937334..020840e1 100644
--- a/documentation/current/solutions/web-technology/eiffelweb/eiffelweb-tutorial/processing-requests.wiki
+++ b/documentation/current/solutions/web-technology/eiffelweb/eiffelweb-tutorial/processing-requests.wiki
@@ -23,7 +23,7 @@ The browser sends in the ''In'' a stream containing the data relative to the use
The response has to contain an HTTP header in order to be understood by the browser. Depending on the nature of the reply, an HTML page, a simple re-direction, an error notification, you will select different features and options. Your application must send at least a response header, indicating the status of the request if known. You may want to attach to it the text you wish to send back to the user. This text is usually written in HTML, so that it will display nicely on the user's browser; you can use for this purpose the class HTML_PAGE. You may then send the header followed by your text using the features send_to_browser of classes CGI_RESPONSE_HEADER and HTML_PAGE.
-{{note| '''Note''': You may not write into a file before you have sent the answer to the browser. }}
+{{note|You may not write into a file before you have sent the answer to the browser. }}
===Dealing with Cookies===