about summary refs log tree commit diff stats
path: root/edit.mu
Commit message (Collapse)AuthorAgeFilesLines
* 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..
* 1618Kartik K. Agaram2015-06-211-2/+2
|
* 1615Kartik K. Agaram2015-06-211-1/+1
|
* 1613 - edit: first event in event loopKartik K. Agaram2015-06-211-1/+60
| | | | No way to quit yet, though.
* 1611 - switch to keyboard+mouse eventsKartik K. Agaram2015-06-201-2/+18
|
* 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.
* 1601Kartik K. Agaram2015-06-191-0/+19
|
* 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.
* 1580Kartik K. Agaram2015-06-161-7/+9
|
* 1579Kartik K. Agaram2015-06-161-0/+11
|
* 1578 - editor inside 2-column layoutKartik K. Agaram2015-06-161-17/+67
|
* 1577 - vocabulary for drawing bordersKartik K. Agaram2015-06-161-24/+65
|
* 1576Kartik K. Agaram2015-06-161-0/+50
|
* 1575Kartik K. Agaram2015-06-161-0/+8
|
* 1573Kartik K. Agaram2015-06-161-1/+40
|
* 1572Kartik K. Agaram2015-06-161-2/+45
|
* 1570Kartik K. Agaram2015-06-161-1/+31
|
* 1568 - starting on editor widget in ernestKartik K. Agaram2015-06-161-123/+15
|
* 1551 - initial sketch of layoutKartik K. Agaram2015-06-111-1/+53
| | | | | | | | | | | | | | | Two columns: edit code on left and run code on right. In both columns, the action is at the top of the screen, and stuff gradually flows downward unless pulled back up. Stuff you run on the right side will eventually become reproducible test cases that runs constantly on every change. We also have a tentative signature for the 'edit' routine: it'll take an input string and return an output string when it finishes. More columns expand to the right. Number of columns shown will remain fixed at any time depending on screen width. But for now we support exactly two columns.
* 1547Kartik K. Agaram2015-06-091-0/+1
|
* 1545 - sketching out a simple editor widgetKartik K. Agaram2015-06-081-0/+81
|
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-18/+0
| | | | I've tried to update the Readme, but there are at least a couple of issues.
* 497 - strengthen the concept of 'space'Kartik K. Agaram2015-01-021-1/+1
| | | | | | | | | | | | | | | | | | | | 'default-scope' is now 'default-space' 'closure-generator' is now 'next-space-generator' The connection to high-level syntax for closures is now tenuous, so we'll call the 'outer scope' the 'next space'. So, let's try to create a few sentences with all these related ideas: Names map to addresses offset from a default-space when it's provided. Spaces can be strung together. The zeroth variable points to the next space, the one that is accessed when a variable has /space:1. To map a name to an address in the next space, you need to know what function generated that space. A corollary is that the space passed in to a function should always be generated by a single function. Spaces can be used to construct lexical scopes and objects.
* 428 - cleanup odds and endsKartik K. Agaram2014-12-141-12/+12
|
* 403 - 'function' is more clear than 'def'Kartik K. Agaram2014-12-121-1/+1
|
* 401 - stop abbreviating opsKartik K. Agaram2014-12-121-3/+3
| | | | | We expect users to come across mu from arbitrary bits of code, so try to make each line as self-contained as possible.
* 341 - standardize traces againKartik K. Agaram2014-11-271-1/+1
|
* 314 - better syntax for functionsKartik K. Agaram2014-11-241-2/+2
|
* 202 - variable names for edit.muKartik K. Agaram2014-11-011-11/+12
|
* 181 - fix inconsistent metadataKartik K. Agaram2014-10-301-2/+2
| | | | | We have cases where 'type' is stored in memory, so it can't be a literal type like 'offset'.
* 175 - have 'new' write array size automaticallyKartik K. Agaram2014-10-291-2/+0
|
* 160 - fix stale editor testKartik K. Agaram2014-10-281-13/+13
|
* 145 - delete random programsKartik K. Agaram2014-10-141-17/+0
| | | | | | | | | They need a type table to work, but I'm keeping type tables next to the tests. Everything needs to be a test from now on. (But first some fixes to the terminal primitives.)
* 121 - finally I can alloc a 2D arrayKartik K. Agaram2014-10-071-9/+11
|
* 113 - slight progress working with screen 2D arrayKartik K. Agaram2014-10-061-0/+18
| | | | | Why did it take forever to realize nobody will set the array length, that I have to do it for myself?
* 100Kartik K. Agaram2014-10-051-1/+1
|
* 99 - edit.mu looks much cleaner nowKartik K. Agaram2014-10-051-17/+8
|
* 95Kartik K. Agaram2014-10-041-0/+25