reflecting codebases

[GoogleCodeExporter]

I'd love to use gource for showing the evolution of Pitivi, but the fact that 
file nodes "time out" and fade away from the display after a while is a 
dealbreaker.

I want gource to show both contributor activity and codebase complexity. This 
means:
- not removing file nodes unless the file was actually removed from the source 
tree
- analyze all the files right at the start and show them as nodes, instead of 
waiting for commit activity on a file to show it in the graph

That would make gource a killer analysis app for me.

Original issue reported on code.google.com by nekoh...@gmail.com on 19 May 2012 at 9:29

[GoogleCodeExporter]

...aaaand I should have read the man page better :) turns out there is the "-i 
0" parameter (I was searching for words such as "timeout").

However, I guess the second point still stands as a possible enhancement 
request: with "-i 0" analyze all files as a batch from the start instead of 
waiting for them to be touched.

Original comment by nekoh...@gmail.com on 19 May 2012 at 9:55

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Hi,

No worries. That -i flag is one of the most common that people want to adjust 
so I might try to make it a bit easier to find. I may add some of these things 
on an toggle-able head up display in the future.

There is another old request to implement scene population that I haven't 
gotten around to. I agree it would be nice a feature.

Cheers

Andrew

Original comment by acaudw...@gmail.com on 23 May 2012 at 7:02

• Changed title: reflecting codebases
• Changed state: Done
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

If most users want to use "no timeout" for files, maybe it could be a candidate 
to become the default setting. Just some food for thought ;)

Original comment by nekoh...@gmail.com on 23 May 2012 at 3:34

• Added labels: ****
• Removed labels: ****