Where is Lisping headed?
Lisping is in the App Store, initial sales and feedback are extremely encouraging, and the first update to fix an issue with unicode, add support for the retina display, and improve inline comments is on its way through the approval process. This begs the question - what comes next? where is Lisping headed?
One of my first priorities is support for other Lisps, specifically Clojure. There is no hope of executing Clojure on the iPad as it is dependant on the iOS-prohibited Java runtime, but Lisping will provide an unbeatable way to edit Clojure on the go. Potentially the clojurescript project or even a cloud offering will eventually allow for execution as well.
Lisping's appearance will become configurable in the next few updates. I intend to add a preferences plugin, because as fond as I am of Solarized dark, it is not to everyone's taste. Also, font and size need to be configurable.
Soon after that I will experiment with iPhone/iPod Touch devices and make Lisping a universal application. Lisping's parse tree editor will be even more valuable on the smaller screens where keyboard interaction is even less practical.
Stepping back a bit, Slide To Code is heading towards a Python development environment. As I perfect Lisping's editing mechanics, the code is being refactored ready to start on a Python version. There are many problems with editing python in this way, but it is a great language, and it will be a perfect fit for Lisping's parse tree editor.
Posted on 7 April 2012
Based on a work at http://slidetocode.com/blog
Slide to code blog is licensed under a Creative Commons Attribution 3.0 Unported License