gquilt -- a PyGTK GUI wrapper for quilt et al

Features

Currently, point and click interfaces are only provided for a small (frequently used) sub set of quilt's and mq's commands:

1. an Open menu item in the Playground that allows the root directory for the quilt or mq playground to be selected,
2. a New menu item in the Playground that allows a new quilt or mq playground to be created,
3. a Pop All menu item in the Actions that allows all currently applied patches to be popped off the stack,
4. a Push All menu item in the Actions that allows all currently unapplied patches to be pushed onto the stack,
5. a Combined Diff menu item in the Actions that allows a combined diff of all currently applied patches to be generated and optionally saved to a file,
6. an Import Patch Series menu item in the Actions that allows an existing patch set to be imported into the current repository,
7. tool bar buttons that execute common operations on the top applied patch, and
8. pop up menus (triggered by the right mouse button) over the playground files tree, patch files tree and patch series list that execute common operations such as adding files to the top patch, etc.

To compensate for the incomplete coverage of quilt's and mq's command sets a text entry widget is provided in the tool bar where arbitrary quilt or hg commands (depending on the back end in use) may be executed. All quilt commands initiated by the user (either by point and click or the provided entry widget) are echoed (with a time stamp) to the console widget at the bottom of the main window as is the resulting output from the quilt command. To enable easy distinction between stdout and stderr output the former is printed in black and the latter in red.

As it is possible for quilt or mq/hg commands to be issued via the command line outside of gquilt, it is possible for the information displayed by gquilt to be out of sync with the repository's actual state. It is safe for gquilt to be in this state as it never uses displayed information to make decisions and always uses the current repository state however, as it can be confusing for the user, the Views item in the menu bar provides means for remedying this situation should it arise.

Development

Source Control