Ron - thanks for posting Stephane's email.
And I apologise up front if the following seems like the mindless rant of a noob.
I think Ron is spot on with suggesting Seaside as a good starting point. A big reason is that it *is* the very reason I am involved with the Squeak Doc Project.
A week ago I contacted Lukas Renggli by email about Seaside and Pier. My purpose was to get permission to "refactor" his writings into something more accessible to noob's - something I thought I could do as I learnt it for myself. He gave his permission and then suggested I write to the Pier list about what I am doing. Unfortunately the only response was to go join the Squeak Doc Team.
So I did. But with interest in a documentation effort by Lukas, and now by Stephane, there may be the interest needed to make it successful.
Here's some personal history (hope I don't bore anyone):
I'm not a programmer (well, not yet). I'm interested in products that can help companies that I work for and web frameworks are a big part of that. That is how I got to ST and Squeak - by finding out about Seaside. I just mucked around on the Seaside and Pier websites and dove into the frameworks and realised that as a noob I was absolutely lost. And the more I looked for information the more I realised there is none for a person at my level. OK - there are some high level descriptions, but nothing that made the framework accessible to me.
So I thought - this is open source, it's about pitching in - why don't I write it myself! Yeah, it's a bit of a stretch (as you know, Ron, I'm still struggling with basic ST issues). But if I'm going to learn it anyway why don't I write about it and contribute it back to the cause. Because if I got here, there will be others behind me too, and they will be less forgiving of the lack of documentation and perhaps turn away - which would be a pity.
SO - not to lessen the need to document other parts of Squeak and it's core, I do think starting on a project like Seaside would actually benefit the rest of the Squeak community. 1) It is a magnet to ST and Squeak from a growing web community. 2) It seems like a fairly active community, so there is a better chance of it being successful 3) An early success will create momentum in the documentation of other areas/topics.
Paul
On Fri, Apr 06, 2007 at 04:58:01PM -0700, Paul Bennett wrote:
SO - not to lessen the need to document other parts of Squeak and it's core, I do think starting on a project like Seaside would actually benefit the rest of the Squeak community.
- It is a magnet to ST and Squeak from a growing web community.
- It seems like a fairly active community, so there is a better chance of
it being successful 3) An early success will create momentum in the documentation of other areas/topics.
I have started gathering together Seaside Documents at http://wiki.squeak.org/squeak/5671 and Seaside tutorials at http://wiki.squeak.org/squeak/792#Seaside
So far, I have collected 2 documents and 9 tutorials. I am taking time currently to summarize the tutorials, but if someone else would be willing to do that (especially if someone is reading them anyway; hint hint ;-) I would be grateful
Lukas Renggli told me on IRC that Seaside 2.8 (in development) has a lot more comments than previous Seasides; that should help us in our effort.
I know this can work; let's make sure it does.
squeak-doc@lists.squeakfoundation.org