Index: openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html,v diff -u -r1.48.2.11 -r1.48.2.12 --- openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html 23 Jun 2016 08:32:45 -0000 1.48.2.11 +++ openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html 19 Nov 2016 09:21:53 -0000 1.48.2.12 @@ -10,7 +10,7 @@
displaying objects and their properties
manipulating or acting on objects in some way (by creating, editing, linking, etc)
housing procedures, packages, data models and other prerequisite code Essentially, we want our files named in a fashion that reflects their purpose.
-Under the page root (and the template root if using the Style package): +Under the page root:
For naming files that enable a specific action on an object, use this format:
object-verb.extension
@@ -26,7 +26,7 @@
Thus, the page to edit a bookmark is /bookmarks/edit.tcl
.
For naming files that display the properties of a primary object - such as the bookmark object within the bookmark module - use this convention:
-
one.
extension
+one.extension
For example, the page to view one bookmark is
/bookmarks/one.tcl
. Note that no verb is necessary for display-type files.
@@ -55,7 +55,7 @@
ad-
description-procs.tcl
File names also appear within pages, as linked URLs and
-form targets. When they do, always use abstract
+form targets. When they do, always use abstract
URLs (e.g., user-delete
instead of
user-delete.tcl
), because they enhance maintainability.
@@ -219,4 +219,4 @@
Further standards for Tcl library files are under discussion; we plan to include naming conventions for procs. -