#4291 NORM Never A: Icon for the journal items

Zarro Boogs per Child bugtracker at laptop.org
Thu Oct 18 20:40:30 EDT 2007


#4291: Icon for the journal items
-------------------------------+--------------------------------------------
  Reporter:  marco             |       Owner:  Eben          
      Type:  defect            |      Status:  new           
  Priority:  normal            |   Milestone:  Never Assigned
 Component:  interface-design  |     Version:                
Resolution:                    |    Keywords:                
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by HoboPrimate):

 * cc: HoboPrimate (added)


Comment:

 Replying to [comment:5 Eben]:
 > Replying to [comment:3 HoboPrimate]:
 > > I agree with Bert: If you get a file which isn't a Sugar activity, it
 is an "object" which hasn't been "acted" with yet by any XO user.
 > > After opening it _with_ an activity, then it belongs _to that_
 activity, replacing the original icon.
 >
 > On the other hand, though, say you download a .pdf from the web.  By
 default, that .pdf is going to open with Read.  For all intents and
 purposes, that .pdf is a book.  Wouldn't it be quite clear to indicate
 this directly in the UI, by simply identifying that object as a book,
 since that how it will act upon resuming?  there is no way to open it with
 read without making the association and changing the icon, so why create a
 temporary state where it feels "generic" just to override that as soon as
 it's read?

 Ah, I see your point. Then, how would an icon for an SVG file behave?
 Initially use the icon of a future picture viewer activity, but if opened
 with a future svg editor, switch to that activity icon? Also, remember
 that there are pdf editors, and we can assume that one day they will come
 to Sugar as well, which poses the same question.

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



More information about the Bugs mailing list