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

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
2 2  
3 3  = Introduction =
4 4  
5 -A WODisplayGroup is a versatile way of fetching objects from the database and displaying them.
5 +A [[WODisplayGroup>>http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/com/webobjects/appserver/WODisplayGroup.html]] is a versatile way of fetching objects from the database and displaying them.
6 6  
7 7  Some of the options a WODisplayGroup can provide you are:
8 8  
... ... @@ -17,11 +17,11 @@
17 17  
18 18  {{/info}}
19 19  
20 -* If you have moved your development to WOLips, the "default" display group is created using the Display Group component editor
20 +* If you have moved your development to WOLips, the "default" display group is created using the //Display Group// component editor.
21 21  
22 -* 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.
22 +* 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.
23 23  
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
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
25 25  
26 26  {{info}}
27 27