And don't be too afraid to create more pages, one page for each view. If
you find that you have to duplicate code in the pages you could probably
put that into services and components and that way your code will be
easier to maintain than one complex page.
Thiago H. de Paula Figueiredo skrev
On Sun, 21 Nov 2010 15:24:18 -0200, Mats Andersson
wrote:
And don't be too afraid to create more pages, one page for each view. If
you find that you have to duplicate code in the pages you could probably
put that into services and components and that way your code will be
easier to maint
On Sat, 20 Nov 2010 08:14:03 -0200, Timo Nentwig
wrote:
White labeling. Same code, different appearance.
As Juan said, CSS can solve most of your problem here. If you need HTML
structure differences, not just appearance ones, you can use blocks,
components and the Delegate component. Ex
Timo, css should be used to modify the appearance of the content rendered by
pages or components and because the nature of css you can always override
parts defined in your component.
Doesn't css fulfill your requirements ?
On 20 Nov 2010 11:14, "Timo Nentwig" wrote:
>
> On Nov 19, 2010, at 18:24
Timo
On 20 Nov 2010 11:14, "Timo Nentwig" wrote:
>
> On Nov 19, 2010, at 18:24, Thiago H. de Paula Figueiredo wrote:
>
>>> Btw, what's your scenario and why is the multiple templates per page a
>>> requirement for you? Maybe you could achieve what you need with
>>> Components...
>>
>> I'm also cur
On Nov 19, 2010, at 18:24, Thiago H. de Paula Figueiredo wrote:
>> Btw, what's your scenario and why is the multiple templates per page a
>> requirement for you? Maybe you could achieve what you need with
>> Components...
>
> I'm also curious to know what these requirements are. I never needed t
On Fri, 19 Nov 2010 14:14:22 -0200, Everton Agner
wrote:
PS: About the Locale scenario, i don't know if you would need to have 2
page classes also.
No need for different page or component classes for different locales. One
page or component class, multiple templates, one for each locale.
PS: About the Locale scenario, i don't know if you would need to have 2 page
classes also. I just know you could do something like it, but never
implemented.
Btw, what's your scenario and why is the multiple templates per page a
requirement for you? Maybe you could achieve what you need with
Compo
As far as I know, you can Localize your TML files. Example: you can have an
Edit_en.tml and an Edit_pt.tml for a Edit.java page class. But that handles
only the Locale scenario... I don't know if it works only for Pages or if
it's possible on Components also...
But you can render output without ha
Hi!
So, I'm a tapestry (5.1) noob and so far I was unable to figure whether it
fulfills a requirement essential to me: is it possible to have different tml
files for each component? So far it seems like each component has exactly one
tml file.
thx
tcn
--
10 matches
Mail list logo
