|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Suggestion needed on UI fields editability
Submitted by Athen OShea on Fri, 09/05/2008 - 17:23.
Tags:
Clive_c wrote:
Hi Gurus,
I have a web application that persist some information. The information are displayed on the UI and the editability of the fields are dependent on certain condition/fields. Even the buttons are constraint by these conditions and fields.
Right now, these conditions/logic of determining if a field is editable or a button should be enable/disabled are encapsulated in a class. Is there anyway I can better manage them?
Appreciate responses from all.
Posted for user by Athen.