|Posted: 03/31/2010, 1:56 AM
Building on bobsmith's post below, I would like to highlight the need for the following specifically in relation to EDITABLE GRIDS
• Editable grids that support underlying datasources containing fields with defaults.
Currently CCS assumes that an empty row with a default is the same as a new record and saves it. The workaround solutions outlined below restrict the use of various server side events
See these posts:
• Autofill support in Editable Grids including support for listboxes
See the following code examples for the workaround solution and please implement out of the box:
• Consistent naming conventions for control ids in editable grids.
• Out-of-the-box options in editable grids for not only "how many empty rows" but how many empty rows OR "new empty row button" or "automatic empty row" as per the examples in the example pack.
It seems that Editable Grids are such an important feature and so widely used that better implementation would really add a lot to the product and to clean development.
The custom solutions can get very messy when you have to break the CCS grayed out code. The worry when custom coding also is that what happens when a new version comes out? May be my code will all fail. That's why we need consistent naming and full integration of features.
RAD tools for rich UI controls: