search

gvaish / todomvc-mojito

TodoMVC implementation using Mojito (See http://todomvc.com and https://github.com/addyosmani/todomvc)
0 stars 0 forks source link

Routing #4

Open gvaish opened 12 years ago

gvaish commented 12 years ago

Mojito supports routing but it's an HTTP routing. The TodoMVC examples are pure-client-side.

Questions:

  1. Should I use Mojito routing?
  2. Any HTTP call to a new end-point means page refresh. Is implementing routing for TodoMVC really a good idea?
gvaish commented 12 years ago

@caridy @drewfish @rwaldura

Can you guys help in taking this decision - whether or not to use routing? More basic question - does it really make sense here since mojitProxy::invoke does a large part of the hard work for me.

caridy commented 12 years ago

@gvaish this is the exact same use-case we are trying to solve with the YAF integration into mojito, in which case, you should be able to use routing to change the state of the page without trigger a navigation event. For now, you will have to do it manually by using "invoke" and potentially the YUI pjax (http://yuilibrary.com/yui/docs/pjax/) to update the url.

gvaish commented 12 years ago

Awesome @caridy, for the update.

So, I'll continue with the mojitProxy::invoke mechanism... but will add a placeholder in the readme. And to demonstrate the difference between the current implementation and pjax (as and when it comes), I'll keep dependency on mojito 0.4.4 for the current case.