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
Loving the Mo.js examples, look so gorgeous. Im seriously thinking of adopting it for my SVG application. However, after reading Sarah's mo.js tutorial, Im a bit curious about when you want to move to purely SVG enviroment for positioning & animations?
My app is purely SVG, with just the SVG parent container within a div.
My needs will be mainly animating the g containers, which house different shapes & text content etc. In some cases, it will be quite performance heavy. However, judging by the various issues here, you seem to have been most conscious of the performance.
So my question is, do you intend to have the position / other bits without a container 'div' for SVG elements?
The text was updated successfully, but these errors were encountered:
mojs will tweak the parent option in the future, so you will be able to transparently add the modules inside html or svg elements (right now you can add them only inside html). Re: timing -- it won't lend too soon I guess, I think in a month or so.
Just wondering -- you request the same modules work inside svg or just having the tools to animate existing svg elements ?
Ideally, I would like the same existing functionality to be able to work in SVG. I haven't reviewed the tools yet so right now dont see myself using them, however, that may change after the review :D
A lot of the animations that I have in mind are pretty basic e.g.
animating credit cost of a user action onto the screen & disappearing it after a setTimeout.
animating a stream of svg elements (easily over a few hundred) on to the screen, one after another.
However, your pretty animations are giving me food for thought :)
Hi Oleg,
Loving the Mo.js examples, look so gorgeous. Im seriously thinking of adopting it for my SVG application. However, after reading Sarah's mo.js tutorial, Im a bit curious about when you want to move to purely SVG enviroment for positioning & animations?
My app is purely SVG, with just the SVG parent container within a
div
.My needs will be mainly animating the
g
containers, which house different shapes & text content etc. In some cases, it will be quite performance heavy. However, judging by the various issues here, you seem to have been most conscious of the performance.So my question is, do you intend to have the position / other bits without a container 'div' for SVG elements?
The text was updated successfully, but these errors were encountered: