14 Aug
2004
14 Aug
'04
11:51 a.m.
hi diego
Lukas will certainly reply more lengthly. One of the problem is that
when you want to build advanced user interface you end up having to
mess up with the low-level protocol while with seaside we have real
objects all the way up. In SWI lukas mimicked as much as he could the
design behind Seaside but without its power. We took this decision
because we wanted to have SW be cross dialects.
Now Smalltalk/X, GNUSmalltalk does not support continuation (even if it
*may* be easy to add them I do not know). Each time we started to build
complex user interface (such as wizards or more user friendly interface
the code gets brittle and not really easy to write and maintain).
For this reason david started to develop in SW SmallBB and then he
ended up coding it in Seaside.
Stef
On 14 août 04, at 11:22, Diego Gomez Deck wrote:
Hi folks,
I'm quiet new on this list, my apologies if my question was already
answered.
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?
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?
Cheers,
-- Diego