Hi Hans
> For me, Wiki's are are interesting thing for issue tracking, where 
> issue may be bugs, requirements or documentation. For the first step I 
> worked with Zwiki, a Zope based form of a Wiki.

Lukas is zope expert and make money installing and developing web site 
with it ;)

>  From this, I identified some (personal) basic requirements for using 
> a Wiki in software engineering (to be understood  as  hypothesis):
>
> - - Wikis makes it easy to create information chaos, if there are no 
> good mechanisms to avoid it
> - - Wikis have big potential in collaborative enviroments, but there 
> is a great danger that they become useless after short time of usage
> - - From this point, Wikis usage should have not too much an not to 
> less rules (workflow)
> - -  The easy information model of wikis should be reflected by easy 
> usage
> - - Visualization,  tracking and workflow / rules are key parts for 
> success  of  wiki usage in software engineering
Agree

> - - information only has existence if it is recorded AND if it is 
> easily accessable (sounds trivial but is so hard to implement) - like 
> a book in a library which was set in the wrong shelf.....

That's why we are working on a good search engine for SmallWiki (not in 
the 1.0 version)

>
> Because I think about Zope as a powerful but complicated tool, I hope 
> a Smalltalk wiki will make it easer to make my dream true of a simple, 
> collaborative collecting and organizing information manager 8-)))

So you have to look at SmallWiki because its real name should have been 
SmallCMS.
What I suggest to you is take VisualWorks NC, go to the public store 
repository and try it. We build it with the idea that
other people would like to extend and create new tools on top of it.

Stef

>
>
> Greetings
>
> Hans
>
>>
>> The object representation of a page or document: in SmallWiki page 
>> are not text treated using regexpr but real objects.
>> So ***everything*** is an object. Therefore we have the complete 
>> power to navigate within these objects and use visitor to render, 
>> check validate the structure of the wiki. You can also extend 
>> SmallWiki in a much more easily way than Swiki (at ESUG people 
>> reported that Swiki extension was really difficult).
>>
>> Our objectives are to provide a framework in which people can 
>> customize their wikis the way they want with the minimal effort, to 
>> develop wiki components that can be plugged into a wiki, to provide 
>> wiki component for wiki management (such as give me all the page 
>> containing more than 3 attachements). Lukas built for example a 
>> button that create a glossary of a complete wiki in 10 minutes.) 
>> Right now the last point is weak becase we focused on the 
>> infrastructure and design with several refactorings. SmallWiki has 
>> configurations so that you can declare the components you want to use 
>> in a page and you can specify using css how these components should 
>> be rendered. The idea is that SmallWiki page or folder can have 
>> different component. For example luaks is used to have a style for 
>> presentations that are run as SmallWiki page, or a page showing 
>> online the results of running the SmallWiki tests. These are just 
>> different configurations of > components.
>>
>> Stef
>>
>>
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (Darwin)
>
> iD8DBQE/iHtEX8NXna8434cRAt42AKDei1/nGpxbc0RxyHYt0E5j6ZXkFgCfc9pS
> tMSLvCp036OdbreYQ8MQwnI=
> =JQ43
> -----END PGP SIGNATURE-----
>
>