teliva - Fork of Lua 5.1 to encourage end-user programming

	Commit message (Collapse)	Author	Age	Files	Lines
*	clean up first paint of editor	Kartik K. Agaram	2021-11-05	1	-0/+1
\|
*	utterly ghastly way to rerun script after edit	Kartik K. Agaram	2021-11-05	1	-2/+8
\|
*	stitch editor in	Kartik K. Agaram	2021-11-05	1	-1/+4
\|
*	menu entry: cleanly exit	Kartik K. Agaram	2021-11-05	1	-3/+21
\|
*	colors: init_pair/color_pair	Kartik K. Agaram	2021-11-05	1	-0/+26
\|
*	.	Kartik K. Agaram	2021-11-05	1	-17/+17
\|
*	make some space for the global menu	Kartik K. Agaram	2021-11-05	1	-0/+15
\| \| \| \|	We'll eventually need some interface to add entries to it.
*	move getch out of window scope	Kartik K. Agaram	2021-11-05	1	-13/+10
\| \| \| \|	The window only matters for output, which seems like a stupid interface.
*	resist the temptation to add to the Lua API	Kartik K. Agaram	2021-11-05	1	-20/+0
\| \| \| \| \|	Instead we'll include code in the Lua app itself, to minimize the differences between what runs on regular Lua and what runs on Teliva.
*	hanoi.lua _almost_ working	Kartik K. Agaram	2021-11-05	1	-6/+26
\|
*	window:getch()	Kartik K. Agaram	2021-11-05	1	-0/+13
\| \| \| \| \|	But how do we get curses.getch() to work? I don't see it implemented in lcurses.
*	curses print constants	Kartik K. Agaram	2021-11-05	1	-0/+72
\| \| \| \| \| \| \|	Very satisfying to debug the difference between lcurses putting the module table in an upvalue. Since I implicitly call initstr() rather than define it as a primitive, I don't need to bother with that. I am awesome. Lua is awesome for giving me that sense.
*	grouping	Kartik K. Agaram	2021-11-05	1	-0/+4
\|
*	mvaddch/mvaddstr	Kartik K. Agaram	2021-11-05	1	-0/+33
\| \| \| \| \|	I think we now have all the output functions/methods we need. Just some constants remaining.
*	attron/attroff	Kartik K. Agaram	2021-11-05	1	-0/+18
\|
*	window:getmaxyx()	Kartik K. Agaram	2021-11-05	1	-0/+22
\|
*	.	Kartik K. Agaram	2021-11-05	1	-0/+1
\|
*	window:clear()	Kartik K. Agaram	2021-11-05	1	-0/+7
\|
*	reindent	Kartik K. Agaram	2021-11-05	1	-7/+7
\| \| \| \| \|	I'm trying to follow the style of lua sources even when they're not my preference. lcurses code is a bit different.
*	ohh, that word 'index' was key	Kartik K. Agaram	2021-11-05	1	-0/+4
\|
*	oh, that's just a cosmetic thing	Kartik K. Agaram	2021-11-05	1	-0/+13
\| \| \| \| \| \| \| \|	So why isn't this working? a = curses:stdscr() a:addstr(abc) The error is "attempt to index global 'a' (a userdata value)"
*	copy metatable name from lcurses	Kartik K. Agaram	2021-11-05	1	-3/+3
\| \| \| \| \|	Makes no difference to the results of: print(curses:stdscr())
*	snapshot	Kartik K. Agaram	2021-11-05	1	-2/+61
\| \| \| \| \| \| \| \| \|	Not quite working. curses.stdscr() is returning userdata, not a window. This is true even of the raw array example from the book. So we need to learn something new here. How does lcurses's Pinitscr return a special window object? From what I can tell it's just putting the results of lc_newwin() on the stack. Which is the same as my curses_newwin() here.
*	stdscr binding	Kartik K. Agaram	2021-11-05	1	-0/+12
\| \| \| \| \|	print(curses.stdscr()) print(curses:stdscr())
*	starting on curses library	Kartik K. Agaram	2021-11-05	1	-0/+40
	First piece of working new vocabulary: print(curses:cols()) Just pulling in code from lcurses for the most part. But I'm trying to understand its internals as I gradually add them in, after my more blunt first approach of packaging up lcurses/ext failed. Overall plan for Teliva's API: - start out with a 'curses' library that does what people who are used to ncurses/lcurses expect. - over time create a more opinionated library called 'screen' or 'window' or something.