Re: Vincent_ Next Step

Hi Pradeeban,

Thanks for your reply. Yes, just as you said, I need to plan more time
because we need implement it in 3 OS platforms.

the timeline I modified as following and I want to know when and how
should I create my own branch to commit code? thanks

1.    Now-May 10: Studying the spec and the code, and discussions with
the mentor and community on its design and how it might best be
implemented this topic. Make a simple design of class diagram and
function diagram.
     including: SVN Branches build and code style learning.

2.    May 11 - May 17: (one week) Make a clear design of class diagram
and function diagram. The data communication must be clear.

3.     May 18 - May 27: (one and half weeks) Implement: make Frame
expandable in Windows.

3.     May 28 - Jun 6: (one week) Implement: make Frame expandable in Linux.

3.     Jun 7 - Jun 14: (one week) Implement: make Frame expandable in Mac.

4. Jun 15 - Jun 21 : (one week) test and code refactor.

5. Jun 22 -  Jun 28 : (one week) Implement: make Frame expandable in
Windows. (50% finish)

6.   Jun 28 - Jul 9: (one week)  Prepare for Google Mid-term evaluations

7. Jul 9 - Jun 15 : (one week) Implement: make Frame expandable in
Windows. (100% finish)

8. Jul 15 - Jun 22 : (one week) Implement: make Frame expandable in Linux.

9. Jul 22 - Jun 27 : (one week) Implement: make Frame expandable in Mac.

10.  Jun 27 -Aug 1 : (one week) Test and code refactor

11.   Aug 1 - Aug 10 :   (one week)  Prepare some document that Google needed

Vincent

2012/4/29 Kathiravelu Pradeeban <kk.pradeeban@gmail.com>:
> Hi Vincent,
> Sounds fine. Just make sure that the development involves multiple
> platforms, hence testing will take more time. The major problem we
> have with the "Dialog Improvements" project is to find a student who
> is capable of coding and testing from multiple platforms.
>
> Since you have already built AbiWord on all three platforms, this may
> not be a big issue for you. We will also have to agree upon the
> milestones for the mid evaluations during this design phase - how much
> of the work should be completed by the mid evaluations.
>
> Regards,
> Pradeeban.
>
> On Sat, Apr 28, 2012 at 6:58 AM, vincent vincent
> <vincent.abiword@gmail.com> wrote:
>> Hi Pradeeban,
>>
>> In the following weeks, I would like to do the things as following:
>>
>>
>> 1.    Now-May 10: Studying the spec and the code, and discussions with
>> the mentor and community on its design and how it might best be
>> implemented this topic. Make a simple design of class diagram and
>> function diagram.
>>       including: SVN Branches build and code style learning.
>>
>> 2.    May 11 - May 17: (one week) Make a clear design of class diagram
>> and function diagram. The data communication must be clear.
>>
>> 3.     May 18 - Jun 1: (two weeks) Implement: make Frame expandable.
>>
>> 4.    Jun 1 - Jun 14: ( two  weeks) Implement: Table setting dialog improvement.
>>
>> 5.    Jun 15 - Jun 27: (one and half week) test the two implemented
>> parts and code refactor
>>
>> 6.    Jun 28 - Jul 9: (one week)  Prepare for Google Mid-term evaluations
>>
>> 7.    Jul 10 - Jul 24: (two week)  Implement: Rotate-text setting
>>
>> 8.    Jul 24 - Aug 1 : (one week) Test and code refactor
>>
>> 9.   Aug 1 - Aug 10 :   (one week)  Prepare some document that Google needed
>>
>>
>>
>>
>>
>> And I want to hear more about your advices, thanks
>>
>>
>>
>> Vincent
>
>
>
> --
> Kathiravelu Pradeeban.
> Software Engineer.
> WSO2 Inc.
>
> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
Received on Wed May 2 08:58:02 2012