Tim, As far as why one custom form appears and not the other, I'm not sure. If you send me the corresponding .tbc file, I can take a look to see if something looks incorrect there. Also, please indicate for which class the form does not appear.
As far as showing different forms based on different ontologies, it may be that a form for the class is defined in both .tbc files, in which case TBC (and TBE) will randomly choose one of those form definitions. If you have a form definition in the UI file, then in the base ontology you need to delete the form definition for the same class. Yes, TBE will respect allValuesFrom restrictions for autocomplete (type-ahead). On Wed, Aug 24, 2011 at 8:49 AM, TIM Smith <[email protected]> wrote: > Hi, > > I'm trying to create custom forms for entering data in TBE. > > Following the instructions in TBE App Dev and Composer Help, I create a > general form for two classes, clear the TBL sessions, reload the TBE app and > only one of the forms shows up - consistently. They are configured the same > (other than the specific properties) and are sub classes of the same parent > (not owl:Thing) > > I do not understand why one would appear in TBE and the other would not. > The form appears almost correctly when creating instances in TBC - since > some of the properties are defined in the form AND are part of > owl:Restrictions on the class, they show up twice on the form in TBC. This > does not happen in TBE. > > In addition, I would like to keep the form definitions separate from the > class definitions so that I can create different views of a class depending > on how I'm using it - much like SWPs. For example, I might want one form > for a Person class when used with a project ontology and another form for > Person when used with a social networking application. > > I've adopted the design pattern where I define my ontology in one file, > create a new file for instances and a third file for UI-related components. > > Can I define a Form in the UI file for a class defined in the ontology > file? My interpretation is that I can do this based on the TBC help pages. > I will create separate UI files for each form needed for the same class. > > However, when I try it, TBC begins displaying the custom form definition > when editing the base ontology file - not just the UI file which imports the > base ontology. Thus I'm confused where the form is actually stored (I know > it is in the .tbc file but which .tbc file?) and where to edit it. > > And last... does TBE respect owl:Restrictions when providing instances for > type-ahead? > > Thanks for your help! > > Tim > > > -- > You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include TopBraid > Composer, > TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. > 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-users?hl=en > -- Willie Milnor Sr. Semantic Solutions Developer TopQuadrant, Inc. 330 John Carlyle Street Suite 180 Alexandria, VA 22314 703.299.9330 www.topquadrant.com <http://www.topquadrant.com> Cell: 410.971.7788 -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. 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-users?hl=en
