You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wondering, is there a specific reason for using Raphael as an included svg library (I know its good for backwards compatibility). I was wondering if one of the other libs that allow SVG imports could be better, as you could load in a whole SVG and then animate it for example, whereas I think Raphael has to build things from scratch (Snap.svg.js has the same syntax as it was written by same author).
Not sure if there is any code already included thats dependant on Raphael, so maybe ignore if so!
The text was updated successfully, but these errors were encountered:
Ah why not :), I was actually thinking of Pablo, but couldn't remember if it has SVG import in it or whether there was a reason for Raphael, like some Raphael specific code already in there.
It looks like Raphael was provided for creatures to make use of, but is not part of the system. Some of the jungle creatures do use it - the grass, elephant and stars, but it could be replaced safely here.
Pablo has Pablo.load() to import an SVG into a detached DOM collection and Pablo(element).load() to import and append it to an element.
Just wondering, is there a specific reason for using Raphael as an included svg library (I know its good for backwards compatibility). I was wondering if one of the other libs that allow SVG imports could be better, as you could load in a whole SVG and then animate it for example, whereas I think Raphael has to build things from scratch (Snap.svg.js has the same syntax as it was written by same author).
Not sure if there is any code already included thats dependant on Raphael, so maybe ignore if so!
The text was updated successfully, but these errors were encountered: