Piotr Wlodarek wrote:
1) How do you think in-place-editing will affect Rails development?
The current implementation has minor flaws; the editor requires a model, for example. These will smooth out.
I mean, it's not along with well established conventions, like having
RESTful controllers with strict set of actions.
That is a usability question. The Web 2.0 movement might sometimes require professional usability experts - not feature-zealous programmers - to establish use cases for our software.
Maybe it would be better if we could send the whole form after one field
change, so standard update action could be used, just with new
That will be among the details that are smoothed out.
2) Will in place editing end up as a substitute for standard modify
page? I think it's rather complementary approach and only in some cases.
Start the question with the user's experience. They know, by now, the difference between the pages that submit and refresh, and the pages that change one element at a time. If a given website uses one technique for certain situations, it shouldn't jump to the other technique for similar situations. Giving the user the option to refresh a whole page will return control to them.
3) Could you recommend any article on in-place-editing usability
Books like /Pragmatic Ajax/ suggest that websites must support a Back button and the Favorites bar. Neglecting these would take our usability back a couple decades.
My O'Reilly Short Cut shows how to write unit tests for every detail of any in-place edit field. My resulting usability, however, is a cautionary tale!