mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-08 07:42:33 +01:00
ea60447d34
Date:2008-09-26T02:51:29.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@46 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
20 lines
1.6 KiB
Plaintext
20 lines
1.6 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 - 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:
|
|
* 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).
|
|
|
|
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.
|
|
|
|
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.
|
|
|