(ninth RacketCon): Andrew Blinn – Fructure: A Structured Editing Engine in Racket

Channel:Racket · Length:32:18 · Published:2019-07-19 · Views:9854

Watch on YouTube

Summary

A RacketCon talk presenting Fructure, a prototype extensible structured editing engine in Racket. Language providers define syntactic forms and refactorings as rewrite rules, and editing operates on program structure rather than on text.

Why HN recommends it

Cited as a leading example of structural editing whenever threads discuss alternatives to text-based code editors.

Andrew Blinn gave a neat talk[1] pertaining to structured editing at Racketcon — HN, 2020

Programming language design · Functional programming · Testing, debugging & developer tools

Subtitles (excerpt)

[Music] well thank you very much for that introduction Jay I'm very pleased and slightly terrified to be talking to you all this afternoon about the work I've been doing over the last year basically so yeah my name is Andrew and I've been programming in racket for about two and a half years after being introduced to it during my undergrad which I just finished off at the University of Toronto and yeah this was a project that I thought of basically immediately after encountering racket and I tried out a couple of false starts with it before actually really getting it going in September of last year and let me show you the results of my efforts so aspirationally Speaking fracture is an engine for structured interaction and I'm not going to be talking that much about what I mean by that that's a very kind of general goal but what I have to show you today is a specific application of fracture if you will which is a prototype structured editor for racket code and if you haven't heard the term structured editor before there's a lot of different variations on the concept but the basic idea is that all actions in the editor preserve syntactic well for madness so you can't actually may make a syntactic

On Hacker News

I've seen a few attempts at "structure editors" which are keyboard driven but limit what you can type so it's always syntactically correct. Fructure is an example which looked promising! [VIDEO] — disposedtrolley, 2020-08
For folks interested in this sort of thing, Andrew Blinn gave a neat talk[1] pertaining to structured editing at Racketcon, which credits Cyrus’ work with Hazel. [1] [VIDEO] — loosetypes, 2020-08
using a lisp here simplifies things from implementation and interaction model perspectives. you already have a simple, canonical AST out of the box, which in-principle suffices to support the entire language, not just a toy version. so it makes sense lisps are attractive targets for getting something rolling in this space, though it's certainly debatable whether it's long-term the best choice. (m… — disconcision, 2021-08
I'm not sure I agree with the parent, but to give an example for a non-rectangular UI for manipulating (programming) text: Combine structural editing[1] overlaid on some kind of 3d graph that shows how your entire codebase fits together. [1] [VIDEO] — spaethnl, 2020-04
In my mind the main reason why Vim still has relevance today is for seat-of-your-pants SSH'ing, which admittedly shouldn't be done but it still is. Outside of that... I still have hope for structural editing but I don't see Vim as the innovator in that space anymore. [VIDEO] — threatofrain, 2019-12

Related videos