There is a MetalinkIconStyler already.
But I think that it is better to have stylers for the users of metalinks, e.g.
there is a special
styler for breakpoints.
I see the general styler more as a debug tool (it is off by default).
Marcus
> On 14 Dec 2016, at 05:10, Yuriy Tymchuk <yuriy.tymc...@me.com> wrote:
>
> By the way, we need to add a rubric highlighting to the classes somehow :).
>
> Uko
>
>
>
>> On 12 Dec 2016, at 13:36, Marcus Denker <marcus.den...@inria.fr> wrote:
>>
>> Hello,
>>
>> Not yet. It should be easy to add if we find a good API for it…
>>
>> I will work on it this week (I have blocked some time for RF related
>> hacking).
>>
>> e.g I think we have to extend the syntax for reifications to use classes.
>>
>> something like:
>>
>> arguments: {RFTempReification named: #trachelCanvas};
>>
>> The current symbols then would be the same as using
>>
>> RFReification named: #object
>>
>> But subclasses can be used directly and parametrized.
>>
>> Marcus
>>
>>> On 5 Dec 2016, at 20:42, Peter Uhnak <i.uh...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> what is the best way to access variables from within a metalink?
>>>
>>> for example I have a message send `surface clear` and I want to change it
>>> to `surface clear: trachelCanvas color`.
>>>
>>> I can use #instVarNamed:
>>>
>>> ```
>>> MetaLink new
>>> metaObject: [ :object |
>>> (object instVarNamed: #surface) clear: (object instVarNamed:
>>> #trachelCanvas) color.
>>> ];
>>> selector: #value:;
>>> arguments: #(object);
>>> control: #instead.
>>> ```
>>>
>>> but the above isn't exactly nice, plus it wouldn't work with temporary
>>> variables.
>>>
>>> Thanks,
>>> Peter
>>>
>>
>>
>
>
