In our proposal to move Subclipse to Eclipse.org and become an Eclipse
project, I made several changes to Subclipse to better align it with the
CVS plugin. These changes are in a separate branch, so they are not in
any of the "Subclipse" code.
The idea is that Eclipse has general "Team" capabilities and the specific
tool you use does not fundamentally alter this. You can see some of this
work in Eclipse 3.2, where CVS and Subclipse both use a common History
view, and of course the Synchronize view. The hope is to keep going with
this and also eventually have a common Repositories view that shows all
your repositories, whether they are CVS, SVN or some other tool.
Anyway, the changes I made were to just change some of the unnecesary
differences between our plugins.
1) Look and Feel. Changed to use same icons as CVS (in many cases
meaning no icons). Changed order of menu items to better match their
order, in some cases I think I changed some terminology. We each still
have some options the other doesn't so you can tell the difference, but in
general they just look a lot more alike.
2) Removed Pending Operations view. This view is really unnecessary.
Everything it does is done better with the Synch view. Removing it, takes
an option off the Team menu and our list of views. This helps usability.
3) Removed "Add Keywords" option. I have a personal distate for this
option because I do not think it is obvious everything it exactly does. I
also think that all of the Properties management enhancements we have made
now make this option unnecesary and redundant. Again, removing it helps
usability by taking an option of the Team menu. I'd be particulary
interested in thought on this one. I do not use this option so maybe it
does something that the properties management does not. If so, I'd like
to identify that and see if we can enhance the properties management to
account for it.
4) This is mainly a technical change, but just changed the way that
client adapters are loaded so that it is done via Eclipse plugins and
extension points. One of the ideas here is that we would likely stop
including JavaSVN with Subclipse, and instead it would be a plugin you
could install separate that adds it as an option. You would likely get it
from TMate, but we might include it in our Subclipse update site.
I think these changes are all good candidates for doing directly in
Subclipse and including in the final 1.2.0 release. It would also better
help us show the Eclipse community exactly what we want to contribute and
I think it would help our usability. I would be interested to hear other
opinions on these specific changes.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Sep 20 15:29:37 2006