Teliva - an environment for end-user programming
“Enable all people to modify the software they use in the course of using it.” — https://futureofcoding.org/episodes/033.html
“What if we, and all computer users, could reach in and modify our favorite apps?” — https://www.inkandswitch.com/end-user-programming
“Software must be as easy to change as it is to use.” — https://malleable.systems
What's this, then?
git clone https://github.com/akkartik/teliva
Here's an example app (the Tower of Hanoi):
No matter what app you run, you are always guaranteed access to a single
obvious, consistent way (currently the hotkey
ctrl-e) to edit its sources.
And to run the updates after editing.
Toggle the same hotkey to restart the app with the new sources.
Over time I hope to improve the experience for error messages, failing tests, undoing changes and so on. The emphasis will be on maximizing hackability rather than functionality. In addition to Lua 1.5, this repository currently packages:
- The ncurses library for building text-mode user interfaces. (Alternative documentation)
- A port of the lcurses library providing Lua bindings for ncurses. (Documentation)
- The Kilo text editor. (With a fantastic walk-through.)
Send all praise to them, brickbats to me. I plan to be extremely parsimonious in taking on further dependencies.
Isn't this just an IDE?
There's one big difference: these apps are not intended to be runnable outside of the Teliva environment. Editing the sources will always be a core feature that's front and center in the UI.
At the moment this isn't much of a restriction given how trivial the differences with Lua are. You also don't get much benefit in exchange for taking on this restriction. Let's see if that changes.
A second, more subtle difference: it's primarily an environment for running apps, and only secondarily for editing them. Starting up the environment puts you in a running app by default. Creating an app from a clean slate is a low-priority use case, as is lots of specialized support for developing complex apps. The sweet spot for Teliva is simple apps that people will want to edit after using for a while.
It's reputedly the fastest interpreted language per line of implementation code.
Will it run any Lua program?
Not quite. My priority is providing a good experience for newcomers to comprehend and modify the programs they use. If it's not clear how to provide that experience for some kinds of Lua programs, I'd rather disable support for them in Teliva and let people use regular Lua (or other languages and environments!) for them.
This approach doesn't make sense for batch programs, I think.
I don't know how to obtain a simple, shallow graphics stack, so there's no support for graphics at the moment.
Teliva initializes the ncurses library by default, so apps should assume they have access to a text-mode window for printing text to, and a keyboard for reading unbuffered keystrokes from. Compare
hanoi.luato get a sense for what changes are needed.
I want to provide sandboxed access to system resources (file system, network, etc.) which will likely create incompatibilities with the standard library. I'm disinclined to try to ‘improve’ on Lua syntax, however. It's not my favorite, but it's good enough.
Teliva is not tested much at all yet. This is my first time programming either in Lua or within Lua. So bug reports are most appreciated if Lua programs behave unexpectedly under Teliva.
Will it run any ncurses program?
Hopefully. ncurses is extremely portable; I don't test on all the configurations ncurses supports. In particular, I assume terminals with colors and UTF-8 support.
Will it run any Lua lcurses program?
There will likely be some exceptions that I'll record here as I encounter them:
- lcurses has some strange “smarts” that result in
window:getch()not behaving like the global
curses.getch(). Teliva is consistent with the underlying ncurses.
What's with the name?
Teliva is the Tamil root for ‘clear’. Very much aspirational.