<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Oct 10, 2006, at 9:04 PM, Chris Thomas wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">On Oct 9, 2006, at 5:24 PM, Allan Odgaard wrote:</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Is there a reason for not enabling the close button of the window? Otherwise I would link that to cancel.</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A close box would be an ambiguous third choice. I would not necessarily expect it to cancel. CrashReporter has a live close box, where I frequently select the close box rather than cancel, but it always prompts a light afterthought of 'wait a minute, that can't be right -- what did I just do?'</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Making the diff visible in the UI sounds like a good idea (as Benoit mentioned) -- most people do not find it, and when I tell them about it, they act as if I just gave them 100 bucks ;)</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Yup. To add to what I previously said on this subject:</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">When I saw Thomas's modifications to the status window, it became clear that the status window and the commit window _could_ converge. Not entirely clear that they _should_. But, ideally, I'd like to be able to add, revert, etc. from the commit window. All these commands could be added to the new action popup, or they could be added in iTunes store-like fashion, similarly to the way the status window works, but using less of the screen (though perhaps considerably more cluttered in that space).</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">In such a universe, we'd remove the preflighting check for conflicts and unknown files, and list them with the rest of the files, but unchecked by default, as external files are now.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Would it be better to go the Ruby/HTML/JavaScript route and make the status window also serve as the commit window? It would probably be prettier, but it might not be as usable.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Just some thoughts.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Chris</DIV></BLOCKQUOTE></DIV><BR><DIV>Despite being a web developer and the guy who wanted all that carp in the status window...</DIV><DIV>Cocoa beats HTML hands down in almost every way imaginable. (i would've redone it in cocoa if i knew how)</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I would LOVE to have something cocoa totally replace the fancy status window.</DIV><DIV>I think the ideal is TextMate 2's new configurable file drawer/palette though.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I think the status window could survive asis until then.</DIV><DIV>All that stuff that has columns in the status window (revert, add, diff) should be in the contextual/gear menu of the files palette.</DIV><DIV>Assuming there will be a way to filter it by svn state and whatnot.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><DIV>thomas Aylott — <B>subtleGradient </B>— CrazyEgg</DIV></DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>