The program can connect to the daemon and talk to it. (For nodejs, not to imply js is the best choice, just for testing-time, better C/C++) (also know mpd does it)
It being a daemon might make it easier to script with generally, easier to plot/log anything you can query, slicers, viewers, manual control, or the same thing via (something like) Octoprint. It makes things more flexible in terms of how you choose to do things.
Note that you dont have to take this seriously or as neccesarilly your job or anything like that, its like one of those suggestions you let woosh by. I am being a spoiled little brat :p, been using pronterface so far, but now i feel like i should try this one...
Anyway since this is in C++ program, i thought it was a good idea to put the note here. To be specific anyway:
- A subset of the code here would be the reprap-connection library.
- A daemon would use it, and add the inter-process communication bit, and stuff the slicers/viewers can talk to.
- Libraries that are client to the daemon.(C and Python, probably) Program for the commandline.
- Another subset of the code here might be viewing/controlling the printer. (Oeh a slicer too?)
The program can connect to the daemon and talk to it. (For nodejs, not to imply js is the best choice, just for testing-time, better C/C++) (also know mpd does it)
It being a daemon might make it easier to script with generally, easier to plot/log anything you can query, slicers, viewers, manual control, or the same thing via (something like) Octoprint. It makes things more flexible in terms of how you choose to do things.
Note that you dont have to take this seriously or as neccesarilly your job or anything like that, its like one of those suggestions you let woosh by. I am being a spoiled little brat :p, been using pronterface so far, but now i feel like i should try this one...
Anyway since this is in C++ program, i thought it was a good idea to put the note here. To be specific anyway: