#5751 HIGH Never A: Clipboard objects need meaningful labels.

[Zarro Boogs per Child]

#5751: Clipboard objects need meaningful labels.
-------------------------------+--------------------------------------------
  Reporter:  legutierr         |       Owner:  Eben          
      Type:  defect            |      Status:  reopened      
  Priority:  high              |   Milestone:  Never Assigned
 Component:  interface-design  |     Version:                
Resolution:                    |    Keywords:  Update 1?     
  Verified:  0                 |    Blocking:                
 Blockedby:                    |  
-------------------------------+--------------------------------------------
Changes (by legutierr):

  * status:  closed => reopened
  * resolution:  duplicate =>


Comment:

 Replying to [comment:3 Eben]:
 > This is a duplicate of #3117, which points to the specification in the
 wiki.

 Yes, I missed that bug (as otherwise I would have referenced it), and the
 solution described is certainly the best way to give users complete
 information regarding data on the clipboard.

 However, that defect is scheduled for "Future Features", which makes sense
 due to the added complexity of adding thumbnail functionality for images
 and video.  IMHO, this bug is a real killer for anyone who actually uses
 the multiple-clippings feature of the clipboard, and should be fixed
 within a specified, scheduled time-frame.  Furthermore, I believe that
 there are reasons to differentiate the need for a preview and the need for
 descriptive naming, and reasons to actually treat these two as separate
 defects/enhancements:

 First, descriptive naming will make it easier to distinguish between
 clippings that have been saved to the Journal (as long as descriptive
 names are carried over to the Journal).  The user browses the Journal as a
 list of icons and names, and if several objects have the same icon and
 name, the user is forced to exert extra effort/time to differentiate them.
 The Preview functionality will presumably not carry over to the Journal,
 so descriptive naming seems to be the solution to this issue.

 Second, any preview will probably take a second to load, especially
 thumbnails but probably even text (as in the back-forward drop-downs in
 Browse).  I am willing to bet that in the final event, a user will be able
 to quickly run the cursor down the series icons and instantaneously view
 the title of the object, but will not be able to see the preview
 instantaneously: she may have to wait a second for it to pop open, or may
 even have to go into the drop-down and select a preview menu-item.  If a
 user needs *some* information, but not *all* information about a clipping,
 then why make the user wait?

 Third, in the case of text clippings (which is the most common clipboard
 item, and most likely to confuse a user), implementing descriptive naming
 would seem relatively trivial and could be introduced sooner than the
 preview, and with less impact on the code.

 If you don't want to include descriptive naming as an ''additional''
 feature due to resource constraints, let me just say that I'm willing to
 do (some/most/all of?) the coding work on this type of usability feature,
 but certainly not if it goes against the spec or against the intentions of
 the design team.  I realize that what I am proposing requires some change
 to the spec, but could you reconsider this?

-- 
Ticket URL: <http://dev.laptop.org/ticket/5751#comment:4>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system