I did the same but as a component, since i use it in several pages.
The difficulty shows up when i need to use Ajax calls for a zone which
is on the parent page and not on the component ...
Stephane
Chris Lewis a écrit :
Cool, thanks :-)
Martijn Brinkers (List) wrote:
That's exactly what
Hi Chris,
cool approach, maybe can be an entry into howto wikis?
Angelo
Chris Lewis-5 wrote:
>
>
>
> So anyway, here it is:
>
>
> Info.tml
>
> http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";
> t:type="layouts/general">
>
>
>
>
>
>
>
>
Actually, this is a very interesting idea. I did this with a little
more effort...
I created a page, called Message, with two properties: A text message
and a callback. This way I can handle all sort of messages, since "ok"
messages to complicated errors, without having almost no additional(or
repe
Cool, thanks :-)
Martijn Brinkers (List) wrote:
> That's exactly what I do as well.
>
> Martijn
>
> On Sun, 2008-08-03 at 10:49 -0400, Chris Lewis wrote:
>
>> Angelo,
>>
>> Following are the very trimmed down versions of my template and page
>> class. It shows the delegate and blocks, and how
That's exactly what I do as well.
Martijn
On Sun, 2008-08-03 at 10:49 -0400, Chris Lewis wrote:
> Angelo,
>
> Following are the very trimmed down versions of my template and page
> class. It shows the delegate and blocks, and how the block to render is
> determined. I didn't want to use a tradi
Angelo,
Following are the very trimmed down versions of my template and page
class. It shows the delegate and blocks, and how the block to render is
determined. I didn't want to use a traditional page return for a few
reasons: 1) Displaying a simple result message doesn't really need a
full page.
hi cris,
sounds interesting, how about a sample code/template to let us understand
more? thanks.
angelo
Chris Lewis-5 wrote:
>
> Hello all,
>
> I'm wondering how others handle a simple flow where a user fills out a
> form, form is processed, and then a message is shown as a result ("ok"
> or
Hello all,
I'm wondering how others handle a simple flow where a user fills out a
form, form is processed, and then a message is shown as a result ("ok"
or "failed"). I have a simple contact form and am handling this like so:
In my template I have 2 blocks: 1 is the form and the other is the
mess
