[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] GSoC coding

From: Alberto Gimeno <gimenete_at_gmail.com>
Date: Tue, 27 May 2008 16:41:42 +0200

Ok. So I will create a new plugin. Called
org.tigris.subversion.subclipse.ui.graph for example? Or maybe two
plugins: org.tigris.subversion.subclipse.ui.graph and
org.tigris.subversion.subclipse.cache

As I explained in the proposal I think the best will be to use an
embedded database for the cache. So the first thing I think I'll do is
to create a persistence tier to save the log information fetched from
the SVN interface using JDBC. This is: create a database structure as
I explained in the proposal. I can test this part making JUnit tests
and using example log information for different repositories. I will
probably use DbUnit that is an extension of JUnit and I have
experience with it.

Next I want to add an "action" to the context menu. Just below the
Team -> Show History... submenu. This action will perform these steps:
* update the cache information if it needs to be updated. Communicates
with SVN and saves the information in the embedded database.
* query the needed information to build the graph. Makes two queries
against the embedded database.
* build and show the graph.

The first two steps need the persistence tier. The third step at first
won't show a graph. Instead it will dump the information as plain
text, just to see if the cache is working as expected. When I have the
cache finished I will work in the graph: learn about GEF, choose a
graph layout,...

On Tue, May 27, 2008 at 4:13 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Tue, May 27, 2008 at 10:05 AM, Alberto Gimeno <gimenete_at_gmail.com> wrote:
>
>> According to the GSoC timeline the coding period started yesterday. To
>> start coding I think the other student and I should have a branch in
>> the repository.
>
> It would be best to create it as late as possible. You should just be
> able to switch your trunk checkout to the branch and commit when
> needed.
>
> I'd much rather see discussion about what you intend to do. For
> example, in your case the UI for the task is definitely going to go
> into a new plugin so that we can make the dependencies it drags in
> optional. We might just do it all in new plugins, but I could
> potentially see some of it going into our core plugin.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
> For additional commands, e-mail: dev-help_at_subclipse.tigris.org
>
>

-- 
Alberto Gimeno Brieba
Presidente y fundador de
Ribe Software S.L.
http://www.ribesoftware.com
ribe_at_ribesoftware.com
Contacto personal
eMail: gimenete_at_gmail.com
GTalk: gimenete_at_gmail.com
msn: gimenete_at_hotmail.com
página web: http://gimenete.net
teléfono móvil: +34 625 24 64 81
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-05-27 16:49:51 CEST

This is an archived mail posted to the Subclipse Dev mailing list.