[Pharo-dev] Suggested Syntax Highlighting Features for Beginners

J.F. Rick self at je77.com
Tue Apr 8 12:51:20 EDT 2014

I went ahead and created two cases in FogBugz for the respective issues:

That way this issue won't be completely forgotten.

On Fri, Apr 4, 2014 at 7:26 PM, J.F. Rick <self at je77.com> wrote:

> On Fri, Apr 4, 2014 at 6:41 PM, Ben Coman <btc at openinworld.com> wrote:
>> For assignment, I would say bold both := and the variable being assigned
>> to.
> I like that a lot, especially since it draws the two critical elements of
> variable and assignment together. On a minor note, both := and = are
> currently the same color: black. That only furthers the ":= is a message"
> misconception. It might be worthwhile also giving := its own color, given
> its uniqueness.
>> Underlining sounds interesting, but there are a few choices:
>> a. nested underlining - self someMessage: (self otherMessage: arg 1 and:
>> arg2) and: arg3
>> b. non-nested underlining - only underline #otherMessage:and: and not
>> #someMessage:and:
>> c. dynamically underline only message where cursor is located.
> I think you could do nested underlining in the same way that nested blocks
> and parentheses work. someMessage: and the second and: are underlined in
> black. otherMessage: and the first and: are underlined in green. That way
> nesting is clear. This would also be useful for code with nested
> conditionals, probably the most common occurrence of nested multi-part
> messages. I also like (c) as a minimally intrusive change that could help
> novices when they write code. It has the disadvantage that novices couldn't
> look at a piece of foreign code and get where the multi-part messages were.
> Cheers,
> Jeff
> --
> Jochen "Jeff" Rick, Ph.D.
> http://www.je77.com/
> Skype ID: jochenrick

Jochen "Jeff" Rick, Ph.D.
Skype ID: jochenrick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20140408/8d2377cb/attachment-0002.html>

More information about the Pharo-dev mailing list