Topo team of enterprise software system to provide a lot of very useful code management capabilities, by means of these features, the software team can improve their work efficiency, Topo code management system include: the depth of view code, code statistical analysis, code review and automated online Construction of four main functions. This article to tell you about the code statistics.
A: Code statistics portal system in the Topo code module, the system's code base to allow for any startup code to any directory statistical analysis, and the system automatically saves all statistics history.
Of course, Topo system statistical functions of the authority also do well to consider the design, only the project manager can start the code statistics and the maintenance of existing code statistics, project members can only view statistics
Click the top right corner of the functions from the image above the navigation bar "statistical analysis", we can view the previous results, from the bottom of the "boot code statistics", we can always view the directory of the current boot code statistical analysis.
II: statistical parameters directory configured in the selected statistics, click on "start code statistics", will enter the statistical parameter configuration interface, as shown below:
We can give a name from this statistic, of course, the system automatically based on the current statistics of the directory name as the default value. In addition, the statistics, can have set up this statistic which files need to exclude, for example, sql file not want to be statistical, then the only exception in the statistics file type "*. sql" then, the system allows you to exclude any file under any directory match the name of freedom. The system default is empty all the support that statistics Statistics files.
Configured, click "OK" to start statistics.
III: Statistics in the state diagram we can see results display interface, the above operation of the "/ trunk" Statistics are statistics in the state, in general, statistical time-consuming with the specified number of files in library and number of related changes to these files, so if a larger statistics and larger changes in the code base directory of history, time-consuming and would be more longer.
Statistics for a long time-consuming, the user may well start to leave the interface after enumeration, and then check back over time statistics is done, leave the interface and does not interrupt statistical process. Of course, if you want to immediately see results, you do not always hit the "Refresh" button, the system provides an example close the "open automatically refresh," this feature, so you can see the statistics at any time if completed.
Four: the maintenance of statistics to show us the figure of "/ trunk" situation after the completion statistics, all the statistical results are permanent preservation system, so that project members can always see the previous code results.
When the statistics is large, the system automatically paged queries on these results, and provides a path of sorting and filtering to find statistics and other functions, so you can easily find the need to see the statistical results.
The results of previous surveys, the project manager can do the following two operations:
1: re-start statistics.
Each statistic is always the latest version of the code from the start statistics, and statistics are automatically recorded after the current results of the latest version. Statistics started again, the system automatically records the last of the statistical parameters, of course, when the project manager can also be adjusted again before restarting the parameters of Statistics.
2: Delete the statistics system in Topo, statistics kept on the server as a separate file directory, with the increase in the number statistics, statistical results will take up more disk space, if you want to clean up some hard disk space, then the project manager You can also delete the previous statistics are no longer needed.
Friday: After the above results see a few simple clicks, we can see the results of statistical analysis of the code, and as an example, we GoogleCode mpmath code in open source projects carried out a statistical library. Click on the table title bar "libmp", you can see the results of statistical analysis of the following:
1: The total number of rows the code changes over time:
2: The code changes the code intensity changes in the number of lines compared with the code, the code changes can be seen that intensity, to determine the stability of the code.
3: The contribution of the developer:
Contribution of each developer's code, as well as their recent activities of the code 1 year.
4: Developer map submission code
The above is a graphical way to show the last 1 year for each developer's code activity, apparently too much red dot code on behalf of the developer activities frequently.
5: Number of code changes in the situation head office
The results of the previous code with the total number of rows is different and refers to the current statistics of the successive changes in the code directory number of lines of code total. For example: If a file the first 100 lines of code, delete the first 20 lines of code, the second increase of 30 code, then the final total number of lines of code is 100-20 +30 = 110 lines, but the code changes in the number of lines is 100 +20 +30 = 150 lines.
6: Code to submit weekly statistical situation:
7: other statistical elements:
Statistics, such as by file directory, according to the statistical functions of a person is no longer presented here, on these features are interested, to apply for trial Topo it.