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

Author:halw

Browse Source 
Date:2009-08-04T01:52:15.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@272 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-08-04 01:52:15 +00:00
parent 4679137332
commit f5ec6cd1b9
5 changed files with 20 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-incoming/index.wiki
View File

@@ -1,5 +1,5 @@
[[Property:title|EIS: Incoming]]
[[Property:weight|3]]
[[Property:uuid|cf25a603-5446-9964-892c-227c4077a829]]
Incoming mechanism is based on URI, and introduces a new URI scheme: '''eiffel'''. By entering the URI into address of a browser, or clicking on the hyper link, an existing EiffelStudio instance or new EiffelStudio instance will try to resolve the URI and display corresponding resources.
The EIS incoming mechanism is based on URI, and introduces a new URI scheme: '''eiffel'''. By entering the URI into the address field of a browser, or clicking on the hyperlink, an existing EiffelStudio instance or new EiffelStudio instance will try to resolve the URI and display corresponding resources.

4
documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/index.wiki
View File

@@ -5,7 +5,9 @@
Annotations for outgoing EIS links may be applicable to:
* An individual class or feature. In this case the annotation appears in the class text, as part of an Eiffel <code>note</code> clause (the obsolete keyword <code>indexing</code> may still be supported, depending upon which syntax level is chosen in project preferences).
* A target, library or cluster. In this case the annotation appears in the associated ECF file; EiffelStudio provides support for entering it through the [[Information Tool|Information Tool]].
* A target, library or cluster. In this case the annotation appears in the associated ECF file.
EiffelStudio provides support for entering annotations through the [[Information Tool|Information Tool]].
To specify a link between Eiffel and external information, you include such an annotation.

4
documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/eis-outgoing/information-tool/variable-definition.wiki
View File

@@ -6,7 +6,7 @@ EIS supports following types of variables which can be used in '''Source''' of a
** ISE_WIKI = http://dev.eiffel.com
** EIFFELROOM = http://www.eiffelroom.com
* Context related built in variables. These variables can be used in specific context. For instance, '''feature_name''' refers to the name of the feature in which annotation is written.
* Context related built in variables. These variables can be used in specific context. For instance, '''feature_name''' refers to the name of the feature with which an annotation is associated.
** feature_name
** class_name
** group_name
@@ -14,7 +14,7 @@ EIS supports following types of variables which can be used in '''Source''' of a
{{note|This kind of variable is only valid in a annotation that is associated with a component to which the variable name refers. For example, '''feature_name''' has no effect if used in a '''target''' component.}}
* Individual system or library preferences. This kind of variable is defined in your Project Settings. Manage these variables by following this path in the System tree on the left of the Project Setting dialog:
* Individual system or library preference variables. This kind of variable is defined in your Project Settings. Manage these variables by following this path in the System tree on the left of the Project Setting dialog:
<code lang="text">
System -> Target -> Advanced -> Variables
</code>

12
documentation/current/eiffelstudio/eiffelstudio-reference/eiffel-information-system/index.wiki
View File

@@ -1,16 +1,16 @@
[[Property:title|Eiffel Information System]]
[[Property:weight|-2]]
[[Property:uuid|7e0394e1-cb31-fae3-79b6-9d1847ef8db7]]
The Eiffel Information System (EIS) provides a unified mechanism for linking development objects - e.g., classes and features - of Eiffel systems with '''external''' information. External means information other than Eiffel program texts. Usually the tools associated with external information are separate from Eiffel, such as web browsers. Examples of external information and possible corresponding external tools are:
* Web page - the default browser
* PDF document - Acrobat
The Eiffel Information System (EIS) provides a unified mechanism for linking development objects - e.g., classes and features - of Eiffel systems with '''external''' information resources. External means information other than Eiffel program texts. Usually the tools associated with external resources are separate from Eiffel, such as web browsers. Examples of external information resources and possible corresponding external tools are:
* Resource: Web page -- External Tool: default web browser
* Resource: PDF document -- External Tool: Adobe Acrobat
EIS is also intended to be the standard mechanism for obtaining help on Eiffel and EiffelStudio, replacing previous solutions. In that case external tools may actually be Eiffel tools.
EIS is also intended to be the standard mechanism for obtaining help on Eiffel and EiffelStudio, replacing previous solutions. In that case, external tools may actually be Eiffel tools.
EIS makes two mechanisms available to users: outgoing (from Eiffel to external tools), incoming (the reverse).
EIS makes two mechanisms available to users: '''Outgoing''' (from Eiffel to external tools), '''Incoming''' (the reverse).
Examples of outgoing mechanisms include:
* Annotating Eiffel targets, classes and features to include references to external information. Such annotations can include tags.
* Associating EIS '''annotations''' containing references to external resources with certain Eiffel components of Eiffel systems.
* Automatically opening the corresponding external tool to display or edit information associated with an annotation.
* Listing all external information (in a class, cluster or entire system) corresponding to a specified tag.

12
documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/automatic-completion/class-name-auto-complete.wiki
View File

@@ -5,20 +5,24 @@
The EiffelStudio editor will complete class names automatically. This means, for example, when you type in the editor pane:
<code>
a_variable_name: LI</code>
and then triggers the auto-complete, one of two things will happen:
and then triggers the class name auto-completion, one of two things will happen:
* If there is only one accessible class name that begins `<code>LI</code>', then that class name will be automatically placed in the editor pane at the cursor.
* If there is more than one such class name, the editor will propose a list of possible valid class names, as seen in Figure 1.
Auto-completion can be triggered by pressing <code>Ctrl+Shift+Space</code> or by following the [[Edit menu commands|edit menu]] path:
Class name auto-completion can be triggered by pressing <code>Ctrl+Shift+Space</code> or by following the [[Edit menu commands|edit menu]] path:
<code lang="text">
Edit --> Advanced --> Complete Class Name
</code>
Class name auto-completion is also available in the parents "Entry:" text box on the New Class tool. The functionality is the same as in the Editor pane.
Class name auto-completion is most commonly used in the Editor Pane. But the same functionality is also available in other areas of EiffelStudio, for example:
* The "Entry:" text box on the New Class tool.
* Expressions in the editable grid of the Watch tool
* "Class name:" in the New Expression dialog of the Watch tool.
* "Condition" in the Breakpoints dialog
<br/>
==The class auto-completion window==
The class auto-completion window will pop up and display the list of class names which begin with the string `<code>LI</code>'. So, you can imaging the auto-completion as a search for class names using the characters you type followed by a wild card character, the asterisk (`*'). Of course, you don't have to put the asterisk at the end, it's always there by implication. Once you've triggered the auto-completion, you can however use the wild card character in the middle of a string, like this:
Using the example above, when auto-completion is triggered, the class auto-completion window will pop up and display the list of class names which begin with the string `<code>LI</code>'. So, you can imaging the auto-completion as a search for class names using the characters you type followed by a wild card character, the asterisk (`*'). Of course, you don't have to put the asterisk at the end, it's always there by implication. Once you've triggered the auto-completion, you can however use the wild card character in the middle of a string, like this:
<code>
a_variable_name: LI*R
</code>