Hi Offray,

I have not had a look at your code, but I have the impression that the tricky 
part is getting the data. I guess you can open a repository, get all the files, 
and get the data from a .mcz file. When you click on the ‘Browse’ button in the 
Monticello browser, you can see all the classes. Once you have the model, then 
plotting the things is quite trivial.

Have you found the right combination to programmatically inspect a .mcz file? 

Cheers,
Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Sep 22, 2014, at 9:15 PM, Offray Vladimir Luna Cárdenas <off...@riseup.net> 
wrote:

> Hi,
> 
> I'm working on the first version of my draft article about Pharo, wrote 
> inside Pharo itself. I would like to illustrate the process of learning and 
> building the software by making some graphs of the history of the Monticello 
> repository and I'm wondering how difficult this could be. I'm thinking in 
> something like:
> 
> - A bar char with the amount of commits per day since the repo existed.
> - Number of methods in the package.
> - Total lines of code
> 
> Any advice about how to use Moose/Roassal to create a "selfie" of the 
> project's history is welcomed.
> 
> The SmalltalkHub repository is here:
> 
> http://smalltalkhub.com/#!/~Offray/Ubakye/
> 
> Also I have acknowledge the contribution of the Pharo/Moose/Roassal 
> communities, but I'm wondering if there is any custom about how to do it. As 
> soon as I have a more workable draft I will be sharing the link.
> 
> Thanks again,
> 
> Offray
> 

Reply via email to