[Announce] teamGit v0.0.3

Hi all,

This is an announcement for a small project to create a functional git gui. This project was born as kgit a couple of years back when i needed a ui commit tool and none other were mature. My ambitions have grown since then and I recoded it in pure QT4.

The short description of the application :-

Currently it is of course in very early alpha stage. It works stable to do following things,

1. Its a pretty good commit tool. Just double click on unstaged files
to stage them. It supports staging hunks (just double click on the
hunk you want to stage in diff pane)  and the related stuff.  You can
optionally view untracked files and stage them for inclusion as well.
2. Its a preliminary repository viewer, it does not support graphical
representation for want of performance.
3. It has few other git command implemented, a quick issue of pull/
push, a reset command, cherry pick command and some branch management
implemented.

Known problems,
1. Icons make no sense i just dumped kde icons dir to the project
resources and picked the ones i could match or just at random (e.g.
checkout is a smilie)
2. No documentation, will be addressed soon.
3. All git commands can not be canceled in between. But with git thats
not usually a big issue.

Long description:

You can find the info on http://www.devslashzero.com/teamgit

Download http://www.devslashzero.com/teamgit/download (you will need qt-dev > 4.4)

This is so far tested only on ubuntu 8.04 with backports repo enabled and qt update installed.

Ultimate goal of the project is to add much more than just version control on top of git. But giving git a ui will always remain an important goal. You can view continually evolving roadmap at http://www.devslashzero.com/teamgit/roadmap

With this announcement i am looking for feedback on the overall interface design (commit procedure dialogs etc.) and feature requests.

WARNING: never been used out side controlled environment. Use at your
own risk.

Abhijit Bhopatkar - BAIN

bain <bain@devslashzero.com> writes:

Could you please add info about teamGit to the git wiki page http://git.or.cz/gitwiki/InterfacesFrontendsAndTools ? I think just below now defunct and unmaintained KGit (or just above) would be best.

TIA.

P.S. How it differs from othe Git GUIs, like gitk+git-gui, qgit or git-cola?

Will do ASAP

1. gitk and git-gui : its not as ugly :p, well actually neither of
them fulfilled speed requirements on my 'not so old' but 'ancient by
computer standards' p4 laptop.
2. qgit4 : actually its not very different except that i don't find
interface of qgit too friendly. Neway i would have used qgit instead
if it was at the stage its now two years back. i also tried to base my
code off qgit's plumbing unfortunately it wasn't easy to rip it. I
didn't like the complicated unreadable typical c++ code design so
chose not to participate in there. (to make things clear qgit is
excellent, and wonderfully coded. Marc has done real good job of using
c++ to its fullest and this is not a comment on his coding
capabilities. Its only that i am just too poor a c++ developer and
consider c++ too confusing for active contirbution in core design by
others.) So one of the aims i have in teamGit is to keep it as clean
and simple as possible (not easy goal i must add and i might already
be off).
3. git-cola: i hate scirpting used as mainstay applications.

Besides all of the above teamGit differes drastically in its end roadmap. It will ultimately be complete project management tool. A developer should be able to completely manage his coding activities from inside teamGit, plus a team collaberation added as an advantage.

But these are reallllyyyyyy lloooonnngg term goals, if it ever gets there.

Thanks, BAIN

Hi,

bain wrote:

Because there are a lot of UIs and GUIs for git I thought a "feature matrix" could be cool. I created a stub on the mentioned wiki page.

So it'd be nice if you could add a column for teamGit there and perhaps some rows for features that are worth mentioning (if those already exist in teamGit). I was unsure what features are useful to mention, because I do not really use git GUIs. (I only use gitk for history viewing, but only when I'm too lazy to type "git log --decorate --graph".)

Regards,
  Stephan

PS: Such a feature matrix could also be useful for the git web
    interfaces.

On Mon, Oct 6, 2008 at 2:33 PM, Stephan Beyer <s-beyer@gmx.net> wrote:

I volunteer to start a "give a beer to a programmer that eschews writing his own and helps others polish/extend an existing one" fund :-p

cheers,

m