TODO list
---------

Combine percentblack and friends into a single "coverage" binary which takes
a --colourspace option (after all, much of the code is common to both).

Develop a printbill.cups filter (= printbill.lprng)

Hack up some magicfilter-based filters for providing various
functionality...

Add support for pqm --set in web interface

See how hard it is to integrate with lj2ps, for people who absolutely insist
upon having PCL drivers.

I have discovered CUPS, and I am most impressed. Reading the excellent
documentation I get the impression that it should be possible to write a
printbill interface compatible with CUPS. My expectation is that it will not
be a straightforward port but I think that is that this is the future of
Unix printing. Hopefully this should also allow us to properly bill duplex
jobs...

Add support for billing fancy 7-colour printers.

Proper abstraction of Printbill::PTDB_File such that it can use a variety
of back-ends - e.g. SQL, LDAP etc. later... is this really useful? Why the
hell does everyone love SQL so much?? :-P

Try and detect request for duplex printing embedded in PS code? No idea if
this can work... but it would be really nice.

Use real cookies instead of dodgy server-side `cookies'? CGI::Cookie could
be useful.

Online help for the web interface, and more comprehensively expose the
functionality of pqm. Maybe start a "comprehensive printer management" CGI
script (this might be a job for PHP).

Test with MOSIX clustering, see how effective this is (on a fast network
with MFS/DFSA it could be good - but unknown at this time).

Maybe try adding anti-aliasing to Ghostscript's PNG driver - or generate
.ppm/.pgms instead, possibly converting them to png using ImageMagic. This
should improve the accuracy of the billing process, at some processing
overhead cost.

Internationalisation of text messages etc.

More fine-grained job splitting (?)

Optional integration with LDAP - specify LDAP authentication in your
printbillrc file and it will store/retrieve data from the specified LDAP
server. It is an unknown quantity at this point, but would be nice at least
for per-user information. It shouldn't be too hard to do from what I have
seen. If only LDAP had better management tools...
