lazarus/components/fpweb/demo/fptemplate/README.txt
vincents e2d0fec11d fpweb: patch from Attila Borka (issue #13901)
* added note about minimal fpc version
* minor message changes

git-svn-id: trunk@20396 -
2009-06-04 08:29:52 +00:00

57 lines
2.2 KiB
Plaintext

These examples are demonstrating some uses of templates (with FPTemplate) when
generating HTML pages by CGI programs or Apache modules.
(Requires FPC versions past 4/30/2009 /revisions 13062 and later/)
The main idea is to leave the web page designing and look&feel to the web page
designers. Separating the web page design from the back end CGI/Apache
application makes it possible to design, change or redesign a whole website
without modifying a single line of code in the CGI/Apache application.
Back end programmers and web page designers can work parallel easily and
neither side needs extensive knowledge of the other (doesn't hurt, just not
necessary most of the time).
With all this said, none of the examples are focusing on nice look and feel in
their template designs, merely on demonstrating the functionality and use of
templates, template tags and template tag parameters with live applications.
Examples list:
1. /simpletemplate/*.*
The simplest template with one template tag in it to be replaced by the
CGI/Apache application when generating the response page -> {TagName1}
2. /tagparam/*.*
Demonstrating the set up and use of template tag parameter(s)
-> {+DATETIME [-FORMAT=MM/DD hh:mm:ss-]+}
3. /listrecords/*.*
Demonstrates the use of a template tag with multiple template tag parameters
to list multiple records, tables, lists, etc.
4. /fileupload/*.*
Demonstrates uploading file(s) to a web server with the help of a CGI program
or Apache module by using so called "multipart" html forms.
See README.txt
5. /sessions/*.*
These examples demonstrate three different ways to maintain and use sessions
when building web sites that need to carry over or store information to
following web pages, differentiate between visitors, etc.
5.a. /sessions/cookiesessions-auto/*.*
See README.txt
5.b. /sessions/cookiesessions-login/*.*
See README.txt
5.c. /sessions/urlsessions-login/*.*
See README.txt
Note: All of the examples have both CGI and Apache subdirectories. The web
modules (webmodule.pas, webmodule.lfm) for the paired CGI/Apache subdirectories
are exactly the same showing that from a developer's standpoint there is not
too much difference between writing CGI programs or Apache modules with fcl-web
(fpweb).