Hi Simon,

>QooxDoo is turning out to be quite understandable ... So I have built similar data binding in QooxDoo so it is simply a matter of specifying a JSON Store (similar to a VFP table) and a column name (similar to a VFP field) and the framework takes care of loading and saving the values.

I just went over there again and read news about the JS-based backend LIBERATED (upper case their choice..)
Have not looked at their data access layer or anything else yet - if you use it and find the time, pls. give your impressions.

I also horsed a bit around and loaded their demo pages again into different CPU/browser settings -
workable on even on not too current HW, worse but not really bad on android-1Ghz Tegra2,
but also not really fast on current HW - so I guess much of the snap factor might be connected to DL/latency factors,.
which might depend on their backend as I don't think my 16000 DL is the bottleneck.
No big differences when using current browsers in "felt snappines" on the I5 pc.

Do you log the time between user input and "inputready again" times within your fwk ?
If so, what is your time "acceptable" limit and do you have to tweak things to reach it /
how hard/successful is tweaking ? In what areas do need you tweak ?

tia

thomas