>No. You'll want to base your work on >- testing against the OLPC XS - grab the recent 0.6dev2 install image >from http://xs-dev.laptop.org/xs/other/ >- the 'moodle' git tree at http://dev.laptop.org/git >there is a good post on how to test (and develop) moodle on an XS in >the 'server-devel' archives. I normally search the archives with a >site-scoped search like > http://www.google.com/search?q=site%3Alists.laptop.org%2Fpipermail%2Fserver-devel+testing+moodle
the latest dev releases! Okay, onto them the first thing in the morning, and yep i definitely intend to dig up server-devel archives. >So it's no longer an extension of the Journal? I've explored the pycups api well, and I found out that with minimal effort I can create print queues, and do printer sharing + wifi printing. (The fallback strategy) putting all this within an extension is not really perceivable Having a print activity ensures that we have a much flexible way to implement everything in the no xs case. http://materializingsweetness.wordpress.com/2009/06/03/print-metamorphoses/ >Within Moodle. There are two 'views' that I suspect are interesting >1 - the user page, in its 'print queue' tab >2 - a 'course print queue' page in a module, showing all the new / >outstanding documents from all course members >#2 makes me think that this is a more powerful thing than just 'printing'. I will have to explore these options myself, but of course within a course would definitely make me worry less about the greater integration between the group, user and teacher. by integration I mean, the whole having teacher evaluate and such. >No problem. Next week my life will be much calmer, and I'll be more >than happy to have a chat with you. >Apologies again that I'm not more available, Thanks Martin! and np! I'm very happy that we could have the discussion here!
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel