We’ll probably also use it on a project we’re going to do as a proof-of-concept of our framework (see link). It will be a kind of collaborative application that will include real-time chatting, file upload, some kind of wiki, calendar integration and more. Basically an user can create or join various teams, with each team having their own channels and tools. Teams have the option of making the whole team or any of their resources private and to control access to each. It will be made available both as a free service and as source along with a lengthy tutorial on its design and implementation that will be included in the framework’s documentation. We’ll use the framework’s mailing list (and trac) to work on it, so feel free to subscribe and follow the project.

Thanks for your comments. Perhaps a reset method should be added to the list of future upgrades for the plugin. It shouldn’t be difficult at all to do that though.

Out of curiosity what type of application would you be using it in?

I see from the code that it could work very well with the forms plugin and others, allowing you to use it to submit the form diff through AJAX. You’d still have to reenable all the disabled fields after the form gets submitted of course.

It seems to me that the way you are suggesting increases the request size (rather than decreasing it). On top of that there’s a good chance you would have the database record already loaded on the server side so why would you bother putting all the extra overhead of submitting 2 copies of every field when you could no doubt just use the fields in the database record to compare against.

It seems counter productive.

What I do is put a HIDDEN form value called “ORIG_varname” for every input.

On the server side I iterate through varname and compare with ORIG_varname. If they are the same, I unset or remove them from the POST.

Tri Bui