[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: re: Fwd: Re: re[2]: [cgmo-webcgm] lineEdgeTypeDef xml coding
Lofton & Dave, > From Dave... > (Btw, I was going to reply the same thing: the present purpose of the ACI > defaults-setting for line type is just to allow a precise definition of > the generic types 1..5. There is a specific issue in the TC log about > this, deciding what the scope was to be). That's good, thanks. > -Lofton. > Date: Sat, 31 Jan 2009 16:12:47 -0800 > Subject: Re: re[2]: [cgmo-webcgm] lineEdgeTypeDef xml coding > From: David Cruikshank <dvdcruikshank@gmail.com> > To: Don <dlarson@cgmlarson.com> > Cc: Lofton Henderson <lofton@rockynet.com> > It's a pain not being able to respond to the TC... > On negative values of lineIndex. Since this specifies default values in > the CGM file, it only makes sense for positive values. Negative values > would have definitions in the file itself. > dave > On Sat, Jan 31, 2009 at 3:07 PM, Don <dlarson@cgmlarson.com> wrote: > Lofton, > comments below- > > Don, > > Here is the operative DTD snippet: > > <!ELEMENT webcgmConfig ( fontMap?, defaultAttributes? ) > > > ... > > <!ELEMENT defaultAttributes ( lineCap | edgeCap | lineJoin | edgeJoin > > | lineTypeCont | edgeTypeCont | mitreLimit > > | restrTextType | lineEdgeTypeDef | > > hatchStyleDef )+ > > > That means the ACI can have 0, 1, or *more* of any of the things in > parens, > > like lineCap and lineEdgeTypeDef. As far as I can see, there is > nothing in > > the ACI chapter to further restrict. > > I think that is okay. If we have a rule like "last one wins", then > that > > would tell a viewer what to do with multiple occurrences of lineCap in > the > > ACI file. For lineEdgeTypeDef, it would only be multiple occurrences > if it > > were defining the same line type index, in which case again, "last one > > wins". > > Does anyone see a problem with that? > > If it's okay, then we can disambiguate with a single sentence (or two) > in > > the chapter. > That should suffice. > I will also try to use multiple lineEdgeTypeDef in one of my ACI tests. > Did you see my question at end of my last email regarding negative > lineIndex? > [ Another question related to lineEdgeTypeDef, is a negative lineIndex > valid > in ACI lineEdgeTypeDef? I re-call that we debated wheter or not we > wanted > to do this is our last f2f, but just wanted to make sure. As the spec is > now, negative lineIndex is NOT valid.] > Don. > > -Lofton. > > At 03:26 PM 1/31/2009 -0600, Don wrote: > > >All > > > > > >The spec is not clear to me that an ACI file can contain multiple > > >lineEdgeTypeDef elements and attribute sets. > > > > > >For example is this valid? > > > > > ><webcgmConfig > > > <defaultAttributes> > > > <lineEdgeTypeDef lineIndex="1" repeatLength="100" dashLength="10 2 > 5 > > >2" /> > > > <lineEdgeTypeDef lineIndex="2" repeatLength="100" dashLength="10 2 > > >10,2" /> > > > <lineEdgeTypeDef lineIndex="3" repeatLength="100" dashLength="10 2 > 5 > > >2 5 2" /> > > > </defaultAttributes> > > ></webcgmConfig> > > > > > > > > >Since a Metafile has only 1 lineCap attribute by definition, an ACI > can > > >have only 1 lineCap element but since there can be multiple > lineEdgeType > > >definitions in a Metafile, I would think that specifying multiples is > > needed. > > > > > > > > >Another question related to lineEdgeTypeDef, is a negative lineIndex > valid > > >in ACI lineEdgeTypeDef? I re-call that we debated wheter or not we > wanted > > >to do this is our last f2f, but just wanted to make sure. As the spec > is > > now, > > >negative lineIndex is NOT valid. > > > > > > > > >Don. > > > > > >--------------------------------------------------------------------- > > >To unsubscribe from this mail list, you must leave the OASIS TC that > > >generates this mail. Follow this link to all your TCs in OASIS at: > > >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > --------------------------------------------------------------------- > > To unsubscribe from this mail list, you must leave the OASIS TC that > > generates this mail. Follow this link to all your TCs in OASIS at: > > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]