Not particular reason.
It was coded this way because it was what we needed back at this time :)
Please feel free to improve it
Ben
On 03 Jul 2014, at 12:52, Yuriy Tymchuk wrote:
> Awesome. I’ve missed that somehow.
>
> While I’ve got a reply from you, can I ask one specific question?
>
> As
Awesome. I’ve missed that somehow.
While I’ve got a reply from you, can I ask one specific question?
As Roassal’s view is the main handle to control the visualisation, why can’t
Roassal model use a View as a main property, and we have to use a script? The
thing is that if you want to change som
And you can also find some explanations here:
http://spec.st/docs/interpreter/#collect_the_data
Ben
On 03 Jul 2014, at 12:37, Yuriy Tymchuk wrote:
> Hi,
>
> is there any explanation how SpecInterpreter works?
>
> Because in MorphicRoassalAdapter class you have:
>
> defaultSpec
>
> ^
the SpecInterpreter turns this into
RTViewForSpec new whenLastEventChangedDo: model whenLastEventChangedBlock
where model refers to the instance being currently build
Ben
On 03 Jul 2014, at 12:37, Yuriy Tymchuk wrote:
> Hi,
>
> is there any explanation how SpecInterpreter works?
>
> Because
Hi,
is there any explanation how SpecInterpreter works?
Because in MorphicRoassalAdapter class you have:
defaultSpec
^ #(RTViewForSpec
whenLastEventChangedDo: #(model whenLastEventChangedBlock))
and I cannot find out how this symbol magic is working.
Uko
