Difference between revisions of "Documentation/DevGuide/Forms/Logical Forms"
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Documentation/Developers Guide/Forms) |
OOoWikiBot (Talk | contribs) m (FINAL VERSION FOR L10N) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 6: | Line 6: | ||
|NextPage=Documentation/DevGuide/Forms/Forms Container | |NextPage=Documentation/DevGuide/Forms/Forms Container | ||
}} | }} | ||
| − | {{DISPLAYTITLE:Logical Forms}} | + | {{Documentation/DevGuideLanguages|Documentation/DevGuide/Forms/{{SUBPAGENAME}}}} |
| + | {{DISPLAYTITLE:Logical Forms}} | ||
<!--<idltopic>com.sun.star.form.component.Form</idltopic>--> | <!--<idltopic>com.sun.star.form.component.Form</idltopic>--> | ||
Forms as technical objects are also part of the document model. In contrast to control models, forms do not have a view representation. For every control model, there is a control the user interacts with, and presents the data back to the user. For the form, there is no view component. | Forms as technical objects are also part of the document model. In contrast to control models, forms do not have a view representation. For every control model, there is a control the user interacts with, and presents the data back to the user. For the form, there is no view component. | ||
| − | The basic service for logical forms is <idl>com.sun.star.form.component.Form</idl>. See below for details regarding this service. For now, we are interested in that it exposes the <idl>com.sun.star.form.FormComponent</idl> service, as well as the <idl>com.sun.star.form.FormComponents</idl> service. This means it is part of a form component container, and it is a container. Thus, in our hierarchy of models, it can be any node, such as an inner node having children, that is, other form components | + | The basic service for logical forms is <idl>com.sun.star.form.component.Form</idl>. See below for details regarding this service. For now, we are interested in that it exposes the <idl>com.sun.star.form.FormComponent</idl> service, as well as the <idl>com.sun.star.form.FormComponents</idl> service. This means it is part of a form component container, and it is a container. Thus, in our hierarchy of models, it can be any node, such as an inner node having children, that is, other form components, as well as a leaf node having no children, but a parent container. Of course both of these roles are not exclusive. This is how data aware forms implement master-detail relationships. Refer to the [[Documentation/DevGuide/Forms/Data Awareness|Data Awareness]]. |
{{PDL1}} | {{PDL1}} | ||
[[Category:Documentation/Developer's Guide/Forms]] | [[Category:Documentation/Developer's Guide/Forms]] | ||
Latest revision as of 12:59, 15 May 2009
Forms as technical objects are also part of the document model. In contrast to control models, forms do not have a view representation. For every control model, there is a control the user interacts with, and presents the data back to the user. For the form, there is no view component.
The basic service for logical forms is com.sun.star.form.component.Form. See below for details regarding this service. For now, we are interested in that it exposes the com.sun.star.form.FormComponent service, as well as the com.sun.star.form.FormComponents service. This means it is part of a form component container, and it is a container. Thus, in our hierarchy of models, it can be any node, such as an inner node having children, that is, other form components, as well as a leaf node having no children, but a parent container. Of course both of these roles are not exclusive. This is how data aware forms implement master-detail relationships. Refer to the Data Awareness.
| Content on this page is licensed under the Public Documentation License (PDL). |
