UPD Mail Archive: UPD> glossary

UPD Mail Archive: UPD> glossary

UPD> glossary

From: NorbertSchade@oaktech.com
Date: Thu Sep 26 2002 - 10:20:56 EDT

  • Next message: NorbertSchade@oaktech.com: "UPD> UPDF implementation in a Windows based printer driver"

    We see some conversation going on on different reflectors accompanied by
    the announcement of various implementations.
    It may help you simpify things in your mind with a little glossary how
    terms are used in the UPDF world.

    Composite Features:
    A set of basic features, in this case called components, forming a group.
    You may find the abbreviation 'c.f.' used from time to time.
    In theory c.f. can themselves be grouped to a new c.f. on a higher level.

    Dominant component:
    A c.f. can (not must) have one. Exactly one component can be picked, e.g.
    media size as the dominant feature of a c.f. Media.
    If assigned, it is suppose to replace the corresponding basic feature in
    the UI and all according API to the system. The same second all other
    components become hidden in the top level UI as well. All components are
    supposed to be available in a special area of the UI, where the composite
    feature can be managed, let's say to create a new record or edit an
    existing user defined one.
    Without a dominant component all components stay active in the top level
    UI. The c.f. feature serves more like a collective default setting for
    features involved.

    User extensible:
    If a c.f. feature is user extensible, the end user will be able to create
    new records and edit them.
    Predefined records created by the IHV can never be edited, only viewed to
    identify the settings used for single components.
    A nice detail is that a system administrator has the power to switch this
    attribute in a user policy. So s/he can create new records and then block
    the extensibility for all subsequent users.

    The definition of actions, how interference between features should be
    Often mixed up with the term of 'constraints'. Constraints typically define
    a feature by showing up as the set of allowed records.

    A dependency action. Hide special records of special features under special
    Sample: If record 5 of feature A, don't show record 2 of feature B.

    A dependency action. Select special records of special features under
    special conditions.
    Sample: If record 5 of feature A, select record 2 of feature B.

    A dependency action. In case a special condition with a set of features and
    their records involved is identified bring up a message box to indicate the
    condition. Typically offered with an OK and a Cancel button. Cancel brings
    back the previous settings, OK forces the last setting selected to become
    active and the driver is supposed to resolve all conflicting settings.
    Usually the OK case is realized with a Selection action.
    Sample: If record 5 of feature A, show a message indicating that record 2
    of feature B conflicts with record 5 of feature A.

    Hope makes reading easier.
    If you'd see my wall at home, you'd find out that I have these little
    stickers all over my place.


    This archive was generated by hypermail 2b29 : Thu Sep 26 2002 - 10:21:41 EDT