v-0.1 (alpha quality) gwsmhg is available for download at ...

[Peter Arrenbrecht]

On Mon, May 25, 2009 at 7:14 AM, Peter Williams <pwil3058 at bigpond.net.au> wrote:
> Peter Arrenbrecht wrote:
>>
>> On Sun, May 24, 2009 at 6:32 AM, Peter Williams <pwil3058 at bigpond.net.au>
>> wrote:
>>>
>>> ... <http://sourceforge.net/projects/gwsmhg/>.  It is a PyGTK workspace
>>> management GUI using hg and mq.
>>>
>>> It requires pygtk2, pygtksourceview, pycairo, pygobject2 and (of course)
>>> mercurial.  It has only been tested on i386 and x86_64 Fedora 10 Linux
>>> and any testing on other systems would be appreciated.  As would
>>> feedback on usability etc.
>>
>> Basic operations work on Ubuntu 9.04 64-bit.
>>
>> I kind of like the idea of the workspace manager. But how about
>> integrating with TortoiseHg for actual operations like commit? See
>> hgtk within TortoiseHg for how to launch it standalone. Maybe this
>> could even become an extension to TortoiseHg, like `hgtk browse` or
>> something.
>
> Having had a closer look at what hgtk is I've formed the opinion that the
> opposite mechanism to this might be more appropriate.  I.e., as hgtk is
> essentially a command line tool that launches special purpose GUIs and
> gwsmhg is essentially a wrapper around command line tools, I could arrange
> for it to contain a menu to launch some or all of hgtk's GUIs on request.

Yes, on second thought, this sounds like the better approach.

> The only problem that I can foresee is how gwsmhg will know to update its
> displays to take into account changes in the work space's status as a
> consequence of hgtk operations.  The simplest solution to this would be to
> stick a "refresh" button in gwsmhg's main tool bar which the user can click
> whenever he has made changes to the work space from outside of gwsmhg.

Maybe you can talk to Steve (muggs on IRC) about having hooks in hgtk
dialogs that tell you when to refresh.

-parren