There is too much in this thread to respond to individually.  I will just 
say that I agree with Eugene.  Most of the improvements that are being 
sought could most likely be best offered by continuing to improve the 
Synchronize view with features like Commit Sets.  In this particular case, 
the Outgoing Commit Sets feature, as implemented by CVS, provides what is 
being asked for and probably does it in a better way.
It sounds like the biggest problem is that Commit Sets are not API, even 
in Eclipse 3.2.  So we need to either base our implementation on Internal 
code from Eclipse.org, or we have to use their code as a model for 
creating our own version of the same feature.
In a past discussion on this feature, it sounded like at least 2 of our 
committers have already implemented this feature using the internal API. 
Hopefully they will have some time to join a discussion on what they have 
learned and what they think the final approach should be.  Most likely, I 
will not be participating in the initial coding of this feature, but I 
will certainly help with testing and talking it through, and I would 
strongly encourage those that want to work on this feature to do so.
I guess in my ideal scenario, we could copy the needed Eclipse internal 
classes into our namespace and implement them ourselves.  Ideally this 
might even allow us to provide the feature for Eclipse 3.0, but if that is 
not possible, then I think we just need to drop support for 3.0 and move 
to 3.1.  Now that 1.0.x is branched, I think we can do that if we have to. 
 Adding a feature like this would be worth it.
Mark
Eugene Kuleshov <ekuleshov@gmail.com> wrote on 02/06/2006 09:42:14 PM:
> 
>    Guys, maybe you should stop inventing new view and fooling around 
> with those dialogs? It is all already there.
> 
>    View you are looking for is called Synchronize view and it is provide 
> all the infrastructure to see changes and call comparison _editors_.
> 
>    With a correspond data provider it would also allow to group outgoing 
> changes together before committing (either manually or using some tools, 
> e.g. Mylar).
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Tue Feb  7 14:49:20 2006