git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guilhem Bonnefille <guilhem.bonnefille@gmail.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Common library for Git GUIs
Date: Tue, 17 Feb 2009 13:55:04 +0100	[thread overview]
Message-ID: <8b65902a0902170455lda80ea3ybb8ca94eb86d0453@mail.gmail.com> (raw)
In-Reply-To: <20090216212459.GA25046@efreet.light.src>

Hi,

I don't know if it is possible to elect a toolkit. Each toolkit is good.

Concerning the design of the library, I think it is better to split
the library into different layers. The part of the e-world I know
concern Gtk/Gnome, so I will use it for my example.

IMHO, it should be interesting to build a library containing only
GObject'ification of Git and some wrappers/helpers to construct these
objects. For example, some objects to represent authors, commits,
branches, remotes and so on. Coupled to these base-types, this library
should provide solutions to construct these base-types (wrappers
around Git commands and/or internal files).
This library can be named libgit-glib for example.
Such library can help developement of current UI (giggle, gitg,
anjuta-git plugin, and probably others I don't know).

Then, on top of this library, we can imagine another one providing
high-level widgets. But it seems harder to identify common widgets
between different GUI.

In order to justify my idea, take a look at Qt. They started with a
large library, merging low-level with widgets. And then, they split it
in order to allow access to low-level features only.


I'm really interested in such project. So, if someone knows such
project, or create such a project, drop me a line, please.

Regards,
-- 
Guilhem BONNEFILLE
-=- #UIN: 15146515 JID: guyou@im.apinc.org MSN: guilhem_bonnefille@hotmail.com
-=- mailto:guilhem.bonnefille@gmail.com
-=- http://nathguil.free.fr/

  parent reply	other threads:[~2009-02-17 12:56 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 [this message]
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

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=8b65902a0902170455lda80ea3ybb8ca94eb86d0453@mail.gmail.com \
    --to=guilhem.bonnefille@gmail.com \
    --cc=bulb@ucw.cz \
    --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).