Clojurians
#parinfer
<
2016-03-26
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

cfleming02:03:36

@sekao: That’s great, thanks for the report

cfleming02:03:31

Have you noticed them using the slurp-and-barf-lite functionality, i.e. have you seen them inserting and deleting parens in the middle of lines, or is the indent/dedent the main benefit for them?

sekao14:03:44

@cfleming: i think that aspect of parinfer took longer for them to internalize since the behavior is more subtle. a woman in my class was trying to make an input tag in hiccup but she closed the attr map too early so it looked like this: [:input {:type “text”} :name “message”]

sekao14:03:01

she was initially confused when she couldn’t simply write the end curly brace after ”message” but since then I’ve seen her inserting and deleting correctly

sekao14:03:23

i have never explicitly told them the editing rules because i wanted to see if they could figure them out on their own, and so far it seems they are

sekao14:03:03

but yeah, i think indent/dedent was the most intuitive part initially

shaunlebron14:03:09

@sekao: cool, how much longer will they be using it? was it just for the week?

sekao14:03:26

We have another week of clojure. I'm thinking about switching to cursive so we can use the debugger, they do miss that since we used it so much with java

sekao17:03:37

One thing that may help people visualize scope is to color the entire background of a given s expression rather than just the delimiters like rainbow parens does. I wonder if any editor does that

shaunlebron17:03:09

funny, that was @denik's first reaction to seeing lisp

shaunlebron17:03:26

dont know of any editor that does it

shaunlebron17:03:28

i think it might be overwhelming to nested rainbow boxes

shaunlebron17:03:45

unless their borders were collapsed

adamkowalski18:03:05

maybe rather then nested rainbow boxes, the current scope could have a background hue, while the outside scope could use standard rainbow parnes

adamkowalski18:03:35

that way you can see the scope you are working it very clearly, without being overwhelmed with colored boxes everywhere

adamkowalski18:03:07

or even just have a colored rectangular outline rather then a filled in rect

sekao18:03:58

@adamkowalski: great idea, i’m going to experiment with that in my paren-soup project

denik21:03:53

ha! @shaunlebron @sekao I think it would be worthwhile. I’d like a keyboard combination that I have to hold to preview scope - nothing permanent.

denik21:03:51

To understand something one has to look at it from different angles, right? 😉

shaunlebron22:03:17

I feel like sublime text used to outline the current expression you were in automatically

adamkowalski22:03:12

another thing that I thought was a really interesting idea is what is shown here at 14:45 https://www.youtube.com/watch?v=b0EF0VTs9Dc

adamkowalski22:03:06

The idea is context coloring rather than syntax coloring, and the claim is that professional programers don’t benefit from highlighting syntax as they know what it means. instead the color of the text should signify within what scope is it valid