|
When
you set the properties of objects in the Windows Designer, you are
"painting" objects and their components through WYSIWYG
functionality. This WYSIWYG functionality mediates between what you
are doing in the Windows Designer, and how these classes are
represented/defined internally in the ESI repository. This
mediation is possible because you are working on example instances
of classes. You are editing by example.
If you use the ESI action
interface, you edit the ESI object model directly via scripts with
action calls. You do NOT work on example instances, and there is no
mechanism to mediate for you. Therefore, there is much for you to
understand.
Edit Session
What an ESI action script does basically is to perform an edit
session. That is, you open an existing application or create a new
one, and then you perform class definition and class manipulation
activities.
Class Definition
In the class definition activity, you add or delete classes by
calling the corresponding actions (instead of doing it
interactively).
Class Manipulation
In the class manipulation activity, you repeatedly select
components, modify their properties, and then save your work.
Component Selection
To select components you must manually provide context
identifiers, (rather then by means of pointing and clicking).
Property Modification
Properties are modified by setting properties, and by inserting
or deleting controls. Again this is done by calling the
corresponding actions.
|
