Iwan Vosloo wrote
a MAContainerComponent creates its children components
when it get
initialised - all on top of a set of related Descriptions that can never
be replaced by others.
Wouldn't it be simpler to just change visible: to be able to take a
block...
You've hit a limitation of Magritte - forms are fairly static. A "view" is
pretty much just a read-only form. Even when you edit the object, you're
usually editing a cached Memento, not the object itself. I've sometimes
thought about an MAUpdatingMemento, but unless the object is designed for
this (e.g. sends announcements) you'd have to use polling.
Anyway, the upshot is that #visible: doesn't take a block because Magritte's
design freezes forms in time. If you want to do things a different way, it
will take more than a block (which would still only be evaluated once), but
a rethinking of the infrastructure. Of course, this being Smalltalk, why
not!
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Understanding-dynamic-descriptions-tp4840991p4843449.…
Sent from the Magritte, Pier and Related Tools mailing list archive at
Nabble.com.