Claudio Prezzi

If it's complicated to interface with a slicer from the frontend, we could use lw.comm-server (or a separate slicing server) as a bridge. Beside of Marlin, we should consider of...

If we add support for more firmwares, I do probably need to modularize lw.comm-server, otherwise maintenace will be the horror.

An own slicing/rendering/gcode generation server could probably solve some memory and performance limitations of the browser.

That could also open the door to cloud processing.

@arthurwolf Nice info, thank you!

I'm always a bit concerned about performance and memory issues in the browser, so I do prefer to outsource those tasks to a nodejs server.

I love all the cool features we have, but it should not scare beginners away. Unfortunately I am not a big frontend guy, but could we implement some operation mode...

I agree, but I don't have time to implement something like that. Unfortunately it's low on the priority list.

There is a big difference between `G10 L2` and `G92` (and not every firmware handles it the same way): - `G10 L2 P1` is setting **the offsets** only for G54...

@jorgerobles How about a button "find mark" on the jog tab, that searches for the mark, moves to the calculated zero position and sends setZero to the backend?