Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml,v
diff -u -N -r1.52.2.1 -r1.52.2.2
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml 10 Jun 2016 07:35:08 -0000 1.52.2.1
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml 23 Jun 2016 08:32:46 -0000 1.52.2.2
@@ -12,14 +12,14 @@
This tutorial covers topics which are not essential to
creating a minimal working package. Each section can be used
independently of all of the others; all sections assume that
- you've completed the basic tutorial.
+ you've completed the basic tutorial.
Write the Requirements and Design Specs
Before you get started you should make yourself familiar with
the tags that are used to write your documentation. For tips on
editing SGML files in emacs, see .
- It's time to document. For the tutorial we'll use
+ It's time to document. For the tutorial we'll use
pre-written documentation. When creating a package
from scratch, start by copying the documentation template from
/var/lib/aolserver/openacs-dev/packages/acs-core-docs/xml/docs/xml/package-documentation-template.xml
@@ -82,7 +82,7 @@
Add the new package to CVS
Before you do any more work, make sure that your work is
protected by putting it all into cvs. The cvs
- add command is not recursive, so you'll have to
+ add command is not recursive, so you'll have to
traverse the directory tree manually and add as you go. (More on
CVS)
@@ -336,7 +336,7 @@
@@ -1434,7 +1434,7 @@
} ...
- You must not give your your form the same name that your page has. Otherwise HTMLArea won't load.
+ You must not give your your form the same name that your page has. Otherwise HTMLArea won't load.
Convert your textarea widget to a richtext widget and enable htmlarea.
The htmlarea_p
-flag can be used to prevent
@@ -1455,7 +1455,7 @@
ad_form
or you will have problems
displaying the content or handling the data manipulation correctly.
Depending on the data model of your package you either support a content format
- or don't. If you don't you can assume "text/html"
or
+ or don't. If you don't you can assume "text/html"
or
"text/richtext"
or "text/enhanced"
.
The relevant parts in your ad_form
definition are the
switches -new_data
, -edit_data
,
@@ -1474,7 +1474,7 @@
Now the correct values for my_input_field_2
and
format
are passed to the -new_data
and
- -edit_data
blocks which don't need to get touched.
+ -edit_data
blocks which don't need to get touched.
To make HTMLArea optional per package instance define a string parameter
UseWysiwygP
which defaults 0
for your
package using the APM.
@@ -1555,7 +1555,7 @@
Under the Manage section, click on Parameters
- It's fairly self-explanatory at this point. Create the
+ It's fairly self-explanatory at this point. Create the
parameters you want, and then access them in your code using the
parameter::get procedure.
@@ -1674,7 +1674,7 @@
Future Topics
- How to enforce security so that users can't
+ How to enforce security so that users can't
change other users records
How to use the content management tables so that
@@ -1685,7 +1685,7 @@
How to prepare pagelets for inclusion in other pages
How and when to put procedures in a tcl procedure library
More on ad_form - data validation, other stuff.
- (plan to draw from Jon Griffin's doc)
+ (plan to draw from Jon Griffin's doc)
partialquery in xql
How to use the html/text entry widget to get the
"does this look right" confirm page