With regards to the issue I posted below... Note that the file I open in TBE is the Instance data file, which imports the ontology and the UI file.
In order to get TBE type ahead functionality to recognize the classes I added to the UI file (using TBC) I ultimately had to force TBL to rebuild the dictionary for the instance data file by deleting the existing index. That seemed to cause TBL/E to load the re-created UI dictionary as well. In cases where the dictionary for a file that is imported into the file that is opened by TBE is updated, does TBL/E recognize this and reload that dictionary or does it only look at the dictionary for the main file? Thanks, Tim On Thu, Aug 25, 2011 at 12:08 AM, Tim Smith <[email protected]> wrote: > Thanks to all for your suggestions! > > Instead of trying to deal with multiple form definitions in different > files, I'm going to use the TBE Form Definition Class attribute. > > For my first test of this, I created an ontology in one file, put some > instances in another file, and finally created a third file to hold UI > functionality. In the UI file, I created a couple of classes and defined a > custom form for each one. The instance file imports the other two. > > Using the default TBE application, I load the instance file. In the Select > Class Tree, I can see the classes with the forms defined in the UI file. > > However, when I edit the configuration of the Form component in order to > set the Form Definition Class attribute, the text box does not recognize the > name of the class that contains the Form I want to use. I've re-created the > dictionary/index for the UI file, cleared all sessions, and restarted TBE in > a new browser but the Form Definition Class attribute text box still does > not see the class although it is plainly visible in the class tree. > > Anything else I need to try to make this class visible to the configuration > windows? > > Thanks, > > Tim > > > > On Wed, Aug 24, 2011 at 3:04 PM, Bob Ducharme > <[email protected]>wrote: > >> Tim,**** >> >> ** ** >> >> I assume that you’re talking about the forms that are defined in TBC that >> can be used in the TBE Form component, as opposed the Search and Entry forms >> that can also be created in TBE. **** >> >> ** ** >> >> When you define forms in TBC, they are stored I a file that has an >> extension of tbc, like the foaf.owl.tbc file in the TopBraid/Common folder. >> I’ve never seen anyone create multiple tbc form files for the same ontology >> (for example, an additional one for foaf.owl), and doing this, or using two >> different form definitions for the same class in an imported and importing >> graph file, could lead to unpredictable behavior. **** >> >> ** ** >> >> To create different forms in TBE for the same class, you could design them >> in TBC attached to other classes created for that purpose and then use the >> Form Definition Class attribute in TBE to point to the appropriate one. For >> example, let’s say that for the Person class you defined one form attached >> to a new display:PersonSummary class and another to a new >> display:PersonDetail class. When you build your TBE app, you could create >> one Form component to display Person instances and set that component’s Form >> Definition Class attribute (under "Form Attributes" on the TBE Application >> Configuration dialog box) to display:PersonSummary, and you could create a >> separate Form component to also display Person instances but with its Form >> Definition Class attribute set to the display:PersonDetail class. That way, >> you have two different forms to display Person data. **** >> >> ** ** >> >> For even more flexibility in your TBE app, you can set the form >> component’s “Update the Form Definition Class” attribute to switch the form >> from using one class’s form to another (e.g. from display:PersonDetail to >> display:PersonDetail) when a certain TBE event got triggered, to adjust to >> the context of the user’s activity. **** >> >> ** ** >> >> Would this approach help? **** >> >> ** ** >> >> > And last... does TBE respect owl:Restrictions when providing instances >> for type-ahead?**** >> >> ** ** >> >> Not that I know of. **** >> >> ** ** >> >> Bob DuCharme**** >> >> TopQuadrant**** >> >> ** ** >> >> ** ** >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *TIM Smith >> *Sent:* Wednesday, August 24, 2011 8:50 AM >> >> *To:* [email protected] >> *Subject:* [topbraid-users] Questions Creating Custom Forms for TBE**** >> >> ** ** >> >> 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**** >> >> -- >> 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 >> > > -- 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
