Howard Lewis Ship 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.
Oh, yes!
That would also make an excellent living tutorial (someone mentioned
PetStore; yes, somethin
Tim,
regarding the application accompanying the book, I think that the first
chapter of the book doesn't necessarily have to have a full blown
application, fully completed with all bells and whistles. It only needs to
be good enough working application, that could have a "black blox" part that
w
Just to wrap up the initial discussion on this thread, I'll respond here.
Any future discussion should probably occur on the Google Groups.
I've taken a liking to BitBucket (http://www.bitbucket.org/), which is quite
similar to what assemla seems to offer, but also has Mercurial repository,
which
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 progr
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.
On Thu, Sep 4, 2008 at 10:04 AM, Don Ryan <[EMAIL PROTECTED]> wrote:
>
> On 4 Sep 2008, at 17:05, Timothy Sweetser wrote:
>
>> Whe
Ah, should clarify a point: I wasn't arguing for a completely
unstructured environment, just one organized by scope and topic. Break
it down, for example, into IoC Container, App-level Configuration and
Processing, Pages, Components, Forms, Built-in Components, Integration
with Hibernate/Spring/etc
On 4 Sep 2008, at 17:05, Timothy Sweetser wrote:
When people only have an hour a day, and may only write a paragraph
or two, I think that works against us. You decrease the
contribution pool and increase the amount of effort required to get
somewhere.
That's a fair point. The sort of thi
The problem with building the book, from the start, around a working
application (or, vise versa, building an application during the course
of the book), in my mind, is that it requires far more cooperation and
coordination between the contributors. I don't think it really works
to the strengths o
The discussion here (knowingly or otherwise) mirrors something that
comes up a lot when people are debating the pedagogical approaches in
academia. A framework like Tapestry, which comes into its own on
larger projects, is not served well by using toy examples to
illustrate framework featur
roAdmin Dariusz Dwornikowski [mailto:[EMAIL PROTECTED]
Sent: 03 September 2008 19:31
To: Tapestry users
Subject: Re: T5 : [ANN] The book - next steps
I really would love to see a walkthrough on making blog application in
tapestry5+spring+hibernate. Not only the integration, but how to implement
s
Em Wed, 03 Sep 2008 18:44:06 -0300, Howard Lewis Ship <[EMAIL PROTECTED]>
escreveu:
So far, my experience has been to say "We're using Hibernate. It
looks like this. Just play along for now." and that seems to work.
I'm not teaching Hibernate, just explaining enough to satisfy the
demands o
So far, my experience has been to say "We're using Hibernate. It
looks like this. Just play along for now." and that seems to work.
I'm not teaching Hibernate, just explaining enough to satisfy the
demands of the lab. And I think there's great value in the fact that
the applications are "real".
Instead of debating the book's structure first, why don't we start out
by just breaking it down into the various topics and subtopics
(excluding introductions, tutorials, and "prolonged examples") and
working on them? From my perspective, the priority should be first on
compiling and organizing inf
I would suggest that you get a way from the linear, single path flow of
writing book.
I have stopped reading most technical books because they assume that I am a
beginner and am going to read the book in a strictly serial manner.
I would suggest that rather than be chapter focused that you be co
Em Wed, 03 Sep 2008 15:31:05 -0300, ProAdmin Dariusz Dwornikowski
<[EMAIL PROTECTED]> escreveu:
Tapestry alone is no use if you do not have DB.
As a instructor of Java, Hibernate, Spring and other frameworks, my
experience says that people learn way better when they're learning just
one
I really would love to see a walkthrough on making blog application in
tapestry5+spring+hibernate. Not only the integration, but how to implement
simple blog with it, design DAOs, where to put them etc. Tapestry alone is
no use if you do not have DB. In advanced topics I would like to see ex.
acegi
Looked at the TOC.
My thoughts on writing the book line up closely with how I've written
the Tapestry Workshop. I can tell you that, in the Workshop, we are
using Hibernate in the first session (the Workshop consists of themed
sessions, with labs inside the session).
In other words, focus on how
Just an idea, maybe hosting the book on assembla
(http://www.assembla.com) would fit this project needs better.
I've used assembla with great success in the past, it has all the things
we need, an SVN repo, a forum, a chat room, an issue tracker, and more...
Alex Kotchnev wrote:
I've created
Awesome! I'll try to have a look in a couple of hours, and if I can make
the time, I'd like to contribute either in raw content and/or
collaborative editing. As for a discussion channel for the book, why not
use google-groups?
Alex Kotchnev wrote:
> I've created a new project for the proposed book
I've created a new project for the proposed book at
http://code.google.com/p/tapestry5-book , and posted the proposed table of
contents at
http://code.google.com/p/tapestry5-book/wiki/ProposedTableOfContents . Now
that I'm looking at it, it's a little disappointing as the TOC doesn't
really have an
20 matches
Mail list logo
