On Sun, Mar 1, 2015 at 5:19 PM, Thierry Goubier <[hidden email]> wrote:

Le 01/03/2015 09:54, Jan B. a écrit :

A Pharo gui for git would be an excellent thing. As you (and Alan Kay) know,
simple things should be simple, complex things should be possible... With
git itself and its command line, there are lots of complex things possible,
but my opinion is that simple thing are far from simple with git.

I do agree with you on that simple things are far from simple with git ;) and complex things are complex, and things that we shouldn't be doing are possible :)

Nice example of git gui I personally like is github for mac (and github for
windows).
https://mac.github.com  https://windows.github.com

:( No mac, no windows here...

Of course, it is just for github, but it contains all things one usually
needs for commiting, branching etc. in the gui and if something is not so
simple, it has command line, too.

I think this 'GUI for usual things', 'command line for the rest' is probably the pragmatic solution.

So, just for inspiration of overall design... how hard implementation for
git in general might be, that is another thing.

There is a possibility there, which is offered by libcgit integration in Pharo. If one wanted to do a full GUI integration, then it could be easier to do it that way (i.e. low-level access to git concepts, better mastery of those concepts since their understanding is needed when integrating into Pharo).. instead of a high-level flying overhead like GitFileTree does.

Max, Esteban, what do you think?

The other one is to focus on VCS overall, and to consider Monticello GUI refactoring to support concepts such as branches and external merging, so that it could be portable to other VCS (svn, mercurial, bazaar) and support whatever flow is needed out there (see my point during PharoDays 2015).

It could even allow us to let branches appear in .mcz repositories :)

Thierry

I believe there would be some advantage to having a general git GUI app on Pharo for:

* providing a test bed for Pharo libcgit integration

* for others to get some familiarity with Pharo libcgit usage, before adapting any core Pharo to make use of it

* it would be an app that "I" would have the power to add features to