Forums

I've been struggling with the Y.App examples for awhile to figure out how to leverage them to some of our normal data-processing type applications (i.e. heavily tabular DataTables, dialog editing, etc...). Also we decided to do some experimenting with NodeJS to do RESTful type access to our database store.

It looks like we may have succeeded in creating a webpage that has the following features;
1. A DataTable
2. Y.Model representation of each Record
3. Y.ModelList with "sync:read" defined (read all records from a DataSource)
4. Y.View to display a Panel for row editing
5. Uses eric_f's Gallery REST Model Sync to persist back to remote server
6. NodeJS + Express + mysql RESTful server at the back-end

Maybe some of the Y.App experts can look this over at http://blunderalong.com/yui/dta/dt_mv_sync_REST.html and let me know if we are on the correct track.

This isn't built as a Y.App yet, because we'll probably end up using several DT's and other page components within a total application. But at least it's a start.

Comments and suggestions are welcome!

Todd

@ericf
Thanks for your encouragement. Based on your help I was able to update this example remove DataSource completely and do all Gallery REST Model Sync requests to the server. So the ModelList was re-written to use the "sync" layer completely and take the DataSource out.

So now the example works as a DataTable served by a remote source, with editing capability, without using DataSource as an intermediary.

I'm going to check into some performance timings to see how this ModelList sync approach compares on "reads" versus a DataSource read.

Thanks Eric!