Just stepping back I have a question below. First let me say, please don't
take offense if the question is too basic. I grapple all the time with the
question of "is the model logic?", or "is it application specific
Remember that Magritte descriptions help define default dialogs/editors for
*one* imagined application using the object, but there is no way you will
define one set of Magritte descriptions for all applications of instances
of your class. [At least for highly reusable model components.]
Even with "one" imagined solution, Magritte helps you put an interface on
the object, but much of your interaction with the object may be through
other code that does not stop to ask the MagritteDescription how to do
So my first question is: Is this a presentation problem/question or a model
Why not define a method to get the #effectiveDate or whatever method. You
said "to many" relationship, so which date should be displayed if there are
5 associated objects and they all have different dates? This sounds like
some logic that belongs outside of the magritte description.
I quickly gave up trying to be "minimal" with Magritte descriptions. They
are very handy and powerful. So I just clone them to create new ones that
serve my needs... and move on.
On Mon, Oct 7, 2013 at 4:20 PM, John McKeon <p3anoman(a)gmail.com> wrote:
On Sun, Oct 6, 2013 at 10:18 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote:
> I have a described object, let's call it parent. It has a to-many
> The reference may be an instance of multiple classes, but all have a date
> field, which I want to default to the date of the parent object. How do I
> View this message in context:
> Sent from the Magritte, Pier and Related Tools mailing list archive at
> Magritte, Pier and Related Tools ...
Magritte, Pier and Related Tools ...