|
|
|
|
|
|
by decktech
3977 days ago
|
|
|
Maybe someone can explain how this works to me: In the white paper (http://ftp.pwg.org/pub/pwg/BOFs/3d-printing/wd-apple-ipp3d-2...) section 5, it lists a bunch of attributes ("material-type", "filament-retraction-speed", etc.) These are all attributes that would be inputs to a slicer. Furthermore, there are a million such parameters (CUPS will never cover them all), are different between different slicers, are ever-changing, and sometimes undocumented. Why would cups concern itself with these parameters, versus, for example, just acting as a transport for the actual print file (gcode, x3g, etc.)? I feel like this is akin to having CUPS assemble a PDF, versus just acting as a transport for postscript file that gets printed. |
|
|