re-reading your question, I notice that you also want to use a different .tml
file. You might find help in Igor's post
http://blog.tapestry5.de/index.php/2011/06/24/template-skinning/
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/layout-component-selection-based-on-doma
Depending on your use case, you could either:
1. Contribute a ComponentRequestFilter to the ComponentRequestHandler or
2. Contribute a PageRenderRequestFilter to the PageRenderRequestHandler
Either way, the filter will push() an object onto the Environment which your
pages / components can then ac
On Thu, 20 Dec 2012 13:56:28 -0200, ZKN __ wrote:
Hi Thiago,
Hi!
I've tried moving the base page to the "pages" package but that didn't
work again.
Please define 'didn't work'.
I'm not sure what you mean with block parameters but if it means using
some kind of IF statements in the bas
rst because for each new Subclass I will have to make changes to
the base template and second because it will make the base template harder to
read.
Thanks,
Ozkan
Оригинално писмо
От: "Thiago H de Paula Figueiredo" thiag...@gmail.com
Относно: Re: Layout co
On Thu, 20 Dec 2012 12:32:51 -0200, ZKN __ wrote:
Hi,
Hi!
I have a question regarding Layout component:
http://tapestry.apache.org/layout-component.html
Since pages and components "are more equal than they are different" I
was wondering if base pages (located in the base package) can be
Thanks a lot.Fixed
On Fri, Oct 7, 2011 at 9:30 AM, Howard Lewis Ship wrote:
> The source component will be the Layout component, not the TextField
> inside the layout component. This is part of event bubbling; when an
> event bubbles, the source of the event bubbles up as well.
>
> On Thu, Oct 6,
The source component will be the Layout component, not the TextField
inside the layout component. This is part of event bubbling; when an
event bubbles, the source of the event bubbles up as well.
On Thu, Oct 6, 2011 at 9:10 AM, Dimitris Zenios
wrote:
> Hi guys.
>
> I have a layout component whic
Ok, guess this would work in Gerry's case - although it feels like a bit of
a hack.
In my case this wont work as I have a single application and would like to
do the layout/branding in runtime - switching based on domain names.
2010/6/28 Pierce Wetter
>
> On Jun 25, 2010, at 1:31 PM, Magnus Kv
On Jun 25, 2010, at 1:31 PM, Magnus Kvalheim wrote:
> Hi,
> I have a similar requirement for our project where we plan to 'white label'
> an application and brand it in different ways.
> Have been thinking about a way of reusing pages by changing the layout
> dynamically - for example triggered b
Hi,
I have a similar requirement for our project where we plan to 'white label'
an application and brand it in different ways.
Have been thinking about a way of reusing pages by changing the layout
dynamically - for example triggered by domain names, but we haven't started
attempting to implement a
Hi Jan,
This was answered recently on the mailing list:
http://www.nabble.com/Re-%3A-Re-%3A-T5%3A-Layout-question-td16448904.html#a16448904
Peter Beshai
On Mon, Apr 14, 2008 at 2:25 PM, Jan Vissers <[EMAIL PROTECTED]> wrote:
> Thanks Howard,
>
> However this doesn't work for the Component templ
Thanks Howard,
However this doesn't work for the Component templates. It does work for
the Layout component, though. My question is what to add to other
Components, in order to maintain previewability, but without extraneous
element at runtime.
-J.
On Mon, 2008-04-14 at 11:09 -0700, Howard Lew
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
On Mon, Apr 14, 2008 at 11:02 AM, Jan Vissers <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Using
> http://tapestry.apache.org/tapestry5/tapestry-core/guide/layout.html I
> have a setup where the layout component uses a couple of other
> component
HAHA Like I said. I am daft :-p
--
View this message in context:
http://www.nabble.com/Layout-Component-tf3494445.html#a9878953
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
Layout is a component, not a page. It goes into the components
package. So Layout.java needs to be in foo.bar.components, and so
does Layout.html.
Looks like Tapestry found your component but not your template.
Therefore it was treated as a component without a template (which is
valid). Thus t
Your Layout.html should be in
src/main/resources/org/example/myapp/components/MyComponent.html. and
your Layout.java should be in src/main/java/org/example/myapp/
components/MyComponent.java
http://tapestry.apache.org/tapestry5/tapestry-core/guide/templates.html
Anjana Gopinath
True North
I must be daft. I can't make sense of this example. I'm using 5.0.3.
We have a layout like so: (filename: Layout.html)
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
Hello
This layout goes in the "pages" directory.
Then we have a page like so: (filen
Thank you Howard for your reply! - I found my mistake.
BTW: I love Tapestry! I started with the version 3 moved on to the version 4
and now testing the 5th one. You did a great work! If I can help you in any
way, please let me know!
--
View this message in context:
http://www.nabble.com/Layout-
Layout isn't a specific component, its the name for a component that
provides application-specific Layout (I used to call such a component
a "Border", but "Layout" is a more precise term).
Your problem is the use of 5.0.2 vs. 5.0.3 ... the structure of
templates changed between the two. In 5.0.2
Hi!
I have the same problem but i couldn't solve by the posted solution. I'm
using the tapestry 5.0.2
I looked for the Layout component in the core library, but i couldn't find
it, and also not in the 5.0.3 library. Is there another way to implement a
"Border" component?
-Joerg
--
View this mes
Mmm, i think you have an old version of tap5.
The use of the t:type attribute was removed in favor of using the element
name. Perhaps you don't have tap 5.0.3 version.
On 3/30/07, Olivier Jacquet <[EMAIL PROTECTED]> wrote:
I changed the to and that did the
trick! You need to keep the xmnls p
I changed the to and that did the
trick! You need to keep the xmnls parameter though.
Should this be changed in the doc or am I still doing something wrong?
Olivier Jacquet wrote:
Hi,
I'm trying to implement a Layout component as described here:
http://tapestry.apache.org/tapestry5/tap
22 matches
Mail list logo
