At least you get to use a reasonable language to build extensions...
Conversation
1
That'll do it. If you don't want to use the #lang for anything but slides, then this might be overkill relative to just writing some regexps to dump a highlighted picture out of a string.
1
1
Might be good procrastination material for my next talk! At least I'd learn more about Racket's language implementation stuff! Always wanted to have an excuse to learn. 🤔
1
1
You can also go completely over the top like I did for ICFP 16 and have your compiler talk to your slides over a socket for a mini ide in the slides...
1
1
Hah, I liked that one! Where you showed off Pie? Looked super nice.
1
This one was Idris: m.youtube.com/watch?v=pqFgYC
2
1
Pie runs in-process, no need for the socket
1
Yeah, I thought that seemed extravagant! 😂
1
If you write your type checkers and slides in the same language, it makes that kind of trick easy!
1
Perhaps I need to make a Rust slideshow tool....
(nooo, this is the path to the dark side...)
A slideshow that talked to RLS would be about a day's work, I think. Maybe 3 if you've never done Racket GUI programming before.
1
Oh, this is for my own language, Pikelet, which is implemented in Rust. It does not yet have a language server, alas (on the roadmap, hehe). Will be wanting to do a presentation at some stage, so preparing tools before the last minute is always handy!
1
Show replies