Something like this is among the many things I've been plinking
away at for quite some time.  My take on this is at:

http://oasis.canis.uiuc.edu:8080/Squeak/The+Visible+Squeak

This won't be done overnight, so feel free to build whatever
you think will work.  I have a fairly decent EMail inbox parser
that creates a model of EMail folders, messages, and parts.
That's useful if you want to be able to build a variety of tools
for gathering various bits of information from the messages,
such as source code or references to class names ( so you can
track the interest in a given class, for instance ).

However, I'm more interested in being sure that whatever solution
I build will be cross-dialect portable.  So, Squeak-only solutions
aren't of interest to me, neither are VisualWorks-only solutions.
Smalltalk-only solutions are perfectly fine by me.

- les


Ali Chamas wrote:
> 
> I was wondering,
> 
> What if there was a Squeak app running as a servlet
> somewhere, which acted as a central mailing list
> repository. An interface for client versions of Squeak
> could log in, check mail, do contextual searches, see
> how many hits each mail item has received, search by
> topics, and even extend the format/capabilities of the
> email item (could be a squeak object, not just plain
> email text). You could also make sure that by logging
> into the mailing group, you would be able to view all
> past items, while staying in the same app session. You
> could also create disscussion groups, and categories
> of mail items. It also means that we'd all be using
> Squeak to talk about Squeak.
> So basically, instead of using an email-based program
> to read mail from the Squeak server, we just make a
> Squeak image manage the mailing list, run it on the
> server, and use our local copies to log in and learn.
> 
> Does this idea appeal to anyone?
> 
> Ali.
> 
> _____________________________________________________________________________
> http://clubs.yahoo.com.au - Yahoo! Australia & NZ Clubs
> - Got an interest? Build a Club.