about summary refs log tree commit diff stats
path: root/source.lua
Commit message (Collapse)AuthorAgeFilesLines
* Merge lines.loveKartik K. Agaram2024-01-151-2/+2
|\
| * use editor state font for width calculationsKartik K. Agaram2024-01-121-2/+2
| |
| * don't save settings on error in source editorKartik K. Agaram2024-01-121-1/+0
| |
| * fix still more issues with the previous scenarioKartik K. Agaram2024-01-121-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | - source editor always expects relative paths - refresh mocked data There's still one issue after this: the font size saved in the config file is the one we use in tests. More broadly, Editor_state is completely wrong. Ideally I'd just not save any settings for the source editor if the tests fail.
* | Merge lines.loveKartik K. Agaram2023-12-291-6/+4
|\|
| * moar bugfix X-(Kartik K. Agaram2023-12-291-1/+1
| |
| * bugfixKartik K. Agaram2023-12-291-2/+2
| | | | | | | | | | | | | | | | | | scenario: run without config file, quit, run again expected: font size remains the same on second run Before this commit it was increasing on each run. It turns out the font height that you pass into love.graphics.newFont() is not the result of font:getHeight().
| * pull font into editorKartik K. Agaram2023-12-291-6/+4
| | | | | | | | | | Now it adjusts the current font for itself. And it's up to the caller to adjust the current font after.
* | Merge lines.loveKartik K. Agaram2023-09-151-2/+2
|\|
| * source: show file being edited in window title barKartik K. Agaram2023-09-151-1/+1
| |
| * hide line numbers from log browserKartik K. Agaram2023-09-151-1/+1
| |
* | Merge lines.loveKartik K. Agaram2023-09-141-2/+3
|\|
| * always show line numbers in source editorKartik K. Agaram2023-09-141-2/+3
| | | | | | | | | | | | The drawing buttons are now absolutely positioned, which is a horrible hack. But for just the source editor it seems good enough. The alternative is to modify magic constants in all the tests :/
* | Merge lines.loveKartik K. Agaram2023-09-101-7/+0
|\|
| * Revert "deemphasize the source editor"Kartik K. Agaram2023-09-101-7/+0
| | | | | | | | | | | | | | Now that we have decent error handling, I think we can encourage people to press ctrl+e again. This reverts commit 4b43e9e85d985bcedd105fa9693ae751e5b6d0b6.
* | Merge lines.loveKartik K. Agaram2023-09-041-0/+7
|\|
| * show any error after switching to source editorKartik K. Agaram2023-09-041-0/+7
| | | | | | | | | | | | Error_message is a special global. It's set when the app (Current_app = 'run') encounters an error and switches to the source editor, and cleared when switching from source editor back to the app.
* | Merge lines.loveKartik K. Agaram2023-07-111-2/+2
|\|
| * drop an unused argKartik K. Agaram2023-07-111-2/+2
| |
* | Merge lines.loveKartik K. Agaram2023-07-101-57/+29
|\|
| * standardize between run and source some moreKartik K. Agaram2023-07-101-4/+2
| | | | | | | | | | We shouldn't be thinking about saving settings when we're initializing window geometry.
| * simplify saving settingsKartik K. Agaram2023-07-101-5/+1
| | | | | | | | We don't ever call one app's settings while Current_app is the other.
| * bugfix: Windows pushing title bar off screenKartik K. Agaram2023-07-101-43/+20
| | | | | | | | | | | | | | | | | | | | | | I'm learning the hard way that resizing the window is a big deal. Only do this when someone explicitly requests it, otherwise follow LÖVE's defaults. Therefore we're also going to stop trying to be smart when showing the log browser. Leave window resizing to manual operations. Now initialization looks a lot more similar for the run and source apps.
| * delete flags that have never been exercisedKartik K. Agaram2023-07-101-4/+0
| | | | | | | | Initialization is getting complex, and I'm finding bugs.
| * bugfix: preserve window positionKartik K. Agaram2023-07-101-2/+7
| |
* | Merge lines.loveKartik K. Agaram2023-06-041-0/+5
|\|
| * port inscript's bugfix to source editorKartik K. Agaram2023-06-041-0/+5
| |
* | Merge lines.loveKartik K. Agaram2023-05-141-1/+1
|\|
| * hide cursor in log browser windowKartik K. Agaram2023-05-141-1/+1
| |
* | Merge lines.loveKartik K. Agaram2023-04-091-0/+7
|\|
| * deemphasize the source editorKartik K. Agaram2023-04-091-0/+7
| | | | | | | | | | | | | | | | | | This repo does not support freewheeling modification. It's a primitive to enable freewheeling modification in downstream forks. The source editor is a convenience, but it's a sharp tool and can easily leave the app in a broken state that requires dropping down to external tools (editor, file manager) to fix.
* | Merge lines.loveKartik K. Agaram2023-04-031-3/+0
|\|
| * switch source side to new screen-line-based renderKartik K. Agaram2023-04-031-3/+0
| | | | | | | | Also copy over the implementation of links from pensieve.love.
* | Merge lines.loveKartik K. Agaram2023-04-021-11/+1
|\|
| * App.width can no longer take a TextKartik K. Agaram2023-04-011-3/+1
| | | | | | | | | | In the process I discovered the horrible fact that Text.x allocates a new Text. And it gets called (just once, thank goodness) on every single frame.
| * get rid of to_textKartik K. Agaram2023-04-011-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | I've been misunderstanding what Text objects are. They can render a lot of text with a given line height, word wrap, colors in various places. And I've been creating one for every word :facepalm: Unwinding this will take some time. This is just a first baby step for ad hoc text objects. Turns out I don't need to convert to Text to get something's rendered width, just the Font can do that. Thanks to the LÖVE Discord for educating me: https://discord.com/channels/329400828920070144/330089431379869708/1091535487333826580
* | Merge lines.loveKartik K. Agaram2023-03-251-0/+14
|\|
| * experiment at avoiding some merge conflictsKartik K. Agaram2023-03-251-0/+14
| | | | | | | | https://merveilles.town/@akkartik/110084833821965708
* | Merge lines.loveKartik K. Agaram2023-03-231-0/+9
|\|
| * mouse wheel supportKartik K. Agaram2023-03-231-0/+9
| |
* | Merge lines.loveKartik K. Agaram2023-03-181-12/+30
|\|
| * get typed in keystrokes to show on screen on iPadKartik K. Agaram2023-03-181-0/+14
| | | | | | | | Many thanks to Myte for helping test this!
| * extract a functionKartik K. Agaram2023-03-181-10/+14
| |
| * consistently use App names for methods everywhereKartik K. Agaram2023-03-181-2/+2
| |
* | Merge lines.loveKartik K. Agaram2023-03-171-13/+1
|\|
| * get rid of all bifold textKartik K. Agaram2023-03-171-13/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's just uneconomic to maintain given how little I've used it. I have a bug right now and no time to port the bugfix to all the complexities of the B side. I briefly considered tossing out the entire source editor. But I _have_ been using it to browse logs across sessions. The live editor doesn't quite cover all my use cases just yet. We now have duplication in the source editor only for: * syntax highlighting * hyperlinking [[WikiWords]] * ability to hide cursor (when showing file browser or Focus is in log browser)
* | Merge lines.loveKartik K. Agaram2023-03-171-0/+1
|\|
| * state validation in source editor as wellKartik K. Agaram2023-03-171-0/+1
| |
* | Merge lines.loveKartik K. Agaram2023-01-301-1/+0
|\|
| * create a place for graphical log handlersKartik K. Agaram2023-01-301-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | Currently only used in pong.love, but let's keep the bad merge that had it broken since September from occurring again. To do that we'll be consistent across forks on where globals are initialized. I haven't appreciated the implications of main.lua for load order. log.lua comes first just because it's shared by both the main app and its 'source' editing environment. And it just so happens that source.lua was loading after log.lua resulting in the pong.love breakage. Now let's lean into that and enshrine that one should initialize log_render in log.lua.