Thomas DeWeese wrote:
BTW one other point things will be a tad bit more efficient if you append your content under the child svg and then append the svg to the document (rather than appending the svg and then appending your content to the svg).
Jorg Heymans wrote:
why is this? I am very much interested in any efficiency gains !
(At the moment we are trying to optimize performance when appending about 10000 path elements to the DOM tree so any other tips about possible performance/efficiency gains are well appreciated)
The best thing to do for 'large scale' changes is do all your changes out of the main tree and append/replaceChild the result.
Unfortunately dealing with 10,000 path elements is just going to take a while. I will mention that if you can combine path elements into one more complex path element (using 'M' commands between what used to be separate elements for example) this can make a _very_ significant difference in performance (both building and rendering).
Unfortunately, i only create this second svg element once. Subsequent updates are always appended to this element.
I would remove the second SVG from the document then make all my changes and append the result back into the document.
PS I didn't see the commit over on dev@, are commit emails disabled ATM?
Since they reorg the mailing-lists the commit mails are going to [EMAIL PROTECTED] I was under the impression that everyone people subscribed to dev were subscribed to this list as well but you might try subscribing.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
