UPD Mail Archive: UPD> minimum hardware margins

UPD> minimum hardware margins

From: Norbert Schade (norbertschade@comcast.net)
Date: Tue Feb 03 2004 - 13:52:47 EST

  • Next message: Norbert Schade: "UPD> syntax optimization"

    We've finished the review of the media minimum hardware margins.
    The according schemas and instances are available on the web under
    ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/
    Or you can follow the link on the UPDF site.

    I think this is worth reading.

    The way it works:

    1. MediaHardwareMarginsPattern
    We have defined a pattern to specify hw margins.
    We used the custom media size pattern as a template and modified it as needed.
    It is partly verbal, but tells about the values as well. We think it's a good mixture.

    2. MediaHardwareMargins
    This feature is a predefined one.
    Its appearance is permanently set to hidden, as we want this to be used as a reference, but not to appear in the user interface (if somebody desperately needs it, there is always the change of composite features).
    Now this has a number of advantages.
    First every record is only listed once (before it was specified per media size). --> easier maintenance.
    Second you can specify as many records as you may need anywhere. It will not show up in the UI unwanted.
    You can define records especially to be used for landscape, if you need to. Basically you could define a special record for any need.

    3. Dependencies
    We really activate a record in the dependencies.
    Vision something like "if MediaSize is Letter and Orientation is Landscape, the four margins are 1.1.1.1in".
    Fortunately our dependencies offer everything we need to check any condition and start any action.
    Do not use a dominant feature for the action, as you want it checked always.

    4. Generic features
    One may want to create a generic feature called "Edge to Edge Printing", which overwrites all hw margins and sets them to zero when selected.
    No problem. See this request realized in the samples.
    You create the feature records and add a dependencies to select a different hw margin record.
    Be careful with the order of dependencies. They are used in sequential order, master description first, user policy last.

    I think the way it works is a fortunate coincidence of several factors.
    We do not have any open request left with this design.

    Check it out.
    Norbert Schade

    Norbert Schade
    69 Prescott Drive
    North Chelmsford
    MA 01863
    phone: 1-978-251-1017
    email: norbertschade@comcast.net



    This archive was generated by hypermail 2b29 : Tue Feb 03 2004 - 13:57:04 EST