Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extract DOM push.js transitions #683

Open
ndelage opened this issue Sep 29, 2014 · 2 comments
Open

Extract DOM push.js transitions #683

ndelage opened this issue Sep 29, 2014 · 2 comments
Labels

Comments

@ndelage
Copy link

ndelage commented Sep 29, 2014

Summary: Ratchet's view transitions (push.js) are a key for emulating the experience of a native mobile app, but they're tightly coupled with the PJAX approach to loading new content.

Problem: This is a major blocker for developers who want to render then display content on the client without a PJAX request (e.g. client side rendering with Backbone).

Proposed Solution: Separate the PJAX (AJAX, request caching & click/touch binding) and DOM transition responsibilities of push.js into two different files. Then expose a new function (like PUSH) that allows DOM replacement/transitions without retrieving new content via an AJAX request.

I've hacked together a solution for my own use, but I'd like to polish it and submit it as a pull request if the maintainers are interested. /cc @connors

@cvrebert cvrebert added the js label Sep 30, 2014
@miguelcobain
Copy link

I also think this makes sense, although I'm not sure of what approach we would use.
People are using ratchet in their Ember/Angular/Backbone apps and push.js is something that gets a bit in the way in those cases.

@ndelage
Copy link
Author

ndelage commented Oct 1, 2014

I've submitted a pull request: #684

Let's move the discussion there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants