yeap you definitely have a valid point there. Its not a huge loss, since smalltalk code is made to be viewed from inside the IDE anyway. The json formate used also makes it simpler to parse those files. So I can definitely see the logic behind it now. Well I can give it a try and see how it goes from there.
On Sat, Nov 2, 2013 at 11:37 PM, Frank Shearar <[email protected]>wrote: > On 2 November 2013 21:29, kilon alios <[email protected]> wrote: > > I have used Github for smalltalk projects back when I was still using > > Squeak. I just was filling out packages and manually copying the st > files to > > my git repo that I then committed to my Github account. It was the manual > > process of copying and triggering the git commit that I wanted to avoid. > > > > The one thing I dont like about FSGit is that it creates multiple files > per > > package. I would prefer a single file per package containing complete > > declarations of the classes for easier viewing and reviewing of code in > > Github. Is this possible or would I need to hack it ? > > Filetree turns the smallest semantic units - class definitions, method > definitions, etc. - into individual files. This is, from a versioning > perspective, the right thing to do. You don't get merge conflicts that > break anything larger than an individual method/class > definition/whatever. But it does come at a very large cost in that, as > you say, it ruins GitHub as a means of conveniently browsing code. > > Another option is to use Gitocello. It just dumps things out in chunk > format, as you can see here: https://github.com/frankshearar/Zippers > > And as you'll see, chunk format is hideous. > > frank > > > On Sat, Nov 2, 2013 at 5:42 PM, Sven Van Caekenberghe <[email protected]> > wrote: > >> > >> > >> On 02 Nov 2013, at 14:59, kilon alios <[email protected]> wrote: > >> > >> > So any information on how Pharo can be used with Github ? > >> > >> Just to assure you that it works, the whole of Pharo, the image itself, > is > >> completely on GitHub: > >> > >> https://github.com/pharo-project/pharo-core > >> > >> including all releases properly tagged ! > >> > >> Many people, including myself (http://github.com/svenvc), have Pharo > >> Smalltalk code on GitHub. > >> > >> It is just so that currently for most people this is a mirror, not the > >> primary repository. You’ll have to try and study the different > approaches > >> yourself to understand the finer points. > >> > >> Sven > >> > >> > >> > > > >
