[Sugar-devel] [DESIGN] Browse PDF handling

[Manuel Quiñones]

I'm proposing, for the new and fresh Browse wearing WebKit, the
following behaviour when clicking on a link to a PDF:

- the PDF is shown in a new tab, next to the current
- basic document navigation is provided to the user
- as well, a button to save to Journal is provided

Using the save to Journal button, the kid can now read the PDF
starting the full-featured Read activity.

This behaviour is similar to what Safari does, and I think it fits
Sugar user interface better than other approaches we where thinking
before, like start Read directly, which provokes an interruptive
activity switch.  Also this way, an entry in the Journal is made only
if the user ask for it, and allows a quick read of the PDF then you
can decide on storing.

If we go for this, some design decisions should be taken:

- How can we provide basic PDF navigation?
  1. Overload Browse buttons? This are: View zoom-in, zoom-out, Edit
copy, paste, Go back page, go forward page buttons.
  2. Add a special toolbar for PDF, add Save to Journal option in that toolbar

- Where to append Save to Journal button?
  1. In the activity toolbar, like other activities have.  This
matches well basic navigation 1 above.
  2. In a special toolbar.  This matches basic navigation 2 above.

For 1, I fear that may confuse users and may complicate code.  For 2,
we can take Safari as reference.  It adds an overlay horizontally
centered near the bottom of the screen [1].  We can do this with the
new widget GtkOverlay [2].

Am I overlooking something?  Comments?

Credits go to Simon for the investigation :-)

[1] http://dev.laptop.org/~erikos/designs/safari_inline.png
[2] http://developer.gnome.org/gtk3/3.3/GtkOverlay.html
-- 
.. manuq ..