yeap I actually had to use gist to backup an method because smalltalkhub freaked out to me once more. For a strange reason I keep using pastebin even though I have gist account because I keep forgetting about it :D
STH is not useless and most of the time works and get the job done. Also is simpler to learn for people that are unfamiliar with version control. Git is simple enough. The problem with STH is when it has a mental breakdown and of course when you want to commit and STH is not working. So I cannot recommend STHUB personally. Besides git and github being more reliable and more powerful, I really like its design, its simple , efficient and powerful. Also github gives a lot more visibility to projects and that means more visibility to Pharo. Its definetly a win - win situation at least for me. On Fri, Sep 19, 2014 at 1:08 PM, p...@highoctane.be <p...@highoctane.be> wrote: > On Fri, Sep 19, 2014 at 11:32 AM, kilon alios <kilon.al...@gmail.com> > wrote: > >> I have been told that there are some problem with gitfiletree that make >> it not recommended for public consumption and recommendation to newcomers. >> >> I have been using not gitfiletree but filetree alone for the past week >> for my project Ephestos, because I am ok commiting to git via terminal/ >> >> https://github.com/kilon/phEphestos >> >> I have to congratulate people behind filetree it has been a smooth ride >> so far.I had no problems with it at all and I am using git in terminal for >> doing all the git commits and push etc. >> >> filetree also has been very succesful at some major refactoring I have >> done to Ephestos, I had to change the name of an entire class and I had to >> change methods to other classes . Filetree did an excellent job not just >> with the export to st file but actually git was able to see which files >> were deleted and which were renamed. >> >> That meant I did not have to do any git rm . >> >> However I do need to git add every time I add a new method or filetree >> creates a new file. Usually that is not a problem because I can see what >> files are not tracked by git with git status and copy paste their paths to >> git add. >> >> So I will say overall my commits have been a process of saving in >> monticello , git add, git commit and git push which exactly the same >> process I have used for when I was and still coding in python. >> >> So thank you for this tool , I got fed up with the slow downs of >> Smalltalkhub and all its problems and it feels great to be back at using >> github :) >> > > I'd agree to that thing. Took me a while but now the Git based workflow > just feels better. > Also useful is storing snippets as gists. > Git has won, let's embrace that. > This doesn't mean that STH is not useful as a project repository. MCZs are > still the main artifact. > > >> I will keep testing for a couple a months and then completely move to >> github . The only thing I noticed is that sometimes monticello slows down >> but that may well be a problem with Pharo 4. >> > > >
