Trails

[Carl Pelletier <ca...@yahoo.ca>]

Hi everyone, I'm looking for feedback here, I planning of using Trails to help gain speed with my Tapestry 4.0 development. Somebody use it? Should I ? What are the pinfall ? What are your advise...

Thanks for your feedback

Re: Trails

[Peter Svensson <ps...@gmail.com>]

Actually, my first trails (and tapestry) project was for a customer who had
an existing database with lots of odd relationships in it, and which I
managed to map one class at a time, by creating classes with the same name
as the tables and pasting the description into a comment. I didn't have to
make it complete but just did a couple of properties at a time by trial and
horror, and the pages just popped up, existing data and all. It was a
way-beyond-wow moment, to be sure.

Cheers,
PS

On 6/6/06, Kalle Korhonen <ka...@gmail.com> wrote:
>
> On 6/6/06, Peter Svensson <ps...@gmail.com> wrote:
> > Really, I can't see why you _souldn't_ use trails for everything and
> then
> > changes the bits you need to change. If you need to do heavy whiz-bang
> > end-user pages, at least you'll have your administrative pages for free.
>
> Second that, don't see too many reasons why not to use it. If you are
> starting a new project from scratch (or at least without pre-existing,
> fixed schema), it's a no-brainer to use Trails to compliment Tapestry
> and eliminate/reduce the glue code you normally need to write for
> persistence.
>
> Kalle
>
>
> > On 6/6/06, Carl Pelletier <ca...@yahoo.ca> wrote:
> > >
> > > Hi everyone, I'm looking for feedback here, I planning of using Trails
> to
> > > help gain speed with my Tapestry 4.0 development. Somebody use it?
> Should
> > > I ? What are the pinfall ? What are your advise...
> > >
> > > Thanks for your feedback
> > >
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

Re: Trails

[Kalle Korhonen <ka...@gmail.com>]

On 6/6/06, Peter Svensson <ps...@gmail.com> wrote:
> Really, I can't see why you _souldn't_ use trails for everything and then
> changes the bits you need to change. If you need to do heavy whiz-bang
> end-user pages, at least you'll have your administrative pages for free.

Second that, don't see too many reasons why not to use it. If you are
starting a new project from scratch (or at least without pre-existing,
fixed schema), it's a no-brainer to use Trails to compliment Tapestry
and eliminate/reduce the glue code you normally need to write for
persistence.

Kalle


> On 6/6/06, Carl Pelletier <ca...@yahoo.ca> wrote:
> >
> > Hi everyone, I'm looking for feedback here, I planning of using Trails to
> > help gain speed with my Tapestry 4.0 development. Somebody use it? Should
> > I ? What are the pinfall ? What are your advise...
> >
> > Thanks for your feedback
> >
> >
> >
>
>

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

Re: Trails

[Chris Nelson <cn...@yahoo.com>]

Yes, the Trails pages are very customizable.  The
second article I did for java.net covers
customization.  We should probably move this
discussion over to the Trails mailing list.

--- Carl Pelletier <ca...@yahoo.ca> wrote:

> Ok, thanks, that help. Last question: Is it easy to
> change the UI after Trails generate the page ?
> Because, we have some specific needs. We won't use
> the simple layout Trails give after the generation.
> We need to modify the ui to reflect our needs.
> 
> Thanks !
> 
> ----- Original Message ----
> From: Peter Svensson <ps...@gmail.com>
> To: Tapestry users <us...@tapestry.apache.org>; Carl
> Pelletier <ca...@2be.ca>
> Sent: Tuesday, June 6, 2006 10:19:46 AM
> Subject: Re: Trails
> 
> I only use trails for my Tapestry-4 development.
> Mainly because I enjoyed the steep initial learning
> curve of tapestry and needed something to lean on.
> 
> The main reason I liked and like trails is because
> the ant scripts together with hibernate tools
> generate all tables in my MySQL database
> automatically from my POJOs. I just need to grok how
> to @annotate right, which in itself have been
> interresting, so all lookup tables, collections,
> relations, etc. gets done. 
> 
> Another big goodie is that trails have a default
> list, search and edit page for all POJOs, which are
> plain Tapestry html/page combos.  Also, there are
> ant/maven tasks to generate individual list or edit
> pages for POJOs. 
> 
> Then theres the fairly easy to use acegi security (I
> use a separate site to the same database for
> "unsecure" pages out of lazyness), with an ant task
> to add and another to initialize (create default
> tables for admin, etc.) 
> 
> Really, I can't see why you _souldn't_ use trails
> for everything and then changes the bits you need to
> change. If you need to do heavy whiz-bang end-user
> pages, at least you'll have your administrative
> pages for free. 
> 
> Cheers,
> PS
> 
> On 6/6/06, Carl Pelletier <ca...@yahoo.ca>
> wrote: Hi everyone, I'm looking for feedback here, I
> planning of using Trails to help gain speed with my
> Tapestry 4.0 development. Somebody use it? Should I
> ? What are the pinfall ? What are your advise...
> 
> Thanks for your feedback 
> 
> 
> 
> 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

Re: Trails

[Carl Pelletier <ca...@yahoo.ca>]

Ok, thanks, that help. Last question: Is it easy to change the UI after Trails generate the page ? Because, we have some specific needs. We won't use the simple layout Trails give after the generation. We need to modify the ui to reflect our needs.

Thanks !

----- Original Message ----
From: Peter Svensson <ps...@gmail.com>
To: Tapestry users <us...@tapestry.apache.org>; Carl Pelletier <ca...@2be.ca>
Sent: Tuesday, June 6, 2006 10:19:46 AM
Subject: Re: Trails

I only use trails for my Tapestry-4 development. Mainly because I enjoyed the steep initial learning curve of tapestry and needed something to lean on.

The main reason I liked and like trails is because the ant scripts together with hibernate tools generate all tables in my MySQL database automatically from my POJOs. I just need to grok how to @annotate right, which in itself have been interresting, so all lookup tables, collections, relations, etc. gets done. 

Another big goodie is that trails have a default list, search and edit page for all POJOs, which are plain Tapestry html/page combos.  Also, there are ant/maven tasks to generate individual list or edit pages for POJOs. 

Then theres the fairly easy to use acegi security (I use a separate site to the same database for "unsecure" pages out of lazyness), with an ant task to add and another to initialize (create default tables for admin, etc.) 

Really, I can't see why you _souldn't_ use trails for everything and then changes the bits you need to change. If you need to do heavy whiz-bang end-user pages, at least you'll have your administrative pages for free. 

Cheers,
PS

On 6/6/06, Carl Pelletier <ca...@yahoo.ca> wrote: Hi everyone, I'm looking for feedback here, I planning of using Trails to help gain speed with my Tapestry 4.0 development. Somebody use it? Should I ? What are the pinfall ? What are your advise...

Thanks for your feedback 

Re: Trails

[Peter Svensson <ps...@gmail.com>]

I only use trails for my Tapestry-4 development. Mainly because I enjoyed
the steep initial learning curve of tapestry and needed something to lean
on.

The main reason I liked and like trails is because the ant scripts together
with hibernate tools generate all tables in my MySQL database automatically
from my POJOs. I just need to grok how to @annotate right, which in itself
have been interresting, so all lookup tables, collections, relations, etc.
gets done.

Another big goodie is that trails have a default list, search and edit page
for all POJOs, which are plain Tapestry html/page combos.  Also, there are
ant/maven tasks to generate individual list or edit pages for POJOs.

Then theres the fairly easy to use acegi security (I use a separate site to
the same database for "unsecure" pages out of lazyness), with an ant task to
add and another to initialize (create default tables for admin, etc.)

Really, I can't see why you _souldn't_ use trails for everything and then
changes the bits you need to change. If you need to do heavy whiz-bang
end-user pages, at least you'll have your administrative pages for free.

Cheers,
PS

On 6/6/06, Carl Pelletier <ca...@yahoo.ca> wrote:
>
> Hi everyone, I'm looking for feedback here, I planning of using Trails to
> help gain speed with my Tapestry 4.0 development. Somebody use it? Should
> I ? What are the pinfall ? What are your advise...
>
> Thanks for your feedback
>
>
>