Jump to content
Search Community

Sir Hound

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by Sir Hound

  1. Thanks for this Jack - I did my best to scour the docs for some of this so I've clearly missed a few. I'll sort those out first thing tomorrow. To be clear the CommonJS support is more like, can I run this module without polluting the global namespace? As far as I understand it there'll always be some globals with Greensock? And the custom inputs, well my next tutorial will be about that but basically you can wrap any data source up as if it were a mouse-like device and have any value react to those inputs. For example it's relatively trivial to move stuff from a Leap Motion or WebSockets data feed. Anyway it's bed for me, thanks for clarifying some stuff for me here!
  2. Hey Jack and Ice-Frog. I just saw this in my referrals and thought I'd jump in and clear some stuff up. The feature comparison is accurate to the best of my knowledge. It has of course been designed to make Popmotion look great, mostly because I've hammered away on it for two years and think that, while not without its shortcomings, I hope it is great! Or at least one day will be. I treat animation equally with the physics and input tracking, which is why I'm making the most of those aspects and from a Greensock point of view it would be easy to look at that table and think "well that's just physics! Why does that get like 5 ticks!" Which is fair enough but it is a first class citizen in Popmotion. The Timeline aspect of Greensock makes it incredibly powerful, moreso than Popmotion, for animations. We're trying to make an UI-focused framework and Greensock can power much more intricate animations. I haven't stress-tested it either, but I would put good money on Greensock out-performing Popmotion in a stress-test. I know it's always been a core tenant of TweenMax (I used it back in the flash days!) and while we strive to be performant, we don't strive to be used as a 1000x particle generator or anything like that, which I bet Greensock could be. If there's anything specific that we've got wrong, or some features you think deserve a slot on that table (MorphSVG is definitely getting one, like I said on Twitter, "woah") you can let me know here, or on Twitter, or to my email, whatever, and I'll happily amend the table because I haven't purposefully misrepresented either framework. Either way we're going to see the two diverge further as time goes on (which is why the table resembles a venn diagram with certain features) and I won't need stuff like this to explain the framework to people. Thanks!
×
×
  • Create New...