Yes, we are actively working with the YUI App Framework folks (who sit ten feet away at work) to see how the two frameworks can best align.  It's still the early stages, and we're still trying to figure out the best path.

You can expect concrete results on this by end of August. Eric F. (YAF author) is working with the Mojito team.
Follow me on Twitter: http://twitter.com/rw0

Is there any update on YUI App Framework integration?

Thanks.

We expect to release something by end of August.
What is most important to you? What kind of integration would you like to see first?

Client side and server side url routing integration.

Clicking on a link should automatically invoke the controller action without depending mojito view binder.

Subsequence rendering should all happen on the client side. That means the server is responsible for rendering the landing url, then lazy load the rest of the application to the client in the background. After this, the client should never have to call the server anymore unless it needs to invoke a method that only exist in the server affinity.


I guess what I want is being able to run the YUI App Framework on NodeJS, then package up the application and send it to the client.
I don't know how this can be done without throwing away what Mojito is calling the controller, the model, and the view today. :)

check out the demo from the derbyjs guys.

http://directory.derbyjs.com/

the whole application still works if you turn off javascript.

with javascript enable, after loading the landing page, then it loads a fat javascript file http://directory.derbyjs.com/gen/A72UGl5IL_sooCIYHayepg.js that packages up all the controllers, views, models, and templates. Then it sets up a socket channel with the server only to exchange data.

Actually, swapping out mojito model with YUI App Model should be very trivial. It seems like Mojito Model is just a raw JSON object.

Replacing Mojito View + Mojito Binder with YUI App View is going to be tricky.

No doubt, but we've started working on this. It may break backwards compatibility in some places. :(
See also https://github.com/yahoo/mojito/issues/259
Let's contine the discussion there!