Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Typo fix on the intro.md documentation page. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
766f64396ae4e7194ed8d988370e2e4d |
| User & Date: | drh 2018-08-06 11:51:51 |
Context
|
2018-08-31
| ||
| 00:13 | Add the sitemap.md and doclist.html documents. check-in: fbe42f35ca user: drh tags: trunk | |
|
2018-08-06
| ||
| 11:51 | Typo fix on the intro.md documentation page. check-in: 766f64396a user: drh tags: trunk | |
| 11:48 | Avoid an extra \n at the end of the content in an CGI reply. Fix suggested by Gerome Fournier check-in: f914bf8729 user: drh tags: trunk | |
Changes
Changes to docs/intro.md.
75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 |
+ Wapptclsh is statically linked, so there is never a worry about
having the right shared libraries on hand. This is particularly
important if the application will ultimately be deployed into a
chroot jail.
+ Wapptclsh has SQLite built-in and SQLite turns out to be very
useful for the kinds of small application where Wapp excels.
+ Wapptclsh knows how to process "package require wapp". If you
run with ordinary tclsh, you might need to change the
"package require wapp" into "source wapp.tcl" and ship the separate
"wapp.tcl" script together with your application.
We prefer to use wapptclsh and wapptclsh is shown in all of the examples.
|
| |
75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 |
+ Wapptclsh is statically linked, so there is never a worry about
having the right shared libraries on hand. This is particularly
important if the application will ultimately be deployed into a
chroot jail.
+ Wapptclsh has SQLite built-in and SQLite turns out to be very
useful for the kinds of small applications where Wapp excels.
+ Wapptclsh knows how to process "package require wapp". If you
run with ordinary tclsh, you might need to change the
"package require wapp" into "source wapp.tcl" and ship the separate
"wapp.tcl" script together with your application.
We prefer to use wapptclsh and wapptclsh is shown in all of the examples.
|