[Design Patterns] pattern for marking changed items before save

[Eli Cochran]

Oh yeah, the iconography is very weak. I was only endorsing the  
general idea, and the marker in the corner.

The only issue that I have with the marker in the corner is that it's  
very similar to a marker that MicroSoft uses in Excel to indicate  
that there is a comment attached to a cell, although there's is yellow.

- Eli

On Dec 11, 2007, at 10:08 AM, Barbara Glover wrote:

> Hi Eli
> Thanks for sharing this.  It's quite interesting.  I like the idea  
> as well for times when you may want to think about something before  
> it's actually committed.
>
> The little red triangle is an interesting cue marker as well.  And  
> this allows the person as they work on the data to keep track of  
> cells they've changed.  This approach might be especially good for  
> large data sets like shown here.
>
> One thing I found difficult was determining how to save.  It took  
> me some time to notice the Save icon in the upper left corner.  I  
> had been looking in the lower right.
>
> I think this could be another inline edit "pattern".
>
> Barbara
>
> On 10-Dec-07, at 12:15 PM, Eli Cochran wrote:
>
>> 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
>>
>>
>> _______________________________________________
>> fluid-work mailing list
>> fluid-work at fluidproject.org
>> http://fluidproject.org/mailman/listinfo/fluid-work
>

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

Eli Cochran
user interaction developer
ETS, UC Berkeley


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20071211/36e8b317/attachment.html>