I will let lukas reply as he is the guy having the vision and mainly 
implemented everything.

Now my vision or why we proposed with roel this project to lukas.

SmallWiki is designed to be a big plug for other components and not 
only been a wiki. The wiki
is the only first instance. Our long term goal is to have a Zope like 
but Smalltalkish and well designed system.
That people can extend with their own components. But this will take 
time.

When we say well designed this means for example having a good parser 
and not something hacked by hand in the dark.
That's why we used SmaCC. We also thought a lot to have only objects 
everywhere. S

We wanted to be cross dialect as much as possible so seaside is not and 
will not work on
Smalltalk/X, Gnu/Smalltalk. Now lukas was planning to see how to 
migrate to  SeaSide because he is a seaside expert.
and not using it was a conscious decision. (Note that after discussing 
with  alan knight this is not sure that seaside can support heavy load. 
But I'm not expert.)

So do whatever you want. But I could not not tell you that. We will 
continue slowly because this is really important that web is not
only covered by python or PhP frameworks.

Stef


On 11 déc. 03, at 19:39, Cees de Groot wrote:

> ducasse  <squeak-dev at lists.squeakfoundation.org> said:
>> This looks exciting. Now my impression is that if you want to do all
>> that
>> you should really have a look at SmallWiki which is improving slowly
>> but steadily.
>
> Well, we have Squeak web frameworks. When will SmallWiki be ported to
> them? The thing that really ticked me off w.r.t. SmallWiki is that it
> came with (excusez les mots) a bad imitation of Seaside - if the sort
> of interaction that Seaside supports is needed, I rather have the
> original thing (please note: I'm not attacking SmallWiki in any part,
> I'm just wondering the why of it if no precondition of cross-platform
> portability exists).
>
> We have, in Seaside, blog stuff (SBlog); in the form of a domain model
> only at the moment, the Advogato/SqP stuff (which has a 'role' model I
> find infinitely more attractive than anything static); SM2, which Goran
> claims to be a superduper metadata repository, and my Gardner code 
> (which
> does need updating to the latest SmallWiki parser, though). Where does
> SmallWiki fit in? Why should I need to learn something new (and most of
> the people that will hopefully cooperate here)?
> At the moment my idea is to display most of the content with HttpView2,
> which results in nice, stable, url's, and do the interaction with
> Seaside, which allows complex flows. It's just a gut feeling, but I
> think that these together will be an extremely nice environment to work
> in. And they've been proven in battle, another advantage over 
> SmallWiki.
>
> Furthermore, the real strength of the site, I think, will come from
> exporting its data as webservices - not only for syndication, but for
> single sign-on, delivery of metadata to other sites (and vice versa:
> integration of metadata from e.g. SM2). All stuff where a web framework
> will play a minor role.
>
> So, if you don't mind, I think I'll continue as planned, which is to do
> the read ('View') bits with HttpView2 (and for the time being send all
> the updates to mod_virgule).
>
> -- 
> Cees de Groot               http://www.tric.nl     <cg at tric.nl>
> tric, the new way           helpdesk/ticketing software, VoIP/CTI,
>                             web applications, custom development
>
>