[Sugar-devel] Print Support proposal (need input) Beta

[Eben Eliason]

2009/3/19 Vamsi Krishna Davuluri <vamsi.davuluri at gmail.com>:
> Thanks a bunch for replying, Ben!
>
> But as tomeu had pointed out, what of the schools without servers? In that
> case printing would have a need to be done from the laptops themselves.

Everyone knows that I'm always on the side of making absolutely
everything work without a server, when possible.  However, I find it
somewhat unlikely that a school without a server will happen to have a
printer, anyway.

I have to agree that a print to pdf function could be useful, though,
especially since it means that every activity can create output that
can be transferred elsewhere (via email, USB drive, etc.) for
printing.  This provides a method, albeit indirect, for G1G1 users to
print from various activities whose file formats are only understood
by a Sugar activity.

It also means that there would always be a way to send the artifact of
some activity to another XO, without having to send the raw file
(which would require the other XO to have that activity, or another
which supports the format, installed).

- Eben


> And personally I would definitely prefer a client-server approach as it
> simplifies many things. But shouldn't the print-to-pdf be a good addition?
> In my opinion that would at least give the kids something through which they
> can display their presentations to the real world.
>
> one question, the school server will be running on a normal distro, or
> sugar?
>
> I believe pdf printing should be present on the laptops at least, so I will
> push it as an end derivable.
>
> On Thu, Mar 19, 2009 at 11:12 PM, Benjamin M. Schwartz
> <bmschwar at fas.harvard.edu> wrote:
>>
>> Specifically, there are at least 3 different use cases you may choose to
>> support:
>>
>> 1. USB printer connected directly to the Sugar machine.
>>
>> 2. Networked printer, no server. Sugar prints directly over the network.
>>
>> 3. All printing passes through a server.
>>   a. networked printer with restricted access
>>   b. USB printer connected directly the server
>>      and also
>>   1. the server may print every submission immediately
>>   2. apply automatic quotas, or
>>   3. require manual approval
>>
>
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>