t; > 3.0.3. Why fight that battle anew?
> > > >
> > > > I've come to appreciate Tapestry & have found a certain amount of
> > > > efficiency to it, but only after a steep learning curve and plenty
> > of
> > > > frustration. Two
ain amount of
> > > efficiency to it, but only after a steep learning curve and plenty of
> > > frustration. Two examples: dynamic components and application
> catalogs.
> > > Dynamic components is possible, but there's no clear set of examples
> or
>
tration. Two examples: dynamic components and application catalogs.
> > > Dynamic components is possible, but there's no clear set of examples or
> > > documentation. Application catalogs are documented, but don't
> > work. The
> > > workaround is *brutal*, bu
pages are utterly useless.
-Original Message-
From: Jason Suplizio [mailto:[EMAIL PROTECTED]
Sent: Friday, March 03, 2006 2:41 PM
To: Tapestry users
Subject: Re: How to improve Tapestry
I'm in the middle of a comprehensive review for my employer of our team's
Tapestry experience.
there's no clear set of examples or
> > documentation. Application catalogs are documented, but don't
> work. The
> > workaround is *brutal*, but possibleif you're willing to go it
> alone.
> >
> >
> >
> >
> >
> >
> > &quo
> workaround is *brutal*, but possibleif you're willing to go it alone.
>
>
>
>
>
>
> "Todd Orr" <[EMAIL PROTECTED]>
> 03/03/2006 08:45 AM
> Please respond to
> "Tapestry users"
>
>
> To
> "Tapestry users"
> cc
&g
[EMAIL PROTECTED]>
03/03/2006 08:45 AM
Please respond to
"Tapestry users"
To
"Tapestry users"
cc
Subject
Re: How to improve Tapestry
IMHO, the biggest feature that Tapestry is missing is solid dynamic
component generation. Time and time again you'll see devs
One year ago I've posted a solution to load your template from a database,
or generate it dynamically in Tapestry 3. I think that it wouldn't be too
different in T4.
When I say "dynamic", I only mean only once, because of the page pooling
thing. You can do a good abstraction to create your template
I have been considering a solution to this, which I don't think would
change too much. The idea is that we have a component pool much like
we have a page pool. When the template is loaded, the components are
read in so they are ready. So instead of referencing them by object
in memory, they
IMHO, the biggest feature that Tapestry is missing is solid dynamic
component generation. Time and time again you'll see devs asking the
same question in the forums, "how do I dynamically generate..." Each
time someone points out the block, the for, or the if constructs. Yet
these always seem way m
Look at http://www.nextapp.com (a.k.a. echo2).
regards,
Mark
-Original Message-
From: Apache [mailto:[EMAIL PROTECTED]
Sent: Fri 3/3/2006 5:04 AM
To: tapestry-user@jakarta.apache.org
Subject: How to improve Tapestry
I think Tapestry already makes a big step forward
but still there is
This seems to me a departure from the Tapestry objective, as it is a
requirment for a form processing engine. So maybe Tapestry is a bad fit in
this case? Tools like Mandoforms do this kind of thing perhpas better, for a
price!
It might be useful to develop some Tap components to dynamically rende
Try Trails! www.trailsframework.org
> I think Tapestry already makes a big step forward
> but still there is a lot of things that could be made more dynamic and
> free programmers of templates and component definitions.
>
> In my opinion everything could be in the database instead of configuratio
13 matches
Mail list logo
