CUPS Dyesub Backends

  • Status Closed
  • Percent Complete
  • Task Type TODO
  • Category DNP/Citizen
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version 1.0
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: CUPS Dyesub Backends
Opened by Solomon Peachy - 2015-08-26
Last edited by Solomon Peachy - 2018-09-18

FS#539 - Consolidate CW-01 and DNP backends

There's a great deal of overlap; the main difference is the format of the print job. It may make sense to fold the CW-01 stuff into the DNP backend (including the spool format), but alternatively perhaps just a shared library?

Closed by  Solomon Peachy
2018-09-18 18:10
Reason for closing:  Implemented
Additional comments about closing:  All done. Should a tester ever surface.
Solomon Peachy commented on 2018-03-16 20:08

It's now possible to start combining them.   There's under 800 lines of code to port.  If we make a clean break and re-use the generic Citizen/DNP spool format, then it makes more sense to just add cw-01 support into the current dnp/citizen backend. 

This is risky enough that I don't care to undertake this effort without access to a printer.

Solomon Peachy commented on 2018-03-17 01:53

Progress continues; I've achieved a 59% reduction in unique cw-01 code; all that's left is the parser and main loop.

I need to write a converter from old spool format to the "native" format, then I can adapt the main loop.

Solomon Peachy commented on 2018-04-19 01:36

Code's done, and committed. Just needs testing. Once it's working, then Gutenprint can get "native" CW-01 generation path ala other Citizen models.

Solomon Peachy commented on 2018-06-18 17:07

Everything is done, just needs testing.


Available keyboard shortcuts


Task Details

Task Editing