On Mon, Jul 25, 2016 at 06:33:48PM -0400, Sean Glazier 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.

While SmalltalkHub works for code storage, it is also just that, a storage.
Trying to run a service competing with the likes of GitHub, Bitbucket, or 
GitLab is frankly waste of resources that could be better invested into things 
that are relevant for the mission of Pharo.

> 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.

I've seen this argument many times and yet it is completely false.
You can actually retrieve the history of a single method even for languages 
that truly do use just files (C, ruby, …), although a fair bit of scripting 
would be required, but the history is there.
The used FileTree format that writes each method to a file makes this much more 
simpler.

> thing like renames and in cincom namespace renames and moves.

Funny that you mention renames, considering that SmalltalkHub cannot handle 
renames or track changes/moves across packages.

> 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.

class -> directory, method -> file makes it much more easier.
But even if it was all a dump into a single file, the bottom line is, it is 
always only a question of tooling.
After all, don't forget that whatever format you use, if you are storing it on 
hard drive it's in a file. You just have tools on top.

Peter

Reply via email to