From: "Maxime Lévesque" <maxime.levesque@gmail.com>
To: "André Harms" <andre.harms@kuhlsolutions.de>
Cc: git@vger.kernel.org
Subject: Re: Modern Git GUI
Date: Thu, 28 Jan 2010 10:11:16 -0500 [thread overview]
Message-ID: <554f5f781001280711j67753654w10651b53999cab9f@mail.gmail.com> (raw)
In-Reply-To: <e39c1dcf1001231340p67448584pfdbc453cc8fb9ca7@mail.gmail.com>
On one hand, the proliferation of GUIs for Guit should be good
in a darwinian sense. On the other hand, for a new commer there
are so many to try out that the 'better' ones get a diluted visibility.
After trying a few I concluded that the Guit GUIs were in the medieval
stage, then I stumbled upon SmartGit and I found it pretty decent.
One good explanation for why there are so many is that to provide
a GUI that is "as simple as possible but no simpler" is not an easy
problem to solve in terms of UI design, but it is an interesting one.
Cheers
On Sat, Jan 23, 2010 at 4:40 PM, André Harms
<andre.harms@kuhlsolutions.de> wrote:
> Hi,
>
> I know there are several GUIs out there for Git. They are all
> functional and most of them can be used in the daily work with Git.
> In my opinion one thing combines them: they aren't very pretty.
> I currently prefer the CLI to work with Git because it's quick and I
> am happy with it. But I think there are people out there, who don't
> want to use the command-line because they are afraid of doing
> something wrong or anything like this. Additionally the CLI and
> unattractive GUIs are barriers to people who are not familar with a
> SCM-system.
> So I thought about developing a new kind of GUI for Git that looks
> modern and attractive (you know... some eye-candy stuff) and that is
> easy to use. In addition I thought about a built-in console (like we
> know it from first person shooters) so that also people who prefer the
> CLI might use this GUI application too.
>
> Is there anybody who agrees or disagrees? I really would appreciate
> some feedback about that idea.
>
> P.S.:
> Normally I come up with such ideas to the public and ask what others
> think about it when I have some mockups. I am sorry that I haven't any
> right now.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2010-01-28 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 21:40 Modern Git GUI André Harms
2010-01-24 9:50 ` Matthieu Moy
2010-01-24 20:43 ` André Harms
2010-01-25 14:25 ` Johannes Schindelin
2010-01-25 14:30 ` John Tapsell
2010-01-26 11:35 ` Michael J Gruber
2010-01-26 22:39 ` Guilhem Bonnefille
2010-01-28 15:11 ` Maxime Lévesque [this message]
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=554f5f781001280711j67753654w10651b53999cab9f@mail.gmail.com \
--to=maxime.levesque@gmail.com \
--cc=andre.harms@kuhlsolutions.de \
--cc=git@vger.kernel.org \
/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).