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" ---- 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/
