Skip to Content
Last modified by Pascal Robert on 2010/09/19 10:30
From version 9.1
edited by David Holt
on 2007/12/13 14:36
Change comment: Display Group updated to reflect creation using WOLips
To version 10.1
edited by David Holt
on 2007/12/13 14:46
Change comment: Added some clarification to the descriptions and a warning for the missing Master/Detail section

Summary

Details

Page properties
Content
... ... @@ -6,8 +6,12 @@
6 6  * filter your results using queryOperators and pattern matching
7 7  * display Master/Detail pages
8 8  
9 +{{info title="WOLips Component Editor Display Group Tab"}}
10 +
9 9  What follows is a description of how to use the Display Group editor to configure a display group in the .woo file.
10 10  
13 +{{/info}}
14 +
11 11  * If you have moved your development to WOLips, the "default" display group is created using the Display Group component editor
12 12  
13 13  * If you choose to use the Display Group editor, behind the scenes you are actually modifying your component's .woo file. In general you shouldn't modify the .woo file by hand. The Apple docs define this file as containing information that describes WODisplayGroup objects (and a couple of other things like character encoding). The .woo archive is stored in your component's bundle (.wo) and is used to create and configure the display groups at runtime. There is currently no graphical representation in WOLips to tell you whether the WODisplayGroup has been initialized in the component editor. This was something that WOBuilder showed you in the Layout display mode. You'll have to go into the Display Group editor to determine whether it has been configured or not. The other change from WOBuilder is that an instance variable for your WODisplayGroup with the same name that has been defined in the Display Group editor must be added to the .java file. This is no longer automatic. The end result is that WebObjects will automatically instantiate your display group when the page is created using information contained in the .woo.
... ... @@ -20,6 +20,13 @@
20 20  
21 21  * You should name your display group. The convention is to have the entity name in lower case followed by display group (accountDisplayGroup).
22 22  * You must select the entity from your model that you wish to fetch from the database and display in your application (Account).
27 +
28 +{{warning title="Missing"}}
29 +
30 +Need description for Master/Detail display groups here
31 +
32 +{{/warning}}
33 +
23 23  * If you would like to page your results, a convenient way to do so is to set the "Entities per batch" you would like to display on your page. If you think of results pages for Google searches or flickr photo pages, a good rule of thumb is about 10 items per page. You can use the WOBatchNavigation component to paginate the results for you.
24 24  * You can set how you want your query to the database to be processed in the display group fetch. Do you want the text item at the start of the data (prefix), somewhere in the data (contains) or ending the data (suffix).
25 25  * The "Fetches on Load" tells the component whether the values for the entity to be displayed should be fetched from the database when the page is initially created or not.
... ... @@ -30,4 +30,10 @@
30 30  
31 31  [[image:Display Groups - 002.jpg]]
32 32  
44 +{{info title="Xcode/WOBuilder/EOModeler method to create an automatically initializing WODisplayGroup"}}
45 +
46 +What follows is a description of how to use Xcode/WOBuilder/EOModeler to configure a display group in the .woo file.
47 +
48 +{{/info}}
49 +
33 33  * If you are still using Xcode and WOBuilder/EOModeler, getting started with WODisplayGroups requires very little code and most of the display choices can be wired up in WOBuilder. To get started you simply drag the entity you wish to display from your EOModel into the component where you want to create the WODisplayGroup. Another option is to drag a relationship from your EOModel which will automatically set up a WODisplayGroup with Master/Detail information already set. Another option is to create a DisplayGroup component using the template available to you in XCode under the "Add a new file" option.