Lukas is
working on SmallWiki Two based on seaside and once we will
have that SmallWiki will be really powerful.
What is the motivation behind the decision to build the Wiki on top of
Seaside?
As explained in my last mail, SmallWiki 2 isn't built on top of Seaside
but besides. If somebody wants to provide a different web-interface
using other technologies like SSP, VisualWave or Swazoo there is the
possiblity to do this.
Seaside is a wonderful tool to create statefull
applications on top of
the stateless HTTP. So the question could be: What is the motivation
behind the decision to build an statefull Wiki?
Have a look at the action-hierarchy SmallWiki 1 :)
A wiki has got a lot of state:
- currently browsed page (folder/resource
- currently used renderer (viewer/editor/rss/history/...)
- currently logged in user
- currently used layout manager
There are usually lots of other components on a wiki-site, like
- (tree-)menus
- search fields with search results
- field to keep personal data (notes/links/...)
- etc.
State-fullness makes live much easier: try to implement in SW1 the
tree-menu I did in SW2 with just a few lines of code and without the
need to use cookie or header-field-acrobatics ;)
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org