mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2026-04-05 09:39:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

Author:halw

Browse Source 
Date:2009-07-31T21:40:40.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@267 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-07-31 21:40:40 +00:00
parent ec40496d9d
commit 8acc8fc8ae
5 changed files with 19 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,19 +1,19 @@
[[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 - classes, features and so on - of Eiffel systems with external information. This term refers to information other than Eiffel program texts. Usually the tools maintaining external information are separate tools, such as a browser; we call them external tools. Examples of external information and possible corresponding external tools are:
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
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.
The basic mechanisms that EIS makes available to users include two categories: 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.
* By selecting an annotation in EiffelStudio, automatically open the corresponding external tool to display or edit that information.
* Provide a list of all external information (in a class, cluster or entire system) corresponding to a specified tag.
* 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.
Examples of incoming mechanisms include:
* For supported tools, select external information linked to an Eiffel developer object and have EiffelStudio directly open on that object. In 6.2, eiffel: schema is supported on Windows.
* For supported tools, selecting external information linked to an Eiffel developer object and having EiffelStudio open automatically and targeted to that object.