Hey,
OK, I was looking for something that wasn't there (remote data binding), so I
must create the remote Rpc part myself. I have used the AsyncRpc approach
earlier, so that seems doable. But how would I correctly architect this?
(I am just entering the world of where people talk models, controllers and
views.)
Does that mean I should implement a JSON-RPC backed store somehow and attach it
as follows?
Backend -- Rpc -- Store -- Model -- Controller -- View
This section looked interesting but is a short read:
http://manual.qooxdoo.org/1.6/pages/data_binding/stores.html#combining-with-controllers
Yes thats exactly the approach. Try to keep the store away from the view /
controller and see the Model as an independent layer between them. That way,
you can have different kind of views on the same data e.g.
I just came across the experimental REST support in Qooxdoo. As my project is
a demonstrator, I am considering using this:
http://manual.qooxdoo.org/2.0/pages/communication/rest.html
Or should I stay away from it for the moment?
Give it a try. I don't expect much changes there, at least not in the API. That
could be a good approach as well.
Regards,
Martin
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
