In the past two weeks, I have done following things:
1) Complete that new UI for localizedDescription property.
2) Completed support localization for all necessary metadata classes.
The next things I need to do are as follow:
1) Do some test for my branch
2) Make necessary code review
2010-07-23
My GSoC project's progress report - 24/07/2010
In the past week, I have done following things:
1) Analyzed the "add LocalizedMetadata interface" solution, and find that there are only User class don't need description property. So maybe I will just let User class implements interface OpenmrsMetadata.
2) Communicated with devs to make a decision on a initial UI mockup for localizable description.
The next things I need to do are as follow:
1) Complete that new UI for localizedDescription property.
2) To support localization for those necessary metadata classes.
1) Analyzed the "add LocalizedMetadata interface" solution, and find that there are only User class don't need description property. So maybe I will just let User class implements interface OpenmrsMetadata.
2) Communicated with devs to make a decision on a initial UI mockup for localizable description.
The next things I need to do are as follow:
1) Complete that new UI for localizedDescription property.
2) To support localization for those necessary metadata classes.
2010-07-19
My GSoC project's progress report - 18/07/2010
In the past week, I have encountered a error while I am merging trunk into my branch "metadata-localization". This error has blocked me a few days, so my schedule is delayed:-(
But, I have resolved this error, accroding to Ben's suggestion in mailing list. Thanks for his help:-)
I think this week, I should speed up!
The next things I need to do are as follow:
1) Analyze whether the solution 'add LocalizedMetadata interface' is enough, and do *not* need any modification, because it also needs to deal with description's localization.
2) Communicate with Mike and request a second code review.
3) Consider how to support description's localization.
But, I have resolved this error, accroding to Ben's suggestion in mailing list. Thanks for his help:-)
I think this week, I should speed up!
The next things I need to do are as follow:
1) Analyze whether the solution 'add LocalizedMetadata interface' is enough, and do *not* need any modification, because it also needs to deal with description's localization.
2) Communicate with Mike and request a second code review.
3) Consider how to support description's localization.
2010-07-10
My GSoC project's progress report - 10/07/2010
In the past week, I have done following things:
1) Completed my second project presentation.
2) Completed localization support for RelationshipType's aIsToB and bIsToA properties
3) Added LocalizedMetadata interface and BaseOpenmrsMetadata super class, according to the discussion about my project from dev mailing list.
The next things I need to do are as follow:
1) Analyze whether the solution 'add LocalizedMetadata interface' is enough, and do *not* need any modification, because it also needs to deal with description's localization.
2) Communicate with my Mentor about my work till now and hope to request a second code review soon.
3) Consider in advance for how to support description's localization.
1) Completed my second project presentation.
2) Completed localization support for RelationshipType's aIsToB and bIsToA properties
3) Added LocalizedMetadata interface and BaseOpenmrsMetadata super class, according to the discussion about my project from dev mailing list.
The next things I need to do are as follow:
1) Analyze whether the solution 'add LocalizedMetadata interface' is enough, and do *not* need any modification, because it also needs to deal with description's localization.
2) Communicate with my Mentor about my work till now and hope to request a second code review soon.
3) Consider in advance for how to support description's localization.
2010-07-03
My GSoC project's progress report - 03/07/2010
In the past week, I have done following things:
1) Discuss with my mentor and other devs about how to support localization for those special metadata, such as Privilege, Role, etc.
2) Update those common methods of HibernateUtil and add related unit tests for it.
3) Update project wiki page and also paste sql functions(for mysql, postgresql and oracle) into project wiki page.
The next things I need to do are follow:
1) Apply Ben's suggestion and do localization support for RelationshipType
2) Talk with my mentor about my project progress and request a code review to my recent changes(complete localization support for most metadata)
3) Prepare for my second project presentation
1) Discuss with my mentor and other devs about how to support localization for those special metadata, such as Privilege, Role, etc.
2) Update those common methods of HibernateUtil and add related unit tests for it.
3) Update project wiki page and also paste sql functions(for mysql, postgresql and oracle) into project wiki page.
The next things I need to do are follow:
1) Apply Ben's suggestion and do localization support for RelationshipType
2) Talk with my mentor about my project progress and request a code review to my recent changes(complete localization support for most metadata)
3) Prepare for my second project presentation
2010-06-26
My GSoC project's progress report - 26/06/2010
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
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
2010-05-29
My GSoC project's progress report - 30/05/2010
In the past week, I have done following things:
1) Create and abstract out a generic edit UI for EncounterType
2) Modify related methods in HibernateEncounterDAO
3) step 1) and 2) together completed the localization support for EncounterType
4) Update and add some necessary unit tests
The next things I need to do are supporting the "name" property's localization for other Metadatas.
1) Create and abstract out a generic edit UI for EncounterType
2) Modify related methods in HibernateEncounterDAO
3) step 1) and 2) together completed the localization support for EncounterType
4) Update and add some necessary unit tests
The next things I need to do are supporting the "name" property's localization for other Metadatas.
2010-05-22
My GSoC project's progress report - 23/05/2010
In the past week, I have done following things:
1) Reached an agreement for the final requirements and design thoughts of my project and update project wiki page according to the final requirements and design thoughts.
2) Requested the "metadata-localization" branch for my project.
3) Started to code, and I have completed tasks in phase "Create And Apply LocalizedString", in advance. You can see all tasks in phase "Create And Apply LocalizedString" from project's Project Plan
The next things I need to do are create edit UI for EncounterType and discuss whether this edit UI is feasible, together with Mike.
1) Reached an agreement for the final requirements and design thoughts of my project and update project wiki page according to the final requirements and design thoughts.
2) Requested the "metadata-localization" branch for my project.
3) Started to code, and I have completed tasks in phase "Create And Apply LocalizedString", in advance. You can see all tasks in phase "Create And Apply LocalizedString" from project's Project Plan
The next things I need to do are create edit UI for EncounterType and discuss whether this edit UI is feasible, together with Mike.
2010-05-15
My GSoC project's progress report - 16/05/2010
In the past week, I have done following things:
1) Collect the reviews about my project's requriments and design thoughts from the dev group(Mike, Mark, Ben, Burke, Darius, etc).
2) Update my project's wiki page according to the reviews from group. And also Mike have created a wiki page about his preferred design thoughts in wiki. Thanks a lot and his preferred design thoughts help me a lot. I like the ideas in this page.
3) Complete a project plan(Timeline) for my project, Mike and me will reach an agreement on this plan later.
The next things I need to do are mockup some examples for the new editing UI of EncounterType together with Mike and get some feedback from group; reach an agreement for the final requirements and design thoughts of my project together with Mike; request a branch for my project before starting to code.
1) Collect the reviews about my project's requriments and design thoughts from the dev group(Mike, Mark, Ben, Burke, Darius, etc).
2) Update my project's wiki page according to the reviews from group. And also Mike have created a wiki page about his preferred design thoughts in wiki. Thanks a lot and his preferred design thoughts help me a lot. I like the ideas in this page.
3) Complete a project plan(Timeline) for my project, Mike and me will reach an agreement on this plan later.
The next things I need to do are mockup some examples for the new editing UI of EncounterType together with Mike and get some feedback from group; reach an agreement for the final requirements and design thoughts of my project together with Mike; request a branch for my project before starting to code.
2010-05-08
My GSoC project's progress report - 07/05/2010
In the past about ten days(28.April - 7.May), I have done follow things:
1) Create a wiki page for my project -- Localization Tools
Here is the url link for this page: http://openmrs.org/wiki/Localization_Tools
Now all requirements and design thoughts in this wiki page hasn't been determined at last. Thanks for my mentor -- Mike Seaton. He has added a "Initial Design Subject To Review" section for me, and this section helped me a lot. It make me more clearly with my design thoughts.
2) Mike (my mentor) also helped me group our devs who are interested in my project to discuss and agree on the requirements and high level specification of my project. Now we have already get some review from this group.
I think the next steps for me before starting to code, are that I need to collect any helpful reviews from devs who are interested in my project, and improve my design thoughts in project's wiki page. Also I have some questions need to resolve, such as understand how to search a metadata's name in locale hierarchy, and how to design a generic UI for editing localized metadata.
1) Create a wiki page for my project -- Localization Tools
Here is the url link for this page: http://openmrs.org/wiki/Localization_Tools
Now all requirements and design thoughts in this wiki page hasn't been determined at last. Thanks for my mentor -- Mike Seaton. He has added a "Initial Design Subject To Review" section for me, and this section helped me a lot. It make me more clearly with my design thoughts.
2) Mike (my mentor) also helped me group our devs who are interested in my project to discuss and agree on the requirements and high level specification of my project. Now we have already get some review from this group.
I think the next steps for me before starting to code, are that I need to collect any helpful reviews from devs who are interested in my project, and improve my design thoughts in project's wiki page. Also I have some questions need to resolve, such as understand how to search a metadata's name in locale hierarchy, and how to design a generic UI for editing localized metadata.
2010-04-27
Happy for participating GSoC 2010
I am happy that I win in GSoC 2010. And I can work for OpenMRS as a GSoC student again:-)
In this summer, I will work on "Localization Tools" and be guided by Mike Seaton.
Here, I will thanks for many many guys who help me.
Thanks Mike Seaton, thank you for giving me such a precious chance to work in this year's GSoC.
Thanks Ben Wolfe, thank you for giving me many good suggestions while I am preparing for my GSoC proposal.
Thanks Michael Downey, thank you for spending a lot of time on administrating the entire process of Students' GSoC apply.
I also want to thanks many other people who also did a lot contribution for GSoC, both Mentors and Students.
At last, Congratulate other GSoC students on winning in this year's GSoC! Let us make great efforts and work for OpenMRS, together:-)
In this summer, I will work on "Localization Tools" and be guided by Mike Seaton.
Here, I will thanks for many many guys who help me.
Thanks Mike Seaton, thank you for giving me such a precious chance to work in this year's GSoC.
Thanks Ben Wolfe, thank you for giving me many good suggestions while I am preparing for my GSoC proposal.
Thanks Michael Downey, thank you for spending a lot of time on administrating the entire process of Students' GSoC apply.
I also want to thanks many other people who also did a lot contribution for GSoC, both Mentors and Students.
At last, Congratulate other GSoC students on winning in this year's GSoC! Let us make great efforts and work for OpenMRS, together:-)
Subscribe to:
Posts (Atom)