mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-07 23:32:42 +01:00
8acc8fc8ae
Date:2009-07-31T21:40:40.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@267 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
20 lines
1.5 KiB
Plaintext
20 lines
1.5 KiB
Plaintext
[[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
|
|
|
|
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).
|
|
|
|
Examples of outgoing mechanisms include:
|
|
* Annotating Eiffel targets, classes and features to include references to external information. Such annotations can include tags.
|
|
* 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, selecting external information linked to an Eiffel developer object and having EiffelStudio open automatically and targeted to that object.
|
|
|