On 7/13/07, CARASSO Felipe <Felipe.CARASSO@gemalto.com> wrote:
> I understand your problem and I'm quite sure that everyone else does too. It's just that there aren't many options from the
> plugin side to get around it.
>
> I can think on the following options (without actually evaluating their feasibility):
>
> 1. Instead of opening the Compare dialog from the Commit dialog, Subclipse could either:
>
> a) Turn the Commit dialog into something that would include the Compare, or
>
> b) Open a wrapper that would include the Compare plus some text field that would allow to change the commit message while
> browsing the Compare.
I do not think the commit dialog will be changing. I have toyed with
the idea of adding a compare drawer or something, but I think the UI
space would be too constrained for it to work.
> 2. Add some kind of Commit view in the Synchronize perspective.
I think that the Synchronize view and the Change Set feature are going
to be the answer. This allows you to edit the commit message and
store it until you are going to commit. All we need is for someone to
look at the code and see if the dialog where you enter the message can
be made modeless and then see how well that works. Since this dialog
and the editing of the commit message is nice and self-contained, this
would be the best place to tackle this problem and it is arguably the
best way to solve it anyway.
There just aren't a lot of modeless dialogs in Eclipse so it remains
to be seen how well it will work in real life.
Anyway, this would be a nice small task for someone to work on to get
started with Subclipse. The class name is CommitSetDialog.
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Jul 13 22:00:52 2007