Woah, you're good Robby!
Now that you mention it, it's true that I see this blue box more often.
Well, then, if at some point you feel like coloring contracts... ;)
On Sun, Nov 11, 2012 at 4:30 PM, Robby Findler
wrote:
> Actually, the documentation blue boxes thing in the upper-right corner
> (
Actually, the documentation blue boxes thing in the upper-right corner
(is that also what you're referring to by the identifier information
rectangle) does this. I did it as kind of an experiment to see how
well that approach would work. It seems to be going okay so far, and
it could be generalized
> I'm not sure if that's the best thing, but
> the reason I did it that was was to avoid colors flashing around, as
> the check syntax information comes and goes as you edit the buffer.
>
Ah yes, there might be this problem indeed.
Maybe it could be possible to keep a "partial" state of the syntax
Check Syntax does have this information, but currently uses it only
for tooltips (to indicate who is to blame). Generally speaking, the
coloring is based only on lexing information (like "is this a string?"
"is this a paren?" etc). I'm not sure if that's the best thing, but
the reason I did it that
Hi,
Starting my Xmas wish list:
In case some developer doesn't know what to do (sure...), I think it would
be visually quite helpful if contracts could be syntax-colored, for example
in lighter blue. That would help quickly distinguish between the actual
code and the debugging code.
Thanks :)
Lau
5 matches
Mail list logo
