Marbles: Difference between revisions

Line 161:

In summer, I plan to follow the following schedule:

#Preparation phase( Time : April 25 - ~~may25~~ )

#Preparation phase( Time : April 20 - may15 )

#*gathering requirements of the project

#*getting involved with Mentor in verifying and validating the requirements.

#*~~Architectural design / Pseudo code~~.

#* Writing abstract classes for all widgets and specifications

#* Creating of canvas to support widget dragging and dropping.

#*This phase, I would be communicating with people as much as possible, getting requirements and verifying with people or community. I would also go to the pre-releases of similar softwares to get prons and cons and trying to improve in our project development.I am sure to get community support on this very interesting project.

#Coding Phase ( Time: May 25- July1 { This phase would be subdivided to different phases } )

#*'''Delieverables''' Final design and technical approach to mentors and getting reviewed by them.

#Coding Phase ( Time: May 15- July1 { This phase would be subdivided to different phases } )

#*divisions for coding timeline

#* ~~decide approach for programming~~

#* Implementation of program generator to generate the required code.

#* ~~actual coding~~, ~~testing accordingly~~

#* Creation of programming libraries such as History generation, View modifier, function associations for code generation.

#* ~~documenting code parallely~~

#* Work on intelligent sizers HBOX or VBOX to minimize the use of old technique sizers in UI creation.

#* ~~periodically sharing information~~ with ~~mentors~~ and ~~community members~~

#* '''Delieverables''' Basic UI design with dragging and dropping facility for widgets and UI application output as a python code.

~~#* This phase will include actual coding. Since I already knew the related technologies~~ and ~~familiar to sugar development process. I can devote more time to coding and thus improving the project at each phases. I will share doubts with community if occurs~~.

#Testing Phase ( Time: July7- July 25 )

#* ~~full~~ testing of system with different ~~phases~~

#* Creation of final UI output for UI builder.

#* Creation of help activity for helping students in UI building.

#* Full testing of system with different widgets.

#* use coverage analysis to know the redundance code and improving it further

#* ~~fixing bugs if any~~

#* Documentation support for widgets and UI creation.

~~#* Last minute changes before final submission~~

~~#* finish any documentation steps if left.~~

# Final Evaluation ( July 26 - END )

~~#* After coding, this is the most interesting part for me. Past I have also worked on code coverage tools~~ for ~~python~~ and ~~I really like this efficency measurement whicha also helps a lot in improving run-time~~. ~~I will go for different testing tools on program, Some tools I would like to go with~~

#* This phase is basically for porting the UI builder solution to sugar's upstream development and checking for bugs in different environment.

~~#*coverage or flegleaf tools for anlaysis. ~~

#* '''Delieverables''' full said project to sugar community.

#*I will use boost algorithms to improve run-~~time if it comes under requirement.~~

~~#Finalizing phase / Revision ( Time: from August 1 to~~ END.)

#* ~~review of code/ algorithm~~

~~#* production of coverage reports, analysis, performance etc.~~

~~#* discussions on limitations of software~~ and ~~beneficials~~.

#* ~~preparing final deployments for various systems~~.~~ ~~

~~#* Documentation stuffs would go in this phase~~

Time line: Seems very little time to do so many things, but I will try to give the best from my side.

@@ Line 161: / Line 161: @@
 In summer, I plan to follow the following schedule:
-#Preparation phase( Time : April 25 - may25 )
+#Preparation phase( Time : April 20 - may15 )
 #*gathering requirements of the project
 #*getting involved with Mentor in verifying and validating the requirements.
-#*Architectural design / Pseudo code.
+#* Writing abstract classes for all widgets and specifications
+#* Creating of canvas to support widget dragging and dropping.
 #*This phase, I would be communicating with people as much as possible, getting requirements and verifying <br> with people or community. I would also go to the pre-releases of similar softwares to get prons and cons and trying to improve in our project <br> development.I am sure to get community support on this very interesting project.
-#Coding Phase ( Time: May 25- July1 { This phase would be subdivided to different phases } )
+#*'''Delieverables''' Final design and technical approach to mentors and getting reviewed by them.
+#Coding Phase ( Time: May 15- July1 { This phase would be subdivided to different phases } )
 #*divisions for coding timeline
-#* decide approach for programming
+#* Implementation of program generator to generate the required code.
-#* actual coding, testing accordingly
+#* Creation of programming libraries such as History generation, View modifier, function associations for code generation.
-#* documenting code parallely
+#* Work on intelligent sizers HBOX or VBOX to minimize the use of old technique sizers in UI creation.
-#* periodically sharing information with mentors and community members
+#* '''Delieverables''' Basic UI design with dragging and dropping facility for widgets and UI application output as a python code.
-#* This phase will include actual coding. Since I already knew the related technologies and familiar to sugar development process. I can devote<br> more time to coding and thus improving the project at each phases. I will share doubts with community if occurs.
 #Testing Phase ( Time: July7- July 25 )
-#* full testing of system with different phases
+#* Creation of final UI output for UI builder.
+#* Creation of help activity for helping students in UI building.
+#* Full testing of system with different widgets.
 #* use coverage analysis to know the redundance code and improving it further
-#* fixing bugs if any
+#* Documentation support for widgets and UI creation.
-#* Last minute changes before final submission
-#* finish any documentation steps if left.
+# Final Evaluation ( July 26 - END )
-#* After coding, this is the most interesting part for me. Past I have also worked on code coverage tools for python and I really like this <br> efficency measurement whicha also helps a lot in improving run-time. I will go for different testing tools on program, Some tools I would like<br> to go with
+#* This phase is basically for porting the UI builder solution to sugar's upstream development and checking for bugs in different environment.
-#*coverage or flegleaf tools for anlaysis.<br>
+#* '''Delieverables''' full said project to sugar community.
-#*I will use boost algorithms to improve run-time if it comes under requirement.
-#Finalizing phase / Revision ( Time: from August 1 to END.)
-#* review of code/ algorithm
-#* production of coverage reports, analysis, performance etc.
-#* discussions on limitations of software and beneficials.
-#* preparing final deployments for various systems.<br>
-#* Documentation stuffs would go in this phase
 Time line: Seems very little time to do so many things, but I will try to give the best from my side.