RoboPaint NG Release feature implementation checklist

[techninja]

Since the creation of the PaperJS branch, I've pushed over 170 commits to basically do a heavy refactor of the entire RP system to fit better with the way that Paper.JS and Electron play together. I'm creating this issue to whittle down and make it clear what's left before this can be fully released. These are mostly in order of priority or how I intend to write them, top to bottom.

Drawing

• Implement Paper NG stroke & fill in working modes with new settings (Next Generation (NG) Fill/Stroke Options/settings #226)
• Implement Paper NG stroke & fill settings pages with preview (Next Generation (NG) Fill/Stroke Options/settings #226)
• Implement some kind of basic media creation utility for custom colors and pen color groups (with defaults). [Putting this off till more discussion around NG Media and Implements  #234]
• Make multicolor pen (wait/resume) tool changes for color work (with calibration), likely requires unified messaging below...
• Calibration, buffer pause/resume available globally via new pop-out status helper (Add unified calibration wizard overlay #213). The more I use the other modes, the more clear it is that future modes shouldn't have to attempt to duplicate the work for it. Less required boilerplate the better, and more standard user facing UI.

Mode Support/Mode API

• Unified cancel, form settings management, and cncserver control
• Clean, nice looking unified modal messaging. Electron's MessageBox Is native and very good with custom boxes, summary, detail and more!
• Support for mode color SVG/png icons, & "teaser" image
• Persistent API extensions via package.json (for Recreate Remote Paint as an actual mode #227, etc)
• Convert Print & Edit mode for NG
• Convert Example mode for NG
• Convert Remote Print for NG Mode

Dropping:

• Convert Manual mode for NG
  • Manual mode has been a dumping ground/testing area for a long time, and really without a better definition of what it's for/what it actually does, I don't see a good reason to spend time on it. At minimum it will ship and have support for painting selected shapes with a fill/stroke, but anything beyond that does not help the final product.
• Semi-automatic qTip for unified hover titles (support base modes at least)
  • The reasoning behind doing this originally was because the hover text was being cut off, but apparently now that's fixed in the latest 0.34.0 Electron
  • The logistics of moving out qTip initialization from RP proper into modes before it's actually where we want it in the base app, is not sound. Modes can use qTip right now, but they have to manage their own styles & translation swap, so I can't really recommend it.

"Beyond" features: These have been on the agenda for years, but have never become anything too real. I feel as if the time is about right, but it will take more time, and it does mean less effort given to ensuring basic features are as absolutely polished as they can be, so I'm not saying they'll be done before the next release.

• Merge in basic multi-bot support. This has stagnated in a branch confused by design, and maybe it just needs a kick in the pants and some time to play around with the implementation a bit.

[forresto]

Excited for multicolor pen (wait/resume) tool changes. One suggestion related to my not seeing the overshoot option (#229): switching to pen mode could also turn overshoot off.

Edit: just read the comment; that's in the works 👍 .

[techninja]

Bleh. "example"/Text mode is feature complete now, and really quite useful and fun, though the UI design kinda sucks, but it's not like that's any kind of surprise. How the heck do you fit in that many sliders into one place? Sheesh.

Questions/comments/PRs for this mode should go here: https://github.com/techninja/robopaint-mode-example