<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">On Sunday 03 May 2009 06:29:26 pm Albert Cahalan wrote: > Vamsi Krishna Davuluri writes: > > So, talking to Tomeu, we agreed that for Write and Read using > > the gtkprint would be best as both support it as a printing API. > > The focus on "Write and Read" is short sighted and may lead > to inflexible solutions. Read was selected to contain the "send to print" code because Tomeu expressed some concerns about the maintainability of that code in the Journal. Also, we agreed that going through read is good for reviewing the pdf output and saving paper on badly formatted docs. > > Now, the current plan is: > > 1) We do journal printing only, albeit, the respective > > activity opens the file. > > Eh, OK. Provide a script called /usr/bin/lpr which runs ps2pdf > or directly runs gs. This lets normal software, which is already > designed to output standard Postscript to lpr, work just fine. > After conversion, put the PDF into the journal. > > Better yet, just toss the file into the journal without conversion. > > BTW, this can also be implemented as a filter script that the > normal lpr program invokes for the default printer. The priority is on sending the docs to cups-pdf for conversion and then talking to Moodle for teacher review. It is a good idea to have the code that sends docs for printing (to Moodle, a local printer, or one discovered by avahi) in a reusable module that a /usr/bin/lpr script can use. > > Now here a cross road is presented: > > > > 1) Do we use a print dialog inside each activity that can save it as pdf, > > print or export a pdf to moodle If we are going to keep everything inside Read for now. It'll be best to have the print button only in Read. The use case we had discussed was like this: open the file in Read, if its not ps/pdf Read converts it using cups-pdf, displays it, and then you can use the print button in its toolbar. The converted file gets added as a journal entry right after conversion. The datastore already contains code to hard link identical files, so disk space usage in multiple conversions is kept to a minimum. Read could add a pointer to the pdf in the original entry's metadata as well. Adding a print dialog to every activity (e.g. Adding some gtkprint support in sugar-toolkit) should be optional for GSoC. First we should concentrate on getting entries printed, and getting teacher review right. Then we can move code around for legacy support and nice "print me" buttons. > > 2) Do we use separate buttons for each of these operations? > > > > What of the user experience? > Separate buttons provides a distinction that will be important > in some environments. Some places will want immediate printing. > > For now, the "print" button can be almost the same as the other, > but with the output PDF marked for near-term deletion. > > "Make PDF" and "Print now" seem like fine names. > I agree. Just a print button for now. The PDF will be generated on startup anyway. We can have the cups-pdf local printer in the printer selection dialog when we provide other printing methods. > > The initial plan was to make Read the global printing station, > > how do you find this idea? > > Starting up Read just to print something is not nice. Read may > even cause an out-of-memory condition. For sure, there is no need > to very slowly render a big document that doesn't even need to be > seen on the screen. This is to encourage review and to keep the code away from the Journal. The code can then be moved to Glucose. Also, distributing a modified Read for testing will be considerably easier than patching the Journal. > > the teacher checks his print page in moodle, views the file (either > > through fancy javascript or a download) and approves/disapproves > > for printing. Kennedy then logs into his moodle print page and > > checks if the job was success or not, and if he has a comment from > > his teacher. > > I can barely imagine that happening in a real classroom. Try this: > > The student brings his XO to the teacher's desk, with his work shown > on the screen. The teacher looks at the work, then lets the student > plug his XO into a printer which sits on the teacher's desk. > > > Printing resources can be very expensive for most schools, so > > the system should include a way for students to submit jobs to a > > queue and for an administrator to preview and approve or denie them. > > Tux Paint can rate limit a student's printing. For example, a setting > of 60 will be once per minute. > > Do not forget that this issue is more social than technical. In addition > to any discipline, the teacher can simply turn off the printer. This is > advisable in any case; many printers use excessive power in standby. I dont see a teacher having a printer on her desk. Most schools here in Uruguay (and I dare say in Perú) don't even have printers. If there is one, it will be where the server/administration is. And possibly locked in a cage (like we have the servers now). So that scenario is going to be priority one. Next will be of course provide local printing when a full-blown cups installation is present (which we dont want to have as a sugar dependency for now). As I also see many kids having printers in their homes. > _______________________________________________ > IAEP -- It's An Education Project (not a laptop project!) > IAEP@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep -- Andrés</body></html>