2016-11-07 10:43 GMT+01:00 Dimitris Chloupis <kilon.al...@gmail.com>:
> " > Aready done. Look for Jan Vrany tools or Cuis. IMHO, not convincing to me > (Jan's format is even more conflict-oriented than Filetree metadata, but it > is a design goal). Cuis git repository is a mess to me; very hard to build > a coherent 'rebuild a new Cuis here' process on it like I routinely do on > Pharo." > > > Cuis I downloaded it, does not seem to have such a tool, talking about > auto export of code. > Cuis basically delegates everything to git and use one file per package. > > Jon Vrany which I found here > > https://github.com/janvrany?tab=overview&from=2015-12-01&to= > 2015-12-31&utf8=✓ > > appears that he has not done any Smalltalk coding for more than a year and > I could not find one repo that has such tool. > He has a nice lib interface targetting both mercurial? and git; a kind of ancestor to Pharo libgit effort. Mainly targeted at Smalltalk/X > > Just to make it clear what I am proposing here is not just a replacement > for filetree but I complete bypass of Monticello. I have been a frequent > visitor of the pharo mailing lists for more than 5 years not I never head > of such a thing. It is also the first time I mention this idea as well. I > had in my mind for so long but it has been a low priority because filetree > worked without any issues other than browsing the code in code editor and > online Github. > > "I've seen over the years many, many attempts at replacing the filetree > format. I used to contest and debate, now I just let them go and die a few > months later. Because none of the alternatives are clearly superior, and it > is not worth the effort to reimplement." > > Well if by dying you mean none else but me will use it, most certainly you > are correct. But all my projects are foremost personal I never make > something for public consumption other than offering a helping hand with > Pharo documentation. > I mean really dying: like in even the creator isn't using it anymore. You really need good code to hold something alone over the years, something that keeps working across Pharo versions as they evolve with minimum changes. Trust me on that! One strategy is to base yourself on stable core components of Pharo. Some stuff in Pharo changes a lot, some has been very stable since Pharo 3 (or upgraded very nicely while maintaining the same API). You may be better off reimplementing stuff changing too fast / or too buggy in their current incarnation, just to decouple yourself: when you go for a self/alone project, your goals do not align with the main image. > > I am perfectly ok with the fact that people do not use my projects. > > And foremost its not as if a tool that would bypass monticello and > filetree and gitfiletree and iceberg has any chance to be used when for > months now the mailing list has been talking about Iceberg. > > Its clear that I want to live outside the image. > > Its clear that others want to live inside the image. > > Its clear that I am a tiny minority , if not the only one. > I think you're less radical than you believe :) Thierry
