> On 25 Sep 2015, at 08:58, Nicolai Hess <[email protected]> wrote:
>
>
>
> 2015-09-24 12:06 GMT+02:00 Andrei Chis <[email protected]
> <mailto:[email protected]>>:
> Hi,
>
> Currently SHRBTextStyler does not highlight variables in the playground.
> This could be added by extending SHRBTextStyler >>#resolveStyleFor: with
>
> workspace
> ifNotNil: [(workspace hasBindingOf: aVariableNode name)
> ifTrue: [^ #workspaceVar]].
>
> Yes, I tried it already, but I couldn't get it to work.
> I would like to have some way to add this to the semantic analyser step.
> If the workspace is defined as a requestore scope, the variable analysis
> should work the same way as if we actual "compile" the code.
>
>
>
> Still this could cause some problems given how MorphicTextAdapter integrates
> Rubric.
>
> MorphicTextAdapter>>setEditingModeFor:withBehavior: can translate #beForCode
> from Spec to #beForSmalltalkScripting in Rubric.
> However for #beForSmalltalkScripting to work the model has to provide
> methods for managing bindings which MorphicTextAdapter does not.
>
>
> This is really difficult, especially because the actual model is different
> for Nautilus code panes and of course any spec based text/code model.
Yes, we really need to put some work into having a unified model behind all our
tools… it’s getting very hard to do anything how it is now.
Marcus
