#2151 NORM Trial-3: Need icons for clippings in clipboard

[Zarro Boogs per Child]

#2151: Need icons for clippings in clipboard
-------------------------------+--------------------------------------------
  Reporter:  Zack              |       Owner:  tomeu  
      Type:  defect            |      Status:  new    
  Priority:  normal            |   Milestone:  Trial-3
 Component:  interface-design  |     Version:         
Resolution:                    |    Keywords:         
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by Eben):

 * cc: okada (added)
  * owner:  Eben => tomeu
  * status:  assigned => new

Comment:

 I've attached a first pass at the clippings.  There are 6 "primitive
 types" for which icons are specified:

  - image
  - video
  - audio
  - text
  - url
  - data

 Data is, of course, the most generic and may be used for any type of
 clipping whose type is otherwise not covered by the primitives.  The SVGs
 have the proper entities, so they should be ready to go.  We may change a
 few of these in the future (in particular, we're unhappy with using a non-
 universal music note for the audio file...), but this should get the
 system working.

 We'd also like to recommend an addition (unless this already exists, I'm
 not sure) to the clipboard API which allows activities to provide custom
 icons for clippings as they are created.  This goes hand in hand with our
 treatment of objects within the interface and within the Journal.  Many
 activities will have "sub-activity" objects which are still formally
 defined and should have an associated icon separate from the icon for the
 activity itself.  We want to embrace this idea and adding support for
 providing icons for custom types is a step in the right direction.

 Let me say a few things to clarify the idea of clippings vs. objects vs.
 activities:

 '''Clippings:''' are transient objects by nature.  They represent a piece
 of data that is independent of any particular activity id (it does ''not''
 take the id of that it was copied from) and has no version.  Clippings, of
 course, may be "upgraded" into activities by selecting the "Keep in
 Journal" action.  All data created via standard copy mechanisms should be
 represented as clippings unless specifically told not to by the activity.
 Examples are an image from a web page in Browse or some text from a story
 created in Write.

 '''Objects:''' are permanent and self-contained.  They can have associated
 metadata and can also live inside the Journal.  They will have a creator,
 but don't have an associated activity id or a history.  These will
 generally appear in the clipboard when a "whole object" is copied from
 within an activity.  Examples might be a "loop object" or an "instrument"
 in TamTam.

 '''Activity objects:''' are permanent and self-contained objects that have
 an activity id which tracks changes with versions in the Journal.  They
 may have associated metadata.  Most importantly, they have a specific
 association with an activity (the application) that they open in and share
 an icon with.  Activity objects will appear in the clipboard when a whole
 Journal entry is copied to the clipboard.

-- 
Ticket URL: <http://dev.laptop.org/ticket/2151#comment:6>
One Laptop Per Child <http://laptop.org/>