273
edits
Changes
Jump to navigation
Jump to search
Line 344:
Line 344: + + + + + + + + + + + +
Development Team/Project Ideas (view source)
Revision as of 12:37, 1 April 2009
, 12:37, 1 April 2009→Homework turn-in
==== Homework turn-in ====<!-- keep that title if you move the entry, there are inbound links. -->
==== Homework turn-in ====<!-- keep that title if you move the entry, there are inbound links. -->
* "Homework turn-in" support: Certain metadata on a file causes new versions to be pushed out over the net (via SMTP, rss, or other; note that Moodle already has [http://docs.moodle.org/en/Email_processing support] for routing from special email addresses to a "location"). No new UI in Sugar, and a trivial amount of changes to Moodle.
* "Homework turn-in" support: Certain metadata on a file causes new versions to be pushed out over the net (via SMTP, rss, or other; note that Moodle already has [http://docs.moodle.org/en/Email_processing support] for routing from special email addresses to a "location"). No new UI in Sugar, and a trivial amount of changes to Moodle.
[10:18] <homunq> If you'd rather something with PHP in it, I'd recommend the homework turn-in one. That one's really poorly documented. Basically, the steps are:
[10:18] <homunq> 1. figure out a plan for including sugar metadata in the html download links from moodle
[10:19] <homunq> 2. when downloading an assignment, put metadata of "send this back to adress xxx in server"
[10:20] <homunq> 3. When saving new, worked-on versions of the assignment, mark them for upload to the server
[10:22] <homunq> 4. when you see the server, and the homework deadline is not past, the sugar core automatically uploads the latest version. You could decide to use SMTP upload (already somewhat implemented in moodle) or something else like rss or REST or whatever.
[10:22] <homunq> any questions, happy to clarify.
==== Research projects: unpolished code ====
==== Research projects: unpolished code ====