I would suggest you not to wait because this will take time (3 to 4 months to get something complete) except if people hlep but lukas is in a bootstrap phase now. Stef On 14 août 04, at 10:13, Serge Stinckwich wrote:

Yes, there is a some compatibility, but not too much. E.g. the model of the structures and documents is much more sophisticated, so it won't be possible to load the SmallWiki 2 into a SmallWiki 1 image and use the same model. However writing a visitor walking through SmallWiki 1 and producing a SmallWiki 2 will be simple. SmallWiki 2 separates clearly the model from the gui-representation. This means that there will be a bundle containing just the SmallWiki model (structure, document, metadata, visitor, security, commands, tests) and no GUI functionality. Simultanously I am working on a web-interface using Seaside. It can be loaded independantly from the model and attached to any wiki-model. As well I'm playing with an inspector-extension to let the user work on the wiki within the conveniant Smalltalk-GUI. Other interfaces should be easily feasible (command-prompt, swazoo, ...). However, Actions written for SmallWiki 1 won't be compatible with the new Seaside interface (I think most peoble will be targeting this view), there are simply too much differences. But you can make porting easier if you try to keep the functionality in separate classes as much as possible and let the action render only the view. Btw, the rendering of SmallWiki 1 is compatible with the way Seaside does. Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org

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 everyone, I would know which version of smallwiki ( and which version of the other bundles like swazoo) should I choose when loading SmallWiki. Selecting the last versions of each on Asterix made me have 101 errors when launching the tests of SmallWiki. Thank you, Frederic