<p>Something to watch out for is that many websites already like to open a separate tab or window for PDF documents, sometimes via Javascript and sometimes by setting the target frame/window. </p>
<p>Sometimes these sites directly link the PDF file; other times they attempt to include it inline. </p>
<p>If we intend to support tabbed browsing, these behaviors could result in an "unused" tab being opened besides the one showing the document. </p>
<div class="gmail_quote">On Feb 2, 2012 7:00 AM, "Manuel Quiñones" <<a href="mailto:manuq@laptop.org">manuq@laptop.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm proposing, for the new and fresh Browse wearing WebKit, the<br>
following behaviour when clicking on a link to a PDF:<br>
<br>
- the PDF is shown in a new tab, next to the current<br>
- basic document navigation is provided to the user<br>
- as well, a button to save to Journal is provided<br>
<br>
Using the save to Journal button, the kid can now read the PDF<br>
starting the full-featured Read activity.<br>
<br>
This behaviour is similar to what Safari does, and I think it fits<br>
Sugar user interface better than other approaches we where thinking<br>
before, like start Read directly, which provokes an interruptive<br>
activity switch. Also this way, an entry in the Journal is made only<br>
if the user ask for it, and allows a quick read of the PDF then you<br>
can decide on storing.<br>
<br>
If we go for this, some design decisions should be taken:<br>
<br>
- How can we provide basic PDF navigation?<br>
1. Overload Browse buttons? This are: View zoom-in, zoom-out, Edit<br>
copy, paste, Go back page, go forward page buttons.<br>
2. Add a special toolbar for PDF, add Save to Journal option in that toolbar<br>
<br>
- Where to append Save to Journal button?<br>
1. In the activity toolbar, like other activities have. This<br>
matches well basic navigation 1 above.<br>
2. In a special toolbar. This matches basic navigation 2 above.<br>
<br>
For 1, I fear that may confuse users and may complicate code. For 2,<br>
we can take Safari as reference. It adds an overlay horizontally<br>
centered near the bottom of the screen [1]. We can do this with the<br>
new widget GtkOverlay [2].<br>
<br>
Am I overlooking something? Comments?<br>
<br>
Credits go to Simon for the investigation :-)<br>
<br>
[1] <a href="http://dev.laptop.org/~erikos/designs/safari_inline.png" target="_blank">http://dev.laptop.org/~erikos/designs/safari_inline.png</a><br>
[2] <a href="http://developer.gnome.org/gtk3/3.3/GtkOverlay.html" target="_blank">http://developer.gnome.org/gtk3/3.3/GtkOverlay.html</a><br>
--<br>
.. manuq ..<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</blockquote></div>