resolve conflicts

akkartik

Sep 5, 2024, 9:00 PM

KLY5ZP3NCLTXI5OPVHXI7HVYEU6TDC6W22PKYVRBZXX7MLAKIF5AC

Dependencies

[2] 2534RME6 standardize some copy between forks
[3] GWY3MDWP clarify that PRs and patches are both welcome
[4] PK25ETNW resolve conflicts
[5] FSQ7OI4M new fork: a template for carousel-based apps
[6] ZTMRQZSW Readme
[7] MD3W5IRA new fork: rip out drawing support
[8] HUDGLWXF include instructions to install LÖVE
[9] D4FEFHQC flesh out Readme
[10] 4VUVVW6J update Readme and settle on a project name
[11] WKJYU3EP document gotchas on mobile
[12] UOGZZY3L link to reference from Readme
[13] KSL52BPS link to Freewheeling Apps page
[14] AMYOQ4QW fine, I'll add a badge
[15] FS2ITYYH record a known issue
[16] ZT6T2H7N update known issues
[17] 2DVVKKVA flesh out Readme
[18] BPYWIU62 new fork: template for live programming with editor widgets
[19] DFXPZNH6 Merge lines.love
[20] Q4WRCUWD screenshot
[21] 3WSB7ZTV resolve conflicts
[22] GO566FZS pijul bug
[23] QKFHDM6J resolve conflicts

Change contents

resurrect zombie in README.md at line 2

[5.37]→[4.25:119](∅→∅),[5.37]→[4.25:119](∅→∅)

[![0 dependencies!](https://0dependencies.dev/0dependencies.svg)](https://0dependencies.dev)
resolve order conflict in README.md at line 2

[5.917]

[4.25]
resurrect zombie in README.md at line 7

[5.11635]→[5.918:1218](∅→∅),[5.11635]→[5.918:1218](∅→∅),[5.1218]→[2.32:100](∅→∅),[5.1218]→[2.32:100](∅→∅),[2.100]→[5.1287:1630](∅→∅),[5.1287]→[5.1287:1630](∅→∅),[5.1287]→[5.1287:1630](∅→∅),[5.1630]→[5.32:33](∅→∅),[5.1630]→[5.32:33](∅→∅),[5.33]→[2.101:609](∅→∅),[5.33]→[2.101:609](∅→∅)

Copy this repo to get a leg up creating tiny, low-maintenance, cross-platform
apps that you can make changes to right on a phone or tablet.

It comes bundled with a few optional goodies:
* Support for tap-to-pan and pinch-to-zoom gestures over an infinite 2D
surface for arbitrary graphics and UI.
* A tiny widget library for quickly creating arbitrary UI elements.
[Here's an example of the kinds of things you can add to the global variable `widgets`.](https://akkartik.itch.io/carousel/devlog/665231/a-sprite-editor-in-100-lines-of-code)
* A typographic scale for scaling the font size of text in visually pleasing
increments.

Tap the 'edit' button and then poke around the 'load' menu to learn more.

This repo is an example of a [Freewheeling App](http://akkartik.name/freewheeling),
designed above all to be easy to run, easy to modify and easy to share.

## Getting started

Install [LÖVE](https://love2d.org). It's just a 5MB download, open-source and
extremely well-behaved.

[Run the app using LÖVE.](https://love2d.org/wiki/Getting_Started#Running_Games)

## Hacking

You can edit the app and UI right on your device. However, there are some
gotchas to be aware of when editing such apps on a phone:
resurrect zombie in README.md at line 34

[5.19]→[5.107:926](∅→∅),[5.19]→[5.107:926](∅→∅)

* If you upgrade LÖVE you lose all your local apps and their saved settings.
This includes code changes. It's hard to get code changes out due to mobile
restrictions. I can't come up with an alternative to copy-paste. This
imposes a strict limit on the number of changes I'm willing to make to a
large app on my phone.

* If you upgrade such apps after making local changes to them, you might see
strange errors. Local changes are written to an overlay directory, whereas
upgrades modify the app in place. The two locations create lots of
opportunity for conflicts to arise.

To mitigate this issue, such apps by default list local changes in the
output editor every time they run. That will hopefully act as a reminder.
There's also some helpers for deleting local changes in the 'scratch' page.
edit in README.md at line 34

[2.609]

[5.107]
edit in README.md at line 112

[5.117]→[5.36:37](∅→∅),[5.132]→[5.36:37](∅→∅),[5.38]→[5.36:37](∅→∅),[5.19]→[5.19:175](∅→∅),[5.19]→[5.19:175](∅→∅),[5.926]→[5.19:175](∅→∅),[5.19]→[5.19:175](∅→∅)

This repo is an example of a [Freewheeling App](http://akkartik.name/freewheeling),
designed above all to be easy to run, easy to modify and easy to share.
resolve order conflict in README.md at line 112

[3.132]