[OT] Check out Gource!

>> On 14.08.2010, at 15:08, David Faught wrote:
>>> Yes, pun intended.  Check out.  Get it?  Gource is a Google Code
>>> project that visually presents the history of a source version control
>>> system.  Maybe someone industrious could figure out how to feed in a
>>> few historical changes files from Squeak ...
>>>
>>> http://code.google.com/p/gource/
>
> On Sat Aug 14 14:09:59 UTC 2010, Bert Freudenberg wrote:
>> Should be rather simple:
>>
>> http://code.google.com/p/gource/wiki/CustomLogFormat
>
> To make it interesting, maybe a Squeak method should equate to the
> gource "file" in the Custom Log Format.
> It looks like more than the changes file would have to be used.  There
> are a couple of non-obvious things, like where the path of the "file"
> comes from.
> To get what I originally envisioned, apparently the real trick is in
> picking a good set of change files.  I never really browsed through
> the
> complete changes file much before, and it looks like there is a lot
> less there than what I naively thought.  I was envisioning "The
> Complete Squeak History" but that seems unrealistic now.  Maybe.

> On 14.08.2010, at 18:17, David Faught wrote:
>
>>> On 14.08.2010, at 15:08, David Faught wrote:
>>>> Yes, pun intended.  Check out.  Get it?  Gource is a Google Code
>>>> project that visually presents the history of a source version control
>>>> system.  Maybe someone industrious could figure out how to feed in a
>>>> few historical changes files from Squeak ...
>>>>
>>>> http://code.google.com/p/gource/
>> On Sat Aug 14 14:09:59 UTC 2010, Bert Freudenberg wrote:
>>> Should be rather simple:
>>>
>>> http://code.google.com/p/gource/wiki/CustomLogFormat
>> To make it interesting, maybe a Squeak method should equate to the
>> gource "file" in the Custom Log Format.
>> It looks like more than the changes file would have to be used.  There
>> are a couple of non-obvious things, like where the path of the "file"
>> comes from.
>> To get what I originally envisioned, apparently the real trick is in
>> picking a good set of change files.  I never really browsed through
>> the
>> complete changes file much before, and it looks like there is a lot
>> less there than what I naively thought.  I was envisioning "The
>> Complete Squeak History" but that seems unrealistic now.  Maybe.
> Class category and name might already be sufficient to get a nice visualization, e.g.
>
> Collections/Sequenceable/Heap.st
>
> for class Heap in category Collections-Sequenceable. This would match in other languages, which often use one file per class.
>
> - Bert -
>