PSERVERS CHAPTER STATUS

Remaining issues in order of importance:

• Meshes: How does one scale a mesh relative to a bounding box?

  The edges of mesh patches are given as "path" data which are normally defined in user units. One can look at the pattern paint server for inspiration:

  For pattern paint servers, 'x', 'y', 'width', and 'height' define a unit tile. How these coordinates are defined is determined by the 'patternUnits' attribute (either 'userSpaceOnUse' or 'objectBoundingBox'). The units inside the tile are determined by the 'patternContentUnits' attribute or a 'viewBox'. The interesting thing to note, is that if the 'patternContentUnits' attribute is set to 'objectBoundingBox', the coordinates of any paths with in the tile are defined as a fraction of the bounding box so the path d='m 0,0 1,0 0,1 -1,0 z' outlines the tile. (Tested in Firefox and Chrome.)

  I propose that we add 'meshContentUnits' which with a value of 'objectBoundingBox' would cause the path data in a mesh to be interpreted as a fraction of the bounding box. I further propose that this value would also cause coordinats in a stand-alone (non-paint server mesh) to be defined as a fraction of the the current view port.

  

  Patterns defined three different ways.

• DOM interfaces: solid color, hatches, meshes.
• Content models: hatches vs others.
• Real examples: meshes.