# HG changeset patch # User paulb # Date 1128380727 0 # Node ID 2fa5fb4ba21a2513294ed3e341298a7d4d73516e # Parent 6e64e6d7aea004c5f568e70b49643ee1c192fda5 [project @ 2005-10-03 23:05:27 by paulb] Updated the documentation to describe the updated VerySimple example, along with "macro" attributes. diff -r 6e64e6d7aea0 -r 2fa5fb4ba21a docs/Web-resource.html --- a/docs/Web-resource.html Mon Oct 03 23:04:48 2005 +0000 +++ b/docs/Web-resource.html Mon Oct 03 23:05:27 2005 +0000 @@ -1,23 +1,18 @@ - -
+ -With a completed template after the design, -structure annotation and selector annotation, we may now write a Web +structure annotation and selector annotation, we may now write a Web resource which will expose our form as a Web application, allowing users to input information and to manipulate that information using their Web browser. Whilst XSLForms is just a normal Python package which can be used from many kinds of programs and environments, we -shall concentrate on using the built-in WebStack +shall concentrate on using the built-in WebStack support to build a WebStack application around our form template.
structure_output.xsl
-
-
-
+
The class also has a method which resembles the typical respond
-method of normal WebStack
+method of normal WebStack
resources: the respond_to_form
method is, in fact, a
special version of that method providing ready-to-use information about
the form (or forms) being edited.
We should now have an application which can be deployed and tested using the usual WebStack techniques. However, more advanced templates can be designed, and we shall consider multiple-choice -fields in the next activity in the development process.
- - +fields in the next activity in the development process. +