[
https://issues.apache.org/jira/browse/PIVOT-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055520#comment-13055520
]
Edvin Syse commented on PIVOT-761:
----------------------------------
Yes, and I think it should, because all components can benefit from Validators.
I created a custom DateTimePicker the other day by combining a CalendarButton
and some Spinners inside a BoxPane, and it would be nice if the subclassed
BoxPane could handle the validation.
If Component#store() delegates to a public Component#validateInput(), so that
you can run validateInput() without actually storing, you could also let form
type components choose when to run validateInput(), for example on blur, on
keydown etc.
I created Swing Data Binding last year that implements many of these ideas, and
I must say it works very well in practice :) See http://databinding.tornado.no.
> Test a more generic Validation approach on fields and Containers (Forms, etc)
> -----------------------------------------------------------------------------
>
> Key: PIVOT-761
> URL: https://issues.apache.org/jira/browse/PIVOT-761
> Project: Pivot
> Issue Type: Brainstorming
> Components: wtk
> Reporter: Sandro Martini
> Assignee: Sandro Martini
> Priority: Minor
> Fix For: 2.1
>
>
> Investigating on this field ... both on validating single fields (not only
> text input fields) and Container (like Forms), like in JSF.
> Some reference here:
> http://apache-pivot-developers.417237.n3.nabble.com/Text-validators-td3078385.html
> General idea: put investigation code under /skunk and the minimal set of
> interfaces and classes, and the rest outside (in a dedicated subproject, here
> or under apache-extras).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
