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 Message----- From: Kevin A. Smith [mailto:[EMAIL PROTECTED]] Sent: Monday, August 26, 2002 9:51 AM To: Struts Users Mailing List Subject: RE: RE: Editable/non-editable fields We went back and forth on this on my project, also. What was finally agreed upon was that it might be less confusing for the user to see an input field "grayed out" a la Windows, than to see input fields replaced with text strings, looking like field 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 "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 instead of a html input ... Thanks again tomK ------------------------ "Struts Users Mailing List" <[EMAIL PROTECTED]> wrote: ------------------------ >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----- >From: Tom Klaasen [mailto:[EMAIL PROTECTED]] >Sent: Monday, August 26, 2002 9:09 AM >To: [EMAIL PROTECTED] >Subject: Editable/non-editable fields > > >Hi all, > >It's been some time, but it seems I'm back :) > >I'm currently working on a project where lots of forms are used. The >forms are backed up by a DB. Somewhere in the DB, there is a table which >tells me which fields should be editable and which shouldn't (they >should only be displayed). > >Until now, we were looking in the db manually, and changing tags if some >field changed from editable to non-editable. > >We want to change that: let our application look in the db and decide >whether the current property should be editable or not. > >I've already implemented this for html:text fields (which was fairly >trivial), but now I want to do this for html:select fields also. This >seems to be less trivial to say the least. > >I just looked around on the net and found >http://struts.application-servers.com, but it seems to be too >restricting in terms of layout and granularity. > >Does anybody has any pointers on solutions for editable/non-editable >fields? Basically I want one tag that can decide whether it's editable >or not (based on business logic that I provide). Eg a text tag that is >editable would generate the same output as html:text, if it's not >editable it would be a bean:write followed by a html:hidden. > >(I've used struts some months ago, and I'm not totally up to speed with >its recent developments, so please forgive me if this is a trivial >question.) > >Any pointers are appreciated! > >Thanks, >tomK > > >-- >To unsubscribe, e-mail: > >For additional commands, e-mail: > > > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
