Hi all,
JumpStart 4.11 is ready to use. The latest additions are:
* creating a client-side validator; and
* turning off "validation bubbles".
Here it is:
http://jumpstart.doublenegative.com.au/jumpstart/
All feedback is welcome.
Regards,
Geoff
thanks geoff, your resource has been invaluable.
p.
Geoff Callender wrote:
Hi all,
JumpStart 4.11 is ready to use. The latest additions are:
* creating a client-side validator; and
* turning off "validation bubbles".
Here it is:
http://jumpstart.doublenegative.com.au/jumps
On Wed, 16 Jun 2010 18:24:50 -0300, Jim O'Callaghan
wrote:
Thiago,
Hi!
Thanks for your helpful advice, as usual. Before I junk what I've done
and get stuck in again, would you mind telling me if I can use this
approach to:
All you did until now is in the right direction (DataTypeAna
I very much appreciate what you are doing!
Thanks you,
Andreas
Geoff Callender wrote:
Hi all,
JumpStart 4.11 is ready to use. The latest additions are:
* creating a client-side validator; and
* turning off "validation bubbles".
Here it is:
http://jumpstart.doublenega
Great job Geoff !
On Thu, Jun 17, 2010 at 2:24 PM, Andreas Bohnert wrote:
> I very much appreciate what you are doing!
> Thanks you,
> Andreas
>
> Geoff Callender wrote:
>>
>> Hi all,
>>
>> JumpStart 4.11 is ready to use. The latest additions are:
>>
>> * creating a client-side validator;
Thanks Thiago I'll look into it further - you've clarified it a lot. When I
was talking about storing an object in the component I meant some state I could
store that would persist through the render --> user input --> post so I could
access it afterward and reassign my values to the original e
This is great Geoff thanks. Would have saved me hours when I was replacing
the error bubbles a few weeks back!
Regards,
Jim.
-Original Message-
From: Geoff Callender [mailto:geoff.callender.jumpst...@gmail.com]
Sent: 17 June 2010 11:56
To: Tapestry users
Subject: [ANN] JumpStart 4.11 re
Thanks a lot Geoff.
Regards
François
I'm looking to make replacing error bubbles easier, but that may be
delayed to 5.3 now.
On Thu, Jun 17, 2010 at 8:56 AM, Jim O'Callaghan wrote:
> This is great Geoff thanks. Would have saved me hours when I was replacing
> the error bubbles a few weeks back!
>
> Regards,
> Jim.
>
> -Original
Another option: Write your tests in Groovy, which lets you access private
fields. (Of course you'll get other benefits from using Groovy. In short,
it's a much better language for testing, especially when combined with
Spock.)
Cheers,
Peter
Christian Edward Gruber-3 wrote:
>
> Hey,
>
> S
Hi,
Does the built-in email validator do client-side validation? I’m wondering if I
did something wrong here.
When I use the following, I do not get client-side validation:
Thanks in advance!
D
Forgot to mention the version I'm using - 5.1.0.5.
Thanks,
D
On 6/17/10 12:57 PM, "Dongmei Cao" wrote:
> Hi,
>
> Does the built-in email validator do client-side validation? I¹m wondering if
> I did something wrong here.
>
> When I use the following, I do not get client-side validation:
> v
As far as I know, there is no client validation associated to email
validator. It would be great to provide an empty js declaration, to
let developers provide a js implementation for the validator.
On Thu, Jun 17, 2010 at 9:57 PM, Dongmei Cao wrote:
> Hi,
>
> Does the built-in email validator do
On Thu, 17 Jun 2010 16:57:21 -0300, Dongmei Cao
wrote:
Hi,
Hi!
Does the built-in email validator do client-side validation? I’m
wondering if I did something wrong here.
It doesn't. Please file a JIRA at the Tapestry 5 issue tracker.
--
Thiago H. de Paula Figueiredo
Independent Java, A
I encountered this and use TestUtil (TestUtils?) to extract and set
properties without creating accessors/mutators. Makes the test read
a little less "O-O" but it's perfectly serviceable.
My only issue was that TestUtils is part of the tapestry convenience
test case hierarchy which depend
I have a form which is part of a zone which gets updated regularly (for
example, when the form is submitted).
the first time the pages loads, the form and its textfield's ids are as
expected ie exactly what is entered as t:id
eg
=
however, once the zone has been updated, the ids for the for
Hi All,
I've just noticed that if you update a zone that contains another zone,
you can no longer update the contained zone.
this may be related to my prior post regarding id's changing after a
zone update.
see example: (click 'update zone b' which works, click 'update zone a'
which works,
Regenerate your listeners when you do the partial page render; get the
clientId from each field and make sure you observe changes to that
element. Don't try to predict what ids Tapestry will use.
On Thu, Jun 17, 2010 at 2:29 PM, Paul Stanton wrote:
> I have a form which is part of a zone which g
Set an explcit id parameter for zone B. It looks repetitive, but it's
the correct thing here.
On Thu, Jun 17, 2010 at 2:56 PM, Paul Stanton wrote:
> Hi All,
>
> I've just noticed that if you update a zone that contains another zone, you
> can no longer update the contained zone.
>
> this may be
isn't that what i'm doing via
t:id="zoneB"
?
Howard Lewis Ship wrote:
Set an explcit id parameter for zone B. It looks repetitive, but it's
the correct thing here.
On Thu, Jun 17, 2010 at 2:56 PM, Paul Stanton wrote:
Hi All,
I've just noticed that if you update a zone that contains an
Thanks for the positive responses, folks. I appreciate it.
On 18/06/2010, at 4:58 AM, Howard Lewis Ship wrote:
> I'm looking to make replacing error bubbles easier, but that may be
> delayed to 5.3 now.
>
> On Thu, Jun 17, 2010 at 8:56 AM, Jim O'Callaghan
> wrote:
>> This is great Geoff thanks
Hi all,
I'd like to add an example or two to JumpStart of AJAX in a client-side
validator but I don't have any handy. If you have a simple example of this that
you'd like to throw into the mix then please post it here or, if you prefer,
mail it to me directly. I figure there may be more than on
On Thu, 17 Jun 2010 21:39:03 -0300, Paul Stanton
wrote:
isn't that what i'm doing via t:id="zoneB"?
No. t:id is the component id, while id is the HTML id. If you don't
provide the HTML id, the component will generate one based on the t:id.
--
Thiago H. de Paula Figueiredo
Independent Ja
On Thu, 17 Jun 2010 22:20:45 -0300, Geoff Callender
wrote:
Hi all,
Hi!
This is an example of a RGB string validator that I created for my
Tapestry courses (basic and advanced):
public class RGBValidator extends AbstractValidator {
final private static Pattern PATTERN =
Thanks, Thiago, but it lacks AJAX. I'd like the validator to behave like any
other client-side validator except that it asks the server to help, eg. to
validate that a name has not already been used.
Geoff
On 18/06/2010, at 12:24 PM, Thiago H. de Paula Figueiredo wrote:
> On Thu, 17 Jun 2010 2
On Thu, 17 Jun 2010 23:51:40 -0300, Geoff Callender
wrote:
Thanks, Thiago, but it lacks AJAX. I'd like the validator to behave like
any other client-side validator except that it asks the server to help,
eg. to validate that a name has not already been used.
Yep, I just noticed you wante
Hi,
i have used multiple options to invoke javascript on clicking linkSubmit,
but none works, although they all work with Submit.
a) Invoking javascript from tml page as follows:
function extraStep() {
alert("ENTER extraStep");
}
-${each.title}
[Approve]
When I use a Hidden component on a form for a bean property of type
Integer with a null value...
... I get the following error when submitting:
Caused by: java.lang.RuntimeException: Coercion of to type
java.lang.Integer (via String --> Long, Long --> Integer) failed: For
input string: ""
A tidier option is to wrap the tapestry component in a with an id
and use $("spansId").down()
Howard Lewis Ship wrote:
Regenerate your listeners when you do the partial page render; get the
clientId from each field and make sure you observe changes to that
element. Don't try to predict wh
29 matches
Mail list logo
