> -----Original Message-----
> From: Avi Bryant [mailto:avi at beta4.com] 
> Sent: Wednesday, June 25, 2003 5:23 PM
> To: The general-purpose Squeak developers list
> Subject: Re: [ANN] Jabber
> 
> 
> 
> On Wed, 25 Jun 2003, Jim Benson wrote:
> 
> > Another interesting concept is to link 'persistent' chat 
> with Wikis, 
> > which combines two ideas: the synchronous communication of the chat 
> > world (augmented by making the chats persistent) and the 
> asynchronous 
> > mode of the Wiki. Creating a Squeak based server would facilitate a 
> > much tighter coupling between the two, placing them both in 
> the same 
> > 'space' as it were.
> 
> Yes, I've had this idea in the back of my head for a while.  
> I'd like to combine this with two things:
> - multiple feeds into the wiki: not just chat but also 
> mailing lists, commit logs, issue tracking, etc
> - a simple markup system so that you can, during a chat, say 
> something like "topic: foo", and have the rest of the chat 
> logged to a particular wiki page.  Of course, this same 
> markup would be recognized in any of the other feeds as well. 
>  Ideally it would also have conventions for referring 
> directly to certain revision numbers, bug numbers, etc (see 
> CVSTrac for a nice example of this).
> 
> The problem with having all of this data streaming into a 
> wiki is that you then need to spend a lot of time editing it 
> - you want a "refactoring wiki browser", which is an 
> interesting problem in itself... ;)
> 
> </ramble>
> 
> Avi
> 

Why should you have to edit the data by hand?  If the Swiki stored
content as Squeak Text objects, and just applies the appropriate filter
to the different input stream types to convert them all to Text objects,
and of course applies the appropriate filter to serialize Text objects
into the different output stream types...