Printing in the app right now (tip of v3), lacks all kinds of structure. It is default post rendering and simply starts buffering and emptying the buffer out to the serial port. This is great for exactly one use case: printing to a directly connected and initialized bot, but it leaves a lot to be desired when it comes to almost any other thing, not to mention the final render paths to movement is trashed immediately afterwards.
Alternative operation user stories
As a user I want to be able to render a project into a "print job" with given "settings" and save it to a queue.
As a user I want to be able to simply add a new piece of paper to the bot work surface, confirm a dialog, and print the next item in the queue.
As a user I want to be able to render a project with given settings into a portable "gcode" style file to move elsewhere.
Possible Print Job Settings
Project level defaults inherited from primary defaults
Colorset draw order validation (controlled in colorset, but whatever)
What is the current state?
Printing in the app right now (tip of v3), lacks all kinds of structure. It is default post rendering and simply starts buffering and emptying the buffer out to the serial port. This is great for exactly one use case: printing to a directly connected and initialized bot, but it leaves a lot to be desired when it comes to almost any other thing, not to mention the final render paths to movement is trashed immediately afterwards.
Alternative operation user stories
Possible Print Job Settings
Ideas/Notes: