4 ms·

Reminds me of http://www.lamdu.org/ http://www.lamdu.org/ while trying to remember the name I discovered: https://www.facebook.com/notes/kent-beck/prune-a-co

by chadrs 10y ago

Reminds me of http://www.lamdu.org/ http://www.lamdu.org/ while trying to remember the name I discovered: https://www.facebook.com/notes/kent-beck/prune-a-code-editor-that-is-not-a-text-editor/1012061842160013/ https://www.facebook.com/notes/kent-beck/prune-a-code-editor... http://jetbrains.com/mps http://jetbrains.com/mps https://github.com/cxxtree/cxxtree https://github.com/cxxtree/cxxtree http://www.greenfoot.org/frames/ http://www.greenfoot.org/frames/ http://unisonweb.org/ http://unisonweb.org/ https://github.com/chrisdone/structured-haskell-mode https://github.com/chrisdone/structured-haskell-mode https://www.emacswiki.org/emacs/ParEdit https://www.emacswiki.org/emacs/ParEdit https://github.com/projectured/projectured https://github.com/projectured/projectured

jiyinyiyong 10y ago
Awesome! You may also add these projects: https://github.com/shaunlebron/parinfer https://github.com/shaunlebron/parinfer https://github.com/prettier/prettier https://github.com/prettier/prettier They are fixing the same problem Cirru Project was trying to solve, just in a more practical way.
sedachv 10y ago
Note that some of these (like ParEdit) are just macros for text-oriented editors, and not real structured editors. The earliest structure editor was Interlisp's original structure editor for teletypes, which worked on Lisp lists directly. Editing on teletypes is not anything like editing on video terminals - you are basically forced to edit one line at a time instead of viewing the whole file. That's how ed works. Structured editing made a lot of sense for teletypes because you did not have to worry about putting delimiters in the wrong place, which is very hard to spot when you are doing things one line at a time. There was an Interlisp structured editor (maybe more than one? I'm not sure) written for video terminals in the 1970s. On video terminals structured editing loses a lot of its advantages over text editing and structured editors fell out of style in the 1990s.
Samis2001 10y ago
An addition to this list: http://www.pawfal.org/dave/index.cgi?Projects/Scheme%20Bricks http://www.pawfal.org/dave/index.cgi?Projects/Scheme%20Brick...

by chadrs 10y ago

jiyinyiyong 10y ago

Awesome! You may also add these projects: https://github.com/shaunlebron/parinfer https://github.com/shaunlebron/parinfer https://github.com/prettier/prettier https://github.com/prettier/prettier They are fixing the same problem Cirru Project was trying to solve, just in a more practical way.

sedachv 10y ago

Note that some of these (like ParEdit) are just macros for text-oriented editors, and not real structured editors. The earliest structure editor was Interlisp's original structure editor for teletypes, which worked on Lisp lists directly. Editing on teletypes is not anything like editing on video terminals - you are basically forced to edit one line at a time instead of viewing the whole file. That's how ed works. Structured editing made a lot of sense for teletypes because you did not have to worry about putting delimiters in the wrong place, which is very hard to spot when you are doing things one line at a time. There was an Interlisp structured editor (maybe more than one? I'm not sure) written for video terminals in the 1970s. On video terminals structured editing loses a lot of its advantages over text editing and structured editors fell out of style in the 1990s.

Samis2001 10y ago

An addition to this list: http://www.pawfal.org/dave/index.cgi?Projects/Scheme%20Bricks http://www.pawfal.org/dave/index.cgi?Projects/Scheme%20Brick...