Juergen Schoenwaelder wrote:
Kurt Pfeifle writes:
Kurt> I've used the realllllllly nice scli command line version for Kurt> quite a while now and been able to surprise quite a few people Kurt> with "my secret knowledge" and "my" easy solution to a problem, Kurt> which you guys made possible.
Thanks.
Kurt> Michael Goffioul, the KDEPrint programmer wizard, has started 3 Kurt> days ago to implement a KDE GUI frontend to scli (for those Kurt> curious about the first screenshots, see
Kurt> http://www.geocities.com/kdeprint/skli.html)
Looks cool. I never had the opportunity to test scli with bigger printers with multiple input trays etc. but it seems to work fine.
Definitely! I've tested it with quite some models and it worked with so many, that I think it is a lacking implementation on the part of the vendor if his model doesn't show a "tray 17 is open" message through scli. Anyway, let me know what I can do to help testing all the stuff... Is there a "raw" or "verbose" mode, which lets me log every byte the printer sends back to me in the original state, which you could use? Or is it just that you "implement a defined standard", and look at the written MIBs to develop scli?
Kurt> I had the following compile error during "make":
[...]
This is just the documentation. :-) There seem to be problems with different version of makeinfo or texinfo which I never bothered to track down. You should still have a functional scli binary.
Thanks for the hint. It is true ;-)
BTW, I have makeinfo (GNU texinfo) 4.2.
kde4@kde-bitshop:~/cups-versionen/CVSstuff/scli/scli> makeinfo --version makeinfo (GNU texinfo) 4.0
I'll try to update and see if it lets me then know the documentation... ;-)