mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2026-04-04 09:09:22 +02:00
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:
@@ -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]] }}
|
||||
|
||||
|
||||
|
||||
@@ -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>
|
||||
|
||||
|
||||
@@ -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''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[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. }}
|
||||
|
||||
|
||||
@@ -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}}
|
||||
|
||||
Reference in New Issue
Block a user