By Richard Li and Yon Feldman
OpenACS docs are written by the named authors, and may be edited
@@ -10,7 +10,7 @@
our product will be useful long after the current people building and
maintaining it are around. Following are some standards and guidelines
that will help us achieve this goal:
-
+
All PL/SQL code must be well documented. We must write code that
is maintainable by others, this is especially true in our case
because we are building an open source toolkit than anyone can
@@ -22,7 +22,7 @@
as is possible given the nature of team development. This means
carrying style and other conventions suchs as naming within an
application, not just within one file.
-
Encapsulation of related fuctionality is key to maintainability
and upgradeability of our software. Try to bundle your code into
packages
@@ -141,7 +141,7 @@
click protection, that is, tehy have already gotten an
object_id and now they want to create the object with
that object_id.
-
Some general style guidelines to follow for the purpose of
consistency across applications.
