Skip to Content
Last modified by Pascal Robert on 2010/09/19 10:30
From version 11.1
edited by David Holt
on 2007/12/13 14:54
Change comment: There is no comment for this version
To version 12.1
edited by Pascal Robert
on 2007/12/15 15:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dholt
1 +XWiki.probert
Content
... ... @@ -1,3 +1,7 @@
1 +{{toc}}{{/toc}}
2 +
3 += Introduction =
4 +
1 1  A WODisplayGroup is a versatile way of fetching objects from the database and displaying them.
2 2  
3 3  Some of the options a WODisplayGroup can provide you are:
... ... @@ -6,8 +6,9 @@
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"}}
13 += Creation a WODisplayGroup with WOLips =
10 10  
15 +{{info title="WOLips Component Editor Display Group Tab"}}
11 11  What follows is a description of how to use the Display Group editor to configure a display group in the .woo file.
12 12  
13 13  {{/info}}
... ... @@ -16,10 +16,14 @@
16 16  
17 17  * 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.
18 18  
19 -* The .woo file is optional if all the information required to initialize the display group is contained in the Java file. This is the key to being able to create a display group programatically and leave the automatic initialization behind. By doing this, you will free yourself from several limitations that an automatically initialized WODisplayGroup is forcing on you behind the scenes. The real aim of this document is to show you where the limitations are, and how you can get around them by initializing the WODisplayGroup yourself in the .java file. This will allow you to configure your display groups in a much more powerful and flexible manner for use in your components. The drawback, as with everything in WebObjects, is that as you get further away from the "default" implementation, your need to understand what you are doing increases significantly. Fortunately this document (will soon be[[image:) here to help you fill in the gaps of your understanding]]
24 +* The .woo file is optional if all the information required to initialize the display group is contained in the Java file. This is the key to being able to create a display group programatically and leave the automatic initialization behind. By doing this, you will free yourself from several limitations that an automatically initialized WODisplayGroup is forcing on you behind the scenes. The real aim of this document is to show you where the limitations are, and how you can get around them by initializing the WODisplayGroup yourself in the .java file. This will allow you to configure your display groups in a much more powerful and flexible manner for use in your components. The drawback, as with everything in WebObjects, is that as you get further away from the "default" implementation, your need to understand what you are doing increases significantly. Fortunately this document (will soon be) here to help you fill in the gaps of your understanding
20 20  
21 -[[image:Display Groups - 003.jpg]]
26 +{{info}}
22 22  
28 +!Display Groups - 003.jpg!
29 +
30 +{{/info}}
31 +
23 23  So, if you have chosen the display group which is automatically initialized from the .woo, here is a brief description of the UI elements you see in the Display Group editor:
24 24  
25 25  * You should name your display group. The convention is to have the entity name in lower case followed by display group (accountDisplayGroup).
... ... @@ -26,7 +26,6 @@
26 26  * You must select the entity from your model that you wish to fetch from the database and display in your application (Account).
27 27  
28 28  {{warning title="Missing"}}
29 -
30 30  Need description for Master/Detail display groups here
31 31  
32 32  {{/warning}}
... ... @@ -39,8 +39,14 @@
39 39  
40 40  Here is the resulting .woo file:
41 41  
42 -[[image:Display Groups - 002.jpg]]
50 +{{info}}
43 43  
52 +!Display Groups - 002.jpg!
53 +
54 +{{/info}}
55 +
56 += Creating a WODisplayGroup with Xcode =
57 +
44 44  {{info title="Xcode/WOBuilder/EOModeler method to create an automatically initializing WODisplayGroup"}}
45 45  
46 46  What follows is a description of how to use Xcode/WOBuilder/EOModeler to configure a display group in the .woo file.