#4165 BLOC First D: Write must expose UI to allow specifying output format...

[Zarro Boogs per Child]

#4165: Write must expose UI to allow specifying output format...
-------------------------------+--------------------------------------------
  Reporter:  jg                |       Owner:  uwog                  
      Type:  enhancement       |      Status:  new                   
  Priority:  blocker           |   Milestone:  First Deployment, V1.0
 Component:  interface-design  |     Version:                        
Resolution:                    |    Keywords:                        
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by Eben):

  * owner:  Eben => uwog


Comment:

 I think we'll use "Keep a Copy" for now.  We can easily change the text on
 the menu item later.

 I think that, for 1.0, it's not clear that creating a new icon is an easy
 approach.  Appending the format (or extension) to the title is simpler to
 do, though icons would be helpful for sure.  I think that it's always
 important that the icon match the mime-type of the object, assuming that
 there is one defined on the system for it.

 Perhaps what this means is that, when activities support exporting to
 other formats, they themselves provide the icons for those formats in
 their bundles, so the system can visualize them appropriately.  This is
 kind of a type/creator type argument, where the tuple of (mime-type,
 creator) would determine which icon gets applied.  If the tuple is instead
 (mime-type, null) then the Journal will choose an icon for that mime-type
 from any of the activities which claim to support it, and if there are
 none, it will fall back to using a generic icon (as for the clippings).
 This is the correct approach to identifying objects of various formats
 iconically, but again, we may just want to append the format or extension
 for now because it has much lower overhead at this point.

 For clarification of Kim's comment above, the instance will be ''new'',
 meaning that it will have a new Activity ID (and therefore no associated
 sharing scope or history), and no metadata (unless supplied directly by
 the activity, upon export, of course).

-- 
Ticket URL: <https://dev.laptop.org/ticket/4165#comment:10>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system