As John writes, create custom Morph classes and set them using
#morphClass:. MATextMorph is a nice default if there is nothing
better, because all descriptions have a way to convert their model to
a string. Compared to Magritte-Seaside there are a lot of views in
Magritte-Morph missing, simply because Magritte-Morph never saw the
use of Magritte-Seaside.
Lukas
On 4 January 2012 02:55, Sean P. DeNigris <sean(a)clipperadams.com> wrote:
Exploring around, I found that
MAToOneRelationDescription inherits
class>>#defaultMorphClasses from MAElementDescription, which returns an
MATextMorph, so I thought about subclassing my own description or setting
the default morph class property, but it seems that by the time the
description is looking for a morph class, it may be too late, no? What I
really want is to recursively embed the full editor for the related Author
class in the form for the Book, but I'm not sure exactly where to hook in.
#acceptMagritte: seemed like an obvious place, but everything seems already
figured out by the time it's called - although maybe that's due to caching?
Can caching be turned off to more easily see what's going on?
Lukas, in one of the posts, you mentioned that you had some ideas on how to
fix this. I'd like to have a conversation about that.
Also, for the time being, I'd just like to know where I should hook in to
manually display an editor for the author object. I also want to add
auto-complete to some fields...
Thanks.
Sean
--
View this message in context:
http://forum.world.st/Magritte-Complex-Models-tp4259124p4259524.html
Sent from the Magritte, Pier and Related Tools mailing list archive at
Nabble.com.
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki