Index: openacs-4/packages/acs-core-docs/www/style-guide.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/style-guide.adp,v diff -u -r1.4 -r1.5 --- openacs-4/packages/acs-core-docs/www/style-guide.adp 25 Apr 2018 08:38:28 -0000 1.4 +++ openacs-4/packages/acs-core-docs/www/style-guide.adp 3 Sep 2024 15:37:32 -0000 1.5 @@ -1,7 +1,11 @@ -{/doc/acs-core-docs {ACS Core Documentation}} {OpenACS Style Guide} +{/doc/acs-core-docs/ {ACS Core Documentation}} {OpenACS Style Guide} OpenACS Style Guide + Motivation

Why have coding standards for OpenACS? And if the code works why change it to adhere to some arbitrary rules?

Well, first lets consider the OpenACS code base (all this as of December 2003 and including dotLRN). There are about 390,000 lines -of Tcl code, about 460,000 lines of sql (in datamodel scripts and +of Tcl code, about 460,000 lines of SQL (in datamodel scripts and .xql files), about 80,000 lines of markup in .adp files, and about 100,000 lines of documentation. All told, just about a million lines of "stuff". In terms of logical units there are @@ -98,8 +102,8 @@ 0.1Creation12/2003Jeff Davis -

($‌Id: style-guide.xml,v 1.4 2017/08/07 -23:47:54 gustafn Exp $)

+
($‌Id: style-guide.xml,v 1.4.2.1 2019/11/22 +16:30:46 gustafn Exp $)