In the past week, I have done following things:
1) Talked with my mentor about the length of name column, and I decide to use 1024 as length of name column temporarily in develop phrase.
2) I have completed the optimization for HibernateUtil class, according to the comment of ticket#372. And I also send a request in comment of this ticket to ask other devs help me to review this class together.
3) I have nearly completed half of current metadata's localization support. But the left other metadata, such as Privilege, Role, RelationShip, may be need to be dealt with specially.
The next things I need to do are follow:
1) Discuss with my mentor about how to support localization for those special metadata, such as Privilege, Role, etc
2) Complete the left metadata's localization support
3) Prepare for my second project presentation
2010-06-23
My GSoC project's progress report - 23/06/2010
I am sorry that I have posted last week's progress report till today. Because my computer encounter a small problem and lost network about a few days.
In the past week, I have done following things:
1) I have attended the last week's code review call at June, 14. And address out all comments from call and other devs' personal comments.
2) I have made a part of code changes, according to the notes from code review. But here is remainly two questions need to resolve: decide on length of 'name' column, and optimization for HibernateUtil class.
3) I also resolved the previous exception "Found shared reference to collection ...". It's because that I haven't completely support all metadata's localization, this exception won't happen after I completely support all metadata's localization.
Oh, In the past week, I haven't do much work. So in the following days, I should speed up. And I also need to preserve a few time to prepare my second project presentation in July, 8.
The next things I need to do are follow:
1) Decide on the length of 'name' column
2) Complete the optimization for HibernateUtil class
3) Begin to support other metadata's localization
In the past week, I have done following things:
1) I have attended the last week's code review call at June, 14. And address out all comments from call and other devs' personal comments.
2) I have made a part of code changes, according to the notes from code review. But here is remainly two questions need to resolve: decide on length of 'name' column, and optimization for HibernateUtil class.
3) I also resolved the previous exception "Found shared reference to collection ...". It's because that I haven't completely support all metadata's localization, this exception won't happen after I completely support all metadata's localization.
Oh, In the past week, I haven't do much work. So in the following days, I should speed up. And I also need to preserve a few time to prepare my second project presentation in July, 8.
The next things I need to do are follow:
1) Decide on the length of 'name' column
2) Complete the optimization for HibernateUtil class
3) Begin to support other metadata's localization
2010-06-12
My GSoC project's progress report - 12/06/2010
In the past week, I have done following things:
1) I have tried to move localizedName property into BaseOpenmrsMetadata, but still have a error need to resolve. It's the "Found shared references to a collection:xxx" exception.
2) I have made several discussion with other devs, about LocalizedStringSerializer's use case, now I have refacted this class and move all its methods into LocalizedStringUtil
3) I have created database convenient function for Oracle.
4) I also determinted the code review day. It's June, 14. All my written codes in branch will be reviewed in that day's code review call.
The next things I need to do are follow:
#1 Collect comments from the upcoming code review for my branch.
#2 Reading existing comments about ticket#372, discuss with other devs and make some necessary modification.
#3 I need to difine a LocalizationException, and throw it when end-user enter a too-long localized string.
#4 Continue to find the reason for "Found shared references to a collection:xxx"
1) I have tried to move localizedName property into BaseOpenmrsMetadata, but still have a error need to resolve. It's the "Found shared references to a collection:xxx" exception.
2) I have made several discussion with other devs, about LocalizedStringSerializer's use case, now I have refacted this class and move all its methods into LocalizedStringUtil
3) I have created database convenient function for Oracle.
4) I also determinted the code review day. It's June, 14. All my written codes in branch will be reviewed in that day's code review call.
The next things I need to do are follow:
#1 Collect comments from the upcoming code review for my branch.
#2 Reading existing comments about ticket#372, discuss with other devs and make some necessary modification.
#3 I need to difine a LocalizationException, and throw it when end-user enter a too-long localized string.
#4 Continue to find the reason for "Found shared references to a collection:xxx"
2010-06-04
My GSoC project's progress report - 04/06/2010
In the past week, I have done following things:
1) Started a discussion in dev list to decide that moving localizedName property into BaseOpenmrsMetadata class.
2) Request a Code Review for all my changes done for localization of EncounterType
3) In the waiting phase for code review, I have created database functions for Mysql and PostgreSQL.
4) I also completed my first project presentation yesterday. It goes smoothly. Only one defect I think is my listen and oral english is poor, thanks to I have prepared a google doc for my presentation, so it doesn't impact my presentation a lot:-)
The next things I need to do are follow:
#1 Collect comments from the upcoming code review for my branch and also suggestion from dev mailing list
#2 Do changes, according to the information collected from #1
#3 After complete all changes, I hope I can merge all my current changes from branch into trunk to support localization of EncounterType
#4 Continue to write out the database function for Oracle
1) Started a discussion in dev list to decide that moving localizedName property into BaseOpenmrsMetadata class.
2) Request a Code Review for all my changes done for localization of EncounterType
3) In the waiting phase for code review, I have created database functions for Mysql and PostgreSQL.
4) I also completed my first project presentation yesterday. It goes smoothly. Only one defect I think is my listen and oral english is poor, thanks to I have prepared a google doc for my presentation, so it doesn't impact my presentation a lot:-)
The next things I need to do are follow:
#1 Collect comments from the upcoming code review for my branch and also suggestion from dev mailing list
#2 Do changes, according to the information collected from #1
#3 After complete all changes, I hope I can merge all my current changes from branch into trunk to support localization of EncounterType
#4 Continue to write out the database function for Oracle
Subscribe to:
Posts (Atom)