Index: openacs-4/packages/acs-core-docs/www/tutorial-pages.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-pages.html,v diff -u -N -r1.42 -r1.43 --- openacs-4/packages/acs-core-docs/www/tutorial-pages.html 11 Dec 2010 23:36:32 -0000 1.42 +++ openacs-4/packages/acs-core-docs/www/tutorial-pages.html 31 Jul 2011 23:11:46 -0000 1.43 @@ -1,51 +1,51 @@ - -Creating Web Pages
Alex logo
Prev Chapter 8. Development Tutorial Next

Creating Web Pages

by Joel Aufrecht

+ +Creating Web Pages
Alex logo
Prev Chapter 8. Development Tutorial Next

Creating Web Pages

by Joel Aufrecht

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

Install some API

As a workaround for missing content-repository functionality, copy a provided file into the directory for tcl files:

-    cp /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/files/tutorial/note-procs.tcl /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/tcl/

To make this file take effect, go to the APM and choose "Reload changed" for "MyFirstPackage".

Page Map

Our package will have two visible pages. The first shows a list of all objects; the second shows a single object in view or edit mode, and can also be used to add an object. The index page will display the list, but since we might reuse the list later, we'll put it in a seperate file and include it on the index page.

Figure 8.5. Page Map

Page Map

Build the "Index" page

Each user-visible page in your package has, typically, - three parts. The tcl file +

Install some API

As a workaround for missing content-repository functionality, copy a provided file into the directory for tcl files:

+    cp /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/files/tutorial/note-procs.tcl /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/tcl/

To make this file take effect, go to the APM and choose "Reload changed" for "MyFirstPackage".

Page Map

Our package will have two visible pages. The first shows a list of all objects; the second shows a single object in view or edit mode, and can also be used to add an object. The index page will display the list, but since we might reuse the list later, we'll put it in a seperate file and include it on the index page.

Figure 8.5. Page Map

Page Map

Build the "Index" page

Each user-visible page in your package has, typically, + three parts. The tcl file holds the procedural logic for the page, including TCL and database-independent SQL code, and does things like check permissions, invoke the database queries, and modify - variables, and the adp page - holds html. The -postgres.xql - and -oracle.xql files contains + variables, and the adp page + holds html. The -postgres.xql + and -oracle.xql files contains database-specific SQL. The default page in any directory is - index, so we'll build that - first, starting with the tcl file:

[$OPENACS_SERVICE_NAME postgresql]$ cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackages/www
-[$OPENACS_SERVICE_NAME www]$ emacs index.tcl

Paste this into the file.

ad_page_contract {
+      index, so we'll build that
+      first, starting with the tcl file:
[$OPENACS_SERVICE_NAME postgresql]$ cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackages/www
+[$OPENACS_SERVICE_NAME www]$ emacs index.tcl
Paste this into the file.
ad_page_contract {
     This is the main page for the package.  It displays all of the Notes and provides links to edit them and to create new Notes.
 
     @author Your Name (you@example.com)
     @cvs-id $Id$
 }
 
 set page_title [ad_conn instance_name]
-set context [list]
Now index.adp:
<master>
-  <property name="title">@page_title;noquote@</property>
-  <property name="context">@context;noquote@</property>
-<include src="/packages/myfirstpackage/lib/note-list">
The index page includes the list page, which we put in /lib instead of /www to designate that it's available for reuse by other packages.
[$OPENACS_SERVICE_NAME www]$ mkdir /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/lib
-[$OPENACS_SERVICE_NAME www]$ cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/lib
-[$OPENACS_SERVICE_NAME lib]$ emacs note-list.tcl
template::list::create \
+set context [list]
Now index.adp:
<master>
+  <property name="title">@page_title;noquote@</property>
+  <property name="context">@context;noquote@</property>
+<include src="/packages/myfirstpackage/lib/note-list">
The index page includes the list page, which we put in /lib instead of /www to designate that it's available for reuse by other packages.
[$OPENACS_SERVICE_NAME www]$ mkdir /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/lib
+[$OPENACS_SERVICE_NAME www]$ cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/lib
+[$OPENACS_SERVICE_NAME lib]$ emacs note-list.tcl
template::list::create \
     -name notes \
     -multirow notes \
-    -actions { "Add a Note" note-edit} \
+    -actions { "Add a Note" note-edit} \
     -elements {
 	edit {
 	    link_url_col edit_url
 	    display_template {
-		<img src="/resources/acs-subsite/Edit16.gif" width="16" height="16" border="0">
+		<img src="/resources/acs-subsite/Edit16.gif" width="16" height="16" border="0">
 	    }
 	    sub_class narrow
 	}
 	title {
-	    label "Title"
+	    label "Title"
 	}
 	delete {
 	    link_url_col delete_url 
 	    display_template {
-		<img src="/resources/acs-subsite/Delete16.gif" width="16" height="16" border="0">
+		<img src="/resources/acs-subsite/Delete16.gif" width="16" height="16" border="0">
 	    }
 	    sub_class narrow
 	}
@@ -62,11 +62,11 @@
                mfp_notesx n
         where  n.revision_id = ci.live_revision
     } {
-	set edit_url [export_vars -base "note-edit" {item_id}]
-	set delete_url [export_vars -base "note-delete" {item_id}]
-    }
[$OPENACS_SERVICE_NAME lib]$ emacs note-list.adp
<listtemplate name="notes"></listtemplate>
You can test your work by viewing the page.
Create the add/edit page.  If note_id is passed in,
-      it display that note, and can change to edit mode if appropriate.  Otherwise, it presents a form for adding notes.
[$OPENACS_SERVICE_NAME lib]$ cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/www
-[$OPENACS_SERVICE_NAME www]$ emacs note-edit.tcl
ad_page_contract {
+	set edit_url [export_vars -base "note-edit" {item_id}]
+	set delete_url [export_vars -base "note-delete" {item_id}]
+    }
[$OPENACS_SERVICE_NAME lib]$ emacs note-list.adp
<listtemplate name="notes"></listtemplate>
You can test your work by viewing the page.
Create the add/edit page.  If note_id is passed in,
+      it display that note, and can change to edit mode if appropriate.  Otherwise, it presents a form for adding notes.
[$OPENACS_SERVICE_NAME lib]$ cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/www
+[$OPENACS_SERVICE_NAME www]$ emacs note-edit.tcl
ad_page_contract {
     This is the view-edit page for notes.
 
     @author Your Name (you@example.com)
@@ -83,7 +83,7 @@
 } -new_request {
     auth::require_login
     permission::require_permission -object_id [ad_conn package_id] -privilege create
-    set page_title "Add a Note"
+    set page_title "Add a Note"
     set context [list $page_title]
 } -edit_request {
     auth::require_login
@@ -94,7 +94,7 @@
 
     set title $note_array(title)
 
-    set page_title "Edit a Note"
+    set page_title "Edit a Note"
     set context [list $page_title]
 } -new_data {
     mfp::note::add \
@@ -104,15 +104,15 @@
 	-item_id $item_id \
 	-title $title
 } -after_submit {
-    ad_returnredirect "."
+    ad_returnredirect "."
     ad_script_abort
-}
[$OPENACS_SERVICE_NAME www]$ emacs note-edit.adp
<master>
-  <property name="title">@page_title;noquote@</property>
-  <property name="context">@context;noquote@</property>
-  <property name="focus">note.title</property>
+}
[$OPENACS_SERVICE_NAME www]$ emacs note-edit.adp
<master>
+  <property name="title">@page_title;noquote@</property>
+  <property name="context">@context;noquote@</property>
+  <property name="focus">note.title</property>
   
-<formtemplate id="note"></formtemplate>
And the delete page.  Since it has no UI, there is only a
-     tcl page, and no adp page.
[$OPENACS_SERVICE_NAME www]$ emacs note-delete.tcl
ad_page_contract {
+<formtemplate id="note"></formtemplate>
And the delete page.  Since it has no UI, there is only a
+     tcl page, and no adp page.
[$OPENACS_SERVICE_NAME www]$ emacs note-delete.tcl
ad_page_contract {
     This deletes a note
 
     @author Your Name (you@example.com)
@@ -127,7 +127,7 @@
 set title [item::get_title $item_id]
 mfp::note::delete -item_id $item_id
 
-ad_returnredirect "."
+ad_returnredirect "."
 # stop running this code, since we're redirecting
 abort
Prev Home Next
Setting Up Database Objects Up Debugging and Automated Testing
docs@openacs.org
View comments on this page at openacs.org