RE: [cgmo-webcgm] new Style Pttributes -- LETD, HSD, LTIO

["Galt, Stuart A" <stuart.a.galt@boeing.com>]

Lofton,

Is this more what you were looking for?

The use cases that I was trying to capture with the defaults column
were:

- The ability to be able to specify a default behavior of elements that
are not allowed in a version 1 or 2 file.  For example Line Cap is not 
allowed in a version 1 file.  It would be nice to be able to specify the
value without upgrading the file to version 3+.

- The ability to be able to define the sizes of the dash, dots, spaces, 
line spacing (for hatches) for the line types that are pre-defined.
This
is useful to make lines look consistent across viewers and hard-copy
versions.

- The ability to be able to specify preferred font substitutions to 
enable mapping the font specified in the CGM and system fonts.  This 
is not actually called out in the table.


The use cases for the DOM column were:

- The ability to be able to define line (and hatch) styles for negative
indexes.  Being able to manipulate these styles at runtime (via the DOM)

it would enable creating the illusion of movement along a line (or
within
a fill).

- Changing line and edge types can be used to draw the user attention to

certain portions of the image.  Modifying the fill style and/or index
can be
used for the same purpose.

- By making shapes (rectangles, circles, closed polygons, etc) that
surround
points of interest and using a fill style of none and then controlling
the
edge visibility attention can be drawn to complex regions (even multiple
regions).
This is similar to how highlight of a region works now, but this would
allow
edges to be different color if needed.

Useless cases:

- Disclaimer: I don't use markers and never have...  But being able to
change
them would allow for implementation of things like To-Do or checklists?

- Disclaimer: I don't use the text score element either... The only use
case 
I could think of was to be able to dynamically underline text.  But this
is
a case of a solution looking for a problem.




--
Stuart Galt
SGML Resource Group
stuart.a.galt@boeing.com
(206) 544-3656

 

> -----Original Message-----
> From: Lofton Henderson [mailto:lofton@rockynet.com] 
> Sent: Tuesday, October 16, 2007 4:25 PM
> To: cgmo-webcgm@lists.oasis-open.org
> Subject: [cgmo-webcgm] new Style Pttributes -- LETD, HSD, LTIO
> 
> Two comments...
> 
> LETD as Style Property:  The table shows "no" for Line and 
> Edge Type Definition (LETD) and Hatch Style Definition (HSD) 
> in the Style Properties column (DOM and/or XCF).  This is not 
> how I remember the discussion.  As I recall, there were at 
> least some people that thought LETD was essential (HSD also).
> 
> Am I remembering wrong?  Did the TC decide that LETD-like and 
> HSD-like functionality were not to be offered as Style 
> Properties (and through XCF)?
> 
> Support for LTIO:  There is also a comment about Line Type Initial
> Offset:  "[1] Support for this element seems limited."  I 
> actually got the opposite impression, that it is considered 
> fairly simple to implement, and is generally implemented.  
> But about the latter I might have assumed too much.
> 
> Vendors (Ematek, LST, PTC, SDI) ... have you implemented it 
> (Line Type Initial Offset)?
> 
>   -Lofton.
> 
> At 09:27 PM 10/16/2007 +0000, stuart.a.galt@boeing.com wrote:
> >I have updated the table based on the 10/10 telecon.
> >-- Mr. Stuart Galt The document revision named Style Attributes
> >(Attributes_Table.doc) has been submitted by Mr. Stuart Galt to the 
> >OASIS CGM Open WebCGM TC document repository.  This document is 
> >revision #1 of Attributes_Table.pdf. Document Description: Style 
> >Attributes for "defaults" and view time control. View 
> Document Details:
> >http://www.oasis-open.org/apps/org/workgroup/cgmo-webcgm/docu
ment.php?d
> >ocument_id=25742
> >Download
> >Document: 
> >http://www.oasis-open.org/apps/org/workgroup/cgmo-webcgm/down
load.php/2
> >5742/Attributes_Table.doc
> >Revision: This document is revision #1 of Attributes_Table.pdf.  The 
> >document details page referenced above will show the 
> complete revision 
> >history. PLEASE NOTE:  If the above links do not work for you, your 
> >email application may be breaking the link into two pieces.  
> You may be 
> >able to copy and paste the entire link address into the 
> address field 
> >of your web browser. -OASIS Open Administration
> 
> 
>