qct 0.4 released

[Satish Balay]

On Mon, 18 Dec 2006, Steve Borho wrote:

> > I think its better to split this functionality in different actions.
> > HCT has this functionality splitup. I think 'bk' also had this flag
> > separate from the 'diff' functionality.
> >    - when a select is toggled the diff is also shown
> >    - when the file name is selected - diff is shown [without a toggle
> >      for select]
> 
> I might go this route eventually, however there is a shortcut 'CTRL+N' 
> which cycles through all the diffs without having to even visit the 
> file list window.

I had tried this earlier - and initially tought it also toggled the
select flag. Not I realise it doing smething - but not what I
expected.

Basically - when I have 3 modified files - If I hit Ctrl-N - then it
shows the diff of the 2nd file but it also unhighlights the 3rd file.

And in some cases [combination of Ctrl-N & toggle] I see a 'gray'
highlight. I keep assuming blue - select, white - unselect, but don't
know what gray means.

I think its better to have visual cues for each of these 2 functions
separated.

> 
> You're basic work-flow should be like this:
> 
> o You decide it's time to check in some work, so you run 'hg qct'
> o You look at the file list to see what files are commitable, then
>   decide whether this is one commit or multiple commits.  You use CTRL+N
>   to look at the diffs made to each file.
> o If this is a single commit, you type in the commit message and then
>   hit CTRL+O.  You're done.
> o If this requires multiple commits, you type in your first commit
>   message then deselect the files you want to leave out ([TAB] sends you
>   to the file list and spacebar toggles the files).  You hit CTRL+O to
>   make the first commit.
> o Qct will refresh the file list with the remaining commitable files,
>   auto-selects those which are already revisioned, clears out the old
>   commit message and places the focus back in the commit message window.
> o wash, rinse, repeat
> 
> You can do all of this without touching the mouse, which I find much 
> more efficient.  But your comment is correct, the mouse interaction 
> with the file list is currently klunky.

I think having a non-mouse work-flow is good to have. But at the same
time it will be nice if the visual cues are clear.

Thanks,
Satish