qct 0.7 released

Source:                 http://www
.borho.org/~steve/qct-0.7.tar.gz
win32:                  http://
www.borho.org/~steve/qct-0.7-win32.exe
Repo:                   http://hg.borho.org/qct

New in 0.7:
    Support for Mercurial Queues
    Cache scheme for hg back-end
    Make most recent commit log messages available for
re-use
    Enable multi-selection in the file-list
    Improved support for symbolic links in Mercurial
back-end
    Added a man-page
    Worked around a Qt problem (multiple press events from
one click)
    Worked around more Windows path problems
    setup.py will build UI file iff it does not exist

Feedback appreciated, especially on the new MQ support.  The
next release 
should have subversion and git back-ends.

-- 
Steve Borho (steveborho.org)
http://www.borh
o.org/~steve/steve.asc
Key fingerprint = 2D08 E7CF B624 624C DE1F  E2E4 B0C2 5292
F2C6 2C8C

On 1/17/07, Steve Borho <steveborho.org> wrote:
> On Wednesday 17 January 2007 08:33, you wrote:
> > On 1/16/07, Steve Borho <steveborho.org> wrote:
> > > On Tuesday 16 January 2007 14:20, Steve Borho
wrote:
> > > > What I'm considering w.r.t. meld is to
offer a side-by-side diff of the
> > > > current working directory file against
it's parent revision (hg cat).
> > > > The user can then move some diffs out of
the working copy and into the
> > > > cached parent version in order to prune
down the changes to just those
> > > > you want to commit (meld offers much
finer control than just selecting
> > > > hunks).  This way qct can still commit
the working copy of the files
> > > > you have selected in the file list and
doesn't have to muck about with
> > > > patch files.
> > > >
> > > > After the commit, qct will copy back
your initial working copy thus
> > > > auto-magically giving you back your
remaining changes.
> > >
> > > This is now on the tip:  http://hg.borho.org/qct
> >
> > OT: is qct written with Qt4?
>
> Yes, and PyQt4
>
> > Does is work with Qt3?
>
> Unfortunately, no.  I made an attempt at back-porting
it a few weeks ago, but
> didn't make it too far.  It would take a substantial
re-write to get it to
> run on Qt3 (for instance the checked file list would
have to be
> re-implemented by hand).

So I will need to upgrade to Qt4, which will break other
apps built around Qt3?

On St, 2007-01-17 at 09:43 -0600, TK Soh wrote:
> On 1/17/07, Steve Borho <steveborho.org> wrote:
> > Unfortunately, no.  I made an attempt at
back-porting it a few weeks ago, but
> > didn't make it too far.  It would take a
substantial re-write to get it to
> > run on Qt3 (for instance the checked file list
would have to be
> > re-implemented by hand).
> 
> So I will need to upgrade to Qt4, which will break
other apps built around Qt3?

No, Qt3 and Qt4 are not mutually exclusive. You can have
them installed
both.

-Lukáš