After looking at the source code for the LinkSubmit core component, I see a
lot of potential for a more generic component/mixin that could solve lots of
other problems.
What I need right now (and quite often) is a Select component that submits
the form and triggers an event to let the component cl
Forget the question, I tested it myself and it works :)
See the blog post for the complete working solution, that enables any
element to submit the form and trigger an event, like a regular submit.
http://tinybits.blogspot.com/2010/05/mixin-to-allow-any-element-to-submit.html
On Fri, May 21, 201
Nice!
- Original Message -
From: "Inge Solvoll"
To: "Tapestry users"
Sent: Friday, 21 May, 2010 11:34:11 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: T5: LinkSubmit should be generic
Forget the question, I tested it myself and it works :)
See the blog post for the compl
There is the "bible" section in the left hand menu on the Tapestry website.
Uli
On 20.05.2010 10:53, Charith Madusanka wrote:
Hi ,
Tapestry have any developer guide or some thing like that?
charith
-
To unsubscribe, e-mail
Hello,
Is there any documentation/examples about multiselect controls in
Tapestry5? Anyone has implemented this already?
regards,
Genís
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands,
2010/5/20 Thiago H. de Paula Figueiredo
>
> The issue here is how to render something after you render the block. I
> guess you need to implement it as a RenderCommand. It receives the render
> queue (RenderQueue instance), so you can add more RenderCommands to it. To
> render a Block inside a Re
there is a small compilation issue - ProcessSubmission should inherit from
ComponentAction, not from ComponentAction, shouldn't it?
--
View this message in context:
http://old.nabble.com/T5%3A-LinkSubmit-should-be-generic-tp28630552p28631907.html
Sent from the Tapestry - User mailing list arch
You're right, it was the blog tool that stripped it off :) Fixed now.
On Fri, May 21, 2010 at 12:07 PM, paha wrote:
>
> there is a small compilation issue - ProcessSubmission should inherit from
> ComponentAction, not from ComponentAction, shouldn't it?
>
>
> --
> View this message in context:
>
In left menu I can't find it. Can you put the url to "bible"
section please...
charith
On Fri, May 21, 2010 at 2:13 PM, Ulrich Stärk wrote:
> There is the "bible" section in the left hand menu on the Tapestry website.
>
> Uli
>
>
> On 20.05.2010 10:53, Charith Madusanka wrote:
>
>> Hi ,
>>
>> T
On Fri, 21 May 2010 08:28:16 -0300, Charith Madusanka
wrote:
In left menu I can't find it. Can you put the url to "bible"
section please...
Search for "Bible" in http://tapestry.apache.org/tapestry5.1/ and you'll
find it.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestr
On Fri, 21 May 2010 06:44:28 -0300, Łukasz Jazgar
wrote:
Now I know that RenderQueue is not a queue but stack (!!!).
It's a queue rendering a stack of components, so the ordering is a little
tricky, but it's still a queue. :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tap
thanx Thiago.
charith
On Fri, May 21, 2010 at 6:25 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Fri, 21 May 2010 08:28:16 -0300, Charith Madusanka <
> charithc...@gmail.com> wrote:
>
> In left menu I can't find it. Can you put the url to "bible"
>> section please...
>
If "multiselect" means what I think it does... we've had good luck with the
ChildSelect component in the lombok library.
http://lombok.demon.co.uk/tapestry5Demo/test/components/DynamicSelect
2010/5/21 Genís Pujol
> Hello,
>
> Is there any documentation/examples about multiselect controls in
>
Cool. It reminds me of a question I've been meaning to ask.
What's the best way to define the default value for component parameters?
Is it:
@Parameter(defaultPrefix = BindingConstants.LITERAL)
private String clientEvent = "change";
or:
@Parameter(value = "change", defaultPrefix =
On Fri, 21 May 2010 10:55:17 -0300, Bryan Lewis
wrote:
Cool. It reminds me of a question I've been meaning to ask.
LinkSubmit is a component, but we could have a mixin like Inge suggested.
:)
What's the best way to define the default value for component parameters?
Is it:
@Parame
For anyone who's looking for json pretty-printing in development mode,
Howard was nice enough to implement this and it is now available in
the latest Tapestry 5.2 snapshots.
Ben
On Wed, Feb 24, 2010 at 4:44 AM, Ville Virtanen
wrote:
>
> Hi,
>
> this definitely sounds something T5 should do as it
By "nice enough" he means "paid to". A lot of the goodness in
Tapestry 5.2 is coming in paid for by Ben's company, Widen. Hats off
to them!
On Fri, May 21, 2010 at 12:01 PM, Ben Dotte wrote:
> For anyone who's looking for json pretty-printing in development mode,
> Howard was nice enough to imp
17 matches
Mail list logo
