All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhijit Bhopatkar <bain@devslashzero.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
	Jonas Fonseca <fonseca@diku.dk>,
	Marco Costalba <mcostalba@gmail.com>,
	David Aguilar <davvid@gmail.com>,
	Henk <henk_westhuis@hotmail.com>, Frank Li <lznuaa@gmail.com>
Subject: Re: [RFC] Common library for Git GUIs
Date: Wed, 18 Feb 2009 11:26:14 +0530	[thread overview]
Message-ID: <1234936574.20168.11.camel@bain-laptop> (raw)
In-Reply-To: <20090216212459.GA25046@efreet.light.src>


> Looking at the current situation with Git GUIs, I thought it might be useful
> to create a generic library that would make it easier to develop git guis
> (especially plugins to various tools) and to add a new features to many of
> them with less effort. What do you people think about such idea?
> 
I don't think lack of library is holding this back, all the
functionality is exposed through cli and i find it perfectly fine
interface. ( on teamgit side its lack of devtime :( thats holding it
back) On the other hand a generic Qt/Gtk lib to interface with cli's
would be nice.
In any event i do not plan to switch to a library. Mainly because there
is no value add (barring performance). And of-course, i already worked
so hard to interface with the cli :D.

> Unfortunately in current situation no gui really supports all I would need to
> get my colleagues at work to accept git (they are somewhat obsessed with
> plugin to Visual Studio and explorer and generally avoiding command line).
> I started working on VS plugin some time ago, but I feel like a bit more
> reuse would be in order.
BTW take a look at git extensions for windows, it should provide both,
win ui and VS plugin based on msysgit

> 
> The proposed library should contain:
> 
I think an effort to convert git into libgit+cli is already underway,
unless i missed something very obvious and you are talking about/for the
same effort.

Anyway,
Sorry folks no interest here.

BAIN

      parent reply	other threads:[~2009-02-18  5:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 21:24 [RFC] Common library for Git GUIs Jan Hudec
     [not found] ` <e5bfff550902162337m43156398kb06320796838c953@mail.gmail.com>
2009-02-17  7:40   ` Fwd: " Marco Costalba
2009-02-17 19:28   ` Jan Hudec
2009-02-18  8:04     ` Marco Costalba
2009-02-19  7:30       ` David Aguilar
2009-02-17 12:55 ` Guilhem Bonnefille
2009-02-17 20:39   ` Jan Hudec
2009-02-17 20:08 ` Pieter de Bie
2009-02-17 21:21   ` Jan Hudec
2009-02-17 23:45     ` Johannes Schindelin
2009-02-18  5:52       ` Jan Hudec
2009-02-18  1:38     ` Frank Li
2009-02-18  5:57       ` Jan Hudec
2009-02-18  6:02         ` Abhijit Bhopatkar
2009-02-18  5:56 ` Abhijit Bhopatkar [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=1234936574.20168.11.camel@bain-laptop \
    --to=bain@devslashzero.com \
    --cc=bulb@ucw.cz \
    --cc=davvid@gmail.com \
    --cc=fonseca@diku.dk \
    --cc=git@vger.kernel.org \
    --cc=henk_westhuis@hotmail.com \
    --cc=lznuaa@gmail.com \
    --cc=mcostalba@gmail.com \
    --cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.