scttnlsn / backbone.viewkit Goto Github PK

If the value of the transition property does not change the transition end event does not fire. Use a setTimeout to ensure that an end event is always triggered.

I think that since Backbone has been significantly updated (and because you can't use raw.github.com as a CDN anymore) neither of your demos work.

Webkit only hardware accelerates 3d transitions.

els.css(Config.transform, 'translate3d(' + delta + 'px, 0, 0)');

It makes a big difference in some mobile browsers. Here's a stack overlfow post about it http://stackoverflow.com/questions/1103129/slow-animation-with-webkit-transform-translate-in-iphone-os-3-0

Wouldn't it be better if, especially when sliding, the new view gets rendered, put in place off-screen, and then as the old view slides out the new one gets slid in? It's a bit of a jarring effect now, especially when compared to the way NestedList's in Sencha work for example. I'm not quite comfortable enough with Backbone to write the entire implementation, but I could prototype the entire animation sequence for you...

hello! i'm using bower package manager, and it gulls 0.1 version, without patchs for detach etc., please update version tag and optionally add component.json file...

Hey Scott,

I'm having some trouble with getting animations to work reliably. I have a contact-form on the bottom of http://development.yieldr.divshot.io (work in progress, form isn't connected yet). If you fill out the form, and submit it, there's no animation. If you refresh the page however, and without filling in the form type in App.FormController.showThanks() in the console, it works completely as expected. The weird thing is that I'm calling the exact same function in my code (see this line of code).

Have you come across this behavior before?

Thanks!

• Steven

If the render method needs access to the view stack it requires doing something like:

var view = new MyView();
viewStack.push(view);
view.render();

Being forced to think about this order of operations is not ideal. I can't really think of an example where one wouldn't want to render the view they are pushing onto the stack so perhaps pushView should just call render after the view is added to the stack.

the api for the the ViewStack had me pondering though.. in my script i alias "replaceView" with "swapView". First reason, obviously its less to type, its synonymous with the original function name, and it adds a bit of fun a la "push, pop, 'n' swap." food for thought..your efforts are very much appreciated (and applauded!)