Does anyone have any feedback on this patch? I don't expect it is perfect
or complete, but I'd like to understand if this is the approach you'd expect
for implementing this feature.
https://issues.apache.org/jira/browse/ADFFACES-391
On 3/16/07, Danny Robinson [EMAIL PROTECTED] wrote:
OK,
Sorry - I've been wanting to have a look at it, but been
generally swamped. Hopefully soon...
-- Adam
On 4/20/07, Danny Robinson [EMAIL PROTECTED] wrote:
Does anyone have any feedback on this patch? I don't expect it is perfect
or complete, but I'd like to understand if this is the approach
OK, I've posted an initial patch so client-side validation matches
server-side here: https://issues.apache.org/jira/browse/ADFFACES-391
Feedback gratefully received.
Description:
Attached patch file will provide an alternative client-side validation mode
where message layout and appearance
Trinidad already has essentially the same functionality - input components
can be marked as autoSubmit, at which point tabbing out will automatically
trigger a server-side submit, and error messages will be automatically
inserted into tr:messages, if present. (There's an existing bug where
the
Guys,
Would there be support for an enhancement to the client-side validation so
that it behaves in the same way as the server-side logic? Meaning, we'd get
rid of the javascript alert dialog and instead dyanamically show/hide the
error messages in the page.
If so, I'll raise a JIRA issue and
may be you can use GWT compiler for client side validation as well, it is
also under Apache 2 license.
On 2/28/07, Danny Robinson [EMAIL PROTECTED] wrote:
Guys,
Would there be support for an enhancement to the client-side validation so
that it behaves in the same way as the server-side logic?
are you talking about still using JS for the client side
converter/validator stuff,
but just don't use alert(), instead using a web2.0-ish dialog ?
The validator/converter stuff isn't just an alert(). We have client
side Converter (with getAsObject/String) and Validators (with
validate) and
I was thinking that instead of displaying alert, the messages would appear
in the same place as they do in server-side. So keep the existing
javascript validator/converter stuff but change where/how it is displayed.
We'd probably have to render a hidden container for each field, which the
I've been reiterating the necessity for this time and again ;) - I'd
be pretty much for an addition like this.
regards,
Martin
On 2/28/07, Danny Robinson [EMAIL PROTECTED] wrote:
I was thinking that instead of displaying alert, the messages would appear
in the same place as they do in
I'd be happy to see functionality like this too. The trickiest part
is, I think, figuring out how to clear the messages.
I agree with Matthias that we don't need GWT. We already
have the client-side JS. It's just the code that decides to
turn the messages into an alert that is the problem.
the difference is with GWT, user can write java code for client side
validation instead of JS.
they can compile it with their own Java IDE.
but I also agree that adding another dependency to MyFaces is not good,
specially dependency to such a big project.
On 3/1/07, Adam Winer [EMAIL
11 matches
Mail list logo