#3741 NORM First D: Browse global bookmarking/sharing in session

[Zarro Boogs per Child]

#3741: Browse global bookmarking/sharing in session
-------------------------------+--------------------------------------------
  Reporter:  erikos            |       Owner:  Eben                  
      Type:  defect            |      Status:  new                   
  Priority:  normal            |   Milestone:  First Deployment, V1.0
 Component:  interface-design  |     Version:                        
Resolution:                    |    Keywords:                        
  Verified:  0                 |  
-------------------------------+--------------------------------------------

Comment(by Eben):

 I'll reiterate my view of FRS goals.

 Session bookmarks:

  - stored with the session's entry in Journal
  - immediately shared with activity participants
  - should be draggable object, treated as a URL (not as image)
  - actions: remove, copy, star (global bookmark)

 Global bookmarks:

  - stores page for offline viewing (only top level)
  - When the page is visited, the stored version is displayed, along with
 an alert indicating how old the page is and the option to refresh it.

 Questions:

  - Do global bookmarks really appear as an entry in the Journal, or are
 they a "property of the URL" that is stored hidden, but presented anytime
 the URL is later visited?
  - Can global bookmarks truly span all Browse sessions, so that stored
 pages are shown for a given URL regardless of what session it was created
 in.
  - If we do create Journal entries for global bookmarks, what happens when
 you resume one directly?  I think the beset option is to treat it as a new
 Browse session, independent of the session it was created in.
  - What do we do about "rich" content in offline viewing?  Can we use CSS
 to put in placeholders for movies/audio that would take too much room to
 store?  Can we use CSS to style the links so that it's clear they aren't
 clickable (when viewing offline)?

 Please give some feedback about these questions so I can know what's
 possible, and how to break this up into tickets for implementation.
 Thanks!

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