That is not entirely true. Although it is true that elements later
in the document are drawn over elements previous in the document, if
you try document.getElementById('someID'), the first element in the
document matching that ID is returned rather than the last one.
--- In [email protected], [EMAIL PROTECTED] wrote:
>
> Let me add my bit here - since I recently explored using the
shadow tree
> for the sue element itself:
>
> By directly replacing "content" into the main tree you lose
modularity.
> Here is my situation embed an SVG file within a parent SVG file.
No big
> deal. But, what if you have styling and other defs which have
similar id's
> to the parent/sibling documents. The way it works in SVG is that
the last
> instance will override all others in terms of these id's - so in
effect you
> would probably "lose" some elements of the parent document . This
applies
> to any other elements too such as graphics elements/scripts/etc.
So, if you
> need to have "object oriented" SVG and associated styling/etc.
this shadow
> tree is the way to go. In terms of the overhead I think its there
but not
> that significant compared to the advantages.
>
>
>
>
> Holger
Will
> <[EMAIL PROTECTED] To: svg-
[EMAIL PROTECTED]
> .de>
cc:
> Sent by: Subject: Re:
[svg-developers] Shadow
Tree
> svg-
[EMAIL PROTECTED]
>
ogroups.com
>
>
> 07/02/2005 12:01
PM
> Please respond
to
> svg-
developers
>
>
>
>
>
>
> Mitzie schrieb:
>
> > Hello,
> > I've searched the net as well as the SVG 1.1 and 1.2 specs for an
> > actual definition of a shadow tree. I've found the
definition "For
> > storage of the distributable files, we create "object trees"
which
> > mimic the organization of the
> > source code directory /usr/src (see figure 2). There is one
object
> > tree for each different architecture or
> > operating system. We called the directories where object files
are
> > stored, "Shadow Trees", because their
> > structure is a projection of the source code tree.
> > "
> > however this really does not apply to the RCC rendering model
used in
> > SVG. Can anyone explain what a shadow tree is and why it is
such an
> > advantage to use it?
> >
> > Thanks.
> >
> Hi Mitzie
>
> ok, let me try, if you have a <use> element, the used content gets
> cloned and virtually appended to the <use> element.
> this cloned content is a "shadow tree" of the original element that
> gets <use>ed.
> RCC or now sXBL is taking the concept of "shadow tree"s a step
further,
> by giving you more controll of the creation process and insertion
points
> of a "shadow tree".
>
> hope im not to far off.
> cheers
> Holger
>
>
> -----
> To unsubscribe send a message to:
> [EMAIL PROTECTED]
> -or-
> visit http://groups.yahoo.com/group/svg-developers and click "edit
my
> membership"
> ----
>
> <?---- LSpots keywords ?> <?---- HM ADS ?>
> YAHOO! GROUPS LINKS
>
> Visit your group "svg-developers" on the web.
>
> To unsubscribe from this group, send an email to:
> [EMAIL PROTECTED]
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.
-----
To unsubscribe send a message to: [EMAIL PROTECTED]
-or-
visit http://groups.yahoo.com/group/svg-developers and click "edit my
membership"
----
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/svg-developers/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
