On Sun, Jan 18, 2009 at 6:27 PM, TK Soh <[email protected]> wrote:

> On Sun, Jan 18, 2009 at 6:26 AM, Steve Borho <[email protected]> wrote:
> > It's my intention to unbundle Qct from THG by the next release (0.7).
>  I've
> > made a lot of progress in the last week incorporating Qct features into
> the
> > native PyGtk dialogs.
> >
> > Done:
> > * record/shelve support - better than Qct
> > * hgignore management - better than Qct
> > * keyboard workflow - nearly as good as Qct
>
> You are the referring to keyboard shortcut? We should have them on all
> the GUI windows.


I agree.  Can we agree on common short-cuts for each dialog?  We might
be able to add them in a general way.


> > * exposed gtools.diffbottom in thgconfig, for Qct style layout
> >
> > TODO:
> > * Move precommit.username hook from hgconfig to hggtk and thgconfig
> > * Detect merges (two parents) and modify UI as necessary (disable file
> > selection, etc)
>
> We are already doing merge detection. Though I just found a small bug
> on the header checkbox, where it should have been disabled in merged
> repos.
>

Yes, I saw that you did start work in this direction.  The merge workflow,
where
you're supposed to commit the entire workspace at once, didn't match well
with
the new record/shelve features, so I made the merge case more "special".  It
could probably use more work, but what I pushed this morning is close to
what
I expect it will need to do.


> > * Detect applied patch queue, switch to qrefresh mode, update patch
> > description
>

I added basic support for qrefresh, much less than what Qct had, but it
dawned on
me that this really belongs in a separate app.  We could make a pretty nice
MQ
app with the record/shelve tools, but it doesn't belong in the commit/status
tool.


>
> > * Unbundle qct and hgconfig from installer patch queue and forest
>

This is done now, but untested.


>
> > * Make sure Qct will work with THG when installed separately (new windows
> > installer for Qct)
> > * copy/move/rename support
>
> I thought we just added them in 0.6. Maybe you meant to improve on them?


Yes, I think there's room for more improvement here to help the user detect
renames and copies that were done without Mercurial's knowledge.

--
Steve
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to