I recently ran into another situation that it would be great to have you consider when you think about the commit process. I used Ctrl +Click to choose a bunch of files in the browser interface, then tried to commit. I ran into a merge conflict. I dealt with the merge conflict, then had to Ctrl+Click again to re-choose the files. I tried to commit, but ran into another merge conflict...you get the idea. I'd like the commit interface to remember the set of files I selected so I don't need to re-select them if the commit process takes several tries. Thanks for considering this.
Lucinda On Jan 3, 6:32 pm, Dirk Stoop <[email protected]> wrote: > Hi Lucinda and Ray, > > Thanks for the additional feedback, we'll take all of it into > consideration. > > - Dirk > > On Jan 3, 4:25 am, lucinda <[email protected]> wrote: > > > Thanks for theupdate... > > > I'll try to orient myself to using the browser interface, but I've > > been finding it somewhat inefficient forcommit. I generally know > > exactly what level of the tree I need tocommitfrom, and when I go to > > do acommit, I want: 1) a really easy-to-read list of the changed > > files under that level, 2) a really easy way to choose which files > > belong in thecommit-set, and 3) a really easy way to diff changes. > > For me, the browser interface doesn't seem efficient. Multi-selection > > with a mouse is clunky, and I don't want a tree view forcommit. Even > > when I just view the "changed" tree, I have to scroll vertically to > > see all of the changed files. > > > You mentioned that showing unversioned files in thecommitdialog > > seems like blurring the line, and while I understand why you say that, > > I really want that option, since I'd like to skip the browser > > interface altogether! I think the browser is great for most things, > > but I'd love to see it paired with a powerful, efficientcommitdialog > > that's optimized to its purpose. If you guys are willing to consider > > that direction, Tortoise has done a nice job with theircommitdialog. > > > Thanks again for theupdate. I'll stay tuned. > > > On Jan 2, 4:48 pm, Dirk Stoop <[email protected]> wrote: > > > > Hi Lucinda, > > > > We are considering to add this functionality in a future release. > > > > Regarding 1. Diffing from thecommitwindow: I think that would be a > > > nice feature to have, something I'd find quite handy myself too. > > > > Re. 2. 'Enabling/disabling' items in thecommitdialog: I'm > > > personally less certain about that, since I'm worried it would make > > > thecommitdialoga bit busy. The current way of committing > > > selectively is to use multiple selection in the browser; adding this > > > feature would blur the line somewhat between what the browser's for > > > and what thecommitdialogis for, but that's true for both topics. > > > > There's something to say for a more powerfulcommitdialog, my main > > > concern is losing some of the clarity of Versions' interface by > > > providing too much overlap between browser andcommitdialog. Once we > > > have disabling/enabling of items, it'd be just one step further to > > > allow adding unversioned files from thecommitdialog, and so on with > > > the next extra feature. > > > > These are just some of my personal off-the-bat opinions on where we > > > could/should take thecommitdialog. We will have to work out some > > > prototypes of a more powerfulcommitdialogand see how they work and > > > feel. And maybe if we're lucky, we'll come up with an even better way > > > to make pre-commitreviews more fluid. > > > > So definitely under consideration, but not yet decided exactly what, > > > how and when. > > > > I hope I've answered your question a bit. I'd love to say "Yes, we're > > > building that", but until we have a prototype that 'feels right' we're > > > not ready tocommit– pun not intended – on shipping anupdatewith > > > these features. > > > > Thanks, > > > - Dirk > > > > the Versions team > > > > On Dec 30 2008, 6:39 pm, lucinda <[email protected]> wrote: > > > > > My development group relies heavily on code reviews, including self- > > > > reviewing all changes before they are committed. The following > > > > improvements to theCommitwindow would make self-reviews much easier > > > > for us: > > > > > 1. Provide the ability to diff the working copy of a file with the > > > > base from theCommitwindow. > > > > > 2. Provide the ability to add and remove files from thecommitset by > > > > using checkboxes in theCommitwindow. > > > > > I see that these features have been requested already. Are they being > > > > considered for a release anytime soon? Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/versions?hl=en -~----------~----~----~----~------~----~------~--~---
