This category is for EVOKE documentation: see also documentation front page
latest update 11 Dec 08
EVOKE licence
by site administrator 09 Feb 10
A. HISTORY OF THE SOFTWARE
EVOKE was created in 2007 by Ian Howie Mackenze, with contributions from
Allister Noble and Christopher J Hurst. It was evolved from the deepcore
library of the DeepSystems Partnership (www.deepserver.net), which was
developed through several versions by Christopher J Hurst and
Ian Howie Mackenzie over the years 2000 to 2007. ....(more)
utility functions in Page.py
by ian 24 Dec 09
if you have Page admin rights you can use, for any page, (via url - e.g. /evoke/page/123/tidy):
list_config
lists contents of self.Configlist_items
....(more)
EVOKE description
by ian 08 Mar 09
EVOKE is a web application builder, written in Python, with the following features:
very high level programming
using python, a custom configuration system, and a custom pythonic templating language: "evo".
data objects:
a generic data storage interface which presents data to the programmer as simple python objects, and manages MySQL databases in the background. This includes automatic generation and maintenance of MySQL databases, based on data schemas, declared in config files, which use simple custom types. The interface is currently implemented for MySQL only, but a SQLite implementation is in the pipeline. ....(more)
very high level programming
using python, a custom configuration system, and a custom pythonic templating language: "evo".
data objects:
a generic data storage interface which presents data to the programmer as simple python objects, and manages MySQL databases in the background. This includes automatic generation and maintenance of MySQL databases, based on data schemas, declared in config files, which use simple custom types. The interface is currently implemented for MySQL only, but a SQLite implementation is in the pipeline. ....(more)
evo reference
by ian 07 Jan 09
EVO is a templating system used in EVOKE to generate HTML output.
Master evo templates are in base/evo, while each app can add templates or override base templates in its own code/evo folder. Beware when overriding base templates, as updates to base may change these templates in ways that break your override templates. ....(more)
EVO template files
EVO template files are found in the evo folders, and their names end in .evo. Template file names are typically of the form: Classname_methodname.evo.Master evo templates are in base/evo, while each app can add templates or override base templates in its own code/evo folder. Beware when overriding base templates, as updates to base may change these templates in ways that break your override templates. ....(more)
EVOKE versions
by site administrator 26 Nov 08
EVOKE version numbers are in the form version.revision
The version number is displayed at the foot of the help page. ....(more)
ODD version numbers are development versions, and should not be considered stable.
EVEN version numbers are stable release versions.
The version number is displayed at the foot of the help page. ....(more)
EVOKE overview
by site administrator 08 Nov 08
evoke consists of the following components:
....(more)
installation
by site administrator 08 Aug 08
Installation of evoke requires the following pre-installed (on a posix platform):
Optionally, apache, or another webserver may be used to front-end the system and serve up flat content. ....(more)
- python2.4 or later
- PIL with jpeg support
- twisted
- MySQLdb
Optionally, apache, or another webserver may be used to front-end the system and serve up flat content. ....(more)
EVOKE system design
by ian 28 Apr 08
history
1 - assayserver (2001): zserver, XML
2 - deepserver (2005) : twisted/apache, XML
3 - evoke (2007) : twisted/apache, .evo
features ....(more)
development log archive
by site administrator 13 Nov 07
this is material from the old deep wiki, created during the development of evoke, and containing some materials which may be of use in preparing evoke documentation
....(more)