[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Re: 3 XML Design Principles

• To: "Bullard, Claude L (Len)" <len.bullard@i...>
• Subject: Re: Re: 3 XML Design Principles
• From: Jeff Rafter <lists@j...>
• Date: Mon, 31 Jan 2005 14:14:56 -0700
• Cc: "Roger L. Costello" <costello@m...>, xml-dev@l...
• In-reply-to: <15725CF6AFE2F34DB8A5B4770B7334EE07206BA4@h...>
• References: <15725CF6AFE2F34DB8A5B4770B7334EE07206BA4@h...>
• Reply-to: lists@j...
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

> OTOH, since ROUTEs are from DEF names to DEF names, USEd 
> objects can get you in trouble.  If for example, you 
> send a transform to the rotation field, all of the 
> USE'd objects spin.  

In SVG this is roughly similar-- but in general because of the box model 
the rotations are cumulative-- so you can rotate a rotation without much 
penalty. Where things get sticky in SVG is calculating out the CSS 
inheritance and selectors. Applying textures maybe similar-- but 
multiply that against all of the possible CSS properties and you don't 
end up saving much time with regard to performance. To be fair to 
Roger's original post, this is a slightly orthogonal tangent... it is 
just a real world example where an id/idref mechanism isn't all it is 
cracked up to be. Or in Len's case, is a far better approach.

Cheers,
Jeff Rafter

• References:
  • RE: Re: 3 XML Design Principles
    • From: "Bullard, Claude L (Len)" <len.bullard@i...>

• Prev by Date: RE: Re: 3 XML Design Principles
• Next by Date: RE: Re: 3 XML Design Principles
• Previous by thread: RE: Re: 3 XML Design Principles
• Next by thread: RE: Re: 3 XML Design Principles
• Index(es):
  • Date
  • Thread