Oops...Forgot to give you an answer. To control which listener is called
there is an optional second parameter to the client side
tapestry.form.submitForm() function that specifies the submit name..
The standard listener types attached to the Form component are all named one
of the constants in o
Heh...It will be done very soon, but I'm attacking one problem at a time and
am currently in validation logic still. (actually currently finishing up
last items to convert tapestry testing infrastructure to use TestNG...those
unit tests sure do run a lot faster now! ie doesn't retardedly
re-instan
On Wed, 28 Jun 2006 14:46:34 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
A...I had almost forgotten what your original question was. I
wouldn't
try this yet with EventListener. Use
onchange="tapestry.form.submitForm('your
form id')" for now.
Heh, perhaps I've bitten off more than
A...I had almost forgotten what your original question was. I wouldn't
try this yet with EventListener. Use onchange="tapestry.form.submitForm('your
form id')" for now.
I haven't added the logic to manage hidden form field data ~yet~, but after
I do that is what will make this work without re
On Wed, 28 Jun 2006 14:26:43 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
Sure, does "async=true|false" sound like a good parameter name? (It'll
only
apply when using submitForm)
That works for me.
While that should take care of my problem, does that mean there's no way
to force the
I should say "sure" = I'll make the quick change and deploy snapshot if it
sounds good.
On 6/28/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Sure, does "async=true|false" sound like a good parameter name? (It'll
only apply when using submitForm)
On 6/28/06, Kevin Menard < [EMAIL PROTECTED]> w
Sure, does "async=true|false" sound like a good parameter name? (It'll only
apply when using submitForm)
On 6/28/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
On Wed, 28 Jun 2006 11:42:58 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
> You don't need to do anything at all if you use the Event
On Wed, 28 Jun 2006 11:42:58 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
You don't need to do anything at all if you use the EventListener stuff.
Tapestry will do all the hard work under the covers for you. (ie you can
take out that onchange="javascript" stuff )
Time for yet another ques
clientValidationEnabled still means ~almost~ the same thing on the Form
component, only it has less to do with whether or not a particular .js file
is loaded as I'm letting dojo do that for me now..
This is something I've been avoiding thinking about until things stabilize a
little more, but the
On Wed, 28 Jun 2006 12:38:20 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
Yeah, "oops". I should probably refactor that @Shell inclusion part to
have
dojo included by default, and let people opt-in for ajax-specific
functionality on a per page/component basis.
Yeah, the current way seem
Hmmm"Sort of" . I've started doing snapshot releases of it via maven2
but no documentation and not exactly done yetIt's sort of a use if you
want but at your own peril. (unless you are reporting bugs, in which case
I'll probably be pretty responsive )
http://tapestry.apache.org/tapestry4.
Excuse me, but is it out .. ? I mean 4.1.
Cheers,
PS
On 6/28/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Yeah, "oops". I should probably refactor that @Shell inclusion part to
have
dojo included by default, and let people opt-in for ajax-specific
functionality on a per page/component basis.
Yeah, "oops". I should probably refactor that @Shell inclusion part to have
dojo included by default, and let people opt-in for ajax-specific
functionality on a per page/component basis.
Dojo is included within the tapestry jar, so you shouldn't have to go
through very much to use it now. (unless
That's even easier!
@Shell now has an ajaxEnabled parameter
>From Kevin Menard <[EMAIL PROTECTED]>:
> On Wed, 28 Jun 2006 11:42:58 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
> wrote:
>
> > You don't need to do anything at all if you use the EventListener stuff.
> > Tapestry will do all the hard
On Wed, 28 Jun 2006 11:42:58 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
You don't need to do anything at all if you use the EventListener stuff.
Tapestry will do all the hard work under the covers for you. (ie you can
take out that onchange="javascript" stuff )
That's awesome. No more
You don't need to do anything at all if you use the EventListener stuff.
Tapestry will do all the hard work under the covers for you. (ie you can
take out that onchange="javascript" stuff )
On 6/28/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
On Wed, 28 Jun 2006 11:08:29 -0400, Jesse Kuhnert <[E
On Wed, 28 Jun 2006 11:08:29 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
If you find yourself doing this this way you should still question it,
because now you can do this much more simply:
Your page/component class listener method:
@EventListener(events="onchange", targets="country",
Ahh...That is one particular piece I've so far (maybe someone can change my
mind ) decided to not support in a backwards fashion. (ie attaching new
behaviour to core js objects should be avoided ).
Here is the new interface for dealing with forms:
http://svn.apache.org/viewvc/tapestry/tapestry4/t
Hi,
Is there any info on triggering form events in Tapestry 4.1? My old code
no longer works (probably due to the move to dojo). E.g., I used to be
able to do something like the following:
That no longer causes the form to refresh.
Any info would be much appreciated.
Thanks,
Kevin
--
19 matches
Mail list logo
