Posted by
Iwan Vosloo on
Aug 17, 2015; 9:27am
URL: https://forum.world.st/Understanding-dynamic-descriptions-tp4840991p4843420.html
On 05/08/2015 14:35, Iwan Vosloo wrote:
> On 05/08/2015 13:13, Stephan Eggermont wrote:
>>
>>> Op 5 aug. 2015 om 11:42 heeft Iwan Vosloo <
[hidden email]> het
>>> volgende geschreven:
>>>
>>> But it seems that visible: can only take a Boolean, which the
>>> description then retains for the lifetime of the description.
>> Normally the evaluation happens at component creation time. You can
>> however use a builder that evaluates at other points in time. The
>> component has a reference to the description so everything you need
>> is there. You just need a smarter builder and/or component
>>
>
I have looked at this a bit more... but still have no clue as to how to
do this. I get lost somewhere between MAPRagmaBuilder and the fact that
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 similar to addCondition: and always evaluate that block when
isVisible is called (for example)? This can be done consistently for a
bunch of other things too, like isReadonly, isRequired etc.
Regards
- Iwan
--
Reahl, the Python only web framework:
http://www.reahl.org_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki