Flyspray:: Flyspray::CUPS Dyesub Backends: Recently closed tasks http://bugs.shaftnet.org/ 2018-09-18T18:10:15Z FS#539: Consolidate CW-01 and DNP backends 2018-09-18T18:10:15Z 2015-08-26T04:12:50Z

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?

Solomon Peachy http://bugs.shaftnet.org/:539
FS#550: Verify support for D707 2018-09-18T18:09:48Z 2016-10-07T02:03:18Z

Code's complete, but needs to be verified.

 

Solomon Peachy http://bugs.shaftnet.org/:550
FS#604: Use a simpler URI scheme 2018-09-18T18:08:41Z 2018-08-14T20:25:58Z

Currently the URI scheme is a little convoluted:

     prefix://iManufacturer/iModel?backend=XXX&serial=YYYY

I'd like to move to something much simpler:

     prefix://backend/serial

Now that the core code returns a unique, per-model string that can be used to look up the backend, this is a far simpler approach to take.  We'll have to support the old scheme indefinitely though.

Solomon Peachy http://bugs.shaftnet.org/:604
FS#541: Validate Mitsubishi CP-D90 support 2018-05-20T02:11:13Z 2016-04-28T22:41:05Z

It looks like it's an evolution of the D70 family, with one critical exception -- it appears as if the color/thermal compensation is performed in the printer instead of the driver!

Solomon Peachy http://bugs.shaftnet.org/:541
FS#601: Figure out a way to add a generic test harness for file parsing 2018-05-13T13:09:37Z 2018-05-10T02:14:19Z

Right now there's no way to parse the input files without the printer being attached first.

Would require shimming libusb...

Solomon Peachy http://bugs.shaftnet.org/:601
FS#600: Add support for CUPS Command files 2018-04-28T21:53:04Z 2018-04-27T15:48:17Z

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.

Solomon Peachy http://bugs.shaftnet.org/:600
FS#596: Figure out if Citizen CW-02/OP900II are closer to CX or CY series 2018-03-27T00:04:19Z 2018-02-22T19:35:06Z

...or if they need their own designation in Gutenprint and selphy_print.

It looks like they don't map entirely cleanly to either for avialable print options, but the real question is the firmware version tests for features.

Solomon Peachy http://bugs.shaftnet.org/:596
FS#599: Enhance Magicard driver to allow for different options on the duplex side. 2018-03-18T18:45:05Z 2018-03-10T21:54:23Z

At minimum, the overcoat hole is different on front vs back (eg smartcard vs magstripe).

Magstripe probably only belongs on the back, smartcard on the front.

Holokote and holopatch likely need to be different too.

Solomon Peachy http://bugs.shaftnet.org/:599
FS#597: Allow for aliases in backend names? 2018-03-16T19:38:04Z 2018-02-22T19:40:13Z

That would allow us to present a 'modern' name for the backend but still provide backwards compatibility.

eg: dnpds40 -> dnp_citizen or mitsu9550 -> mitsu9xxx or mitsup95d->mitsu_p9x

Another approach would be to make things more fine-grained.

 

Solomon Peachy http://bugs.shaftnet.org/:597
FS#532: Verify support for S1245 2018-01-27T01:29:07Z 2015-07-23T17:59:08Z

Code complete, but needs testing.

Solomon Peachy http://bugs.shaftnet.org/:532