Gutenprint / CUPS Dye-sublimation drivers

  • Status Closed
  • Percent Complete
  • Task Type TODO
  • Category Common Code
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Medium
  • Reported Version 1.0
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Gutenprint / CUPS Dye-sublimation drivers
Opened by Solomon Peachy - 2017-11-24
Last edited by Solomon Peachy - 2019-12-13

FS#586 - Add JSON output

This might not be feasible in a general sense due to the need to interact with CUPS.  But it's worth investigating.

Closed by  Solomon Peachy
2019-12-13 20:36
Reason for closing:  Implemented
Additional comments about closing:  Implemented in global code. dnp and hiti stubs added. Rest of models will follow as testing ability permits.
Solomon Peachy commented on 2019-12-10 17:03
There's a desire for a more uniform status/etc reporting structure in an easily machine-readable format. A common denominator might be: * Timestamp (%F %H:%M:%S) * Printer Info * Manufacturer * Model * Serial Number * FW Version * Media * Human readable type (eg "5x7 HQ") * Capacity * Remaining prints * Counters * Lifetime * ??? (anything else make sense?) * Status (eg printing, idle, error XXX) So: 1) Define data structure to hold all of this, and define function signature to query it 2) Update backends to add method to query this info 3) Add function to emit this info as JSON and human readable text? 4) ???
Solomon Peachy commented on 2019-12-12 14:34
I have an early version of this implemented, with two backends (dnp, hiti). No JSON yet, but that's next. WIP!
Solomon Peachy commented on 2019-12-13 14:41
JSON output implemented. Once I figure out how to integrate it cleanly I'll commit and push.


Available keyboard shortcuts


Task Details

Task Editing