Summer of Code/2009/Print Support: Difference between revisions

Line 114:

:for printing

:'''4 What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

:'''April 20th to May 26th:'''

* Research the sugar API extensively

* Write sample D-BUS communication programs

* Hack into moodle code, and create purposeful hacks (modifying the limits for plugin in consideration, and such)

* Talk with the design team and produce prototype interface designs

* Look into moodle APIs

* Focus on the bare essential dependencies required to get the job done

:'''Milestone 1'''

:'''Week 1 : '''

:Start writing code which actually configures the network printer server side, and on the clients side.

:'''week 2 : '''

:Write code which prints to local configured pdf clients side, and start working on UIs for this and integrating into sugar

''' week 3 '''

:Finish working on UIs, add buttons to each activity, and append a new printer module(api) to Sugar packages (api)

Mile stone 1 result:''See to it that the code can print to a local printer, a network printer and the pdf virtual printer. But ofcourse apart from pdf printing others will be disabled. Get mentor and community feedback.

'''Milestone 2'''

'''week 4 '''

:Start working on moodle, build a 'For printing' page plugin, see to it that it accepts files from client side, and stores them in moodle's webfolder (datastore)

'''week 5'''

:Add interfaces for teacher logins and student logins, and write code to perform operations depending on the users/teachers interactions.

: And start working on a php script for shell commands to directly print to the network printer.

'''week 6'''

:Finish working on the logical part and start working on creating a nice html layout for the page, get feedback and make corrections accordingly.

'''week 7'''

:Test code on a server with a printer, and test if everything works, get mentor and community feedback, and if any integration bugs remain, drill on them.

:Milestone 2:'' It would be to finish the moodle plugin, and see to it that printing can be done through it''

====You and the community====

@@ Line 114: / Line 114: @@
 :for printing
+:'''4 What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''
+:'''April 20th to May 26th:'''
+* Research the sugar API extensively
+* Write sample D-BUS communication programs
+* Hack into moodle code, and create purposeful hacks (modifying the limits for plugin in consideration, and such)
+* Talk with the design team and produce prototype interface designs
+* Look into moodle APIs
+* Focus on the bare essential dependencies required to get the job done
+:'''Milestone 1'''
+:'''Week 1 : '''
+:Start writing code which actually configures the network printer server side, and on the clients side.
+:'''week 2 : '''
+:Write code which prints to local configured pdf clients side, and start working on UIs for this and integrating into sugar
+''' week 3 '''
+:Finish working on UIs, add buttons to each activity, and append a new printer module(api) to Sugar packages (api)
+Mile stone 1 result:''See to it that the code can print to a local printer, a network printer and the pdf virtual printer. But ofcourse apart from pdf printing others will be disabled. Get mentor and community feedback.
+'''Milestone 2'''
+'''week 4 '''
+:Start working on moodle, build a 'For printing' page plugin, see to it that it accepts files from client side, and stores them in moodle's webfolder (datastore)
+'''week 5'''
+:Add interfaces for teacher logins and student logins, and write code to perform operations depending on the users/teachers interactions.
+: And start working on a php script for shell commands to directly print to the network printer.
+'''week 6'''
+:Finish working on the logical part and start working on creating a nice html layout for the page, get feedback and make corrections accordingly.
+'''week 7'''
+:Test code on a server with a printer, and test if everything works, get mentor and community feedback, and if any integration bugs remain, drill on them.
+:Milestone 2:'' It would be to finish the moodle plugin, and see to it that printing can be done through it''
 ====You and the community====