Author:admin

Date:2008-09-25T16:19:15.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@44 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
jfiat
2008-09-25 16:19:15 +00:00
parent 7d4e6a18b3
commit 2780526eae
234 changed files with 374 additions and 382 deletions

View File

@@ -66,7 +66,7 @@ The editor lets you search for text and replace occurrences, individually or glo
To start a search, make sure the Search Tool is active by clicking the Search button in the top toolbar (this one we'll let you find) or using the <code> Edit </code> <code> --> </code> <code> Find </code> menu entry.
{{note| ''Note that although we are studying Search as part of the Editor, this function also applies to any textual form displayed in the Context Tool; make sure to start a Search from the tool that you want to search.'' }}
{{note|that although we are studying Search as part of the Editor, this function also applies to any textual form displayed in the Context Tool; make sure to start a Search from the tool that you want to search.'' }}
{{note|If you press CTRL - <code>F</code> in a tool you will get a quick search bar that quickly allows to search for something in the current text.}}

View File

@@ -4,10 +4,10 @@
To find a word or an expression in a text, you can use the [[Search tool|search tool]] . If it is not displayed, you can make it appear by clicking on its icon [[Image:tool-search-icon]] in the tool bar. This tool will allow you to search a word or a regular expression and to replace it if you want to. It can be case sensitive and look for isolated words.
'''Note''': The [[Search tool|search tool]] will look for the wanted word in the editor or in the context tool, depending on which one has the focus.
{{tip| '''Tip''': There are several accelerators that will make it even easier to perform a search. They are detailed in the [[Search functionality|editor help]] . }}
{{tip|There are several accelerators that will make it even easier to perform a search. They are detailed in the [[Search functionality|editor help]] . }}
{{tip| '''Tip''': You can use the quicksearch to search in the current text. Press CTRL + F to get the quick search bar. }}
{{tip|You can use the quicksearch to search in the current text. Press CTRL + F to get the quick search bar. }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|6ec8ca83-fbe0-e02c-2570-68b5f3931083]]
Once you [[Centering tools on a component|centered the editor]] on a class, you have access to its [[Class formatters: Basic text view|basic text]] . If the class is compiled, the [[Feature tool: Introduction|feature tool]] shows the list of the features that are defined or redefined in this text. You can also view [[Clickable view|clickable]] , [[Class formatters: Flat view|flat]] , [[Flat Contract view|flat contract]] and [[Contract view|contract]] views of the class in the editor. The class tab in the context tool can display more information. If the [[Centering tools on a component|context tool is independent]] , [[Centering tools on a component|center it]] on the wanted class and select this tab. You can then see information about the features ( [[Routines|routines]] , [[Attributes|attributes]] , [[Exported features|exported features, ]] [[Class views|etc.]] ..) of the class, its [[Ancestors|ancestors]] and [[Descendants|descendants]] or its [[Clients|clients]] and [[Suppliers|suppliers]] . <br/>
The [[Metric tool: Introduction|metric tool]] provides another kind of data. It allows you to compute a complete set of [[How to analyze a project: Introduction|measures ]] on your class.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Looking for a class|Looking for a class]] }}

View File

@@ -2,7 +2,7 @@
[[Property:weight|1]]
[[Property:uuid|daff6cb5-89bd-4281-4c1e-cf031391a34b]]
To view information about a cluster, you have to center the context tool on this component. Then the [[Metric tool: Introduction|metric tool]] will provide a complete set of measures that you will able to compute.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Looking for a cluster|Looking for a cluster]] <br/>
[[How to analyze a project: Introduction|Analysing a project]] }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|0151eab9-ee25-210a-bed9-b2709e9fa5f0]]
Once you [[Centering tools on a component|centered the editor]] on a feature, you have access to its text. The feature tab in the context tool can display more information. To have access to it, you have first to center the context tool on the wanted class and select the feature tab. You can then consult the different views of the text of the feature ( [[Feature formatters: Basic text view|basic text]] or [[Feature formatters: Flat view|flat]] ) and other information such as its [[Callers|callers]] or its [[Descendant versions|descendant]] versions. <br/>
The [[Metric tool: Introduction|metric tool]] provides another kind of data. It enables you to compute some [[How to analyze a project: Introduction|measures]] on your feature.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Looking for a feature|Looking for a feature]] }}

View File

@@ -7,7 +7,7 @@ To profile an executable, the profiler must first be enabled. To enable the prof
* Click '''OK'''.
* You must [[Generating executables|recompile]] your project for the changes to take effect.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Profiler wizard: Introduction|Profiler reference]] }}

View File

@@ -11,7 +11,7 @@ These commands are also available in the '''Project''' toolbar [[Image:project-
To solve the errors that occur during the Eiffel compilation, use the [[Error wizard|compilation error wizard]] . For errors occurring during the C compilation, check that the installation is not corrupted and refer to your C compiler documentation for more information.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Command line: Introduction|Command line options]] <br/>
[[Compiler|Compiler]] }}

View File

@@ -23,7 +23,7 @@ The generated C library should be located in the EIFGENs|target_name|W_code dire
To generate a C library from a C compiler, please refer to the documentation of your C compiler.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Using libraries|Using libraries]] <br/>
[[CECIL|CECIL library: calling Eiffel routines from C programs]] <br/>
[[Command line: Introduction|Command line options]] }}

View File

@@ -7,7 +7,7 @@ To modify the assertion level in a generated binary (executable or library),
* Click '''OK'''.
* You must [[Generating executables|recompile]] your project for the changes to take effect.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[8 Design by Contract (tm), Assertions and Exceptions|Assertions in Eiffel]] }}

View File

@@ -17,7 +17,7 @@ Removing the '''Execution Trace''' will optimize the executable in size and spee
All these options are located in the [[Advanced Options|Project Settings]] dialog, in the '''Advanced''' section. They are only effective during finalizations.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Profiler wizard: Introduction|Profiler reference]] }}

View File

@@ -8,7 +8,7 @@ To use an Eiffel precompiled library:
* Add a new precompile group to your target.
* You must [[Generating executables|recompile]] your project from scratch for the changes to take effect.
{{note| '''Note''': You can only use one precompiled library at a time in a project. To use more than one, you should precompile all the libraries you want to use together in a single precompiled library. }}
{{note|You can only use one precompiled library at a time in a project. To use more than one, you should precompile all the libraries you want to use together in a single precompiled library. }}
To use a C library:
* Open the [[Externals Options|Project Settings]] dialog.
@@ -17,7 +17,7 @@ To use a C library:
* Click '''OK'''.
* You must [[Generating executables|recompile]] your project for the changes to take effect.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Generating libraries|Creating libraries]] <br/>
[[Adding a cluster|Adding classes and clusters from Eiffel libraries without precompiling the library]] <br/>
[[C externals|Making C calls in Eiffel]] }}

View File

@@ -11,7 +11,7 @@ To create a multithreaded program or library:
{{warning| '''Caution''': Make sure the external and precompiled libraries you use have also been compiled with support for threads. }}
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Generating libraries|Creating libraries]] }}

View File

@@ -6,7 +6,7 @@ To do so, use the [[Preference window overview|preference window]] : select '''P
Click on '''save and exit''' to complete the change.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Preference window overview|Preference window description]] <br/>
[[EiffelStudio preferences: Introduction|Preferences reference]] }}

View File

@@ -2,7 +2,7 @@
[[Property:weight|1]]
[[Property:uuid|b7c1cbac-975b-c6e6-050b-e48b61732a57]]
By modifying EiffelStudio [[EiffelStudio preferences: Introduction|preferences]] , you can change the font and the colors used to display texts in the editor. For more information, refer to EiffelStudio [[Interface|graphical preferences reference]] .
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Customizing class text views|Customizing formatted output]] }}

View File

@@ -6,7 +6,7 @@ EiffelStudio allows you to customize a list of classes that it has to ignore whe
After modifying the list, click on '''save and exit''' to complete the change.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Preference window overview|Preference window description]] <br/>
[[EiffelStudio preferences: Introduction|Preferences reference]] }}

View File

@@ -6,7 +6,7 @@ To do so, first open the [[Preferences Reference|preferences window]] by choosi
After modifying the command line, click on '''save and exit''' to complete the change.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Preferences Reference|Preference window description]] <br/>
[[EiffelStudio preferences: Introduction|Preferences reference]] }}

View File

@@ -9,7 +9,7 @@ It is possible in EiffelStudio to customize some properties of [[Formatters: Int
These properties are set in the [[EiffelStudio preferences: Introduction|preferences]] . You can modify them in the [[Preference window overview|preferences window]] . To open this window, select '''Preferences...''' in the '''Tool''' menu. Then select the "Context tool" sub-category of the "Tools" category in the preferences tree. Click then on a preference on the right to modify its value.
Click on '''save and exit''' to complete the changes.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Preference window overview|Preference window description]] <br/>
[[EiffelStudio preferences: Introduction|Preferences reference]] }}

View File

@@ -4,7 +4,7 @@
There may be up to 26 buttons in the [[Main toolbars|standard toolbar]] and up to 17 in the [[Main toolbars|project toolbar]] . All those buttons are not shown by default though. Only 16 icons are displayed in the default standard toolbar for instance.
It is possible to choose which button are shown and in which order they appear in the toolbars. To do so, use [[Toolbar customization|toolbar customization]] windows. they appear when you choose '''Customize standard toolbar...''' or '''Customize project toolbar...''' in the toolbars sub-menu of the View menu or in the contextual menu of the toolbars (which is displayed when you right-click in the empty space on the right of the toolbars).
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Main toolbars|The toolbars and their buttons]] <br/>
[[Toolbar customization|Toolbars customization windows]] }}

View File

@@ -7,7 +7,7 @@ To do so, click on or select '''Isolate context tool''' in the '''View''' menu.
You can also modify the [[EiffelStudio preferences: Introduction|preferences]] so that next time a window is opened, its context tool will be automatically independent: open the [[Preference window overview|preferences window]] by choosing '''Preferences...''' in the '''Tools''' menu. Select then the "context tool" sub-category in the "Tools" of the preferences tree. Lastly click on "Share addresses between the editor and the context tool" and set it to '''False'''. <br/>
Click on save and exit to complete the change.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Preference window overview|Preference window description]] <br/>
[[EiffelStudio preferences: Introduction|Preferences reference]] }}

View File

@@ -2,7 +2,7 @@
[[Property:weight|0]]
[[Property:uuid|ff77b886-4a47-2ba4-eac7-ae051934a3f5]]
Some of [[EiffelStudio Editor Introduction|the editor]] properties are customizable. [[Automatic completion: Introduction|Automatic completion]] , for instance, can be partially or totally disabled, and inserted strings can be defined by the user. Some accelerators are customizable too. For more information, please refer to the [[Editor Preferences|editor preferences reference]] .
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Changing texts display|Text colors and font customization.]] }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|a1d33a03-a691-d7ea-c081-55c2c991e77f]]
* To create a new class pick from the '''Create a new class''' button. [[Image:16x16--new-class-icon]] Then drop on the diagram where you want to place the class bubble. A dialog now appears where you can enter a name and specify the cluster.
{{seealso|'''See Also'''<br/>
{{seealso|<br/>
[[New class command|Creating a new class using the address bar]] }}

View File

@@ -2,7 +2,7 @@
[[Property:weight|1]]
[[Property:uuid|f9b79d1c-6ca7-d0a3-1374-e71a8b450644]]
To create a new feature just [[Creating client/supplier links|add a new client link]] in the diagram.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Adding a feature: Introduction|Creating a new feature]] }}

View File

@@ -5,9 +5,9 @@
{{warning| '''Caution''': An action that deletes one or more files or directories cannot be undone! }}
{{tip| '''Tip''': Turn on '''Automatic backups'''. EiffelStudio will make a copy of each class file every time a compilation is done. }}
{{tip|Turn on '''Automatic backups'''. EiffelStudio will make a copy of each class file every time a compilation is done. }}
{{seealso|'''See also'''<br/>
{{seealso|<br/>
[[Removing items from a view|Removing items from the view only]] }}

View File

@@ -6,7 +6,7 @@
# Drop on the desired supplier class.
# The '''Create feature''' dialog appears. See [[Adding an attribute|Creating an attribute]] or [[Adding a function|Creating a function]] using the feature wizard for more information.
{{seealso|'''See Also'''<br/>
{{seealso|<br/>
[[Creating client/supplier links|Creating client/supplier links]] <br/>
[[Creating inheritance links|Creating Inheritance links]] <br/>
[[New feature dialog: Introduction|Feature wizard]] }}

View File

@@ -6,7 +6,7 @@
# Drop on the desired supplier class.
# The '''Create feature''' dialog appears. See [[Adding an attribute|Creating an attribute]] or [[Adding a function|Creating a function]] using the feature wizard for more information.
{{seealso|'''See Also'''<br/>
{{seealso|<br/>
[[Creating aggregate client/supplier links|Creating aggregate client/supplier links]] <br/>
[[Creating inheritance links|Creating Inheritance links]] <br/>
[[New feature dialog: Introduction|Feature wizard]] }}

View File

@@ -5,9 +5,9 @@
# Start pick-and-drop on the class where the parent should be added.
# Drop on the desired parent class.
{{note| '''Note''': This action will also add the parent in the class text. }}
{{note|This action will also add the parent in the class text. }}
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Creating client/supplier links|Creating client/supplier links]] <br/>
}}

View File

@@ -9,7 +9,7 @@
<br/>
<br/>
{{note| '''Note''': You cannot delete the view "DEFAULT". }}
{{note|You cannot delete the view "DEFAULT". }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|b46746cc-28e9-0db6-7d26-7aa553605e00]]
* You can adjust the behavour of the physics mode by altering various parameters in the physics settings dialog. To disaply the physics setting dialog press this button [[Image:diagram-physics-settings-icon]] .
{{tip| '''Tip''': To see the effects of each parameter modify it whilst your diagram is in view and you will see the diagram adjust to the new settings dynamically. }}
{{tip|To see the effects of each parameter modify it whilst your diagram is in view and you will see the diagram adjust to the new settings dynamically. }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|a30d39b6-67a6-6456-f409-e26f5e870629]]
* You may anchor a class to the diagram by right clicking the figure and dropping it onto the anchor button [[Image:diagram-anchor-icon]] .
{{tip| '''Tip''': To see the effects of anchoring [[Turn on Physics Mode|turn on physics mode]] and then anchor a class as described above. Now [[Adjusting Physics Settings|open the physics settings dialog]] and adjust the sliders. In the diagram you will see all anchored classes do not move whilst those surrounding them adjust to the new settings. }}
{{tip|To see the effects of anchoring [[Turn on Physics Mode|turn on physics mode]] and then anchor a class as described above. Now [[Adjusting Physics Settings|open the physics settings dialog]] and adjust the sliders. In the diagram you will see all anchored classes do not move whilst those surrounding them adjust to the new settings. }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|70e4813e-84b5-48e7-dddb-0e7f601125e3]]
* To change the display quality of the diagram press the Toggle Quality button [[Image:diagram-toggle-quality-icon]] .
{{tip| '''Tip''': Lower quality display is faster for drawing so is recommended for very large diagrams. }}
{{tip|Lower quality display is faster for drawing so is recommended for very large diagrams. }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|2a40c334-b223-3dbf-8c85-abf19a72213f]]
* If you do not want to hide the cluster, only its contents, iconify it by double clicking on the cluster label. Double clicking it again returns the cluster to its normal state.
{{tip| '''Tip''': If the entire cluster is of no relevance to your diagram, [[Removing items from a view|hide it from the view]] altogether. }}
{{tip|If the entire cluster is of no relevance to your diagram, [[Removing items from a view|hide it from the view]] altogether. }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|537ce4ac-5993-4b8f-af4a-55a2c6193da2]]
* To remove an class, cluster, or link from the current view, use pick-and-drop to drop it in the '''Remove figure''' hole. [[Image:general-reset-icon]] . To remove a link handle you can also the same technique
{{note| '''Note''': If you want to remove the item from the system, use the [[Deleting items|Delete]] hole. }}
{{note|If you want to remove the item from the system, use the [[Deleting items|Delete]] hole. }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|03910ac4-6236-0a1d-667e-3a7c25b10c78]]
* You can turn on and off physics to the diagram by pressing the physics mode button [[Image:diagram-toogle-physics-icon]]
{{tip| '''Tip''': The particular configuration of the classes in your system when using the physics mode is determined by the various settings in the [[Adjusting Physics Settings|Physics Setting Dialog]] . }}
{{tip|The particular configuration of the classes in your system when using the physics mode is determined by the various settings in the [[Adjusting Physics Settings|Physics Setting Dialog]] . }}

View File

@@ -4,7 +4,7 @@
* The cluster legend allows you to quickly determine which classes in the view belong to which clusters in the system by changing the colors to match those of cluster assigned ones. Pressing the legend button [[Image:diagram-show-legend-icon]] will display a list of all the clusters in the system for which at least one class is visible in the view. Next to each cluster name is a color, and pressing the top right color square will automatically set a unique color for each cluster and change the classes belonging to that cluster to match. Pressing again the legend button will hide it from view. The image below shows the legend in use and the classes colored.
[[Image:cluster-legend]]
{{tip|'''Tip:''' Use the cluster legend also to quickly see sub-cluster organization within your overall cluster design.}}
{{tip|Use the cluster legend also to quickly see sub-cluster organization within your overall cluster design.}}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|87528ee4-72c4-57c3-81f0-8d5bda425276]]
* In order to switch from coding to designing, click the '''Diagram''' tab in the '''Context''' tool. Open the context tool by checking menu item '''View | Explorer Bar |Context'''.
{{tip| '''Tip''': To make sure all your changes are in the diagram, perform a compilation. }}
{{tip|To make sure all your changes are in the diagram, perform a compilation. }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|35cb87d8-14c9-f3ce-5275-83c1ec61d746]]
Almost all actions in the diagram tool are undoable. Every action that can be undone, can also be redone. For advanced undoing, open the history tool.
{{tip| '''Tip''': Undo actions cannot be undone. Use redo to undo an undo action. }}
{{tip|Undo actions cannot be undone. Use redo to undo an undo action. }}
* To undo the last action, click '''Undo last action'''. [[Image:general-undo-icon]]
* To redo the last action, click '''Redo last action'''. [[Image:general-redo-icon]]
* To undo all actions up until a specific action:
@@ -12,7 +12,7 @@ Almost all actions in the diagram tool are undoable. Every action that can be un
[[Image:history-tool]]
{{note| '''Note''': When an action is performed that cannot be undone, the history tool is emptied. }}
{{note|When an action is performed that cannot be undone, the history tool is emptied. }}

View File

@@ -4,14 +4,14 @@
A dialog window is dedicated to the creation of new classes.
[[Image:new-class-dialog]]
A list of all the clusters of the system lets you to choose in which one the new class will be inserted. The name of the new class and the name of the corresponding file can be set thank to two text fields above the list. It is also possible to define whether the class should be deferred or expanded, what its creation feature is (if any), what its parents are and whether the default feature clauses should be generated.
{{tip| '''Tip''': You can change the class text that is generated by default by editing the following files:$ISE_EIFFEL\studio\help\defaults\$ISE_PLATFORM\full.cls (with default feature clauses) and ...\empty.cls (without default feature clauses). }}
{{tip|You can change the class text that is generated by default by editing the following files:$ISE_EIFFEL\studio\help\defaults\$ISE_PLATFORM\full.cls (with default feature clauses) and ...\empty.cls (without default feature clauses). }}
To make the window appear, you can:
* Click [[Image:16x16--new-class-icon]] in the [[Main toolbars|standard toolbar]] .
* Select '''New class''' in the '''Tools''' menu.
* Type the name of the new class in the class field of the [[Main address bar|main address bar]] or the [[Context tool address bar|context tool address bar]] . The current cluster will then be preselected.
* Use the [[Diagram tool: Introduction|diagram tool]] : Pick the icon [[Image:16x16--new-class-icon]] and drop it on the diagram in the right cluster. This will make the dialog window appear with the chosen cluster selected.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Removing a class|Removing a class]] }}

View File

@@ -15,7 +15,7 @@ If you want to create a subcluster, give it a name and select its parent in the
To import an existing cluster, you can also go to the '''Groups''' section in the [[Group Options|Project Settings dialog]] and click '''Add cluster'''. Although this solution may be slightly more tedious, it gives access to more options.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Removing a cluster|Removing a cluster]] }}

View File

@@ -1,16 +1,5 @@
[[Property:title|Editing a project]]
[[Property:weight|2]]
[[Property:uuid|d04c152e-1749-9e9f-0503-ec505478471e]]
* [[Adding a cluster|Adding a cluster]]
* [[Adding a library|Adding a library]]
* [[Adding a class|Adding a class]]
* [[Adding a feature|Adding a feature]]
* [[Removing a cluster|Removing a cluster]]
* [[Removing a class|Removing a class]]
* [[Removing a feature|Removing a feature]]
* [[Moving a class|Moving a class]]
* [[Changing project parameters|Changing project parameters]]

View File

@@ -2,7 +2,7 @@
[[Property:weight|7]]
[[Property:uuid|10947266-61c8-ddd5-445e-9eb0de61cd05]]
To move a class from a cluster to another one, you have to use the [[Diagram tool: Introduction|Diagram tool]] . First, [[Centering tools on a component|center the tool]] on the cluster that contains the class you want to move. Then, if the destination cluster is not shown on the diagram, [[Pick-and-drop mechanism|pick]] it in the [[Cluster tool: Introduction|cluster tool]] and drop it in the [[Diagram tool: Introduction|diagram]] . Once both clusters are displayed, you just have to drag the class to its destination.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Looking for a class|Find where a class is]] <br/>
[[Looking for a cluster|Find where a cluster is]] }}

View File

@@ -9,7 +9,7 @@ To remove a class, you can:
{{warning| '''Caution''': Picking a feature and dropping it on the delete icon, or calling '''Remove current item''' as the editor is centered on a feature, will not remove the feature but the class to which it belongs. }}
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Adding a class|Adding a class]] }}

View File

@@ -6,7 +6,7 @@ To remove clusters, you can:
* [[Pick-and-drop mechanism|Drop a pebble]] of this component on [[Image:16x16--general-delete-icon]] in the [[Main toolbars|standard toolbar]] or in the [[Diagram tool: Introduction|Diagram tool]] [[Diagram toolbar|toolbar]] .
* Use the cluster tab in the project configuration window.
{{seealso| '''See also''' <br/>
{{seealso|<br/>
[[Adding a cluster|Adding a cluster]] }}

View File

@@ -2,7 +2,7 @@
[[Property:weight|6]]
[[Property:uuid|8779bb5f-44d4-48fa-7320-d3c02c3dc176]]
To remove a feature, you may of course delete the corresponding lines in the class text. You can also use the Diagram tool if it is an attribute or a function. To do so, make sure that supplier links are shown in the diagram (if [[Image:diagram-supplier-link-icon]] is not pressed, click it). Pick the link that correspond to the feature you want to remove and drop the pebble on [[Image:16x16--general-delete-icon]] .
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Adding a feature: Introduction|Adding a feature]] }}

View File

@@ -11,9 +11,9 @@ Under '''Create project''', several options are offered, which depend on the pla
* '''Vision2 application''' creates a new project that includes the [[EiffelVision Introduction|Eiffel Vision2 library]] . This is the perfect choice to start a platform-independent graphic application, or even any graphic application, since EiffelVision2 is easier to use than platform-specific libraries. This option is available on all platforms.
* '''WEL application''' generates a project using the [[WEL|Windows Eiffel Library(WEL)]] . This option is recommended for projects needing advanced Windows features, or Windows applications that are time-critical, since the graphic functionality provided by WEL is more efficient than the one provided by Vision2, which on the other hand provides a platform-independent abstract interface. This wizard is only available on Windows.
All those options are also available in the ''' File'''/ '''New project...''' menu. This pops up a dialog with all the options to generate a new project: [[Image:create-a-project]]
{{tip| '''Tip''': If you checked the "Don't show this dialog at startup" checkbox in the start-up dialog but want to get it back, you can use the [[Discardable dialogs|Preferences dialog]] to reset the default value. }}
{{tip|If you checked the "Don't show this dialog at startup" checkbox in the start-up dialog but want to get it back, you can use the [[Discardable dialogs|Preferences dialog]] to reset the default value. }}
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Retrieving a project from a configuration file|Retrieving a project from an configuration file]] }}

View File

@@ -7,7 +7,7 @@ This dialog also allows you to select which target to compile and you can also s
'''Reset user settings''' removes all stored custom information about the project (but not the configuration of the project itself). For example last used target, locations where this project has been compiled, arguments and working directory.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[EiffelStudio: Creating a new project|Creating a new project]] }}

View File

@@ -9,7 +9,7 @@ The first page of the Documentation Wizard lets you choose between the available
[[Image:doc-wizard-filter-selection]]
{{tip| '''Tip''': The nicest output is produced by the '''html-stylesheet''' format. }}
{{tip|The nicest output is produced by the '''html-stylesheet''' format. }}
Now the wizard asks you to select the clusters you want to produce documentation for:
@@ -19,7 +19,7 @@ In the next page you can specify indexing items on which HTML metatags will be b
[[Image:doc-wizard-indexing-selection]]
{{note| '''Note''': This page is only available for HTML documentation. }}
{{note|This page is only available for HTML documentation. }}
You can then pick the formats you need among those available. For example, you might need a file containing the '''Cluster hierarchy''' of your system or, for each class, a file containing the '''Contracts''' of that class. At this point you can also decide to generate BON diagrams for the clusters selected in the previous page.
@@ -29,13 +29,13 @@ If you have checked '''Cluster diagrams''' in the previous page, you will now be
[[Image:doc-wizard-view-selection]]
{{note| '''Note''': Cluster diagrams are only available for HTML documentation. }}
{{note|Cluster diagrams are only available for HTML documentation. }}
Here comes the last page; you can choose the directory where the documentation is going to be generated:
[[Image:doc-wizard-path-selection]]
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Generating XMI documentation|Generating XMI documentation]] }}

View File

@@ -13,7 +13,7 @@ On the second and last page, you can choose the directory where the XML file is
[[Image:doc-wizard-path-selection]]
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Generating multi-format documentation|Generating multi-format documentation]] }}

View File

@@ -13,7 +13,7 @@ You can get more information about the evaluated metric. See [[Viewing measure d
{{warning| '''Caution''': When calculated, a measure is not saved. }}
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Saving a measure|Saving a measure]] <br/>
[[Viewing measure details|Detailing a measure]] <br/>
}}

View File

@@ -7,7 +7,7 @@ To save the result of evaluation of a metric:
# Select a file to use to store the results. If you specify a non-existing file, it will be created, if you specify an existing file it will be overriden. The selection of the file can be done by clicking on the button with the three dots in the '''Archive Management''' frame.
# Click the '''Start metric archive evaluation'''.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Evaluating a measure|Evaluating a measure]] <br/>
[[Viewing measure details|Detailing measures]] <br/>
}}

View File

@@ -7,7 +7,7 @@ It is possible to have some details when evaluating a metric.
# Click the '''Run selected metric and show detailed result''' button and the result will appear in the '''Detailed Result''' tab of the metric tool.
# To come back to the main interface click again on '''Metric Evaluation''' tab of the metric tool.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Evaluating a measure|Evaluating a measure]] <br/>
[[Saving a measure|Saving measures]] <br/>
}}

View File

@@ -7,7 +7,7 @@ The goal is to load the archive of a (preferably different) project, to compare
Once the archives are selected, click the '''Compare''' button to start the comparison. It will bring you to the '''Detailed Result''' tab.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Creating an archive|Creating an archive]] }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|d8bd6d77-a5dc-df38-a796-6fa8a07ddf29]]
Users may want to archive the result of the system they are working on. To create an archive is basically the same as [[Saving a measure|saving a measure]] .
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Comparing to an archive|Comparing to an archive]] }}

View File

@@ -12,7 +12,7 @@ For more information about criterion, read the [[Criterion References|Managing c
A summary of the metric you just defined appears in a textual representation in the '''Expression''' text field.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Managing new metrics: Introduction|Managing metrics]] <br/>
[[Criterion References|Managing criterion]] }}

View File

@@ -11,7 +11,7 @@ To define a linear metric, you must select the '''Metric Definition''' tab and c
A summary of the metric you just defined appears in a textual representation in the '''Expression''' text field.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Managing new metrics: Introduction|Managing metrics]] <br/>
}}

View File

@@ -12,7 +12,7 @@ To define a ratio metric, you must select the '''Metric Definition''' tab and cl
A summary of the metric you just defined appears in a textual representation in the '''Expression''' text field.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Managing new metrics: Introduction|Managing metrics]] <br/>
}}

View File

@@ -9,7 +9,7 @@ To follow an object state between pauses of the application, pick and drop it in
You can also query features dynamically by using the evaluation tool, which can be very useful to have glimpses of the C memory of the system, for instance.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Interrupting an application|Pausing an application]] <br/>
[[Callstack tool: Introduction|Call stack tool]] <br/>
[[Objects tool: Introduction|Object tool]] <br/>

View File

@@ -7,7 +7,7 @@ The <eiffel>[[ref:/libraries/base/reference/exceptions_chart|EXCEPTIONS]] </eiff
When an exception is raised while the application is being debugged, the application stops immediately and the debugger displays the context in which the exception occurred, whether or not the exception is rescued.
{{seealso| '''See Also''': <br/>
{{seealso|<br/>
[[8 Design by Contract (tm), Assertions and Exceptions|Reference of exceptions]] }}

View File

@@ -9,7 +9,7 @@ Two methods can be used to pause a debugged application:
To kill a debugged application, use the [[Stop a debugged application]] , located in both the debug menu and the project toolbar.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Running an application|Running a program]] <br/>
[[Using breakpoints|Using breakpoints]] }}

View File

@@ -22,7 +22,7 @@ It is also possible to dynamically start and stop the profiler in a program. To
* Call [[ref:libraries/base/reference/profiling_setting_flatshort|start_profiling]] on this object to start the profiler.
* Call [[ref:libraries/base/reference/profiling_setting_flatshort|stop_profiling]] on this object to stop the profiler.
{{tip| '''Tip''': To profile only part of a program, turn off the profiler at the very beginning of the program, turn it on just before the part of the code that should be profiled, and turn it back off after this section. Typically, it results in the following code: }}
{{tip|To profile only part of a program, turn off the profiler at the very beginning of the program, turn it on just before the part of the code that should be profiled, and turn it back off after this section. Typically, it results in the following code: }}
In the root feature:
@@ -52,17 +52,17 @@ And in the feature(s) that needs to be profiled:
end</code>
{{note| '''Note''': Even if the profiler should only work in certain sections of code, the '''Profiling''' check box of the [[General Target Options|Projects Settings]] dialog must be checked or the '''profile''' option must be set on certain clusters. }}
{{note|Even if the profiler should only work in certain sections of code, the '''Profiling''' check box of the [[General Target Options|Projects Settings]] dialog must be checked or the '''profile''' option must be set on certain clusters. }}
Once the profiler has been enabled and the program has been recompiled, it is necessary to launch the program.
{{tip| '''Tip''': It is possible to profile debuggable(frozen/melted) executables as well as finalized ones. It is more interesting to profile finalized executables, though, since the execution speed is more representative of what will be obtained by your end users. }}
{{tip|It is possible to profile debuggable(frozen/melted) executables as well as finalized ones. It is more interesting to profile finalized executables, though, since the execution speed is more representative of what will be obtained by your end users. }}
When the program exits, a file named 'profinfo' should be generated next to it.
All that's left to do is launch the [[Profiler wizard: Introduction|Profiler wizard]] and follow the instructions.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Generating executables|Generating executables]] <br/>
[[Running an application|Running a program]] <br/>
[[Tuning a program|Tuning a program]] }}

View File

@@ -12,13 +12,13 @@ Melted and frozen executables can be debugged. Several methods can be used to la
** The [[Step out of a feature]] , which launches the application and stops it as soon as the application exits the feature it is stopped in.
{{tip| '''Tip''': All the above commands can be accessed either in the '''Project''' toolbar or in the '''Debug''' menu. <br/>
{{tip|All the above commands can be accessed either in the '''Project''' toolbar or in the '''Debug''' menu. <br/>
They can be used either to launch the program or to resume its execution after it has been paused. }}
* It is also possible to select '''Run to breakpoint''' in a [[Breakpoint editing|breakpoint context menu]] to have the application be launched and executed until it reaches the selected execution line.
Finalized executables can also be run, but they are not debuggable and cannot be interrupted. To run a finalized executable, use the [[Run a finalized executable]] , located in the '''Project''' menu and the '''Project''' toolbar.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Generating executables|Compiling an executable]] <br/>
[[Using breakpoints|Using breakpoints]] <br/>
[[Interrupting an application|Interrupting an application]] }}

View File

@@ -8,7 +8,7 @@ To change the command line arguments used when debugging:
* In this dialog, you can change the current arguments and also store and load argument sets.
* Click '''OK'''.
{{tip| '''Tip''': To get the command line arguments in a program, it is possible to either define the root feature as taking an array of [[ref:/libraries/base/reference/string_8_chart|STRING_8]] objects, or to use the [[ref:/libraries/base/reference/arguments_chart|ARGUMENTS]] class, which provides a lot of functionality linked with command line arguments. }}
{{tip|To get the command line arguments in a program, it is possible to either define the root feature as taking an array of [[ref:/libraries/base/reference/string_8_chart|STRING_8]] objects, or to use the [[ref:/libraries/base/reference/arguments_chart|ARGUMENTS]] class, which provides a lot of functionality linked with command line arguments. }}

View File

@@ -5,7 +5,7 @@ To change the status of one breakpoint, it is possible to use the [[Breakpoint e
To change the status of several breakpoints at the same time, the easiest way is to use the [[Breakpoint commands|breakpoints-related commands]] , which have actions at feature-scope, class-scope and system-scope.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Running an application|Running an application]] <br/>
[[Interrupting an application|Interrupting an application]] <br/>
[[Breakpoints: Introduction|Breakpoints reference]] }}

View File

@@ -22,7 +22,7 @@ To modify the debug clauses status:
* Click '''OK'''.
* You must [[Generating executables|recompile]] your project for the changes to take effect.
{{tip| '''Tip''': Debug clauses make it easy to remove all debug messages when finalizing a system. }}
{{tip|Debug clauses make it easy to remove all debug messages when finalizing a system. }}

View File

@@ -3,9 +3,9 @@
[[Property:uuid|52206181-e002-0914-d98d-c817d32ec02e]]
Located in the '''View''' menu, named either '''Link context tool''' or '''Unlink context tool''', this command allows you to switch between the two possible [[Address bars: Introduction|addressing modes]] . It is also accessible through the main toolbar ( [[Image:context-link-icon]] ).
{{note| '''Note''': This command only applies to the development window where it is invoked, and this setting is not automatically saved when exiting EiffelStudio. }}
{{note|This command only applies to the development window where it is invoked, and this setting is not automatically saved when exiting EiffelStudio. }}
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Development Window Preferences|Change the default data sharing]] <br/>
}}

View File

@@ -9,11 +9,11 @@ It also contains history arrows, and by clicking on the cluster, class or featur
[[Image:context-address-window]]
{{tip| '''Tip''': Labels in this address bar are pickable, to send the address to other tools easily. }}
{{tip|Labels in this address bar are pickable, to send the address to other tools easily. }}
{{note| '''Note''': The context tool only has an address bar if it is unlinked from the editor. }}
{{note|The context tool only has an address bar if it is unlinked from the editor. }}
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Change data share mode|Unlinking the context tool]] }}

View File

@@ -12,9 +12,9 @@ It has several components:
It is possible to type a class or feature name to center the editor on it. Typing a class name that does not exist in the set of known classes pops up a dialog to create a class of that name.
{{tip| '''Tip''': Wildcards (* and ?) are available in these fields. }}
{{tip|Wildcards (* and ?) are available in these fields. }}
{{tip| '''Tip''': The history is also accessible in the '''View/Go to''' menu. }}
{{tip|The history is also accessible in the '''View/Go to''' menu. }}

View File

@@ -11,9 +11,9 @@ Select the destination folder by expanding the tree and by clicking it. The top
Pressing '''OK''' moves the source item to the destination folder. Pressing '''Cancel''' discards the dialog box and does not move the source item.
{{tip| '''Tip''': You can also move items around by picking them in the favorites tree and dropping them where you want. }}
{{tip|You can also move items around by picking them in the favorites tree and dropping them where you want. }}
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Favorites tree|Favorites tree]] <br/>
}}

View File

@@ -9,7 +9,7 @@ Clicking on a class name sets its name in the top text field, whereas double-cli
The selected class goes to the root of the favorite tree. It is then possible to [[Move to Folder command|move]] it to a different favorite folder.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Favorites tool: Introduction|Favorite tool]] <br/>
[[Favorites menu|Favorite menu]] <br/>
}}

View File

@@ -10,7 +10,7 @@ A dialog is then popped up in which it is possible to select the name of the new
Enabling the '''recursive''' option makes the compiler search not only the cluster directory but also all its sub-directories for classes. <br/>
The '''library''' option optimizes compilations, since the classes inside a library cluster are compiled only once. However, if you modify the classes inside a library cluster, the modifications will not be taken into account in your project. Besides, you cannot add or remove classes in a library cluster, so use this option with care: if you intend to create new classes inside this cluster later in your design, do not select the library option. You should use this option only if the new cluster is given an existing directory, which already contains classes that you will not modify.
{{tip| '''Tip''': You don't have to enter a path for the new cluster if you choose to create a sub-cluster: the new cluster directory will be a sub-directory of the directory of the parent cluster, and its name will be the name of the newly created cluster. }}
{{tip|You don't have to enter a path for the new cluster if you choose to create a sub-cluster: the new cluster directory will be a sub-directory of the directory of the parent cluster, and its name will be the name of the newly created cluster. }}

View File

@@ -36,7 +36,7 @@ Search backwards: If this option is selected, the tool will highlight the previo
'''Note''': If the search tool hits one end of the text, it will automatically continue from the other end. <br/>
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
There are keyboard shortcuts and menu entries to launch searches without using the search tool directly. They are described the [[Search functionality|editor section]] of this help. }}

View File

@@ -39,7 +39,7 @@ finish_freezing > c:\output_path\OUTPUT</code>
It will go the directory where your project is located and compile your Eiffel code using the `config.ecf' file located in your project directory and compile automatically the C code. All outputs will be stored in the file `c:\output_path/OUTPUT'.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[EiffelStudio: Command line options|Command line compiler options]] }}

View File

@@ -148,7 +148,7 @@ When running the Generate command with no arguments, you will be prompted for th
You can also type in the arguments directly without waiting to be prompted, as in command => g profinfo finalize eiffel <br/>
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Profiler Wizard|Profiler wizard]] }}

View File

@@ -179,7 +179,7 @@ You must now run "finish_freezing" in:
with | replaced by \ if your platform is Windows, / if it is Unix. To execute the C compilation and linking part of the finalization, change directory to ''your_project_path''|EIFGENs|''target_name''|F_code as indicated and execute '''finish_freezing'''.
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Batch compilation|Batch compilation]] }}

View File

@@ -4,7 +4,7 @@
[[Property:uuid|c22fad22-3dce-cf2c-1d24-4e70fc29f3f3]]
==What's new==
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
* Implemented once manifest strings. They can be used at the same places where normal manifest strings can be used, e.g.:
<code>s := once "abc"
io.put_string (once "Hello World!")</code>

View File

@@ -4,7 +4,7 @@
[[Property:uuid|fc50f98f-4dfd-0173-23d4-9db219dde0cf]]
==What's new==
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
* Support for new expanded semantics defined in ECMA-367. The current limitations are: no copy semantics in the .NET code generation, and still no generic conformance.
* Inline agents as defined in ECMA-367 with the limitation to only accept the do form.
* Added possibility to define agents on attributes or externals.

View File

@@ -4,7 +4,7 @@
[[Property:uuid|83f6c19c-b0da-6acb-0333-a92d445cfe56]]
==What's new==
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
* Added support for multiple constraints in formal generic parameters.
* The root class can now be a generic class, and thus one can now specify a root type.
* The notion of creation readiness according to ECMA Eiffel standard (2nd edition, chapter 8.12.12) is implemented.

View File

@@ -4,7 +4,7 @@
[[Property:uuid|32beeca8-08df-4918-b231-8a14114fdd62]]
==What's new==
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
* Multiple errors are reported for each compilation degree.
* Experimental support for Non-conforming Inheritance has been added (Classic only). Classes may now be inherited (using inherit {NONE} but no conformance of that class is implied.
* Attachment marks are supported. Now it's possible to specify whether an entity is attached or detachable:

View File

@@ -4,7 +4,7 @@
[[Property:uuid|20122f4c-22c6-d0ee-c38b-36908ca86ad2]]
==What's new==
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
* Exceptions as objects are now implemented.
* Added support for new ~ operator which can compare 2 objects safely regardless of their type.
* Added detection of harmful catcall at runtime (harmless ones are currently ignored).

View File

@@ -2,7 +2,7 @@
[[Property:link_title|]]
[[Property:weight|-9]]
[[Property:uuid|fc1e73f4-5646-aa41-e7fe-97dc6f3ceb04]]
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
==Added classes==
* New basic classes have been added: <eiffel>INTEGER_8</eiffel>, <eiffel>INTEGER_16</eiffel>, <eiffel>INTEGER_64</eiffel> and <eiffel>WIDE_CHARACTER</eiffel>. <eiffel>INTEGER</eiffel> is now specified as having a 32 bits representation

View File

@@ -9,7 +9,7 @@ The dynamic library window that appears when selecting this menu is mainly compo
[[Image:shared-library-window]]
{{note| '''Note''': The layout of this wizard is slightly different on Windows and on Unix systems, because the index and calling convention fields never appear on Unix systems. }}
{{note|The layout of this wizard is slightly different on Windows and on Unix systems, because the index and calling convention fields never appear on Unix systems. }}
To add a new feature to the definition file, you can either:
* Pick the feature from any place in EiffelStudio and drop it into the list. If several creation procedures exists in the container class, a dialog is popped up to give the choice between all possible creation procedures.
@@ -23,7 +23,7 @@ It is also possible to check the validity of the definition file. This command
Other commands, located in the '''File''' menu, give standard file operations, such as opening [[Image:general-open-icon]] a definition file, creating a new definition file [[Image:new-document-icon]] ,or saving the current definition file [[Image:16x16--general-save-icon]] .
{{tip| '''Tip''': Although the wizard can handle several files during the same EiffelStudio session, remember that only one file can be used in the project settings to effectively generate a shared library. }}
{{tip|Although the wizard can handle several files during the same EiffelStudio session, remember that only one file can be used in the project settings to effectively generate a shared library. }}

View File

@@ -3,7 +3,7 @@
[[Property:uuid|f3926dd7-eb68-7a82-39f0-b4f5ea891436]]
Basically, once the Eiffel definition file is created, the compiler will generate a set of files and will compile them to generate the Dynamic library into the ''EIFGENs/target_name/W_code'' or ''EIFGENs/target_name/F_code'' directory.
{{note| '''Note''': To generate and compile these files, you have to indicate the definition file that should be used in the [[Advanced Options|advanced node of the project settings]] of your system. This way EiffelStudio will know which one to use. If you do not specify any definition file, nothing will be generated. }}
{{note|To generate and compile these files, you have to indicate the definition file that should be used in the [[Advanced Options|advanced node of the project settings]] of your system. This way EiffelStudio will know which one to use. If you do not specify any definition file, nothing will be generated. }}
The set of files is composed of:
<div>

View File

@@ -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''' <br/>
{{seealso|<br/>
[[External commands editor dialog|External commands Editor dialog]] }}

View File

@@ -53,7 +53,7 @@ Note that any existing breakpoint can be referenced by an implicit tag with ''"'
<center> [[Image:breakpoint-dialog-when-hits]] </center>
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Breakpoint commands|Breakpoint commands]] <br/>
[[Breakpoint information command|Breakpoint information command]] <br/>
}}

View File

@@ -17,7 +17,7 @@ Note: you can sort by clicking the column, especially the first column which pro
<center>Display all breakpoints in a list filtered by a tag using button [[Image:breakpoints-list-filter-button]] <br/>
[[Image:breakpoints-list-filter]] </center>
{{seealso| '''See Also''' <br/>
{{seealso|<br/>
[[Breakpoint commands|Breakpoints commands]] <br/>
[[Breakpoint information command|Breakpoint information command]] <br/>
}}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[Breakpoint editing|Breakpoint menu]] <br/>
[[Breakpoint commands|Breakpoints commands]] <br/>
[[Breakpoint information command|Breakpoint information command]] <br/>

View File

@@ -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''' <br/>
{{seealso|<br/>
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
[[Generating executables|Compiling in Workbench mode]] }}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[Eiffel Debugger Execution: Introduction|Execution commands]] }}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
[[Generating executables|Compiling in Workbench mode]] }}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
[[Generating executables|Compiling in finalized mode]] }}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
[[Generating executables|Compiling in Workbench mode]] }}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
[[Generating executables|Compiling in Workbench mode]] }}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
[[Generating executables|Compiling in Workbench mode]] }}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[Eiffel Debugger Execution: Introduction|Execution commands]] }}

View File

@@ -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. <br/>
{{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. <br/>
If you press the [Control] key during the dropping, you will add the dropped object as itself. }}

View File

@@ -5,9 +5,9 @@ In both grids of the [[Objects tool: Introduction|object tool]] , objects are di
To do so, inherit from the class <eiffel>DEBUG_OUTPUT</eiffel> 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 <eiffel>NUMERIC</eiffel> class inherits from the <eiffel>DEBUG_OUTPUT</eiffel> one so that it is possible to see the value of *_REF objects without expanding them. }}
{{sample|The <eiffel>NUMERIC</eiffel> class inherits from the <eiffel>DEBUG_OUTPUT</eiffel> 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. }}

View File

@@ -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 <code>class_name</code>, <code>type_name</code>, <code>dynamic_type</code>, <code>field_count</code>, <code>deep_physicial_size</code>, and <code>physical_size</code>
{{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.}}

View File

@@ -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. }}

View File

@@ -25,7 +25,7 @@ The diagram tool uses the [http://bon-method.com BON] (Business Object Notation
[[Image:bon-class-root]]
{{seealso| '''See also''' <br/>
{{seealso|<br/>
[[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.
<div> [[Image:bon-cluster-iconified]] [[Image:bon-cluster]] </div><br/>
{{seealso| '''See also''' <br/>
{{seealso|<br/>
[[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
<div> [[Image:bon-inheritance]] </div><br/>
<br/>
{{seealso| '''See also''' <br/>
{{seealso|<br/>
[[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
<div> [[Image:bon-client]] [[Image:bon-agg-client]] </div><br/>
<br/>
{{seealso| '''See also''' <br/>
{{seealso|<br/>
[[Creating client/supplier links|Creating client/supplier links]] }}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[EIS incoming Examples|Examples]] }}

View File

@@ -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''' <br/>
{{seealso|<br/>
[[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''' <br/>
{{seealso|<br/>
[[Variable Definition|Variable Definition]] }}
<code><note ise_support="EIS" protocol="pdf" name="Project Requirement" src="($PROJ)/docs/requirements.pdf" nameddest="4.1"/></code>

Some files were not shown because too many files have changed in this diff Show More