Not only printing. Still in places were there are connectivity, many times is so bad, than having the possibility of enable anything similar to offline navigation is great. And many kids do not have connectivity in their houses too. Gonzalo <div class="gmail_quote">On Fri, Jun 3, 2011 at 12:02 PM, Sridhar Dhanapalan <<a href="mailto:sridhar@laptop.org.au">sridhar@laptop.org.au</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> We get asked about printing all the time. While I understand why this is a deliberate omission in Sugar, it can be nonetheless annoying for teachers. This approach seems to be a good compromise. Sridhar <div><div></div><div class="h5"> On 30 May 2011 00:04, Sascha Silbe <<a href="mailto:silbe@activitycentral.com">silbe@activitycentral.com</a>> wrote: > Requests for print functionality in Sugar have been voiced repeatedly, > including during EduJam 2011. Adding support to Browse for exporting the > currently loaded document as PDF is a major step in that direction since > Browse can render (and thus export as PDF) a variety of file formats, > including HTML, bitmap graphics (PNG, JPEG) and SVG. > > The Portable Document Format (PDF) is designed to preserve the layout of the > document and thus is poorly suited for applications like "offline" reading of > web pages (there is no re-flowing to suit the dimensions of the screen). For > these tasks there are better solutions like wwwoffle [1], Webified [2] or > creating a derivative of the Help activity [3]. > > Direct print support has been deliberately omitted. Anything that gets > exported from the learners system should be recorded and preserved in the > Journal. Exporting PDFs from individual activities to the Journal and > implementing print support in a single, specially designed activity that > operates on the PDFs not only ensures that all exports are recorded in > the exact form they left the computer, but also relieves activity authors > from the need to provide print support in their activity. The user won't get > confused by multiple different ways to configure printing from within the > various activities. > > Because PDF is a standard interchange format, this also enables more (and > better!) ways of sharing documents (while preserving their exact form) than > printing. > > Sascha Silbe (2): > Generalise GetSourceListener to SaveListener > Add support for exporting ("printing") to PDF > > browser.py | 92 +++++++++++++++++++++++++++++++++++++++++++++++++++----- > webtoolbar.py | 10 ++++++ > 2 files changed, 93 insertions(+), 9 deletions(-) > > [1] <a href="http://www.gedanken.demon.co.uk/wwwoffle/" target="_blank">http://www.gedanken.demon.co.uk/wwwoffle/</a> > [2] <a href="http://wiki.sugarlabs.org/go/Webified" target="_blank">http://wiki.sugarlabs.org/go/Webified</a> > [3] <a href="http://activities.sugarlabs.org/en-US/sugar/addon/4051" target="_blank">http://activities.sugarlabs.org/en-US/sugar/addon/4051</a> > -- > 1.7.2.5 > > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </div></div></blockquote></div>