Could you give examples of code searches that you would be able to do in the history.
I think that for searching the history of a method or class, it is simpler (and faster) to do it in git than it is to do it in monticello. On Tue, Jul 26, 2016 at 1:31 PM, Dimitris Chloupis <kilon.al...@gmail.com> wrote: > Github has a search code facility , unless you mean something else. We > could take advantage of that and unite it with our ability to browse > implementors and classes. There is no limit how deeply we can integrate > with git and github and we can extend both via Pharo to make them more > Pharo friendly. > > On the subject of smalltalkhub it was always of question who will maintain > it. But is one thing to want something another to take control and > responsibility for it. None stoping anyone from contributing to anything. > Problem is sthub will need a ton of work to be a good alternative to > github. > > On Tue, 26 Jul 2016 at 01:36, Sean Glazier <sglazier...@gmail.com> wrote: > >> Thank you, Peter for documenting that :-). While I think git tools are >> OK, my opinion though is that Smalltalk hub should be moved forward as >> well. At cincom the Store experience started out painful and it has its >> quirks, but one of the advantages is that I could write tools to do things >> like browse senders and implementors in the repository. I git you are >> working with files and text and it does not have the notion of classes and >> methods and the value of being able to see the history of the class / >> methods. It is valuable when needing to understand not just the current >> implementation but where it came from. In Store, I could search and see >> when a method was present of a class and in what version lets say it got >> dropped unintentionally for instance. Even more important I think is to >> also note thing like renames and in cincom namespace renames and moves. >> I was working a while back on a way to have a persistent diary for a >> class that could note these histories and maintained and more importantly >> searchable from the image. >> I wrote tools too, to attach to a number of databases (repositories) and >> search for classes and the comments. Helpful when you are searching to see >> if someone else has solved a problem before. Git tools can tell you a lot >> about the repository you are publishing to and comparing code etc. But it >> does not help you to search across repositories and the data. >> >> I know this idea is a tall order. If we improved our tools to beable do >> this, no matter what the repository is behind it, that would be very >> helpful and powerful. I think it is a challenge in git because it is >> dealing with text and does not have a notion of what a class is etc. If we >> continue and put in more powerful search abilities, it will require using >> different paradigm in representing code so we can do more powerful things >> with the repository. We can browse the class without loading it but that >> gets us only so far. >> >> Just my 0.02 ;-) >> >> >> >> Kind Regards, >> >> Sean Glazier >> >> >> On Mon, Jul 25, 2016 at 1:28 PM, Peter Uhnak <i.uh...@gmail.com> wrote: >> >>> Hi Juraj, >>> >>> I've finally forced myself to finish a guide on using gitfiletree: >>> https://www.peteruhnak.com/blog/2016/07/25/how-to-use-git-and-github-with-pharo/ >>> so hopefully it will be of some use to you. >>> >>> Couple of notes: >>> * GitFileTree loaded from Catalog still doesn't work in Pharo 6, >>> so use the script Thierry provided >>> * There's some pain associated with some operations (e.g. >>> merging, loading), this will be addressed sooner or later by IceBerg, which >>> is hopefully the future of git in Pharo ( >>> https://github.com/npasserini/iceberg ) >>> >>> Peter >>> >>> On Mon, Jul 25, 2016 at 11:47:24AM -0400, Juraj Kubelka wrote: >>> > Hi Alexandre, >>> > >>> > I will first give a try. I think once the Pharo community moves to >>> GitHub, it will help to all. It could be painful, but SmalltalkHub is also >>> painful and we are loosing other opportunities that GitHub service offers. >>> > >>> > I agree that it could be painful. I am fine using external GIT tools. >>> Even for Java (or other) projects I use external GIT tools. The important >>> is that we can easily deploy projects and people can load it (,e.g., >>> Catalog Browser). >>> > >>> > Cheers, >>> > Juraj >>> > >>> > > On Jul 25, 2016, at 09:14, Alexandre Bergel <alexandre.ber...@me.com> >>> wrote: >>> > > >>> > > Hi Juraj, >>> > > >>> > > Although I find very appealing to work with Git, it is still very >>> painful. Some of the issues I feel right now: difficult of merging, >>> checking for source code differences, there is unfortunately a difference >>> between installing using Metacello and cloning a repository, … >>> > > We can discuss it if you want (I am back in Chile). >>> > > >>> > > Alexandre >>> > > >>> > > >>> > >> On Jul 25, 2016, at 8:41 AM, Juraj Kubelka < >>> juraj.kube...@icloud.com> wrote: >>> > >> >>> > >> Hi, >>> > >> >>> > >> can you point me to a latest (best) way to use GitHub for Pharo >>> projects (Pharo 6)? >>> > >> >>> > >> Is the GitFileTree project the way to use it? >>> > >> >>> > >> How does ConfigurationOf change? >>> > >> >>> > >> Thanks! >>> > >> Juraj >>> > > >>> > > -- >>> > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > > Alexandre Bergel http://www.bergel.eu >>> > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > > >>> > > >>> > > >>> > > >>> > >>> > >>> >>> >>
