Re: Accessing a string from a display group.
Re: Accessing a string from a display group.
- Subject: Re: Accessing a string from a display group.
- From: Matt Harmon <email@hidden>
- Date: Wed, 11 Jan 2006 15:54:11 -0700
Quoting "Jerry W. Walker" <email@hidden>:
Hi, Matt,
Hi Jerry and everyone else and thanks for your response(s).
You should see three files listed there with
suffixes: .html, .wod, .woo. Click on the file with the .woo suffix
and Xcode should show you a plist containing the initialization
parameters for the WOComponent, which should include the
initialization for the display group.
Indeed, these are there and the .woo file contains a specification for the
DisplayGroup.
For your immediate problem, go to the WODisplayGroup JavaDocs. The
display group is holding an array of EOs. You want to get to that
array to manipulate its elements in some way. The array is given to
you through the allObjects() method:
public NSArray allObjects()
Provides all of the objects collected by the WODisplayGroup. This
collection differs from that provided by displayedObjects. Typically
this collection will comprise the results of the last fetch from the
WODisplayGroup's dataSource.
Well, this is what I suspected...Though when I call the allObjects() method on
the DisplayGroup in question, the application fails. The code compiles without
error, which to me indicates that the method is, of course, valid for the
object and that the object exists, but that I'm missing something (probably
very simple) in the execution of (or setup for) the method.
It's helpful to simply peruse the WODisplayGroup API page and the
WODisplayGroup.Delegate Interface page, reviewing the members and
methods described there.
Calls to DisplayGroupInQuestion.valueForKey() and also cause the
application to
fail.
In general, if your predecessor used display groups extensively on a
project that you will be maintaining as you suggest, you will be far
better off learning and working with his/her display groups, than you
will be if you try to take it all back down to the code level.
Indeed, in these cases a DisplayGroup is a perfect choice. (Perhaps it sounded
as though I was complaining before regarding the use of DisplayGroups but I
wasn't...I meant to emphasize the importance of this information relative to
the application in question).
My earlier reference to programmatically attaching the DisplayGroup to
a "hard"
fetch specification was based on the examples I've seen which provide
information about inserting, saving and deleting the objects in a
DisplayGroup.
I've had difficulty locating an example of accessing (and evaluating) a
variable
within a DisplayGroup. This lead me to believe that this was perhaps
"Something
That One Does Not Do" in WebObjects.
Anyway, thank you very much for the information that you have provided,
Matt Harmon
Attachment:
biniadt3kWgMZ.bin
Description: PGP Public Key
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden