Thanks for this. The advantage (I assume) of a master detail page is that one presumably can set the master object and the key for the relationship and so that component can take responsibility (in a model independent way) for creating, editing and deleting objects hanging off that relationship key.
Using a list with a dedicated pagecontroller will work but perhaps for the simple uses I have (address history, telephone numbers) a master detail subclass may be worth some careful thought on my part. I'll keep you posted! Mark On Wednesday, February 17, 2010, Ramsey Lee Gurley <[email protected]> wrote: > Anjo, > > It basically looks like a select page with an edit underneath it. There's a > screenshot here: > > http://developer.apple.com/legacy/mac/library/documentation/WebObjects/Developing_With_D2W/WalkThrough/WalkThrough.html#//apple_ref/doc/uid/TP30001015-DontLinkChapterID_5-TPXREF104 > > Only slightly terrible? (^_^) I can see room for improvement. "It would be > nice if it did multi-row edits" was the first thing that came to mind when I > saw the screenshot. > > Mark, > > it sounds like you can do what you need to do with a simple list component. > Just put a D2WDisplayToManyFault as your property level component in your > edit page for Patient phone numbers. That will link you off to a list page. > Then, in your list page, you can edit and delete with the table actions and > using a pageController or nextPageDelegate in conjunction with an > ERDControllerButton or ERDActionBar respectively, you can put an 'add new > phone number' button into the interface and have that produce a create phone > number page. All the Master-Detail buys you is an edit section in the same > page as the list. Anjo probably has something similar in Wonder already, > although I'm not certain what that component would be right off the top of my > head. > > Ramsey > > > On Feb 16, 2010, at 4:33 PM, Anjo Krank wrote: > >> I never heard of this either, which is why it's not in Wonder. Do you have a >> screenshot? Is it as terrible as the Edit relationship pages? >> >> Cheers, Anjo >> >> >> >> Am 16.02.2010 um 21:59 schrieb Mark Wardle: >> >>> Hi. >>> >>> I was trying to work out why I didn't know about BASMasterDetailPage, >>> NEUMasterDetailPage or WOLMasterDetail or indeed their superclass >>> D2WMasterDetailPage. >>> >>> It is because there isn't a Wonder equivalent. Wen generating a new >>> look using the (helpfully supplied) Wonder scripts, one doesn't end up >>> with a MasterDetailPage subclass automatically. >>> >>> Which makes me think.... I must be doing something wrong here. I know >>> (by now) that if I start ruminating on starting some new body of code >>> in Webobjects/Wonder then I'm usually on the *wrong* track! >>> >>> Therefore, let me rephrase the question please! >>> >>> I have a custom component displaying patient information. These are >>> sometimes editable and so there is an edit button with a component >>> action. This action creates and returns a D2W page. For instance, each >>> patient may have any number of "telephone" entities (a one to many). >>> It doesn't make sense for users to search (like that seen in >>> EditRelationship) - hence my prior post - but I do want users to add, >>> edit, and delete telephone numbers for that patient. If other people >>> aren't using a MasterDetailPage (its not in Wonder) then what are >>> people using? >>> >>> What is the correct D2W component for handing one to many >>> relationships such as these? >>> >>> Thank you, >>> >>> Mark >>> >>> >>> On 16 February 2010 02:17, Ramsey Lee Gurley <[email protected]> wrote: >>>> >>>> On Feb 15, 2010, at 5:32 PM, Mark Wardle wrote: >>>> >>>>> Dear all, >>>>> >>>>> I'm trying to subclass and customise D2WEditRelationshipPage to create >>>>> a custom look (in fact, I'm subclassing ERNEUEditRelationshipPage). >>>>> >>>>> Specifically, I want to be able to customise the page using the rule >>>>> system. >>>>> >>>>> Firstly, I want to hide the "query" button and the "query" panel. >>>>> >>>>> In the WOD file, I can see: >>>>> >>>>> DisplayQuery: WOConditional { >>>>> condition = displayQuery; >>>>> } >>>>> >>>>> but the displayQuery attribute of the component is part of >>>>> D2WEditRelationshipPage, and I don't have the source code to that. >>>> >>>> >>>> Jadclipse is your friend (^_^) >>>> >>>> http://wiki.objectstyle.org/confluence/display/WOL/Useful+Eclipse+Plugins >>>> >>>> That isn't rule based. It is simply a boolean returning internal page >>>> state. >>>> >>>> >>>>> Secondly, I want to customise the browser component - in fact, replace >>>>> it with an embedded D2WList instead but all of the actions link into >>>>> D2WEditRelationshipPage and without decent documentation (and the >>>>> source code), it is very difficult. >>>> >>>> >>>> I'm not sure I follow you exactly, but it sounds like you may want to look >>>> into subclassing a master-detail type of page. It looks a bit like an >>>> edit relationship page with no query. >>>> >>>> http://developer.apple.com/legacy/mac/library/documentation/WebObjects/Developing_With_D2W/WalkThrough/WalkThrough.html#//apple_ref/doc/uid/TP30001015-DontLinkChapterID_5-TPXREF104 >>>> >>>> Or perhaps a edit list page from Wonder. >>>> >>>> >>>>> This is an issue with subclassing more generally obviously. >>>>> >>>>> Am I missing s -- Dr. Mark Wardle Specialist registrar, Neurology Cardiff, UK _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
