Nice - thanks :-)
--
View this message in context:
http://www.nabble.com/Templating-with-Tapestry-5-tf3659025.html#a10226122
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
Went down this road recently.
You have a Layout component (call it what you want)
some static stuff
and each page uses the layout;
body body
if you want more flexibility, you can pass in other components as
parameters, and use t:delegate to render them
body body
ecific
> >> information.
> >> >>
> >> >> Then Layout.html would look something like:
> >> >>
> >> >>
> >> >> Layout.java looks like this:
> >> >> class Layout {
> >> >> private String
r;
>> >>
>> >> accessors here
>> >> }
>> >>
>> >> The problem occurs because Layout.html does NOT
>> grab
>> >> the injected string
>> >> names put resolves the component to be o
e of type
> >> navbar which does not exist.
> >>
> >> I am doing this because the look-and-feel of the
> >> application carries 3
> >> layers of components. The layers have just been
> >> created to wrap the
> >&
because the look-and-feel of the
>> application carries 3
>> layers of components. The layers have just been
>> created to wrap the
>> components in Yahoo UI divs mostly. I don't want to
>> have to redo the default
>> layout on every tapestry page if somethin
ut and inject components
> into the layout. The
> layout class doesn't know what component goes where,
> it should just hold a
> basket of injected components and the template
> should know where to put the
> components.
>
> Any ideas?... or is there a better way?
>
inject components into the layout. The
layout class doesn't know what component goes where, it should just hold a
basket of injected components and the template should know where to put the
components.
Any ideas?... or is there a better way?
--
View this message in context:
http://www.n
