History: CountLocsDev

• Where are we?

Whe have a simple bash command to do a count of LOCs over all relevant files:

find <tiki-base-dir> -type f -print0 -wholename "./templates_c" -prune\
-name "*.php" -o -name "*.sql" -o -name "*.css" -o -name "*.js" -o \
-name "*.tpl" -o -name "*.inc" | xargs -0 cat | pcregrep -cv \s*\n

As you can see, this counts just not empty lines.

pcregrep is a special grep-command evaluating the pattern as a Perl regular expression. The commandline-switch -c does a count and -v negates the regular expression.

• Where do we want to be?

It would be nice to have some script (maybe in doc/devtools) to automate this process and output some more differentiated information (effective LOCs, comments, how many in which type of file, etc.)

amette: A Perl script would be good!? Better ideas? Are there any tools out there, that could do the job? I evaluated sloccount, but that doesn't consider the files we want and can't be customized easily to do it.

• Who is working on what? (Priorities/goals/majors issues/roles)

Who is working here generally? Link UserPage.
amette

• Bugs
• RFEs
• tech support
• patches

  
  
  

List of other products with similar/interesting/related features.

Here I would like to see some "editorial" content. How do our features compare to others?

This is where new features being developed and only in CVS are documented. When the CVS becomes RC/official release, the info in the CVS docs is transferred to update the official docs (FeatureXDoc).

Where ideas can be exchanged, debated, etc. Interested people can subscribe to the wiki page and/or to these forums as they would a mailing list.