Hello Randy,

Thank you for your reaction. How I'm working at the moment is as follows :
- I have a "stock" application. Originally it was NetKernel native. But although I understand how to make them technically, I am lousy in making gui's.
- I've created a raw (no formatting) equivalent for all my server requests, returning JSON / XML (I provide both).
- I'm testing one javascript framework after another, every time creating a new version of my stock application
- Points are given for speed of adaptation (mine), speed of the resulting code, ease of creating a 'profesionally looking'-application

I added qooxdoo on the list (after ExtJS, which should be finished by the end of this week - strange, ExtJS basically has the same license policy as NetKernel). My observation on JSON is based on what I find in all those frameworks. XML is always provided, but often as an 'afterthought' and always with the remark that JSON is a lot more efficient. I can't say myself if that is true or not, but originally I only intended a raw XML interface to the server ... so I'm slowly converting.

Regards,
Tom