111–120 of 143 posts
Available at http://tweenui.com/animator/
What do you think? How does it stack up?
Was it very painful to develop this great GUI or is GWT/HTML5 at a point where it's OK?
I'm happy to see that you're using Canvas for the published animation. It's the only way to go for artistic animation where content needs to update at every frame -- CSS just isn't enough for that.
Some three years ago, I made a HTML5 animation tool that outputs to Canvas + video: http://radiapp.com
Despite all the hours I put in, I never managed to figure out a way to turn it into a real product. I think you will fare better :)
There's a lot of nice things about this UI, well done! The difference between "animation" and "design" modes isn't quite obvious at first glance. The switch doesn't tell you anything, so you have to experiment to find out what it means. I'm happy to see that you're using Canvas for the published animation. It's the only way to go for artistic animation where content needs to update at every frame -- CSS just isn't en…
I really like that it's using GWT too! You don't often see much GWT apps these days.
yeah, we had internal debates whether to use gwt or just js, gwt side won and we (most of us!) do not regret it :)
I'll have to add a shameless plug to the visual HTML5 editor in the browser that I've built. Also created with GWT, and using GreenSock JS for animations. Available at http://tweenui.com/animator/ What do you think? How does it stack up?
Earlier quoted context omitted.
yeah, we had internal debates whether to use gwt or just js, gwt side won and we (most of us!) do not regret it :)
if it's not too private, i'd like to hear about some of the details of the debate you had! What was the arguments against GWT? what was the arguments against pure js?
gwt pros: - java (excellent tooling, static typing, reliable refactoring) - code splitting and async loading (although we don't use it as much as we thought we would) - easy live debugging in devmode (will be gone soon) - rpc (although we switched to our own) - same model (java classes) on a client and on a server
but frankly most of it is basically java. we knew that the team will be 5-10 devs at least, we knew that the codebase will be big, so the java is obvious choice.
js pros: language a bit nicer (but it sucks anyway comparing to scala which is our server side :), better performance - no gwt wrappers/layers.
