143
edits
Changes
Jump to navigation
Jump to search
Line 64:
Line 64: + + Line 72:
Line 74: − +
Summer of Code/2009/Print Support (view source)
Revision as of 01:43, 27 March 2009
, 01:43, 27 March 2009→About your project
:'''2)''' The print button on click, prints the screen objects into PDF format. This will be turned into a nice sugar.print API.
:'''2)''' The print button on click, prints the screen objects into PDF format. This will be turned into a nice sugar.print API.
: (The first two steps would essentially mean a Save as PDF hack)
:'''3)''' This is an interesting step, we have two implementations here: 1) the XO case 2) No XO case
:'''3)''' This is an interesting step, we have two implementations here: 1) the XO case 2) No XO case
:'''4)''' Through moodle the teacher will have a page displaying the contents of the print datastore along with user names attached, and he/she will be able to download them to his remote system, and check them and approve them for printing if he/she wishes. After his/her approval or disapproval (that is a delete along with an option why) the information is held in the datastore, and the user can view it in the form of history transactions pertaining to his id, and teacher can view a finite list of previous transactions pertaining to all.
:'''4)''' Through moodle the teacher will have a page displaying the contents of the print datastore along with user names attached, and he/she will be able to download them to his remote system, and check them and approve them for printing if he/she wishes. After his/her approval or disapproval (that is a delete along with an option why) the information is held in the datastore, and the user can view it in the form of history transactions pertaining to his id, and teacher can view a finite list of previous transactions pertaining to all.
: (These steps would mean a) moodle print queue, web interface b) (3) a cp activity that bypasses the need to use (2) if you're in Sugar)
:'''In-Depth analysis:'''
:'''In-Depth analysis:'''