CUPS Dyesub Backends

  • Status Closed
  • Percent Complete
    100%
  • Task Type Feature Request
  • 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: CUPS Dyesub Backends
Opened by Solomon Peachy - 2018-04-27
Last edited by Solomon Peachy - 2018-04-28

FS#600 - Add support for CUPS Command files

CUPS defines a "command filter" that gives the ability to perform some actions and queries.

  • ReportLevels -- marker-levels and whatnot.  Highly useful.
  • ReportStatus -- Once we get unified reporting in place, will be handy.
  • AutoConfigure -- Allows the PPD defaults to be updated based on printer configuration.  (!!)
  • PrintSelfTestPage -- For printers that support it
  • [and others that don't matter]

There appears to be no way to distinguish betwen a command filter vs print filter via the cmdline or environment.  traditionally these are seperate executables that expect different input data.  I'd like to figure out a way to make the backends detect the command stream vs the normal backend data, and do it all in one executable.

Closed by  Solomon Peachy
2018-04-28 21:53
Reason for closing:  Implemented
Additional comments about closing:  Fully implemented in backend. Still need to do the frontend work in Gutenprint (ie PPD generation)
Admin
Solomon Peachy commented on 2018-04-27 15:55

For commands, FINAL_CONTENT_TYPE shall be application/vnd.cups-command -- w00t!

 

Admin
Solomon Peachy commented on 2018-04-28 12:54
'ReportLevels' is now fully implemented. As of this writing there are four backends left to migrate to the new paradigm.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing