On Wed, Jul 18, 2012 at 10:26 AM, Ajay Garg <span dir="ltr"><<a href="mailto:ajay@activitycentral.com" target="_blank">ajay@activitycentral.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Samuel.<br><br>Please find the replies inline.<br><br><div class="gmail_quote"><div class="im">On Wed, Jul 18, 2012 at 7:03 PM, Samuel Greenfeld <span dir="ltr"><<a href="mailto:greenfeld@laptop.org" target="_blank">greenfeld@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I see in the final screenshots that all of the selected items are deselected.<br><br>Is this automatic, or does the user have to choose the "deselect all" button to do this?<br>
</blockquote></div><div><br>This is automatic (on the fly).<br><br><br><br><br><br><br> </div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>Personally I would prefer if the checkboxes remain selected in the source view (if not an erase operation that removes the item). That would allow the user to do multiple actions (Copy then Erase for a "Move"), and confirm after the operation that they selected the items they intended to select.<br>
</blockquote></div><div><br>Well, the code is generic enough, and the above may be accomplished if there is a general consensus.<br><br>However, the current flow (automatic de-selection), "helps" user to "not deselect" "explicitly", in the general case.<br>
<br>I believe that copy-then-erase is a more of a special case, than a general one. <br>For eg., copying-from-a-USB-pendrive-to-journal is more probable, than copying-from-a-USB-pendrive-to-journal-and-then-erasing-the-contents-of-USB-pendrive.<br>
<br><br><br></div></div></blockquote><div><br><br>The original behaviour was to remain these entries selected after operations, exactly by the same reason samuel points out. In terms of cost, as user time, it is a lot more expensive to re-select all those entries (not necessary all) than simply hit the deselect-all button. I would vote for letting these entries selected.<br>
<br><br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><div><br><br> </div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>It seems from these screenshots like we are trying to indicate copying progress by deselecting items as we copy them, and I do not know of another OS that does that.<br></blockquote></div><div><br>The workflow is ::<br>
<br>
(i)<br>Operate on entry "x".<br><br>(ii)<br>Deselect the entry "x".<br><br>(iii)<br>Goto step (i)<br><br><br>Also, it's good if Sugar tries to be different, as long as it does the right thing :P<br>
<br><br><br><br>Regards,<br>Ajay<br><br> </div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br><div class="gmail_quote"><div>
<div>
On Wed, Jul 18, 2012 at 6:57 AM, Anish Mangal <span dir="ltr"><<a href="mailto:anish@activitycentral.com" target="_blank">anish@activitycentral.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>Hi,<br>
<br>
I would like to propose the long-discussed-finally-implemented ;-)<br>
journal entry batch operation and multi selection feature for<br>
inclusion in sugar-0.98. All the necessary and relevant details should<br>
be present in the associated feature page:<br>
<br>
<a href="http://wiki.sugarlabs.org/go/Features/Multi_selection_screenshots" target="_blank">http://wiki.sugarlabs.org/go/Features/Multi_selection_screenshots</a><br>
<br>
AFAIK, This feature was initially brought up in discussions in EDUJam<br>
in 2011 and an initial implementation was made by Martin Abente. The<br>
current implementation, done by Ajay, has been derived from that<br>
keeping the UI experience largely the same while significantly<br>
speeding up operations like select/deselect.<br>
<br>
Should you have any design related questions about this, feel free to<br>
reply to this thread.<br>
<br>
Cheers,<br>
Anish<br></div></div>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</blockquote></div><br>
</blockquote></div></div><br>
</blockquote></div><br>