Re: Re: Re: Editable/non-editable fields

> > cc:

Re: Re: Editable/non-editable fields

<[EMAIL PROTECTED]> cc: 26/08/2002 18:03 Subject: Re: Re

RE: Editable/non-editable fields

ust 26, 2002 4:59 PM To: Struts Users Mailing List Subject: RE: Editable/non-editable fields I don't understand your "The html tags don't support this attribute " The struts tag html:text do have an attribute 'disabled' , so wat is it for , if its not rendered in

Re: Re: Editable/non-editable fields

Are you sure your web server is picking up the latest version of your code? (try adding , if it doesn't appear in your final html, you've got an answer :) ) >From a quick inspection of the code I have here (struts 1.0.2), the disabled >attribute should work (didn't test it yet though) hth, t

RE: Editable/non-editable fields

] Sent: Monday, August 26, 2002 10:59 AM To: Struts Users Mailing List Subject: RE: Editable/non-editable fields I don't understand your "The html tags don't support this attribute " The struts tag html:text do have an attribute 'disabled' , so wat is it for , if i

RE: Editable/non-editable fields

lt;[EMAIL PROTECTED] To:Struts Users Mailing List m> <[EMAIL PROTECTED]> cc: 2

RE: Editable/non-editable fields

lto:[EMAIL PROTECTED]] Sent: Monday, August 26, 2002 10:37 AM To: Struts Users Mailing List Subject: Re: Editable/non-editable fields Hi all; This list works too hard, some solutions comes out before I finish to type! How can you set the "disabled" attribute on the controls (in order to see an

Re: Editable/non-editable fields

Hi all; This list works too hard, some solutions comes out before I finish to type! How can you set the "disabled" attribute on the controls (in order to see an input field "grayed out")? If I put an 'mailto:[EMAIL PROTECTED]> For additional commands, e-mail:

Re: RE: RE: Editable/non-editable fields

g to, so I could very well be >mistaken. > >--Kevin > >-Original Message- >From: Sukhenko, Mikhail (Contr) [mailto:[EMAIL PROTECTED]] >Sent: Monday, August 26, 2002 10:08 AM >To: 'Struts Users Mailing List' >Subject: RE: RE: Editable/non-editable fiel

RE: RE: Editable/non-editable fields

EMAIL PROTECTED]] Sent: Monday, August 26, 2002 10:08 AM To: 'Struts Users Mailing List' Subject: RE: RE: Editable/non-editable fields The "grayed out" feature does not work on all the web browsers though. Be careful with that. I think even Netscape does not support it. -Original

RE: RE: Editable/non-editable fields

eld labels. Just my $0.02 worth . . . --Kevin -Original Message- From: Tom Klaasen [mailto:[EMAIL PROTECTED]] Sent: Monday, August 26, 2002 9:37 AM To: Struts Users Mailing List Subject: Re: RE: Editable/non-editable fields Hi Kevin, Thanks for your reply! This seems to be a good &quo

RE: RE: Editable/non-editable fields

. --Kevin -Original Message- From: Tom Klaasen [mailto:[EMAIL PROTECTED]] Sent: Monday, August 26, 2002 9:37 AM To: Struts Users Mailing List Subject: Re: RE: Editable/non-editable fields Hi Kevin, Thanks for your reply! This seems to be a good "second-choice" solution i

Re: RE: Editable/non-editable fields

Hi Kevin, Thanks for your reply! This seems to be a good "second-choice" solution in case the other one won't work. However, I'm afraid it would clutter the layout and confuse the user to have disabled and non-disabled fields mixed together. A non-editable field should be a html string inste

Re: RE: Editable/non-editable fields

Hi Sri, Thanks for your reply. There are a few problems though: 1) I don't like to have a myriad of logic:equal in the jsp's. They tend to become unmaintainable. 2) More important, there won't be one "global" canEdit property: each field would have to decide for itself whether it's editable

RE: Editable/non-editable fields

If I understand you question correctly, you want to dynamically determine whether to display the data in an editable manner or not. You could save the condition (that determines whether to allow edits or not) in the form bean and then do something like: <%-- Editable version goes here --%>

RE: Editable/non-editable fields

Could you set the "disabled" attribute on the controls? This would still display the info to the user, but they wouldn't be able to edit it. On a previous project, we hacked some of the Struts tags to support this attribute, it wasn't that hard. Maybe a few days of work. -Original Message-