tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Jue" <teamp...@gmail.com>
Subject Re: Tapestry at Denver & Boulder JUGs
Date Mon, 18 Jun 2007 15:09:49 GMT
I vote for both minimal and kitchen-sink examples.  When I was first
starting with Tapestry (and it was also my very first web app ever,
having never started with jsps, etc), the Tapestry Workbench was
overwhelming.  So many things were woven together that I couldn't pick
out the pieces easy enough.  Although, once I started learning more,
it was great to pick out pieces here and there.

I really appreciate the simplicity of the existing Tap 5 archetype.
It also makes it easy to start off your screencasts!

My preference would be a series of quickstarts that take care of "the
way Tapestry 5 does things", enough so that I can just referece a
Hibernate/etc book for the specifics.  And of course, a Advanced Core
archetype to show us the T5 core components running in captivity.

Tap 5 Quickstart  (could stay unchanged)
Tap 5 Advanced Core   (shows off all the core components, like the workbench)
Tap 5 Hibernate (simple like quickstart, that pulls from hibernate and
puts into a grid)
Tap 5 Spring (could be combined with above for Spring Configuration of
Tap 5 Acegi (simple like quickstart that has a login, error and post
login page, with an ASO for the user's details)
Tap 5 Ajax (quickstart using AJAX to selectively refresh the time / hi lo game)

So the simple ones could just be spin offs of the current quickstart.

I am currently using Tapestry Hibernate and Derby (nothing complex
though) with no problems except the ones I've caused--like trying to
create table names that used a reserved keyword.  I'm also having
Tomcat handle the JNDI for it, although Hibernate could do it instead

On 6/18/07, Davor Hrg <hrgdavor@gmail.com> wrote:
> I'm for both minimal and maximal archetype,
> minimal for those who already know what they want and how to use it.
> maximal for those wanting to try or evaluate the framework.
> there definitely are users that haven't tried spring or hibernate
> (or had hibernate, but not hiberante annotations)
> many things can go wrong when you try a new framework,
> and inevitably try to do thing in way not meant to be done for that
> particular framework.
> Davor Hrg
> On 6/18/07, Massimo Lusetti <mlusetti@gmail.com> wrote:
> >
> > On 6/16/07, Howard Lewis Ship <hlship@gmail.com> wrote:
> >
> > > I'm beginning to learn towards the idea that quickstart should evolve
> > > to be the "maximal" Tapestry template (and perhaps we add a "minimal"
> > > archetype for bare-bones).
> > >
> > > Thoughts?
> >
> > To me it seems obvious that this would be a win in T5 popularity, it
> > makes it more a rails-like framework and nowadays this is a top word
> > in the web app development, but i cannot evaluate the effort needed
> > achieving this.
> >
> > It's true that deleting thing is much easier then adding (at least in
> > the correct way) but having a bunch of stuff which you don't actually
> > need (hibernate or spring or upload or what else will come out) and
> > having to delete it without conscience can cause you the same trouble
> > as to have to add them. You've to know how it works.
> > T5 is already doing a great job in making it easy to add a 'feature',
> > just drop the jar in and you're fine, plus if the jar need some
> > configuration it needs for the external libraries it is integrating
> > within T5 not for itself, so basically it is the same of saying: Here
> > are you're needed libraries, configure as you wish. And it seems
> > obvious that if i want to use Hibernate or Spring or what else I've to
> > know how it works and how to configure it.
> >
> > That to say that the current behaviour of T5 modules with the doc is
> > enough for me, if the effort of building the "maximal template" could
> > be directed somewhere else ;)
> >
> > --
> > Massimo
> > http://meridio.blogspot.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message