./wip/quickie, Small footprint, fast Wiki engine written in C++

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 1.1, Package name: quickie-1.1, Maintainer: shaun

Quickie is a small footprint, fast C++ Wiki engine; hence the name.

The fundamental insight for this engine is that wiki pages are read far
more often than they are modified. Thus, the generated HTML can be
cached. It follows that the main code path will check that the .html
file exists and simply copy it to stdout in the vast majority of cases.

The .html file generated from each .wiki file is about the same size as
the .wiki file itself, so there will be no particular I/O advantage,
but there is a huge CPU advantage, and a significant memory footprint
advantage, and since I want to run a wiki on a geriatric 20MB 33MHz 386
machine, this is a good thing.

Online demo: http://quickie.sourceforge.net/cgi-bin/quickie


Required to build:
[pkgtools/cwrappers]

Master sites: (Expand)

RMD160: 2621cde0cdd3fee816b01b987d355d498855c6a1
Filesize: 271.528 KB

Version history: (Expand)

CVS history: (Expand)


   2012-10-07 16:53:42 by Aleksej Saushev | Files touched by this commit (79) 
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
Mark packages that don't or might probably not have staged installation.
   2009-10-11 12:45:10 by Thomas Klausner | Files touched by this commit (261) 
Log message:
Remove obsolete @dirrm lines.
   2008-03-07 23:58:55 by Tobias Nygren | Files touched by this commit (2) 
Log message:
use ${DEFAULT_DISTFILES}
   2006-09-08 06:18:14 by Shaun Amott | Files touched by this commit (13) | Imported package
Log message:
Quickie is a small footprint, fast C++ Wiki engine; hence the name.

The fundamental insight for this engine is that wiki pages are read far
more often than they are modified. Thus, the generated HTML can be
cached. It follows that the main code path will check that the .html
file exists and simply copy it to stdout in the vast majority of cases.

The .html file generated from each .wiki file is about the same size as
the .wiki file itself, so there will be no particular I/O advantage,
but there is a huge CPU advantage, and a significant memory footprint
advantage, and since I want to run a wiki on a geriatric 20MB 33MHz 386
machine, this is a good thing.

    Online demo: http://quickie.sourceforge.net/cgi-bin/quickie