quick server pages
   
Manual page for Overview(TDH)
The Puppy installation of Quisp does not have the full documentation. Please go to the Quisp website at http://quisp.sourceforge.net.
Puppy has installed the commandline executables newproject.sh, buildix, catofs, dataedit, dbcat, shsql, shsql_alter, shsql_create, shsql_fldsel, shsql_join, tabdef, tabmaint and tabo into /usr/bin/.
The executable quisp is a cgi program and is installed in /root/ghttpd/cgi-bin/.
The Quisp project directory is setup in /root/ghttpd/quisp/.

QUISP (quick server pages)
is a simple, complete solution for developing database-driven dynamic web sites. It includes its own embedded SQL database which stores data in ascii text files, and optionally can include an embedded data charting package (ploticus).

QUISP is a template processor that lets you generate HTML on the fly. You create your HTML in a text editor, then add directives such as #include, #if, #for, #while, #sql, or #shell. When a user accesses your page, QUISP loads your page code, evaluates embedded QUISP directives, and sends pure HTML out to the user's browser. Your web site will likely have a number of pages, and you can organize them into directories if you want.

What existing problems does QUISP attempt to address?

  • Currently available dynamic web platforms (such as MySQL / PHP) are complex and require significant time and expertise (as well as system privileges) to install, administer, and upgrade. For some projects, especially smaller ones or prototypes, this sometimes seems like overkill.
  • Dependency on such large underlying systems can cause delays in getting started, and when these underlying systems are upgraded applications can break.
  • Applications written for MySQL/PHP (etc.) cannot be delivered and deployed on remote systems unless those systems are running compatible versions of MySQL and PHP.
  • Dynamic content systems that are tightly coupled to the web server can be cumbersome to customize or upgrade.

    QUISP has been developed as a simpler unified model that has no external DBMS or middleware dependencies, requires no root privileges, and can be extended and customized by an average "C" programmer.

    What makes QUISP special?

  • QUISP depends on no other packages (such as a DBMS) at runtime
  • QUISP is a CGI and works with any generic unix- or linux-based web server
  • easy to install.. no root privilege is generally needed to install or deploy applications
  • easy to copy, clone, or move QUISP web sites
  • extensible.. your "C" language functions can be easily incorporated; it's also easy to execute shell programs and capture the results.
  • QUISP's integrated SQL database (shsql) stores data in ordinary ascii text files.. you can edit data with a text editor or easily import into other software
  • nice HTML forms and SQL interface capabilities
  • an optional integrated data graphing engine (ploticus)
  • "list-centric" features-- small-scale vectorization can be handled by comma-delimited lists
  • nice "web-aware" features such as timeout record locking and comparison operators for intuitive search
  • QUISP uses a syntax that contrasts nicely to HTML or XML, which can help with code readability
  • QUISP reduces project complexity by eliminating the need for full-scale DBMS and middleware

    Who should consider QUISP?

    Developers of small- or medium- scale systems on unix/linux platforms who:

  • don't have a platform such as MySQL/PHP solidly available, or choose not to use it
  • wish to deploy or deliver dependency-free dynamic web site solutions
  • want easy access to their own "C" functions or shell commands
  • want an easy way to add dynamic ploticus graphics into their web pages
  • want to manage data without going through SQL all the time
  • can work within the parameters and limitations of QUISP and SHSQL.

    Who should avoid QUISP?

  • developers whose needs are best met by the functionality, performance, and complexity provided by packages such as MySQL/PHP
  • situations where adherance to existing IT standards is mandatory or where creativity, experimentation, and trying new things are prohibited

    Prerequisites

    You'll need to be on a system with a working web server (but you don't need to have control over that web server). In addition, you should be comfortable with:
  • creating basic HTML pages on your system using a text editor
  • URLs and the difference between a URL and a file pathname
  • CGI basics, and how to install CGIs that will be accessible to your web server
  • Unix skills such as setting file permissions modes, creating setuid executables, and creating soft links.



quick server pages    
Copyright Steve Grubb    


Markup created by unroff 1.0,    May 03, 2004.