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

Re: Getting to 1.0 - a comparison of features with TortoiseSVN

From: Panagiotis Korros <panagiotis.korros_at_gmail.com>
Date: 2004-11-07 20:49:15 CET

Some comments on this discussion

1. Conflict Editor
Eclipse already has a compare/conflict editor. The editor we use to
compare with BASE or remote can be made to work as a three way editor
(like the cvs plugin) comparing local with remote using a common
ancestor (BASE).

2. Merge
We could port the merge synchronizer/participant from the CVS plugin
and use svn merge -dry-run to populate the synchronizer. This would
show a list of resources that need updating and will also show the
conflicts.

3. Update to Revision is in fact a 'Replace with revision' action in
eclipse terms. I think we should keep the eclipse terminology.

4. We could use the ecliplse 3.0 cvs images to make the subclipse
icons to be consistent with the eclipse ui.

5. Subclipse currently is a mixture of eclipse 2.1 and Eclipse 3.0 CVS
code. We should try to use the eclipse 3.0 api more.
In particular the jobs api is a powerful tool to execute commands
(operations) in the background by locking only the affected resources.
A start has been made with the update action that uses the
TeamOparation API. It locks the project that is being updated and
allows the user to work on other projects.
All lengthy subclipse actions should be backgroundable.

6. The sync view is a powerful tool. We use the svn status -u command
to populate a tree with local and and a tree with remote changes.

Implementing it for subclipse has many problems because the javahl
bindings doesn't give anough information to populate it correctly.

Problems:
a. We don't know if a remotely added resource is a file or directory.
b. We don't know the revision that a remote resource was changed.

Currently it not used because it is not complete. things to be done:
               1. Add Commit, Update, Ignore, Add to version control
actions to the sync view (these actions must implement the
SynchronizeModelAction).
               2. The sync view should be made to listen to the
workspace modifications and update itself automatically (partially
implemented and buggy).
               3. Write unit tests

I am working in the sync view but currently i lack the time to make it
work. Any help would be appreciated.

Korros Panagiotis

On Fri, 5 Nov 2004 20:38:07 -0500, Mark Phippard <markp@softlanding.com> wrote:
> > I started a todo list based on your document
> >
> > http://subclipse.tigris.org/roadmap.html
>
> Great.
>
> I kind of thought the lack of support for svn switch and svn merge were two
> of the biggest holes. I do not see them mentioned. Are they already
> supported and I am missing something, do you see them as being part of some
> other feature mentioned, do you just not agree, or did you just miss them?
>
> Mark
>
>
>
>
> _____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
> _____________________________________________________________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>

-- 
Take back the web http://www.getfirefox.com
Received on Mon Nov 8 06:49:15 2004

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