I see your point, I agree. I will do the elimination as is required,
and this time include a milestones/deadlines in my hopefully final
draft proposal.<br>
My main objective will be to send the file from the laptop through the network to the server, have the necessary code for it both sides.(and ofcourse write UIs). (I'm actually having good experience with client-server projects)<br>
<br>But if I should finish this earlier than the GSoC time span, and have sufficient time I will work on print-to-pdf, or since I intend to become a contributor, I will focus on it as an interest. I'd very well like to see myself implement this, so I will do this!<br>
<br><br>So Ben, do I write print-to-pdf in my proposal or not? and if I do, what would be the best way to do it?<br><br>
<br>
<br><br><div class="gmail_quote">On Fri, Mar 20, 2009 at 12:05 AM, Benjamin M. Schwartz <span dir="ltr"></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><div class="im"><br>
<br>
</div>Yes. There are lots of potential use cases that you might support, but<br>
you will not be able to support them all. I am suggesting that you<br>
approach this as a "critical path" problem. Do the absolute minimum<br>
amount of work necessary to achieve useful functionality in some<br>
situations, and then grow it from there.<br>
<div class="im"><br>
<br>
</div>I agree the ability to convert things to PDF would be nice to have. I<br>
even proposed it as a feature of the Journal in June:<br>
<a href="http://lists.sugarlabs.org/archive/sugar-devel/2008-June/006598.html" target="_blank">http://lists.sugarlabs.org/archive/sugar-devel/2008-June/006598.html</a><br>
<br>
What I am saying here is: conversion to PDF within Sugar is not on the<br>
critical path to working print support.<br>
<div class="im"><br>
</div><div class="im"><br>
<br>
</div>Well, that's fine. I just want to warn you against putting too many<br>
things into one Summer of Code proposal. Remember: most Summer of Code<br>
projects fail, because the project is too big and the code never reaches<br>
sufficient quality to be merged into the main codebase.<br>
<br>
- --Ben<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2.0.9 (GNU/Linux)<br>
<br>
iEYEARECAAYFAknCkFoACgkQUJT6e6HFtqQQEACcCmit2diezRw7Jsa3KW9UVuGo<br>
/msAniY1boOs/7GaXuDBnoZdjQ+7QKGQ<br>
=4kja<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br>