I would prefer a prototypical community application to start the usual webapp.
So user management, registration with email validation and capchas, profiles, user groups, fine grained security, optionally simplistic blogs, forums, pm's and a bit of content management etc. I tend to copy that stuff over from older applications everytime, since it is standard in almost all webapps. Having an archetype for that would definitely also give Tap5 a boost in the hobby programmers section. Sure, this overlaps a bit with appfuse, but appfuse tends to be a bit bloated for smaller projects by virtue of the generalizations made. With the community/user base in place it would be possible to go for full featured community apps and portals or for example to an online shop, stock monitors or whatever. If it would be possible to make it easily skinnable I would think it wouldn't take long before "the community" provides with interesting designs and eyecandy. But maybe this is all a bit far fetched ;) Regards, Otho 2009/1/17 James Hillyerd <yimmy...@gmail.com> > I quite like the existing tutorial, I was just disappointed it ended so > abruptly. :) > > I think whatever docs come around in the future, they need to cover more on > Encoders/Translators/Coercers - as that was one of the most difficult > things > for me to learn. Honestly, I still barely understand when to use which. > > -james > > On Tue, Jan 13, 2009 at 10:15 AM, Howard Lewis Ship <hls...@gmail.com > >wrote: > > > I've been coming to the same conclusion. > > > > I'm clearing time with my boss to pursue this, along with several > > online articles. > > > > I have an idea for an application that can demonstrate every bit of > > Tapestry and be useful to boot. > > > > So the "guide" is the reference, what I have planned is the "tour". > > It would replace the tutorial. > > > > > > > > -- > James A. Hillyerd <ja...@hillyerd.com> >
