Hah. Guess you must be laughing at me for being so out of the loop.
Looks like non-modal commit dialogs are already in the works, at least
for CVS. So guess that answers that.
I was thinking more along the lines of commit templates, or some such,
and how nifty it is that you can get that bugzilla field in some commit
boxes, if you enable it, and how nice it would be to have something like
that but from a template, and maybe even something that could get
contributed back to subversion itself, in some form, maybe variable
substitution or whatnot. But anyway, what I was thinking of would need
more realestate, and be more of a view than a dialog, but I'll just wait
and see how the CVS idea comes about or whatever.
Mylar does look nifty, and I like how it's 3.2M4-able. Bleeding edges
pay off too...
Well, back to the grind and whatnot. Thanks for all your ideas everyone!
:Denny
Eugene Kuleshov wrote:
>
> For the record. I think it is waste of time to prepare such comments
> manually. For most of the IDE activities it should be possible to
> capture and track all the changes. Mylar project is going to that
> direction already and I believe the best would be to use it to prepare
> such comments automatically. Though it does need support for outgoing
> change sets.
>
> regards,
> Eugene
>
>
> Jesper Steen Møller wrote:
>
>> 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
>> commit notes.
>>
>> 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.
>
>
> ---------------------------------------------------------------------
> 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 Wed Feb 8 01:20:19 2006