Eugene Kuleshov wrote:
> Denny Valliant 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).
>>
>>
>> Heh. You didn't miss anything. Except the point. :-P I like the fact
>> that you can click on a file in the sync view and have it
>> automatically open in the compare editor*. That's swell. But you
>> glossed over the two salient points I was asking for comment on.
>> Basically #2 and #4.
>> *I use the commit dialog quite a bit, it's nice to be able to see the
>> "diff" from there now ;-)
>
>
> That is what I was talking about. #2 Select those files and add to
> commit set. #4 Edit comment on commit set node. All that time you can
> still open comparison editors. Once done just commit the commit set
> node. That simple. IMHO much more organized then overloaded popup
> dialog with whole bunch of duplicated functionality.
>
> If you are so up to dialogs, why not use TortoiseSVN? It will give
> all the deilaogs you want.
>
> Anyways, it seem you have quite a lot of time in your hands, so I
> can't compete here... and also too lazy to read it all. :-P
I just type fast. :-) It's ok, I think there is a little bit of a
language barrier anyways, reading more probably wouldn't have helped.
We're on the same page, so it's pretty funny.=]
I like Jesper's idea about a view better than a editable node, there
is a lot of info we need to convey when we update a bunch of files, it
deserves more realestate. Coincidence? =P
I'm a little torn about the team api stuff... on one hand, I respect
the need for repository tools (especially) to support older versions of
Eclipse. Applications that utilize them are quite often frozen at
certain versions, and those versions are a usually a major release or so
behind. I'd guess.
Good stuff takes time sometimes (or convoluted, [blank] stuff for that
matter).
On the other hand, if you contribute right to Team, it's better for
future development. Actually, everyone (the various different repository
plugin developers) could get together on Team, whip it out real good and
solid like, and the future would be bright indeed.
That's not gonna happen (life is too demanding, and consensous is hard
to achieve), but open, good hearted conversation between and about the
different repository philosophies/ideas/needs will help show the way to
an awe inspiring place.
You think Team is getting important now, just wait. Good foundatio-
Well, obviously time to get a blog. I'll try to be a little less,
whatever, and more dev. =]
:Denny
>
> regards,
> Eugene
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Tue Feb 7 11:55:45 2006