It's entirely unclear what this project has morphed to. Tomeu, what use is uploading arbitrary journal entries to Moodle? I thought creating pdf output in sugar and enabling uploading of the pdf to Moodle was the point of this project. That is useful in two ways. First, it is a path to assignment turn-in or printing either through Moodle or by other transports to a system configured to print pdfs. It also allows a student to review the printer-ready output to decide if it is worth getting hard copy. <br> <br><div class="gmail_quote">On Tue, Apr 21, 2009 at 9:36 AM, Tomeu Vizoso <span dir="ltr"><<a href="mailto:tomeu@sugarlabs.org">tomeu@sugarlabs.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Tue, Apr 21, 2009 at 18:29, Benjamin M. Schwartz<br> <div class="im"><<a href="mailto:bmschwar@fas.harvard.edu">bmschwar@fas.harvard.edu</a>> wrote:<br> </div><div class="im">> -----BEGIN PGP SIGNED MESSAGE-----<br> > Hash: SHA1<br> ><br> > Tomeu Vizoso wrote:<br> >> Printing is not limited to uploading files to moodle, we provide both<br> >> local and server printing and users will use whatever works in their<br> >> environment.<br> ><br> > I think this is too much for one Summer of Code project. That's why I<br> > have been recommending that we forget about local printing for now.<br> <br> </div>I would actually be happy if we just implemented sending journal<br> entries to the print queue and the moodle module. Print to pdf has<br> several important use cases and I would like to see it implemented for<br> 0.86 for at least Write and Browse, but I don't think it needs to be<br> part of this GSoC.<br> <div class="im"><br> > Anyway, on a purely technical level I think we have reached agreement. (I<br> > do wonder whether the Moodle print queue should also support acting as a<br> > standard print server, so that standard desktops can print into the Moodle<br> > approval queue, but that's a detail.)<br> <br> </div>Yeah, I would prefer if we use simple file upload at first because it<br> works already.<br> <br> There's lots of fun stuff to do in this area, but what gives most<br> value to the user is quite straightforward. We should aim to leave the<br> complicated stuff for the end, as extras, and focus on delivering what<br> matters most first<br> <br> Regards,<br> <font color="#888888"><br> Tomeu<br> </font><div><div></div><div class="h5"><br> > - --Ben<br> > -----BEGIN PGP SIGNATURE-----<br> > Version: GnuPG v2.0.10 (GNU/Linux)<br> ><br> > iEYEARECAAYFAknt9FQACgkQUJT6e6HFtqTjmwCfdM831aiEMbpRiJNQLX8Bf2FY<br> > OH8AniCGOPuqgY/GlR+V2io6+/NyiTnl<br> > =KI8s<br> > -----END PGP SIGNATURE-----<br> ><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> </div></div></blockquote></div><br><br clear="all"><br>-- <br>"It is difficult to get a man to understand something, when his salary depends upon his not understanding it." -- Upton Sinclair<br>