3 ms·
Is there any reason not to just use react-router? Edit: ok I found the createApp mixin and I can see you're doing a lot of stuff in there to support the touchs
by colinramsay 12y ago
Is there any reason not to just use react-router?
Edit: ok I found the createApp mixin and I can see you're doing a lot of stuff in there to support the touchstone app... It would be sweet if you could delegate some of that heavy lifting and integrate with react-router at the same time...
- jed_watson 12y agoYou need a lot more control over how the views transition, pass state, etc. in order to create a native-feeling app. The paradigm of links and parameters falls short, and eventually TouchstoneJS will exert a lot more control over the transitions. Right now we're using CSSTransitionGroup, but I expect we'll move to a JS-based transition method (possibly with tween-state) so you can do controlled or partial transitions (required for things like drawers or swipe-from-left to go back) We have spent a lot of time looking at react-router though, and are using it on other projects, and are / will be borrowing quite a few things :)
- colinramsay 12y agoThat's fair enough. I'm looking forward to testing Touchstone out soon, I've got a test project in mind!