G-code Analysis Caching for "Restart" Function#468

1. G-code Analysis Caching for “Restart” Function

Implement a G-code analysis caching mechanism. When a user initiates a “Restart” on a print job that originated from a file previously uploaded to and analyzed by Simply Print, the system should re-use the existing G-code analysis data instead of performing a new analysis, or showing as “no GCODE analysis found”

1. Live G-code Analysis for non-analyzed Files

Allow for an optional, live G-code analysis to be performed on files that are already on the printer and being printed, but have not been pre-analyzed by Simply Print.

Implementation: When a user starts a print from a non-analyzed G-code file (e.g., a file uploaded via an external slicer or USB drive), the Simply Print client could start to pull the G-code file from the printer's host (e.g., OctoPrint, Klipper) for a full, local analysis while the print is in progress. This would provide the user with the expected print time, filament usage, and other metadata, allowing more accurate filament usage via Simplyprint

1. Quick Recall of Historical Print Jobs via UUID

Implement a system where historical print jobs, once analyzed and printed, are saved with a unique identifier (UUID) that allows for instant analysis on future prints.

Implementation: When a user uploads a G-code file via the Simply Print slicer, it could be saved to the printer's file system with a UUID appended to the filename (e.g., my_dnd_model_c7b9a5c8...gcode). If the user later prints a file with that same UUID in its name, the system would recognize it and instantly pull up the historical analysis data from its cache, bypassing any need for re-slicing or analysis.