Thank you Hugo, I'll explore this way.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Well, i think the only way you could achieve that would be to use the Block
component.
You could create a master page where your component blocks are declared.
That would be the only page your web designer would edit. In the other pages
where you use the components you would would the RenderBlock
Yes there is always workaround but what I liked in the definition of
tapestry is :
Tapestry is organized around four key principles:
* Simplicity
* Consistency
* Efficiency
* Feedback
And I like the first term ;) I like to have SIMPLE file, easy
readable and understandable.
-
Regarding helping the web designers get around the templates, i have found
in the past that providing a master HTML file with server side includes to
include the component templates that you want them to edit worked fine. It
was actually a web designer that suggested this, I think they used
Dreamw
Yes I can understand but this approach is a big constraint, with big
implication for my web designer who need to play in templates and need
to have a good understanding of my templates hierarchy
For me it's an issue with lot of limitation. A simple exemple :
I want to create a component who can
All components declared in a template or class for a component/page are
"embedded components". They all share the same parent component/page
which is returned by getContainer() as you've seen.
This is completely separate from the DOM hierarchy that T5 builds as it
renders. In that case you can na
Hi,
I try to create sub compponent in T5 (5.0.5).
My template is :
Content
In myComponent2 class when i try to access to the Container :
@Inject
private ComponentResources componentResources;
componentResources.getContainer(), tapestry return to me my page and
no
