3 ms·

I'd have to agree, I was pretty impressed. I paused it in a couple of instances when they were showing the HTML source view and I didn't see any canvas tags. Ob

I'd have to agree, I was pretty impressed. I paused it in a couple of instances when they were showing the HTML source view and I didn't see any canvas tags. Obviously they could be added dynamically via JavaScript, but that doesn't seem to be the case as you've said. And to back up your statements, they did stress CSS transformations and there is a DOM view which clearly shows him editing DOM elements which when matched with the source code view implies pure HTML. My hope would be that they'd leverage jQuery to handle the actual dirty work of doing the transformations and focus on the tooling and timeline, though I'd imagine it's too early to know if that's case or they'll be rolling their own scripts. I'm actually surprised someone hasn't made a tool like this for jQuery. I know jQuery and jQueryUI have basic animation support and likely some plugins that build and extend those features, but a dedicated tool for creating advanced timeline and event based animations would be amazing.

DjDarkman 16y ago
Until we get rid of most IE versions, we can't really reliably produce animation in web applications. I have built a very simple image cross-fade effect. I most of my time making it IE compatible.
- WesleyJohnson 16y ago
  I would guess it depends what type of animation you're trying to tackle. jQuery has some pretty slick animation capabilities and it supports IE 6.0+. My point, though not complaint, was that it's more geared towards executing a single animation against a single DOM element or a group of DOM elements. This is incredibly powerful, but when you want to start chaining animations, or "firing" off additional animations when you're mid cycle on your first animation - it gets tricky. For example doing something like... $("#myDiv").animate({top: 50}, 1000, function(){ $("#myDiv").animate({left: 50}, 1000) }); Would move "myDiv" down from 0 to 50 over 1 second and then move it right from 0 to 50 over 1 second. But if I wanted to trigger the left -> right animation midway between the top -> bottom animation there isn't an easy way to do that as far as I know. Currently you'd have to create two top -> bottom animations and split up the distance and duration so you can interject the secondary animation. $("#myDiv").animate({top: 25}, 500, function(){ $("#myDiv").animate({left: 50}, 1000); $("#myDiv").animate({top: 50}, 500) }); That or just execute the 2nd one with a timeout independent of the first... $("#myDiv").animate({top: 50}, 1000); window.setTimeout($("#myDiv").animate({left: 50}, 1000), 500); Neither of those "solutions" are terribly difficult, but it gets more and more complex when you start building on it. If Adobe's EDGE or another set of tools would give you the ability to do this easily, I'd happily pay for it. Anyway, I suppose I'm getting off topic. :)
  - DjDarkman 16y ago
    My issue was this: when I have set the ocacity/trasnparency of an element, in IE6 it did not effect the child elements, which was a real pain to fix. I also had very hard time with aligning elements on top of each other and avoiding CSS rules that behave differently in IE and non-IE browsers. TL;DR: Doing animations in web applications is hard for all the wrong reasons.

DjDarkman 16y ago

Until we get rid of most IE versions, we can't really reliably produce animation in web applications. I have built a very simple image cross-fade effect. I most of my time making it IE compatible.

WesleyJohnson 16y ago
I would guess it depends what type of animation you're trying to tackle. jQuery has some pretty slick animation capabilities and it supports IE 6.0+. My point, though not complaint, was that it's more geared towards executing a single animation against a single DOM element or a group of DOM elements. This is incredibly powerful, but when you want to start chaining animations, or "firing" off additional animations when you're mid cycle on your first animation - it gets tricky. For example doing something like... $("#myDiv").animate({top: 50}, 1000, function(){ $("#myDiv").animate({left: 50}, 1000) }); Would move "myDiv" down from 0 to 50 over 1 second and then move it right from 0 to 50 over 1 second. But if I wanted to trigger the left -> right animation midway between the top -> bottom animation there isn't an easy way to do that as far as I know. Currently you'd have to create two top -> bottom animations and split up the distance and duration so you can interject the secondary animation. $("#myDiv").animate({top: 25}, 500, function(){ $("#myDiv").animate({left: 50}, 1000); $("#myDiv").animate({top: 50}, 500) }); That or just execute the 2nd one with a timeout independent of the first... $("#myDiv").animate({top: 50}, 1000); window.setTimeout($("#myDiv").animate({left: 50}, 1000), 500); Neither of those "solutions" are terribly difficult, but it gets more and more complex when you start building on it. If Adobe's EDGE or another set of tools would give you the ability to do this easily, I'd happily pay for it. Anyway, I suppose I'm getting off topic. :)
- DjDarkman 16y ago
  My issue was this: when I have set the ocacity/trasnparency of an element, in IE6 it did not effect the child elements, which was a real pain to fix. I also had very hard time with aligning elements on top of each other and avoiding CSS rules that behave differently in IE and non-IE browsers. TL;DR: Doing animations in web applications is hard for all the wrong reasons.