[FreeNX-kNX] Some potential messiness in nxprint

[Jeffrey J. Kosowsky]

Forwarding this (along with several other postings) to the list per
Fabian's suggestion... Note: I have also previously posted a copy to
the freenx-devel list.

Jeffrey J. Kosowsky wrote at about 00:18:21 -0500 on Monday, December 10, 2007:
 > Fabian,
 > When I originally wrote the caching logic to speed up listing of the
 > foomatic ppdfiles, I placed the caching logic in nxclient (what would
 > now be nxdialog).
 > 
 > This allowed one to still run "nxprint --drivers" as a standalone
 > routine. Now with the cache logic buried there, you end up writing to
 > the file ".all" in the local directory if you just call it as a
 > standalone since the variable UTILITY_DRIVERS_CACHE is not set. So,
 > I'm thinking that it might be better to put the caching logic back in
 > the utility printing functions in nxdialog.
 > 
 > Alternatively, would it be better to take all the printing utilities
 > out of nxdialog and put them in nxprint and make nxdialog more of a
 > pure dialog generating script.
 > 
 > Also, is the option "nxprint --printers" ever used now?
 > All it really does is call "lpstat -p". And that itself may be wrong
 > since you probably really want to call "lpstat -p -h localhost:$port"
 > since you want to be accessing the local cups process.
 > 
 > The reason that I am writing this is that I am finding that with each
 > new release of freenx, the code gets a bit more complicated and
 > difficult to follow. Of course, the functionality and flexibility is
 > much improved and some areas are tightened up. But at the same time,
 > naturally, some of it gets a bit more difficult to follow -- this is
 > NOT A COMPLAINT -- just an observation about whether it makes sense at
 > some point to take a step back and reorganize the code. For example,
 > it is not always clear (to me) which routines call which other
 > routines and which variables are passed or sourced. The net result is
 > it took me half a day to find the two simple bugs that I reported in
 > the previous email. 
 > 
 > I do of course appreciate all the hard work you have put into building
 > this code and I want to be as helpful as I can with my limited
 > abilities and understanding.
 > 
 > Thanks for all the help!
 > Jeff