Scrividh is a text editor with some IDE features. After a raco pkg new and a bit of typing, I have a simple main.rkt: Let’s use it to build the world’s simplest editor. Have a peek at its excellent documentation. Racket has a GUI library, unimaginitively but helpfully named racket/gui. The full text of that license can be found here. I’ve learned some very interesting things! As for now, by the end of this post, we will have a fully-functional source code editor that is capable of not only editing its own source code, but also of reloading itself dynamically to reflect those changes to its code!Īll code developed in these posts shall be licensed under the terms of the GNU General Public License, version 3. Perhaps I’ll share the rest as I continue forward. Most notably, I need to make some shitty pots. Why just write a plugin? Why not make an editor? It was a good idea, and it kills several birds with one stone. Clojurescript isn’t half bad, and there are many things to like about that project. I suppose I could have tried writing my plugin for LightTable. I didn’t want to be spending my time learning Javascript and Node.js when I could be learning about a language I liked and was likely to want to use in the future. I’ll just say I think Javascript is showing its age and it’s not my cup of tea.
I could go off on a rant about Javascript and the many reasons I find it distasteful, but that’s not what this post is about. I started writing a plugin for Atom and immediately hated the experience.
I’d never done it before, but hey no time like the present, right? So naturally my first instinct was to write a plugin for Atom. And before I liked Atom, I liked LightTable (I still do, to an extent). Recently, I was working on tools, considering how I was going to improve my theorem-proving experience with Coq.
0 kommentar(er)
