t;> > usually writing concrete classes -- tapestry does it's magic on all
>> > the classes under /pages. You can still have an abstract class to
>> > base your pages on, but that class should probably go in /base instead
>> > of /pages, s
e an abstract class to
> > base your pages on, but that class should probably go in /base instead
> > of /pages, since it wont have a page template of it's own.
> >
> > I believe this is covered on the Tapestry 5 main website.
> >
> >
> > On 8/20/07, A
>>
>
--
View this message in context:
http://www.nabble.com/abstract-or-no-tf4298749.html#a12246721
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ses abstract class for page, while others use a regular class, which one is
> better?
>
> a.c.
> --
> View this message in context:
> http://www.nabble.com/abstract-or-no-tf4298749.html#a12235434
> Sent from
Hi,
Some
tutorials(like:http://www.devshed.com/c/a/Apache/Creating-Your-First-Tapestry-Project/)
uses abstract class for page, while others use a regular class, which one is
better?
a.c.
--
View this message in context:
http://www.nabble.com/abstract-or-no-tf4298749.html#a12235434
Sent from
