On Thu, Sep 4, 2008 at 4:29 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > I would say that step 1 would be to collaborative design and implement > the sample application. From that, the outline and division of tasks > should be more attainable.
Let me second that :) When I was building programming courses (e.g. for Apple), I always started by coming up with an example application. The trick is to come up with something straightforward that also reflects the key issues developers will face. Off the top of my head, I'd look for something that is: - Stateful (both in the session and between sessions) - Content-oriented (possibly with a media database) - Potentially multi-user - Amenable to a AJAX-style UI - Amenable to talking to an external system - Interesting to the "Web 2.0" crowd Some possible ideas are a RSS aggregator, a Tinderbox-like webapp (see http://www.eastgate.com/Tinderbox/ ), a Digg clone, etc. ...Richard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
