Thanks, Ivan, Thiago. Indeed, message being - this is possible - and
desirable - at the component level.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/One-Template-to-include-another-TML-JSP-style-tp5716240p5716300.html
Sent from the Tapestry - User mailing list
I think this is not a good solution to have a view page that consists of
form elements. Usually view pages are represented as plain text. But
technically there are two ways to reuse code/markup in tapestry:
1. Composition.
As was mentioned earlier in this thread we can extract all repeatable logic
On Wed, 12 Sep 2012 18:47:35 -0300, netdawg wrote:
Sorry, Thiago, I do not see - why not? Basically, why cannot pages be
allowed simply extend each other?
I haven't said that. Anyway, creating a component is the best, most
flexible and reusable option.
--
Thiago H. de Paula Figueiredo
-
Sorry, Thiago, I do not see - why not? Basically, why cannot pages be
allowed simply extend each other?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/One-Template-to-include-another-TML-JSP-style-tp5716240p5716249.html
Sent from the Tapestry - User mailing list
e about
> editMode. Looking into this. Fighting my laziness of moving all the logic
> from page level to component level - classes, properties, templates - ugh -
> if I am understanding correctly.
>
>
>
> --
> View this message in context:
> http://tapestry.104571
:
http://tapestry.1045711.n5.nabble.com/One-Template-to-include-another-TML-JSP-style-tp5716240p5716247.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
On Wed, 12 Sep 2012 16:46:01 -0300, netdawg wrote:
I think there needs to be a way to contrive this include - simple on the
outside - but the framework handles the complexity somehow in the
back-end.
The framework already provides a very nice way of doing that: write your
own component an
to be a way to contrive this include - simple on the
> outside - but the framework handles the complexity somehow in the back-end.
>
>
>
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/One-Template-to-include-another-TML-JSP-st
;
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/One-Template-to-include-another-TML-JSP-style-tp5716240p5716242.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---
this to avoid label clashes.
I think there needs to be a way to contrive this include - simple on the
outside - but the framework handles the complexity somehow in the back-end.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/One-Template-to-include-another-TML-JSP
t;
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/One-Template-to-include-another-TML-JSP-style-tp5716240.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
ized.
Thanks.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/One-Template-to-include-another-TML-JSP-style-tp5716240.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsu
12 matches
Mail list logo
