#1 stuff for printing
Robert,
Here is my mvPrintChannel class and the changes I made
to mvIO to support it. It seems to work well (for what
it does), it supports all 255 print channels,
headings, footings, paging and seems to function
properly with the PRINT ON -1 channel and all that
rot. What is not handled is that it doesn't get any
changeable parameters like from a PTERM statement
since I don't know how you envisioned these sort
of "environmental" things being passed around. I
didn't feel they really belong in the ini file since
they are dynamic. Right now it is hard coded in the
class for a printer page depth of 66 with top and
bottom margins of 3 and a screen depth of 24 with no
top and bottom margins. Didn't add the "C" option to
heading yet, just got busy.
Also, I had planned to use PCPERFORM or duplicate that
snippet of code to effect actually printing the
generated print file which is stored in the currently
hard coded spooler directory. I had experimented some
with using the printerJob and Pageable but they were
horrifically slow from the rasterization for what are
essentially text jobs that can be submitted to the
regular spoolers (still researching how on a Mac).
Anyway, all this stuff seems to work fine since I am
now using it in a production environment with one of
our smaller packages and get identical outputs to
UniVerse.
Oh, also, this copy of mvIO does not contain some
other changes I had made to support problems with the
DATA statement and the size of the pushback reader
buffer.
stuff for printing
Logged In: YES
user_id=11445
I added the supplied patches to CVS - Thanks!
I am not sure how to handle the PTERM type stuff either,
maybe ask on the mailing list.
The java.awt.print stuff is probably overkill for text only
jobs. On unix or windows just PCPERFORMing the os spooler
should be sufficient at least to start off with.