[Design Patterns] pattern for marking changed items before save

[Eli Cochran]

I stumbled an interesting twist on inline editing. Most of the time  
that I encounter inline editing the pattern is to save the data  
immediately after it's edited. But this example marks each edited  
item and then the user has to explicitly save the data. The design  
has a lot of problems but I like the idea of it, and I like the way  
that they mark the changed bits.

Double-click a cell to edit (like I said, there are issues).

http://creamarketing.net/jqgridview/demos/demo5/

For complex data where you might want to edit things that are related  
to each other or think about your changes before committing them this  
is a great pattern.

It brings up an interesting question though. Can you mix a save on  
edit pattern (which is great for lightweight data) with this edit and  
then explicitly save pattern and have it make sense?

- Eli

. . . . . . . . . . .  .  .   .    .      .         .              .     
                  .

Eli Cochran
user interaction developer
ETS, UC Berkeley


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20071210/4f9737d8/attachment.html>