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
* 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)
* Detect applied patch queue, switch to qrefresh mode, update patch
description
* Unbundle qct and hgconfig from installer patch queue and forest
* Make sure Qct will work with THG when installed separately (new windows
installer for Qct)
* copy/move/rename support
For this last issue, I'm envisioning a new dialog for detecting renames.
It would use the mercurial logic behind addremove -s to make initial
guesses,
then allow the user to double check the results and reject/accept them.
>From the same dialog, the user could pick copy sources, etc.
So, what issues am I missing? What else would you miss?
--
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
