Ben, thanks! yep, CUPS would need 62 MB of estimated disk space after installation according to this site. <a href="http://www.linuxfromscratch.org/blfs/view/svn/pst/cups.html">http://www.linuxfromscratch.org/blfs/view/svn/pst/cups.html</a> can we do a thing, if the user is in need of print-to-pdf (or other future prospects offered by CUPS), couldn't we write a script which installs it on the fly?(has it been done before for xo laptops? install on fly that is? is it feasible?) and the functionalities added like UIs would be enabled accordingly. <div class="gmail_quote">On Fri, Mar 20, 2009 at 12:50 AM, <<a href="mailto:pgf@laptop.org">pgf@laptop.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="im">vamsi krishna davuluri wrote: > 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. > 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) </div>i've only started reading this thread in the middle, so forgive me if i have this wrong: are you planning on installing all of CUPS on every laptop? if so, that seems very expensive from a disk space standpoint. (every megabyte counts on the XO.) the client code should be as lightweight as possible, even if it limits flexibility. (if someone, or some school, needs much greater flexibility, then perhaps an alternate printing client can be installed -- there's no need for one printing client to serve all needs. paul <div><div></div><div class="h5"> > > 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! > > > 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? > > > > > On Fri, Mar 20, 2009 at 12:05 AM, Benjamin M. Schwartz > > > > > > > > > Yes. There are lots of potential use cases that you might support, but > > you will not be able to support them all. I am suggesting that you > > approach this as a "critical path" problem. Do the absolute minimum > > amount of work necessary to achieve useful functionality in some > > situations, and then grow it from there. > > > > > > I agree the ability to convert things to PDF would be nice to have. I > > even proposed it as a feature of the Journal in June: > > <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> > > > > What I am saying here is: conversion to PDF within Sugar is not on the > > critical path to working print support. > > > > > > > > Well, that's fine. I just want to warn you against putting too many > > things into one Summer of Code proposal. Remember: most Summer of Code > > projects fail, because the project is too big and the code never reaches > > sufficient quality to be merged into the main codebase. > > > > - --Ben > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v2.0.9 (GNU/Linux) > > > > iEYEARECAAYFAknCkFoACgkQUJT6e6HFtqQQEACcCmit2diezRw7Jsa3KW9UVuGo > > /msAniY1boOs/7GaXuDBnoZdjQ+7QKGQ > > =4kja > > -----END PGP SIGNATURE----- > > </div></div> > part 2 text/plain 153 <div class="im"> > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </div>=--------------------- paul fox, <a href="mailto:pgf@laptop.org">pgf@laptop.org</a> <div><div></div><div class="h5">_______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </div></div></blockquote></div>