Re: [Gnome-print] Printer & model description files

[Lauris Kaplinski <lauris ximian com>]

Hello!

> About the Default settings, it is better to have them outside on a node
> because when we include nodes, we might want to specify a different set
> of defaults. If they are inside the options, whenever we share nodes we
> will have to share the default settings. 

The real include pattern has to be quite complex anyways.
We have to have a way to:
1. Set custom default
2. Include certain (by name) nodes
3. Include certain (by more complex criterion) nodes
4. Add additional nodes
...
My vision is something like:

Say we have paper definition file, with following data
<Option Type="List" id="Paper" Default="A4">
  <Item .../>
  <Item .../>
</Option>
I am not sure, whether to specify top-level Option - but it may be 
useful, if:
  - we have more than 1 option subtree and we want to selectively pick
    option subtrees
  - we want to check that root id is correct
  ...

Now I can imagine, that including may look like something:
<Include xlink:href="mypaperfile.xml">
  <Exclude>
    <Item Id="Ledger"/>
    <Constraint>Width 600 gt</Constraint>
  </Exclude>
  <Override Default="Letter">
    <Item... my new paper type 1/>
    <Item... my new paper type 2/>
    <Item... overrided paper type subtree/>
  </Override>
</Include>
Well - it does not look like very nice.
There should be opposite of exclude too, but we cannot rename it
  include :(
Override does just that - overrides full tree, starting from
  included tree.

Whether Default is attribute or node does not make big difference
(attributes are nodes too, after all).

Best wishes,
Lauris Kaplinski