springframework-rcp-dev

[Springframework-rcp-dev] Optional error validation overlay

[Andy D. <an...@ma...>]

Hello all,
  As you know, if you have a form with a validation error then you get a 
really cool little "x" in the corner of the component with the error.  
However, I have some rather complex forms and there are some validations 
where I do not desire the little "x" error indicator on the component 
itself.  I want the validation error to prevent the user from 
committing, just like it does now, and I also want the error message in 
the top of the form, but I do not want the "x" on the component.
  I'm thinking about implementing a mechanism where you can tell the 
overlay helper not to "x" particular fields.  Does anyone else see this 
as a good idea?  If so, would it make more sense to put the flag on a 
field basis (maybe a flag in FieldMetadata or a userMetadata), a 
validation-type basis (certain validations do not produce the 'x' - 
maybe a new validation error type), or a component basis (a particular 
client property on the component)?  OR, maybe this functionality already 
exists, and I just don't know about it? :)

  Thanks,
    Andy

Re: [Springframework-rcp-dev] Optional error validation overlay

[Peter De B. <pet...@gm...>]

Andy,

I assume you're talking about custom components that you want to exclude
from the x-overlays.

In that case, I would go for the client property on the component.

Define a String
OverlayValidationInterceptorFactory.DONT_OVERLAY_PROPERTYconstant

then you can do the following in your form:

customComponent = ...;
customComponent.putClientProperty(
OverlayValidationInterceptorFactory.DONT_OVERLAY_PROPERTY, Boolean.TRUE);

then we can adapt the OverlayValidationInterceptor to ignore components that
have this property set tot true.

What do you think?

Peter

On 10/3/07, Andy DePue <an...@ma...> wrote:
>
> Hello all,
>   As you know, if you have a form with a validation error then you get a
> really cool little "x" in the corner of the component with the error.
> However, I have some rather complex forms and there are some validations
> where I do not desire the little "x" error indicator on the component
> itself.  I want the validation error to prevent the user from
> committing, just like it does now, and I also want the error message in
> the top of the form, but I do not want the "x" on the component.
>   I'm thinking about implementing a mechanism where you can tell the
> overlay helper not to "x" particular fields.  Does anyone else see this
> as a good idea?  If so, would it make more sense to put the flag on a
> field basis (maybe a flag in FieldMetadata or a userMetadata), a
> validation-type basis (certain validations do not produce the 'x' -
> maybe a new validation error type), or a component basis (a particular
> client property on the component)?  OR, maybe this functionality already
> exists, and I just don't know about it? :)
>
>   Thanks,
>     Andy
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Springframework-rcp-dev mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>

Re: [Springframework-rcp-dev] Optional error validation overlay

[Andy D. <an...@ma...>]

Thanks for the response, Peter.  Your assumption is correct (no overlay 
on custom component).  However, I just ran into a new case today where 
we have a certain type of validation that we want to always work in this 
way (validation error, but no "x").  I'm thinking the only way to 
accomplish this would be to add some sort of flag to the validation 
message itself?

  - Andy


Peter De Bruycker wrote:
> Andy,
>
> I assume you're talking about custom components that you want to 
> exclude from the x-overlays.
>
> In that case, I would go for the client property on the component.
>
> Define a String 
> OverlayValidationInterceptorFactory.DONT_OVERLAY_PROPERTY constant
>
> then you can do the following in your form:
>
> customComponent = ...;
> customComponent.putClientProperty(OverlayValidationInterceptorFactory.DONT_OVERLAY_PROPERTY, 
> Boolean.TRUE);
>
> then we can adapt the OverlayValidationInterceptor to ignore 
> components that have this property set tot true.
>
> What do you think?
>
> Peter
>
> On 10/3/07, *Andy DePue* <an...@ma... 
> <mailto:an...@ma...>> wrote:
>
>     Hello all,
>       As you know, if you have a form with a validation error then you
>     get a
>     really cool little "x" in the corner of the component with the error.
>     However, I have some rather complex forms and there are some
>     validations
>     where I do not desire the little "x" error indicator on the component
>     itself.  I want the validation error to prevent the user from
>     committing, just like it does now, and I also want the error
>     message in
>     the top of the form, but I do not want the "x" on the component.
>       I'm thinking about implementing a mechanism where you can tell the
>     overlay helper not to "x" particular fields.  Does anyone else see
>     this
>     as a good idea?  If so, would it make more sense to put the flag on a
>     field basis (maybe a flag in FieldMetadata or a userMetadata), a
>     validation-type basis (certain validations do not produce the 'x' -
>     maybe a new validation error type), or a component basis (a particular
>     client property on the component)?  OR, maybe this functionality
>     already
>     exists, and I just don't know about it? :)
>
>       Thanks,
>         Andy
>
>
>     -------------------------------------------------------------------------
>     This SF.net email is sponsored by: Splunk Inc.
>     Still grepping through log files to find problems?  Stop.
>     Now Search log events and configuration files using AJAX and a
>     browser.
>     Download your FREE copy of Splunk now >> http://get.splunk.com/
>     _______________________________________________
>     Springframework-rcp-dev mailing list
>     Spr...@li...
>     <mailto:Spr...@li...>
>     https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Springframework-rcp-dev mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>   

Re: [Springframework-rcp-dev] Optional error validation overlay

[Peter De B. <pet...@gm...>]

Andy,

Just to make sure we're on the same track:

1. there are some custom components that you want exclude from the overlay
mechanism
2. there are certain (type of) constraints that you always want to exclude
from the overlay mechanism -> do you still want the error message to show at
the top of the dialog??

Peter

On 10/4/07, Andy DePue <an...@ma...> wrote:
>
> Thanks for the response, Peter.  Your assumption is correct (no overlay
> on custom component).  However, I just ran into a new case today where
> we have a certain type of validation that we want to always work in this
> way (validation error, but no "x").  I'm thinking the only way to
> accomplish this would be to add some sort of flag to the validation
> message itself?



That would be difficult. The validation message is just that: a message.


  - Andy
>
>
> Peter De Bruycker wrote:
> > Andy,
> >
> > I assume you're talking about custom components that you want to
> > exclude from the x-overlays.
> >
> > In that case, I would go for the client property on the component.
> >
> > Define a String
> > OverlayValidationInterceptorFactory.DONT_OVERLAY_PROPERTY constant
> >
> > then you can do the following in your form:
> >
> > customComponent = ...;
> > customComponent.putClientProperty(
> OverlayValidationInterceptorFactory.DONT_OVERLAY_PROPERTY,
> > Boolean.TRUE);
> >
> > then we can adapt the OverlayValidationInterceptor to ignore
> > components that have this property set tot true.
> >
> > What do you think?
> >
> > Peter
> >
> > On 10/3/07, *Andy DePue* <an...@ma...
> > <mailto:an...@ma...>> wrote:
> >
> >     Hello all,
> >       As you know, if you have a form with a validation error then you
> >     get a
> >     really cool little "x" in the corner of the component with the
> error.
> >     However, I have some rather complex forms and there are some
> >     validations
> >     where I do not desire the little "x" error indicator on the
> component
> >     itself.  I want the validation error to prevent the user from
> >     committing, just like it does now, and I also want the error
> >     message in
> >     the top of the form, but I do not want the "x" on the component.
> >       I'm thinking about implementing a mechanism where you can tell the
> >     overlay helper not to "x" particular fields.  Does anyone else see
> >     this
> >     as a good idea?  If so, would it make more sense to put the flag on
> a
> >     field basis (maybe a flag in FieldMetadata or a userMetadata), a
> >     validation-type basis (certain validations do not produce the 'x' -
> >     maybe a new validation error type), or a component basis (a
> particular
> >     client property on the component)?  OR, maybe this functionality
> >     already
> >     exists, and I just don't know about it? :)
> >
> >       Thanks,
> >         Andy
> >
> >
> >
> -------------------------------------------------------------------------
> >     This SF.net email is sponsored by: Splunk Inc.
> >     Still grepping through log files to find problems?  Stop.
> >     Now Search log events and configuration files using AJAX and a
> >     browser.
> >     Download your FREE copy of Splunk now >> http://get.splunk.com/
> >     _______________________________________________
> >     Springframework-rcp-dev mailing list
> >     Spr...@li...
> >     <mailto:Spr...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Springframework-rcp-dev mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Springframework-rcp-dev mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>

Re: [Springframework-rcp-dev] Optional error validation overlay

[Andy D. <an...@ma...>]

You are correct!
Yes, the error message should still appear at the top AND the form 
should not be committable, but the "x" overlay should not appear.

  - Andy

Peter De Bruycker wrote:
> Andy,
>
> Just to make sure we're on the same track:
>
> 1. there are some custom components that you want exclude from the 
> overlay mechanism
> 2. there are certain (type of) constraints that you always want to 
> exclude from the overlay mechanism -> do you still want the error 
> message to show at the top of the dialog??
>
> Peter
>
> On 10/4/07, *Andy DePue* <an...@ma... 
> <mailto:an...@ma...>> wrote:
>
>     Thanks for the response, Peter.  Your assumption is correct (no
>     overlay
>     on custom component).  However, I just ran into a new case today where
>     we have a certain type of validation that we want to always work
>     in this
>     way (validation error, but no "x").  I'm thinking the only way to
>     accomplish this would be to add some sort of flag to the validation
>     message itself?
>
>
>
> That would be difficult. The validation message is just that: a message.
>  
>
>       - Andy
>
>
>     Peter De Bruycker wrote:
>     > Andy,
>     >
>     > I assume you're talking about custom components that you want to
>     > exclude from the x-overlays.
>     >
>     > In that case, I would go for the client property on the component.
>     >
>     > Define a String
>     > OverlayValidationInterceptorFactory.DONT_OVERLAY_PROPERTY constant
>     >
>     > then you can do the following in your form:
>     >
>     > customComponent = ...;
>     >
>     customComponent.putClientProperty(OverlayValidationInterceptorFactory.DONT_OVERLAY_PROPERTY,
>     > Boolean.TRUE );
>     >
>     > then we can adapt the OverlayValidationInterceptor to ignore
>     > components that have this property set tot true.
>     >
>     > What do you think?
>     >
>     > Peter
>     >
>     > On 10/3/07, *Andy DePue* < an...@ma...
>     <mailto:an...@ma...>
>     > <mailto:an...@ma... <mailto:an...@ma...>>>
>     wrote:
>     >
>     >     Hello all,
>     >       As you know, if you have a form with a validation error
>     then you
>     >     get a
>     >     really cool little "x" in the corner of the component with
>     the error.
>     >     However, I have some rather complex forms and there are some
>     >     validations
>     >     where I do not desire the little "x" error indicator on the
>     component
>     >     itself.  I want the validation error to prevent the user from
>     >     committing, just like it does now, and I also want the error
>     >     message in
>     >     the top of the form, but I do not want the "x" on the
>     component.
>     >       I'm thinking about implementing a mechanism where you can
>     tell the
>     >     overlay helper not to "x" particular fields.  Does anyone
>     else see
>     >     this
>     >     as a good idea?  If so, would it make more sense to put the
>     flag on a
>     >     field basis (maybe a flag in FieldMetadata or a userMetadata), a
>     >     validation-type basis (certain validations do not produce
>     the 'x' -
>     >     maybe a new validation error type), or a component basis (a
>     particular
>     >     client property on the component)?  OR, maybe this functionality
>     >     already
>     >     exists, and I just don't know about it? :)
>     >
>     >       Thanks,
>     >         Andy
>     >
>     >
>     >    
>     -------------------------------------------------------------------------
>     >     This SF.net email is sponsored by: Splunk Inc.
>     >     Still grepping through log files to find problems?  Stop.
>     >     Now Search log events and configuration files using AJAX and a
>     >     browser.
>     >     Download your FREE copy of Splunk now >> http://get.splunk.com/
>     >     _______________________________________________
>     >     Springframework-rcp-dev mailing list
>     >     Spr...@li...
>     <mailto:Spr...@li...>
>     >     <mailto:Spr...@li...
>     <mailto:Spr...@li...>>
>     >    
>     https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>
>     >
>     >
>     -------------------------------------------------------------------------
>     > This SF.net email is sponsored by: Splunk Inc.
>     > Still grepping through log files to find problems?  Stop.
>     > Now Search log events and configuration files using AJAX and a
>     browser.
>     > Download your FREE copy of Splunk now >> http://get.splunk.com/
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Springframework-rcp-dev mailing list
>     > Spr...@li...
>     <mailto:Spr...@li...>
>     > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>     >
>
>     -------------------------------------------------------------------------
>     This SF.net email is sponsored by: Splunk Inc.
>     Still grepping through log files to find problems?  Stop.
>     Now Search log events and configuration files using AJAX and a
>     browser.
>     Download your FREE copy of Splunk now >> http://get.splunk.com/
>     _______________________________________________
>     Springframework-rcp-dev mailing list
>     Spr...@li...
>     <mailto:Spr...@li...>
>     https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Springframework-rcp-dev mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>