Camillo needs to hit you around the head with a command line. You haven't used it. You've heard several people who have used both Monticello and git extensively say that git beats the crap out of Monticello. Go and learn git properly. THEN come back and maybe we can have a conversation.
I always using git from command line. And let me remind you it was me who created Cog mirrors on gitorious.. so, you shoot into the sky here. But i want more than that.. and why i happy to see that github proposes more on top, i do not really see how you can integrate that with usual workflow of smalltalk developer (means navigating/debugging living code in image).
OK, fair enough. I had indeed forgotten about your gitorious work, and in fact if I recall correctly you tried to pushed the VM folk into moving from subversion to git. My apologies.
Oh yes and me too. Because the git model is open and svn not.
okay, lets throw away MC & stuff, migrate everything on file-based file-per-method git repository and then navigate diffs on github, and trying to find senders or implementors of selector using web browser .
I do believe you ought to take a moment and go read the archives. Also, I happen to nearly violently disagree with the file-per-method approach, but that's an entirely different kettle of fish.
But you know what, just forget it. It's not your problem, other people are already solving the problem, and one day hopefully you'll forget all about this while quietly your tools happily use git under the hood, where you neither know nor care.
I actually don't care where files stored , in what format and what service it using. I want to make my life easier integrating those services with image, so i could, without switching contexts (like between image/web browser), do my work faster and more efficient.
Yes, agreed.
So if I can summarise,
* git is not an answer for you because you don't care about the format source is stored in. * git is an answer for me because it immediately gives you a fantastic user interface and hooks into just about everything. * github is not an answer for you because it doesn't provide you with any tools more advanced than a diff * github is an answer for me because you can always implement your own hooks for triggering CI, arbitrary code analysis, etc. Github's commit API will let you give the green light or red light to any commit so you can see at a glance how good a pull request is.
But of course there's nothing stopping one using github OR an-image tools. (Or tools that produce custom images based on github commits that run analyses and then persist somewhere so you can (a) see the analyses immediately and (b) play around with the code.
Mainly I think it's a mistake to reinvent tech _just because_ you simply must work in an image. That's the core behind my moaning. (And yes, I am working on addressing these issues, so I'm not _just_ moaning.)
frank