Re: Creating Custom Printer Banner Page in DCPS?
From: Paul Anderson (paul.anderson_at_hp.com)
Date: 08/01/05
- Next message: Keith Parris: "Re: Interex is Dead!"
- Previous message: Brad Hamilton: "CDE create action application"
- In reply to: JF Mezei: "Re: Creating Custom Printer Banner Page in DCPS?"
- Next in thread: JF Mezei: "Re: Creating Custom Printer Banner Page in DCPS?"
- Reply: JF Mezei: "Re: Creating Custom Printer Banner Page in DCPS?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 01 Aug 2005 19:47:56 GMT
In article <42EE6343.1C66202F@teksavvy.com>, JF Mezei
<jfmezei.spamnot@teksavvy.com> wrote:
> Adding some CR/LFs (or I assume not removing them from your baseline
> source code which I would hope is human readable) would not add a lot
> of overhead in terms of space and performnance and would make it so
> much easier to debug problems.
The source PostScript code is indeed readable by humans, created by the
many anal-retentive engineers who have worked on DCPS over the years.
The code is "packed" at build time. Even though not "packing" it would
probably not cause a performance problem, the thinking through the ages
was to make it hard for people to customize (mess up) their flag pages.
> I'd like to see DCPS create a dictionary containing any/all
> information about that job, including any parameters supplied
> (possibly user defined paramenters as well, the note etc etc). Then,
> when a flag page is called, a specific module would be called, and
> that module could be customizable and just use the variables already
> defined in that dictionary to generate the flag page.
>
> Furthermore, code in the "main" postscript program would then also
> have access to the print job information by accessing that
> dictionary.
Are you suggesting a PostScript dictionary here?
> It would be nice to be able to define the company name there so that
> customers would have their onw company name.
This feature has been requested often.
> Also, while I am at it, DCPS should define a logical associated with
> the queue which would contain the printer name/type as soon as it has
> established communications with the printer and determined its type.
What purpose would these new logical names serve? Would it be helpful
in debugging problems?
I can see how they could be useful, but DCPS already has so many
logical names, and adding "read-only" logical names might make things
more confusing, especially since the product name can be specified with
the DCPS$queuename_PRODUCT_NAME logical name.
Paul
-- Paul Anderson OpenVMS Engineering Hewlett-Packard Company
- Next message: Keith Parris: "Re: Interex is Dead!"
- Previous message: Brad Hamilton: "CDE create action application"
- In reply to: JF Mezei: "Re: Creating Custom Printer Banner Page in DCPS?"
- Next in thread: JF Mezei: "Re: Creating Custom Printer Banner Page in DCPS?"
- Reply: JF Mezei: "Re: Creating Custom Printer Banner Page in DCPS?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|