For me, it's about the development cycle, and part of that cycle is
describing the changes I'm going to commit. The projects I work on are
pretty rigorous about this, and I know many developers are facing that.
That's why I'd like to have better support for this part of the cycle
than what's present in the current commit dialog, such as generated
description of structural changes and other things. For this, the modal
commit dialog is not really useful, I'm imagining a "notes view" that
allows me to review my patch and write notes about each changed
resources, which could then be compiled at commit time.
There could be a place for both resource specific notes and general
The view could be standard in the synch perspective. I'll make an
experimental version one day. This could even tie in with changesets,
and thus probably be better placed in the Eclipse Team support side of
things, so I'll post it there.
Eugene Kuleshov wrote:
> First of all it is not about CVS, but about generic Team
> infrastructure. Unfortunately it had been mostly used for CVS plugin,
> but there are lot of ideas and features already in place ready to be
> picked up and used.
> Let me enumerate what you are trying to do in that modal commit dialog:
> 1. See list of changed files/properties
> 2. Select some of those files for commit
> 3. Be able to see changes (open comparison tool) for each of those files.
> 4. Prepare comment for commit
> Did I miss anything?
> Anyways, all of those actions can be done from Synchronize view and
> all of them (exept entering commit comment) can be done without a
> single dialog (comparison tool is an editor I was talking about in my
> previous email).
> You should really learn in depth how those things are done for CVS
> plugin before going into discussion. I've been using both Subclipse
> and CVS in Eclipse long enough to say that Eclipse CVS integration is
> most convenient and rock solid one I ever seen (from the feature set
> and UI ergonomics) and Subclipse is still have to catchup with that.
> Major missing features are incoming and outbound change sets.
The CVS integration doesn't solve this either, not even in 3.2. So
there's still room for improvement. I'll have a look at Mylar and see
that it adds to the picture.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Feb 7 10:03:39 2006