about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 1711 - start adding methods to editor-data objectsKartik K. Agaram2015-07-052-4/+10
| | | | The menu bar needs separate recipes to render and respond to events.
* 1710 - add notion of a menu barKartik K. Agaram2015-07-051-1/+36
| | | | | Of course, editors might begin below other editors; this is a stopgap solution. Yagni, yagni, yagni.
* 1709Kartik K. Agaram2015-07-041-2/+6
| | | | | More sketching out of a bare-bones scenario. What should happen when we press F9? Print a result somewhere?
* 1708Kartik K. Agaram2015-07-042-17/+22
| | | | | | Simpler gradient computation. But in the end it looks better when the gradient is so subtle as to be irrelevant. Might as well eliminate the gradient altogether.
* 1707 - experimenting with gradient backgroundKartik K. Agaram2015-07-041-1/+35
| | | | But integer division is a fail, as expected.
* 1706 - automatically recompile mu when necessaryKartik K. Agaram2015-07-042-9/+17
|
* 1705 - change background colorKartik K. Agaram2015-07-044-15/+39
|
* 1704 - update layout for a menu bar at the topKartik K. Agaram2015-07-041-9/+10
|
* 1703Kartik K. Agaram2015-07-041-6/+13
|
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-0437-312/+312
| | | | | | | It comes up pretty early in the codebase, but hopefully won't come up in the mu level until we get to higher-order recipes. Potentially intimidating name, but such prime real estate with no confusing overloadings in other projects!
* 1701Kartik K. Agaram2015-07-041-4/+4
|
* 1699 - first-class recipe typesKartik K. Agaram2015-07-035-51/+54
| | | | | It should now be easy to do dynamic dispatch, create higher-order functions, etc.
* 1698Kartik K. Agaram2015-07-035-0/+0
|
* 1697 - edit: starting to run codeKartik K. Agaram2015-07-032-1/+52
|
* 1696 - more cursor-wrap purgingKartik K. Agaram2015-07-021-31/+23
|
* 1695 - better way to handle wrapKartik K. Agaram2015-07-021-235/+29
| | | | | | | Key idea: wrap whenever you type at the right margin, don't wait for line to grow past it. That way you always leave room to acquire the end of the line, and you never have to worry about wrapping just the cursor but not the line. Simplifies a lot of logic.
* 1694Kartik K. Agaram2015-07-011-3/+160
| | | | | | | | | | | | | | | | | | I started fixing scenario editor-inserts-character-at-wrapped-cursor, but as I work further I notice there's an irreconcilable ambiguity in the approach of letting the cursor wrap in a non-wrapped line: if a cursor is at column 0 and the previous line occupies the entire width, should the next character you insert go before (assuming a wrapped cursor) or after the newline (assuming you're at the start of the next line)? No way to distinguish the two cases. One approach would be to delete the newline and have the cursor replace it with whatever you type. Then you have to hit a newline again to separate. But the simpler way is to simply wrap the moment the line grows to width-1, always leaving room for the cursor. Yeah, let's switch to that approach.
* 1693Kartik K. Agaram2015-07-011-3/+4
| | | | Move experimenting with wrapped lines to the right column.
* 1692 - stop mindlessly starting cursor at column 0Kartik K. Agaram2015-07-011-6/+71
|
* 1691 - planned layout for right columnKartik K. Agaram2015-07-011-5/+27
| | | | | | | | | | | We'll start out with just boxes on the right. Unlike the left with its dotted boundaries, the boundaries on the right will be solid lines, to indicate that they are isolated from each other even as they take from all the recipes on the left. As students grow more advanced we'll provide some way to 'pop up' the pre- and post-condition fields inside each sandbox. Those will also have dotted boundaries with the rest of their sandbox.
* 1690Kartik K. Agaram2015-07-0125-1038/+1613
|
* 1689Kartik K. Agaram2015-06-301-1/+21
|
* 1688 - up/down are easyKartik K. Agaram2015-06-301-2/+108
|
* 1687Kartik K. Agaram2015-06-301-3/+4
|
* 1686Kartik K. Agaram2015-06-301-3/+47
| | | | | | All these commented out prints are begging to turn into an app-level trace. But we need interpolation and static dispatch for that, so we can start printing any number of arbitrary types.
* 1685Kartik K. Agaram2015-06-301-0/+39
|
* 1684Kartik K. Agaram2015-06-301-5/+33
|
* 1683Kartik K. Agaram2015-06-301-4/+35
|
* 1682Kartik K. Agaram2015-06-301-19/+19
| | | | Clean up some variable names.
* 1681Kartik K. Agaram2015-06-291-3/+26
|
* 1680Kartik K. Agaram2015-06-291-0/+24
|
* 1679Kartik K. Agaram2015-06-291-10/+43
|
* 1678Kartik K. Agaram2015-06-291-4/+75
|
* 1677Kartik K. Agaram2015-06-291-1/+46
|
* 1676Kartik K. Agaram2015-06-281-1/+1
|
* 1675Kartik K. Agaram2015-06-281-8/+83
|
* 1674Kartik K. Agaram2015-06-281-6/+69
|
* 1673 - editors can now gain/lose 'focus'Kartik K. Agaram2015-06-281-105/+173
|
* 1672 - begin support for multiple editors at onceKartik K. Agaram2015-06-282-5/+44
|
* 1671 - better separate setup from code under testKartik K. Agaram2015-06-275-76/+105
| | | | | Requires better support for special variable names in scenarios like 'screen' and 'console'.
* 1670Kartik K. Agaram2015-06-272-8/+10
|
* 1669 - now it fails in the right placeKartik K. Agaram2015-06-272-2/+10
| | | | ..when building until layer 41
* 1668 - there's a bug in CHECK_TRACE_DOESNT_CONTAINKartik K. Agaram2015-06-273-1/+7
| | | | For starters start making the test fail when building until layer 41.
* 1667Kartik K. Agaram2015-06-261-0/+31
|
* 1666Kartik K. Agaram2015-06-261-23/+23
|
* 1665Kartik K. Agaram2015-06-261-0/+29
|
* 1664Kartik K. Agaram2015-06-251-1/+1
|
* 1663Kartik K. Agaram2015-06-251-1/+1
|
* 1662 - another boundary conditionKartik K. Agaram2015-06-251-16/+51
| | | | It was stale from before I added the § sentinel.
* 1661 - pointing and typing now seems to be workingKartik K. Agaram2015-06-251-6/+43
|