ITT Rule IDL Version 7.0 ユーザーズマニュアル
14
Chapter 1: Overview of iTools
About the iTools Code Base
iTool Developer’s Guide
•
The core iTool component framework classes used to build individual iTools,
visualization types, operations, etc. are formally documented in the IDL
Reference Guide and discussed in detail in this manual. If an object class,
method, or property is necessary for the construction of a new iTool or
component of an iTool, it is formally documented in the IDL Reference Guide
or in this manual. Core iTool framework classes are located in the
visualization types, operations, etc. are formally documented in the IDL
Reference Guide and discussed in detail in this manual. If an object class,
method, or property is necessary for the construction of a new iTool or
component of an iTool, it is formally documented in the IDL Reference Guide
or in this manual. Core iTool framework classes are located in the
lib/itools/framework
subdirectory of the IDL installation directory.
•
Supporting iTool component framework classes — those used to implement
the documented component framework classes — are not formally
documented. As noted previously, the code for these classes is available for
inspection. Supporting iTool framework classes are located in the
the documented component framework classes — are not formally
documented. As noted previously, the code for these classes is available for
inspection. Supporting iTool framework classes are located in the
lib/itools/framework
subdirectory of the IDL installation directory.
•
Derived iTool classes — those used to implement individual iTools and their
features — are not formally documented. These classes are derived from the
formally documented classes, and as such can be understood by referring to the
formal documentation. Derived iTool framework classes are located in the
features — are not formally documented. These classes are derived from the
formally documented classes, and as such can be understood by referring to the
formal documentation. Derived iTool framework classes are located in the
lib/itools/components
subdirectory of the IDL installation directory.
•
iTool user interface routines are not formally documented. These routines use
standard IDL widget programming techniques, and as such can be understood
by referring to the IDL widget documentation. User interface routines are
located in the
standard IDL widget programming techniques, and as such can be understood
by referring to the IDL widget documentation. User interface routines are
located in the
lib/itools/ui_widgets
subdirectory of the IDL installation
directory.
Warning on Using Undocumented Features
While you are encouraged to inspect the iTools code, and to copy or subclass from
derived classes and user interface routines, be aware that classes and routines that are
not formally documented are not guaranteed to remain the same from one release of
IDL to the next. Keep the following points in mind when implementing your own
iTools:
derived classes and user interface routines, be aware that classes and routines that are
not formally documented are not guaranteed to remain the same from one release of
IDL to the next. Keep the following points in mind when implementing your own
iTools:
•
ITT Visual Information Solutions will change undocumented supporting
classes as necessary to improve the iTools system.
classes as necessary to improve the iTools system.
•
ITT Visual Information Solutions may also change undocumented derived
classes to fix problems or add functionality; in these cases, we will make every
effort to preserve backwards compatibility, but this is not guaranteed.
classes to fix problems or add functionality; in these cases, we will make every
effort to preserve backwards compatibility, but this is not guaranteed.
If you create new iTool classes based only on the formally documented iTool
interfaces, your tools should operate properly with future releases of IDL. If you base
your tools on undocumented derived classes, minor modifications may be necessary
to ensure future compatibility.
interfaces, your tools should operate properly with future releases of IDL. If you base
your tools on undocumented derived classes, minor modifications may be necessary
to ensure future compatibility.