16 Oct
2007
16 Oct
'07
10:07 a.m.
Now, I think the issue with the main site is not so
bad, I would just
define my #description methods as normal, right? Since #description
is taken already I guess I have to override it on the instance side
and call MANamedBuilder for: myself?
Yes, that's the simplest possibility.
And the other question is, how do I enforce that when
Magritte wants
to make a new instance of these other two classes that it uses my
custom constructor, not #new?
Magritte does not have the possibility to specify a different
constructor.
Since the custom constructor is going
to expect a portion of the data already, I'm guessing I need some kind
of Memento? I suppose I could just let it create the object with new,
and then have the accessor create the "real" object from this, but
that seems very cheesy.
Yes, if you have descriptions for your constructor arguments you can
use the MAAdaptiveModel to let the user enter the constructor data
and then you feed these values into the constructor itself. I guess
there is no easier way.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch