Hi Damien, thanks for the code, I put it into the latest version of Magritte in the development repository. Hi Ian, this is done in 'Magritte-All-lr.94'. You might also want to try loading 'Pier-Forms-lr.2', that includes a sortable report-view, see attached screen-shot. The report displays the values of the common descriptions of all the children of the current structure. It does not yet allow deleting or editing children directly, but you can navigate to the child using the tree-control and use the appropriate actions there. What do you think? Already more useful without much additional code ;-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch

On 24 Nov 2005, at 19:17, Lukas Renggli wrote: Pretty cool and generic. I like how "Reporting" on the root page displays a sortable list of page titles, neat side-effect! 2 questions: 1. Do pages always have title descriptions? If so, providing a link on the displayed title might be nice. 2. Is there a UI for the batch size of the report? Ian.

Hi I'm playing with the latest Magritte and generating some forms for a couple objects to test out how relationships between objects works, I'm running into some trouble. At first I thought it was something wrong with my code. descriptionProject ^(MASingleOptionDescription selector: #project label: 'Project' priority: 10) reference: MAClassDescription new; options: (MADynamicObject on: [ TMProject repository asArray]); beRequired; beSorted ; yourself but after writing a lenghy email explaining the issue, it struck me what it might be, so I popped into MADescription and commented out the code for validateKind: anObject. Turns out that fixed my issue. Validation was failing because the objects I had in a single option description were proxies coming from goods, and they fail validateKind:, has someone else run into this? Guess I'll just leave it commented out for now until there's a fix, or I figure out what I'm doing wrong.

No, it is the call to isKindOf from the super class that is failing, the call to includes works fine. My project class does implement #= and hash, and uses a UUID string for identity. self kind is resolving to Class class, since isKindOf is being sent to anObject, that should resolve the proxy, so perhaps something is wrong with: descriptionProject ^(MASingleOptionDescription selector: #project label: 'Project' priority: 10) reference: MAClassDescription new; options: (MADynamicObject on: [ TMProject repository asArray]); beRequired; beSorted ; yourself MAClassDescription seems wrong, looking now, I see why isKindOf is failing, I'm not filling the dropdown with classes, but I don't see what's appropriate, without it I get MessageNotUnderstood: TMProject>>do:. So how do I use other domain objects in a SingleOptionDescription rather than just a simple list of symbols or strings? ________________________________ From: owner-smallwiki(a)iam.unibe.ch on behalf of Lukas Renggli Sent: Mon 11/28/2005 5:41 AM To: smallwiki(a)iam.unibe.ch Subject: Re: Magritte Validation Error The method #validateKind: for MASingleOptionDescription look like (I merged in the super-call): MASingleDescription>>validateKind: anObject (anObject isKindOf: self kind) ifFalse: [ MAKindError on: self ]. (self isExtensible or: [ self options includes: anObject ]) ifFalse: [ MAKindError on: self ]. anObject is used as a receiver for #isKindOf: and #= within #includes:. I think the #isKindOf: should resolve any proxies, but there is probably a problem with the #includes:. I think the point is that your project-class doesn't implement #= and therefor defaults to #==, so you the #includes: identity-compares every project with the proxy ... what fails of course. Lukas -- Lukas Renggli http://www.lukas-renggli.ch <http://www.lukas-renggli.ch>

Err, never put a *domain-object* into a single-description ;-) -- Lukas Renggli http://www.lukas-renggli.ch