Holger, That is really cool!
On Jul 22, 2009, at 5:38 PM, Holger Knublauch wrote: > > The applicability of the widget types is controlled by the forms > ontology. You can edit this as forms.owl in TBC and then copy your > updated version into the org.topbraid.forms plugin under <eclipse>/ > plugins/org.topbraid.forms/etc. > > For example, forms:Tree has forms:widgetTypeRange of rdfs:Resource, > meaning that it can be applied to all properties that point to other > resources. This mechanism is not sophisticated enough to distinguish > between transitive properties etc. > > Holger > > > > On Jul 22, 2009, at 3:14 PM, Arthur Keen wrote: > >> >> Irene, >> >> Thanks for the quick reply. I have one more question on the >> applicability of the widget or restrictions of use. For example, are >> Table widgets only applicable to ObjectProperties and are Tree >> widgets >> only applicable to Object Properties that recursively form trees like >> hasChildren on person or hasPart on a bill of materials or worksFor >> on >> Employee. >> >> Arthur >> >> On Jul 22, 2009, at 4:54 PM, Irene Polikoff wrote: >> >>> >>> Hi Arthur, >>> >>> These settings are not for TBC, but rather for the web applications. >>> Widget >>> types get saved in .tbc file which can then be used to drive >>> applications. >>> >>> In the 3.1 release the only widget type that is "honored" by the TBE >>> applications is RichText. This type is available for any property >>> with the >>> range of xsd:String. >>> >>> Regards, >>> >>> Irene >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of >>> Arthur >>> Sent: Wednesday, July 22, 2009 5:24 PM >>> To: TopBraid Composer Users >>> Subject: [tbc-users] What does Preferred Widget Type do? >>> >>> >>> I experimented with the preferred widget type on the forms layout >>> panel in TBCM 3.0.1 and now in 3.10. My expectation has been that >>> the preferred widget type would alter the way the property is >>> displayed on an instance form. However, selecting a preferred type >>> widget ( Default, Table, Tree, TextInput, RadioButtons, or ComboBox, >>> etc.) has no visible effect on the way the property is rendered on >>> an >>> instance form. What is also puzzling is that the same list of >>> preferred widget types appear for ObjectProperties and >>> DatatypeProperties. >>> The docs have no information on the "Preferred Widget Type" feature. >>> >>> Thanks >>> A >>> >>> >>> >>> >>> >>>> >> >> >>> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
