On Tue, Feb 17, 2009 at 6:29 AM, Steve Borho <st...@borho.org> wrote:
> On Tue, 2009-02-17 at 05:21 +0000, TK Soh wrote:
>> On Tue, Feb 17, 2009 at 3:01 AM, Steve Borho <st...@borho.org> wrote:
>> > On Mon, Feb 16, 2009 at 8:52 PM, TK Soh <teekay...@gmail.com> wrote:
>> >> On Tue, Feb 17, 2009 at 2:27 AM, Steve Borho <st...@borho.org> wrote:
>> >>> On Tue, 2009-02-17 at 02:19 +0000, TK Soh wrote:
>> >>>> On Mon, Feb 16, 2009 at 3:36 AM, Steve Borho <st...@borho.org> wrote:
>> >>>> > As specified by our new time based release schedule, today
>> >>>> > was the deadline specified for the feature freeze for 0.7.  Only
>> >>>> > bug fixes will be pulled into the crew repository from today until
>> >>>> > 0.7 is released.
>> >>>> >
>> >>>> > I've been working pretty hard the last couple of days to finish
>> >>>> > a number of loose ends:
>> >>>> >
>> >>>> > * I pushed out a new release of Qct (1.7) that I know works
>> >>>> >  correctly with TortoiseHg as an external application
>> >>>> > * Fixed the overlay support on Vista (issue#1 on bitbucket)
>> >>>> > * Added the new dialogs to the windows context menu
>> >>>> > * Ran all the source code through pychecker, which found
>> >>>> >  more than a few of bugs and pointed out a number of bad
>> >>>> >  habits which I've tried to cleanup.
>> >>>> > * Improved robustness of the commit dialog
>> >>>> >
>> >>>> > >From today, I recommend people grab a nightly build and try
>> >>>> > it out on a non-mission-critical machine and report bugs here
>> >>>> > or on the crew issue tracker.  Most especially, try out the new
>> >>>> > features introduced in this release:
>> >>>> >
>> >>>> > * hgignore and rename dialogs
>> >>>> > * record and shelve features
>> >>>>
>> >>>> In the commit/shelve window, the message line on top of the diff pane
>> >>>> has the same background color as the diff header, making them look
>> >>>> mixed up. Perhaps they need some visual separation between them.
>> >>>>
>> >>>> Also, the message line is empty in status window. Maybe it should be 
>> >>>> removed.
>> >>>
>> >>> Removed in total, or just in the status window?
>> >>
>> >> Good question. Actually the line is taking up some rather precious
>> >> real estate away from the diff pane. If possible, we should remove it
>> >> completely, but you think there's other good way to tell users on the
>> >> rejection of hunks?
>> >
>> > Inside the dialog?  Probably not.  But I was intending to add wiki
>> > pages for each of the new features to explain them to users.  How many
>> > will read them?  Hard to tell.
>>
>> Not many. At least not until they are told after running into some issues.
>
> I think we need to find a way to bring up a welcome HTML page after the
> installer runs.  Maybe a first-time flag in their Mercurial.ini and an
> item in the start menu.
>
>> BTW, I meant removing it from the status window.
>
> I was leaning towards removing it already.

Remove it completely? I saw you did that already.

>> >> BTW, have you tested windows on repos with modified binary files?
>> >
>> > Yes, you just get the git diff header, no hunks for selection.  The
>> > header has the same message you see from record/shelve: this is a
>> > binary file (all or nothing)
>>
>> Then you will see that you can't tell if the file is rejected by
>> looking at the diff pane. Also, the header get 'fused' into the header
>> of the file that followed without any separation, making it
>> potentially confusing.
>
> The first problem could be fixed by reducing the font weight in the diff
> header when the file is unselected.  The second problem is more
> difficult, as the treeview does not allow variable padding per row.  We
> have limited options.
>
> Hmm, one idea is to experiment with a pixmap cell renderer, like the
> changelog browser uses to show parents.  We could add a pixmap to header
> hunks that makes those rows a bit taller.  The pixmap could even show
> the state of the file selection.
>
> --
> Steve
>
>

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Tortoisehg-discuss mailing list
Tortoisehg-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to