Hi,
Am 09.04.2005 um 11:46 schrieb Lukas Renggli:
If you like to satisfy your curiosity I suggest that
you browser the
lecture homepage [1], download the SmallWiki 2 image [2] and browse
the presentation slides [3]. Note that big and important parts, like
the security and persistence, are not yet fished!
[1]
http://www.iam.unibe.ch/~scg/Teaching/AdvancedLabs/index.html
[2]
http://www.iam.unibe.ch/~scg/Teaching/AdvancedLabs/swimages/sw2.zip
[3]
http://www.lukas-renggli.ch/smallwiki/slides/intro.pdf
Thanks !!
I'm currently working on an improved model of the
layout engine. The
idea would be that a wiki is composed from different primitive Seaside
components, e.g. to display the menu, the login status, the current
path and the actual contents. In SmallWiki 1 we had the templates that
were composed statically, in SmallWiki 2 I want to use a meta-document
to describe the look of a page:
*+Heading+*
| *+Menu+* | *+Path+*
| *+Search+* | *+Contents+*
Powered by *SmallWiki*
Heading, Menu, Path and Search are all links to primitive Seaside
components, the + means that they will be embedded and not linked into
the resulting page. Contents is the embedded document. So my rendering
visitor will walk over this meta-document and build the whole
web-page. When reaching the 'contents' it will jump from the
meta-level to the document level of the page currently displayed.
Does this all make sense? Any ideas where to put that meta-document
information? I am currently not quite sure where to store it ...
To enhance to static template structure of SmallWiki 1 is certainly
nice. So for me it makes sense. But I'm not shure what you mean with
"where to store". But it would be nice if such meta document could
itself be rendered and stored like a standard document, like a wiki on
meta level. From this point of view, they should be stored like all
documents too.
Greetings
Hans