Forum OpenACS Development: XOwiki Code Metrics

Collapse
Posted by Malte Sussdorff on
Is there any way to specify which branch the code metrics and package information is collected from ?
Collapse
2: Re: XOwiki Code Metrics (response to 1)
Posted by Malte Sussdorff on
The code is very picky :).

Every adp include has to start on a new line and you need to add the includes in HTML mode.

Not to mention the fact that it is a PITA to work with XOwiki if your browser is in German as the OacsFS/lang/de.js file has an error so whenever you hit edit an error message pops up.

But great that it is there, I will start writing about future plans to the packages we work on.

Collapse
Posted by Malte Sussdorff on
Yikes... When you edit the page (without changing the code for the includes) and hit submit, all changes are lost as there is an error due to the fact that the adp includes are not on a seperate line anymore. Grr... lost all my content again....

For those who do not want to run into the same problems, copy paste the code from below in HTML mode. After that you can start editing the page.

{{adp /www/templates/info-file {package_key contacts}}}

{{adp /www/templates/bug-tracker {package_key contacts}}}

{{adp /www/templates/metrics {package_key contacts}}}

Collapse
Posted by gustaf neumann on
sorry for that. i made the parsing of the adp entries more flexible, one can write now e.g.
{{adp portlets/categories {
    name {Table of Contents}
    open_page de:iMac}
}}
The closing parens should still end a line. get the updated version from cvs...
Collapse
3: Re: XOwiki Code Metrics (response to 1)
Posted by Malte Sussdorff on
Do we have an include for CVS commits? So we could specify "Show last 20 commits for this package on branch oacs-5-2"?
Collapse
5: Re: XOwiki Code Metrics (response to 1)
Posted by Vinod Kurup on
Is there any way to specify which branch the code metrics and package information is collected from ?

No, the code-metrics and info-file includes gather data from the running code base.

In order to get info from other branches, we'd need to get that info from CVS, meaning we'd have to have a nice way to access CVS information. The info-file include wouldn't be hard to do, but the code metrics would involve checking out full versions of each branch so we could do counts of procs, lines and pages.