Not used it tons but easeljs looks like it has the potential to make canvas stuff pretty clean and, equally, backbone.js looks pretty good for simplifying comms on html5 apps (I think both these frameworks attempt to insulate the programmer from browser discrepancies).
If I had time for a well fledged proof of concept that'd be where I started if I wanted an entry point into non-flash rich browser dev that was more than forms & other standard ui (for which jquery is we suited to). Think audio in html5 is still pretty lame though.. On 14 Jan 2012, at 08:18, Ima Newsletta <[email protected]> wrote: > For me, in any case, switching back to prototype is a big leap behind. > Also because applied to html, you will go back into late '90 nightmare that > one thing doesn't work on a particular browser and you do not know why (or > you discover it after a long debugging session... and it always ends up with > a workaround made in order to patch a incompatibility issue in that special > case.... *ARGH*). > Yes, this happens less, but this happend also with jquery. > > > > Il 14/01/2012 08:24, Taka Kojima ha scritto: >> I've done a lot of Flash work and a lot of HTML/JS/CSS, and there is >> definitely some misinformation in this thread. >> >> jQuery for one is not as great as it is touted it be, it's useful for >> things, but it's not the be-all-end-all of HTML development. >> >> It makes it easier to do the following cross browser: >> >> - Query the DOM >> - Animate elements >> - AJAX >> - Event listeners >> >> It does some other stuff, but that's the gist of it. Usually, if you just >> use jQuery, your application is going to be a mess. >> >> JavaScript is a very powerful language, ActionScript 2 is an implementation >> of JavaScript. AS3 is an implementation of the abandoned ECMAScript 4. >> >> Switching from AS3 to JavaScript/HTML requires a bit of a paradigm shift, >> but it's really not that much different (taking into account the current >> capabilities of HTML5/JS/CSS). Instead of Sprites you have divs, yeah there >> are a few more semantics, especially when getting into HTML5 but it's very >> straightforward, an<h1> represents a header,<img> represents an image and >> so on. >> >> The biggest shift is from Classical Inheritance to Prototypical >> Inheritance, but the key thing to note is that there is still inheritance. >> _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
