No of course not. That would have been a deal braker. Personally I prefer using Sourcetree to browser history of commits than using the pharo on board tools. Pharo is good on that respect, but sourcetree is better and smartgit I have used in the past. It also has nice visualisation for branches , merges etc. I have not shown these features in my video tutorial as I was planning to show them to a separate tutorial. I would not mind bypassing monticello completely since its usage is unnecessary at least to me with all these git tools that one can download and use for free. The same is true for other IDEs out there , generally people prefer using dedicate tools.
Usually dedicate tools are hard to beat this is why I believe modularising Pharo is extremely important as will make integrating external tools way easier. I think however that Roassal can be used to visualise in similar way the history as Sourcetree does. So pharo is not far from it but as always its a matter of someone doing the hard work. On Mon, Dec 1, 2014 at 12:21 PM, Hilaire <[email protected]> wrote: > Le 27/11/2014 11:29, kilon alios a écrit : > > My personal opinion on Github and Pharo is that it already works great > > with Pharo. The workflow with filetree is exactly the same as other > > languages that gives the added advantage that you can use all the > > powerful tools you use with other languages for commiting to git and > > github. I have not experienced any kind of issue of problem using github > > with Pharo nor my experience has been any worse than other languages. > > > > With git, don't you lost the capability to browse the history of changes > in your code? > > Hilaire > > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > >
