Electron packaging (start creating desktop app releases)

[1j01]

I want to start producing builds early. I can copy a lot of boilerplate/configuration from jspaint.

Electron and Electron Forge both pretend to be way simpler than they are in practice, but what are you gonna do?

[1j01]

• Fix the build Can't build electron app due to dependency on parent folder #53
• Fix icons in packaged app. I tried a symlink, but Electron Forge broke. I could make the images folder into an internal "resources" npm package, or I could just copy the needed icons into the app. I don't expect to change them frequently, and it would be nice to have a clean separation of what is required by the app, in order to limit the size of the app.
• Handle Squirrel events properly. Don't require serenade-driver or anything until after exit for installer, since if it errors, it's pretty ugly, and may even leave the installer process running. Exit properly. app.quit() doesn't exit immediately!
• Prevent click at startup — especially since the non-traditional Windows installer installs and runs the app in one click! —through some combination of:
  • Dwell clicking shouldn't start until head is detected #41
  • Toggle tracking and dwell clicking from within the UI #10
  • or a welcome screen
  • or SOMETHING
• Establish some sort of release process
• I should make sure the npm package has a README. I've moved it into a folder, so the README is no longer next to the package.json file. Maybe the API.md can become the readme of the library?