On Fri, Sep 25, 2009 at 16:10, Adrian Buehlmann <adr...@cadifra.com> wrote: > > > On 25.09.2009 03:35, Steve Borho wrote: >> On Thu, Sep 24, 2009 at 7:58 PM, Yuki KODAMA <endflow....@gmail.com> wrote: >>> On Fri, Sep 25, 2009 at 03:56, Adrian Buehlmann <adr...@cadifra.com> wrote: >>>> # HG changeset patch >>>> # User Adrian Buehlmann <adr...@cadifra.com> >>>> # Date 1253818443 -7200 >>>> # Node ID d511e32612db7d1e9396da8b3a718073331d506f >>>> # Parent b13d485dec5a26dd813f30c21de23517b94a638f >>>> update: eliminate 'Ways' label, kill 'Show changeset summaries' >>>> >>>> An option to turn off the changeset summaries is uneeded and >>>> needlessly complicates the dialog for the user. >>> Umm... you really like changeset summary XD >>> >>> The reason why I provide that option is just for usability. >>> Look at this screenshot: >>> http://www.flickr.com/photos/netkuy/3951389507/sizes/o/ >>> >>> When I look this for the first time, I was so surprised. >>> I suppose it's too wide and doesn't good for usability. > > Seeing to what cset I update and on what cset I currently > am increases transparency and usabilty of the update > process a lot. > >>> After filling target revision, I have to move mouse cursor >>> from up-left corner to right-bottom corner. Very long. > > The problem here is that the dialog box should > probably made wider. > > I agree that jumping the buttons left and right > isn't good. > > We should aim for having the Update / Cancel button > always at the same distance from the left edge. > > But this Gnome look and feel design by Gtk+ is so desparately > fixed to the right edge of the dialogs that it is > a pain for Windows GUI devlopers. > > But the solution cannot be to add an option > to turn summary lines off together with > -C. *That* is confusing.
Okay, so how about placing it at the side of revision combo or expander? combo: http://www.flickr.com/photos/netkuy/3952446163/sizes/o/ expander: http://www.flickr.com/photos/netkuy/3952446179/sizes/o/ >>> So I want to leave that option, but you really dislike that >>> option, can I truncate the summary line in changeset? >>> Maybe 40 chars will fit with that. >> >> 70 characters is a common limit for summary lines. It would be ok to >> ellipsis '...' the summary if it is longer than 70 chars. > > Truncate at 70 would be fine. > > But I find it funny that we can't find a solution to present > more information, so that we have to resort to suppressing > it. > > It's almost like we would have to pay for using > screen space :) > >> I've been wondering, though, if we want to move the treemodel logic >> that does 'tortoisehg.longsummary' to hglib.py and use it everywhere >> we show changeset summaries. > -- Yuki KODAMA ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
