On 2012-09-07, at 13:49, Frank Shearar <[email protected]> wrote:

> On 7 September 2012 12:15, Camillo Bruni <[email protected]> wrote:
>> who will help?
>> 
>> max and I, stimulated by ESUG, worked on the latest version of FS-Git to 
>> make it stable again.
>> we are very close to have a complete set of git tools written in pharo ready!
>> 
>> missing
>> =======
>> - a better mc integration
>> - a cypress compatible fileout format
>> - complete interaction with the git protocol
>> - a direct way to commit stuff
>> 
>> as always my time is somewhat limited as well and we're the only two 
>> developers working on it...
>> 
>> The current work is available here:
>> http://ss3.gemstone.com/ss/FSGit-Experimental.html
>> https://github.com/dalehenrich/FSGit
> 
> That's great news, Camillo!
> 
> Is it at all possible to try separate (or keep separate) the core of
> the Git-facing stuff from the UI code? Like - and I say this without
> having looked at the structure of FS-Git, so feel free to yell at me
> if necessary - keeping the UI code in a separate package: FSGit-Core
> and FSGit-UI or whatever.

there won't be any UI code, and there isn't any so far :)
for the time being I will revamp the old MCGit interface, which simply
wraps around a certain fileout format to recreate the mc snapshots..

> When moving code between Squeak and Pharo this is by far the most
> painful part of the port. Well, it's not just Squeak that I'm thinking
> of: so many projects would be useful in headless circumstances, and it
> would be really nice to be able to not depend on UI code when you
> don't need it.
> 
> (Having had a look, I see that GitSmartHtppProtocol might have a typo
> in its name?)

yes indeed a typo (blush) :P

Reply via email to