Re: Modern Git GUI

From: Michael J Gruber <git@drmicha.warpmail.net>
Date: Jan 26, 2010, 11:35 UTC
Message-ID: <4B5ED39D.1020804@drmicha.warpmail.net>
In-Reply-To: <43d8ce651001250630p51761f6eyce8b89da6ffcd7b@mail.gmail.com>

[Re-adding cc culled by John. Bad boy :) ] John Tapsell venit, vidit, dixit 25.01.2010 15:30:

Show 19 quoted lines

> 2010/1/25 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>> Hi,
>>
>> On Sun, 24 Jan 2010, Matthieu Moy wrote:
>>
>>> If you decide to go on with your project, either you want to carry it
>>> out alone, or you'll have to convince other developers to join. In the
>>> second case, a good starting point would be to explain why the other GUI
>>> are not good enough, and why you can't just contribute to them.
>>
>> Actually, a much better way would be to be positive, not negative.  I.e.
>> to show something you did, which hopefully entices others to use your
>> project (and maybe contribute to it).
> 
> Actually in this case, I don't think that would be good enough.  My
> first thought would be "why didn't he just add this feature to an
> existing GUI rather than reinventing the wheel yet again".  So there
> would really have to be good reasons why the other GUIs aren't a good
> enough starting point

A first step may be making the feature matrix in the wiki more honest - I've been meaning to do this for ages... For example, a gui which simply calls "gitk" for history view simply does not support history view according to my books, at least not on the same level (gui *integration*) as guis doing this natively. Or else gitk would have all git-gui features and vice versa... or even plain git, for that matter.

Michael