From: Jesse van den Kieboom <jesse@icecrew.nl>
To: Stefan Karpinski <stefan.karpinski@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: git gtk+/GNOME gui application: gitg
Date: Wed, 04 Feb 2009 12:50:28 +0100 [thread overview]
Message-ID: <1233748228.7594.2.camel@wren> (raw)
In-Reply-To: <d4bc1a2a0902031143u2f4beadek507910fe3a6052f@mail.gmail.com>
Op dinsdag 03-02-2009 om 11:43 uur [tijdzone -0800], schreef Stefan
Karpinski:
> On Tue, Feb 3, 2009 at 8:58 AM, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
> >
> > Not yet another one, please!
> >
> > I'm sorry, but that was my first thought. I lost count of how many
> > half-finished GUIs we have, using tcl/tk, gtk, qt, you-name-it-tk. I
> > still don't see any which provide a consistent, "modern", stable GUI for
> > viewing *and* committing, i.e. a replacement for gitk and git-gui.
> >
> > The latter two still seem to be the most feature rich choices, but they
> > suffer somewhat from their implementation language. Just look at the git
> > survey and you know why nobody wants to work on them.
>
> For what it's worth, GitX (OS X only) does both history viewing and
> committing, and seems to be rapidly approaching the feature set of
> gitk and git-gui combined. Unfortunately, I seem to inevitably hate
> cross-platform GUI's---they never feel right or work slickly enough.
> Sad, but true.
This is the reason why I'm developing gitg as a separate application,
and not as a different front end for GitX.
> If GitX and this newer project could share a lot of code base, then
> maybe their co-development would be accelerated and both would end up
> being slick, native, full-fledged GUIs for git.
I try to follow the implementation of GitX very closely since it's the
basis of the development of gitg (it happens to be that I know the
developer of GitX very well).
--
Jesse van den Kieboom
Personal: http://www.icecrew.nl
Professional: http://www.novowork.com
next prev parent reply other threads:[~2009-02-04 11:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 20:05 git gtk+/GNOME gui application: gitg Jesse van den Kieboom
2009-02-03 13:08 ` SZEDER Gábor
2009-02-03 13:08 ` [PATCH 1/3] Fix "multi-character character constant" compile warning SZEDER Gábor
2009-02-03 13:08 ` [PATCH 2/3] Refactor loading xml UI files SZEDER Gábor
2009-02-03 13:08 ` [PATCH 3/3] Try load UI xml files from the current working directory SZEDER Gábor
2009-02-14 21:37 ` [PATCH 2/3] Refactor loading xml UI files Jesse van den Kieboom
2009-02-04 11:50 ` [PATCH 1/3] Fix "multi-character character constant" compile warning Jesse van den Kieboom
2009-02-03 16:58 ` git gtk+/GNOME gui application: gitg Michael J Gruber
2009-02-03 19:43 ` Stefan Karpinski
2009-02-04 11:50 ` Jesse van den Kieboom [this message]
2009-02-04 3:38 ` Miles Bader
2009-02-03 17:00 ` Jakub Narebski
[not found] ` <1233748909.7594.14.camel@wren>
2009-02-04 12:33 ` Jakub Narebski
2009-02-04 7:39 ` Felipe Contreras
2009-02-04 11:48 ` Jesse van den Kieboom
2009-02-04 12:46 ` Michael J Gruber
2009-02-04 14:12 ` Felipe Contreras
2009-02-04 14:18 ` Jesse van den Kieboom
2009-02-04 15:00 ` Felipe Contreras
2009-02-04 14:29 ` Michael J Gruber
2009-02-04 14:33 ` Jesse van den Kieboom
2009-02-04 14:40 ` Michael J Gruber
2009-02-04 14:46 ` Jesse van den Kieboom
2009-02-05 5:46 ` Miles Bader
2009-02-05 20:06 ` Jesse van den Kieboom
2009-02-06 9:49 ` Miles Bader
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1233748228.7594.2.camel@wren \
--to=jesse@icecrew.nl \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=stefan.karpinski@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).