Changes

no edit summary
Line 47: Line 47:  
##*For the teaching of speech sounds and intonation, I will consider using some open-source TTS softwares, for example, espeak the Speech Synthesizer. The best choice might be to use sound files of words and sentences recorded by real human beings. This may be okay for widely used languages like English, but for other smaller languages this could be almost impossible. This may also raise license problems. However, I will let the activity have the potential to add sound files of corresponding entries for some certain languages when coding it.
 
##*For the teaching of speech sounds and intonation, I will consider using some open-source TTS softwares, for example, espeak the Speech Synthesizer. The best choice might be to use sound files of words and sentences recorded by real human beings. This may be okay for widely used languages like English, but for other smaller languages this could be almost impossible. This may also raise license problems. However, I will let the activity have the potential to add sound files of corresponding entries for some certain languages when coding it.
 
##*For the re-distribution of own-made entries, an import and export function will be included so that those changes can be made from the db of this activity on a certain XO into a package to be shared easily with others. If there is any time left at the end of this summer or maybe in the near future, I will design a website to check and store well formed packages of own-added entries so that users from worldwide can download them and import to their own XOs(the reason why I do not want to implement this right now is the consideration that there may be difficulties for most of the XO users to have an Internet access)
 
##*For the re-distribution of own-made entries, an import and export function will be included so that those changes can be made from the db of this activity on a certain XO into a package to be shared easily with others. If there is any time left at the end of this summer or maybe in the near future, I will design a website to check and store well formed packages of own-added entries so that users from worldwide can download them and import to their own XOs(the reason why I do not want to implement this right now is the consideration that there may be difficulties for most of the XO users to have an Internet access)
# 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.
+
# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10(should be May 24 - August 9 this year??); 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 (should be July 12-16 this year??)); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
 
#*Before the summer begins: Finish a draft for UI design. Consult language professors for proper learning methods and think about an approach to implement it. Set required environment and build a HelloWorld activity.
 
#*Before the summer begins: Finish a draft for UI design. Consult language professors for proper learning methods and think about an approach to implement it. Set required environment and build a HelloWorld activity.
 
#*Week 1:Discuss with mentor and have a total plan for the whole project. Decide and clarify all key details to implement the project.  
 
#*Week 1:Discuss with mentor and have a total plan for the whole project. Decide and clarify all key details to implement the project.  
Line 77: Line 77:  
#*Discuss it with my fellows
 
#*Discuss it with my fellows
 
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?  
 
# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?  
#*I will report my progress to my mentor weekly, and post the progress report to the mailing list at the same time. I will also write blog posts( URL: http://blog.csdn.net/zyyyhebe ) to record those problems, questions and my own experience of taking part in the course of the project.  
+
#*I will report my progress to my mentor weekly, and post the progress report to the mailing list at the same time. I will also write blog posts( URL: http://saturntoad.blogspot.com/ ) to record those problems, questions and my own experience of taking part in the course of the project.  
    
====Miscellaneous====
 
====Miscellaneous====
56

edits