The behaviour of the guidesigner can be customized by setting
properties in the file script/guidesign.properties in your
project directory. You can have different settings for different
projects.
For a description of all guidesigner properties see: Appendix B: Guidesigner properties(Reference B: Guidesigner Properties)
You can customize which classes the guidesigner uses as base
classe for the classes it generates. You customize them by writing
<classname>=<customclass> . e.g. if you want
all dialog pages be derived from your class "MyDialog":
DialogPage=MyDialogPageThe following properties for classnames are defined:
DialogPage client side base class for all
dialog pages
EmbeddedPage client side base class for all
embedded pages
NotebookPage client side base class for all
notebook pages
PageServer server side base class for all page
types
EmbeddableComponent client side base class for
all embeddable components
ComponentClient client side base class for all
other components
ComponentServer server side base class for all
component types
Page.include=<package>.* Page.include=at.spardat.krimicee.xma.pagecustomizer.*The needed includes for all component classes are defined by writing
Component.include=<package>.*Setting allComponentsEmbeddable=true tells the
guidesigner to generate all components embeddable. This enables you to
embedd components containing only dialog pages, too.
You can customize the classes the guidesigner uses for server side widget models. This enables you to add additional functionality to the server side widget models. Such server side model classes must be derived from the original widget model classes (see Widget Model Gallery).
The server side model interfaces and classes are customizable individually. E.g. to use your own class "MySimpleWM" for simple widget models, you write the following line in guidesign.properties:
SimpleWMServer=MySimpleWM
See Reference B: Guidesigner Properties for the list of properties to customize each model class.