Done. I think that RoR's implementation is a little bit clunky:
1) too many callbacks, which may be processed on client side 2) too low level 3) unmodular on client side Of course you can always write your own level, which will keep things manageable in complex cases. Unfortunately RoR does come bundled with them. Script.aculo.us and OpenRico take care of some high-level stuff, but while they provide some widgets, they lack unified widget building system. I think that the most clever part of RoR's Ajax is simple yet efficient drag and drop support. If you formulate RoR's Ajax functionality in terms of widgets it comes to: 1) Widget XXX provides YYY functionality. 2) There is a markup code to specify a widget with all required parameters in your HTML. 3) Widget may do callbacks on certain (high-level) events. 4) Widget can be as simple or as complex as possible. Thanks, Eugene "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > On Nov 16, 2005, at 2:34 PM, Eugene Lazutkin wrote: >> Will do. I was hoping that it would be discussed publicly before being >> canned. > > I didn't mean to "can" anything -- I think your assesment of what's good > about AJAX in Rails is quite useful, so I want it somewhere slightly more > prominent than the mail list. Since this is a big issue with lots of > thorns I'm trying to make sure all the important info gets onto that wiki > page so we can all chew on it. > > Jacob
