<br>> Cookie + HTTP POST to a defined URL would work well.<br><br>oh, okay, so I think I should follow these roots.<br><br>>Apologies for not being able to help more this week.<br>
<br>np<br><br>>You'll need to read the code in auth/olpcxs/auth.php -- note that<br>
>_that_ code does a lot of stuff. You don't need to login the user,<br>
>only to identify the right account and put the print request in the<br>
>appropriate queue.<br>
<br>I think i've been working on the wrong moodle, I've been working <br>with the default moodle installation found at <a href="http://moodle.org">moodle.org</a>. How do I <br>get everything XS-Moodle specific? A quick google search points <br>
me to this:<br><a href="http://docs.moodle.org/en/OLPC_XS_installation">http://docs.moodle.org/en/OLPC_XS_installation</a><br>Should I proceed with that?<br><br>>I'd encourage handling the queue from moodle's cron. See admin/cron.php<br>
<br>right, this seems to be exact thing i'd need for dynamic clean-ups.<br>Anything dynamic like a queue.<br><br>>I'm not sure what your UIs look on the Sugar side,<br>
<br>the sugar side, my plan morphed into a completely new Print activity<br>The print activity can read any sugar supported mime and convert it<br>to pdf, and send to moodle etc through a new toolbar.<br>Thats about it.<br>
<br>>but we could<br>
>leverage your work into being a "publish into moodle and/or print"<br>
>action. "Push to moodle where everyone can see it and (if there's a<br>
>printer) the teacher gets and extra button to print".<br><br>You mean the teacher gets a print button within sugar or within<br> moodle?<br><br>>In that case, you will want to add a new tab to the 'user page'. You<br>
>can see how I've added a 'backup' tab and an 'alias' tab.<br>
<br>>3 - it may make sense to add a small activity module for this that<br>
>shows everything that the teacher ok'd to print (so 'printing' is also<br>
>publishing in the online environment for the whole group). Given that<br>
>all of this interaction is scoped to a group (the course participants<br>
>in moodle parlance) it makes sense.<br>
<br>
hmm, I will have to look into how to do this within the scope of a group.<br>also, on my default moodle installation a student can't see the <br>'users page' (i'd guess i can set permissions on that somewhere)<br>
(or)<br>could it be something under courses? if so, as a new module?<br>which loads itself?<br><br>Hope, you won't mind the newbie questions, i've done everything <br>on moodle almost by myself, I will definitely be lacking much.<br>
<br>Thanks,<br>Vamsi<br>