bobdog
Unregistered
|
 |
Posted: June 25 2005,22:55 |
 |
Using some versions of those scripts, like, for example the adaptation where table columns can be sorted in situ might be a reason (http://homes.jcu.edu.au/~ccscb/#SortableGrid).
If a little more functionality were added to the code, it could be possible to cut down the disk space dedicated to documentation storage, shrinking the distro further. The added functionality would be the ability do include variables as inline text (or other content), rather than only as whole entries as is the case with TiddlyWiki now.
Even now, however, wiki page versions of content have smaller sizes than HTML equivalents, which only need to be parsed as HTML when rendered by the browser.
With this in mind, perhaps it would be possible to use a proxy script (in Python, for example), through which 'less vigorous' browsers could simply receive less dynamic HTML versions (CSS-less permalinks) of the output? The larger the amount of documentation used, the more relevant this would become.
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
