Thanks for the update... I'll try to orient myself to using the browser interface, but I've been finding it somewhat inefficient for commit. I generally know exactly what level of the tree I need to commit from, and when I go to do a commit, 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 the commit-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 for commit. 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 the commit dialog 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, efficient commit dialog that's optimized to its purpose. If you guys are willing to consider that direction, Tortoise has done a nice job with their commit dialog. Thanks again for the update. 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 the commit window: I think that would be a > nice feature to have, something I'd find quite handy myself too. > > Re. 2. 'Enabling/disabling' items in the commit dialog: I'm > personally less certain about that, since I'm worried it would make > the commit dialog a 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 the commit dialog is for, but that's true for both topics. > > There's something to say for a more powerful commit dialog, my main > concern is losing some of the clarity of Versions' interface by > providing too much overlap between browser and commit dialog. Once we > have disabling/enabling of items, it'd be just one step further to > allow adding unversioned files from the commit dialog, 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 the commit dialog. We will have to work out some > prototypes of a more powerful commit dialog and see how they work and > feel. And maybe if we're lucky, we'll come up with an even better way > to make pre-commit reviews 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 to commit – pun not intended – on shipping an update with > 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 the Commit window would make self-reviews much easier > > for us: > > > 1. Provide the ability to diff the working copy of a file with the > > base from the Commit window. > > > 2. Provide the ability to add and remove files from the commit set by > > using checkboxes in the Commit window. > > > 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 -~----------~----~----~----~------~----~------~--~---
