The examples
1. The page is the program
Printing, loops, your own functions, and the string builtins — the shape of every ICPP page.
2. Three languages, nothing installed
Python, Java and JSON inside one ordinary .html file,
sharing their values. No Python, no JVM.
3. A form the server answers
Reading what a visitor typed, and the one call that stands between you and a cross-site scripting hole.
Editing them
The files are in the sites directory where this package was
installed. Change one, save, reload the page — there is no build step and
nothing to restart. A page that fails to compile says so in the browser,
with the line number.
Two file kinds are in play, and the difference matters:
| name | what happens |
|---|---|
*.icpp.html | the <?icpp ?> blocks run on the server |
*.html | served as it is — unless page scripts are on for that directory, when python/java/json blocks run too |
The manuals
doc/ICPP_USER_MANUAL.md— the language and every builtin.doc/ICPP_LANGUAGES_GUIDE.md— Python, Java and JSON inside ICPP.doc/IWEBSERVER_USER_MANUAL.md— the server: configuration, page scripts, what it does not do.