[Sugar-devel] [IAEP] The User experience/interface for Printing

[Albert Cahalan]

On Mon, May 4, 2009 at 12:48 PM, Sascha Silbe
<sascha-ml-ui-sugar-iaep at silbe.org> wrote:
> On Mon, May 04, 2009 at 04:44:33AM -0400, Albert Cahalan wrote:
>
>> Sending the docs to cups-pdf for conversion and then talking to Moodle
>> for teacher review can be done via /usr/bin/lpr,
>
> But that would sidestep the Journal and prevent review of the actual output
> (i.e. what it looks like on paper, not on screen - that can be vastly
> different!) before printing.

It wouldn't have to. That could be how all activities put print
jobs into the Journal.

You are essentially using the Journal as client-side print queue,
and Moodle as server-side print queue. You might as well use
the normal (highly compatible) way to submit to a print queue.

FYI, preview isn't going to be perfect anyway. PDF code can
ask the printer for exact dimensions; this info is unavailable
to the Read activity. It can be used for landscape/portrait rotation,
scaling, or whatever. Some enterprising kid may even concoct
a PDF that looks nice in Read, but offensive on paper. Getting
your teacher to approve printing goatse is priceless.