The day after tomorrow starts the OpenJavaDay 2008. I’m travelling this afternoon to Madrid to assist. OpenJavaDay is organized by Sun Microsystem and JavaHispano, a Java community in Spanish.
If someone wants to come I’ll be there 😉
The day after tomorrow starts the OpenJavaDay 2008. I’m travelling this afternoon to Madrid to assist. OpenJavaDay is organized by Sun Microsystem and JavaHispano, a Java community in Spanish.
If someone wants to come I’ll be there 😉
After the initial import, the first commit comes. Before the weekend I did my code to work with a sample repository. Now I’m trying to make it work with a bigger repository: the subclipse repository, with near to 4.000 revisions. I found some bugs and I’m fixing them. For example the replace (“R”) action wasn’t handled at all.
I’m going to test my code on larger repositories. I want to know how long it takes to process all the data with the current implementation. I have several ideas about improving the performance. But all depends on the performance of each step:
Depending on how long it takes each step I will make some improvements or others. I think the most important is the third step because the first and second ones will be big time consumption tasks only for the first time. In advance the first step will only ask for udpates, so the information will be much less compared with the first time. I will post some metrics and will discuss my thoughts in the sublclipse-devel mail list.
In the last post, as Mark noticed, I made a big mistake: posting a screenshot from TortoiseSVN instead of making a screenshot from subclipse 😛 I use TortoiseSVN very much because I use developing environments others than Eclipse when developing in programming languages such as Python or PHP, so I don’t always use subclipse 😛
So here is a screenshot of my code from Eclipse with Subclipse.
Two days ago I got access to the subclipse repository and I have just imported my current code.
Thank you very much Mark!
This is the first screenshot about my progress in the Google Summer of Code.
Of course there is a lot of work to do. This is just the first visual thing I can show you. I have been working with the Draw2d API and I have tried to do something similar to the RevtreePlugin. Each column is a branch and each change is ordered by revision number from the top to the bottom. At the top you can see the names of the different branches.
My project at Google Summer of Code can be divided into two tasks.