about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 1629 - new helper for constructing containersKartik K. Agaram2015-06-232-0/+44
|
* 1628Kartik K. Agaram2015-06-231-37/+37
|
* 1627 - new plan for backspaceKartik K. Agaram2015-06-231-3/+2
| | | | | | First, undo our existing hacky pseudo-support. Some repl tests currently breaking.
* 1626 - made my peace with read-keyKartik K. Agaram2015-06-231-0/+3
| | | | But we certainly can't use it in the editor.
* 1625Kartik K. Agaram2015-06-233-9/+9
|
* 1624Kartik K. Agaram2015-06-232-55/+55
| | | | | | I still want to bring back replace-in-keyboard. No, not exactly that. But saying press 8, press 8, press 8, over and over again, that's a pain.
* 1623Kartik K. Agaram2015-06-221-2/+3
|
* 1622 - done migrating to console interfaceKartik K. Agaram2015-06-221-14/+14
| | | | | | | But still feels rough: Variable names are still funky: 'k' and 'm'. Field names still not copacetic: single-touch-event. Foolish consistencies..
* 1621Kartik K. Agaram2015-06-223-121/+166
| | | | | | | | repl.mu now passing again. But still I have concerns: a) Doubling backslashes in tests. Hard to tell how many levels to add. b) I think the read-key interface needs to go. But then how do we handle send-keys-to-channel and other flows like that in the chessboard app?
* 1620Kartik K. Agaram2015-06-224-11/+28
| | | | | | | | chessboard finally passing all its tests. What made this hard was that for some reason one of the background routines in the main chessboard test wasn't terminating like it used to. And so it was polluting *later* tests. Just clean up that source of contamination for now. Later we'll think about routine termination.
* 1619Kartik K. Agaram2015-06-221-1/+1
|
* 1618Kartik K. Agaram2015-06-218-25/+26
|
* 1617Kartik K. Agaram2015-06-217-43/+40
|
* 1616 - merging keyboard and events into 'console'Kartik K. Agaram2015-06-2110-346/+222
| | | | | Only core layers currently passing. Console apps are probably still broken.
* 1615Kartik K. Agaram2015-06-211-1/+1
|
* 1614Kartik K. Agaram2015-06-214-11/+3
|
* 1613 - edit: first event in event loopKartik K. Agaram2015-06-212-4/+63
| | | | No way to quit yet, though.
* 1612Kartik K. Agaram2015-06-201-0/+7
|
* 1611 - switch to keyboard+mouse eventsKartik K. Agaram2015-06-205-10/+42
|
* 1610Kartik K. Agaram2015-06-201-29/+82
| | | | Reorg.
* 1609Kartik K. Agaram2015-06-201-0/+2
|
* 1608Kartik K. Agaram2015-06-201-5/+0
|
* 1607Kartik K. Agaram2015-06-201-2/+2
|
* 1606Kartik K. Agaram2015-06-201-32/+43
| | | | Rip out keyboard for now, add notion of cursor.
* 1605Kartik K. Agaram2015-06-201-23/+43
| | | | | | | | | | | | | More editor experiments. a) I'm starting out with just a doubly linked list of characters as the editor data structure. Haven't actually started using it yet. b) Rather than provide a top-left-bottom-right bounding box up front, I think I want to allow the bounding box to flow indefinitely down given top, left and right. The old approach mimics traditional windowing systems, while the new one mimics html flowing; I want a single scrollbar for all my rendered elements within a single column.
* 1604Kartik K. Agaram2015-06-201-1/+2
|
* 1603Kartik K. Agaram2015-06-191-6/+15
|
* 1602Kartik K. Agaram2015-06-191-21/+31
| | | | | I forgot to check for nulls before writing prev pointers in doubly linked lists. Tests were accidentally passing.
* 1601Kartik K. Agaram2015-06-192-2/+25
|
* 1600Kartik K. Agaram2015-06-193-0/+7
|
* 1599Kartik K. Agaram2015-06-1912-63/+62
|
* 1598Kartik K. Agaram2015-06-193-5/+27
| | | | | Some tests weren't actually running for the past 5 days. Performed 5 why's.
* 1597 - port more helpers from arc versionKartik K. Agaram2015-06-194-1/+615
|
* 1595Kartik K. Agaram2015-06-181-1/+1
|
* 1594 - removing from start/end of duplex listKartik K. Agaram2015-06-181-4/+67
| | | | | | | | | | This uncovers an issue with this interface to duplex lists: the caller needs to check the result and invalidate any other pointers if it's null (i.e. the list is now empty) We *could* try to encapsulate the list in a header to help the caller manage header pointers. But heck, let's see if writing tests helps call-sites stay on the straight and narrow.
* 1593Kartik K. Agaram2015-06-182-1/+77
|
* 1592Kartik K. Agaram2015-06-181-0/+36
|
* 1591Kartik K. Agaram2015-06-182-3/+60
|
* 1590 - inserting into doubly linked listKartik K. Agaram2015-06-181-0/+62
|
* 1589 - doubly linked listKartik K. Agaram2015-06-181-0/+74
|
* 1588 - undo 1587Kartik K. Agaram2015-06-171-22/+1
|
* 1587 - experimental rendering of recipe namesKartik K. Agaram2015-06-171-1/+22
| | | | | But this is getting too complex too fast. Let's get a simple editor working first without color.
* 1586Kartik K. Agaram2015-06-172-2/+2
|
* 1585Kartik K. Agaram2015-06-1714-29/+29
|
* 1584Kartik K. Agaram2015-06-171-1/+1
|
* 1582Kartik K. Agaram2015-06-172-0/+46
|
* 1581Kartik K. Agaram2015-06-171-1/+1
|
* 1580Kartik K. Agaram2015-06-162-9/+12
|
* 1579Kartik K. Agaram2015-06-161-0/+11
|
* 1578 - editor inside 2-column layoutKartik K. Agaram2015-06-161-17/+67
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-03 21:40:33 +0000