Difference between revisions of "Documentation/DevGuide/Forms/Form Control Models"
m (1 revision(s)) |
m |
||
| Line 13: | Line 13: | ||
An overview of the whole model tree has been provided. With the code fragments introduced above, the following code dumps a model tree to the console: | An overview of the whole model tree has been provided. With the code fragments introduced above, the following code dumps a model tree to the console: | ||
| − | + | <source lang="javascript"> | |
// dump the form component tree | // dump the form component tree | ||
enumFormComponents(getFormComponentTreeRoot()); | enumFormComponents(getFormComponentTreeRoot()); | ||
| − | + | </source> | |
{{PDL1}} | {{PDL1}} | ||
[[Category: Forms]] | [[Category: Forms]] | ||
Revision as of 20:03, 6 April 2008
- FormComponent Service
- FormComponents Service
- Logical Forms
- Forms Container
- Form Control Models
The control models are discussed in these sections. The basic service for a form layer control model is com.sun.star.form.FormControlModel that is discussed in more detail below. A form control model promises to support the com.sun.star.form.FormComponent service, meaning that it can act as a child in our model hierarchy.
In addition, it does not claim that the com.sun.star.form.FormComponents service (plural s) is supported meaning that form control models are leaves in our object tree. The only exception from this is the grid control model. It is allowed to have children representing the models of the columns.
An overview of the whole model tree has been provided. With the code fragments introduced above, the following code dumps a model tree to the console:
// dump the form component tree enumFormComponents(getFormComponentTreeRoot());
| Content on this page is licensed under the Public Documentation License (PDL). |
