Title:
Bug 78843:(Watson Migration Closure)Summary: add CF-ORM support to CFFORMWouldn’t it be nice if one could do this:[code]<cfform entity="myEntity">[code]This would take either the name of an entity (for a data entry form for a new object
| View in TrackerStatus/Resolution/Reason: Closed/Deferred/
Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)
Created: 07/16/2009
Components: CFForm, Standard XML
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 1
Problem:
Summary: add CF-ORM support to CFFORMWouldn’t it be nice if one could do this:[code]<cfform entity="myEntity">[code]This would take either the name of an entity (for a data entry form for a new object), or an entity instance which would provide a form for updating an existing entity.This would generate a form with input controls for each property of the entity, using sensible control types, and possibly a wee bit of clientside validation (number types must be numbers, etc).A lot of people poopoo <cfform>, based a lot on its history of being quite rubbish, but I think it’s actually come a long way, and whilst not the 100% solution to all situations, it’s an 80% solution for 80% of requirements.I also think for a lot of the hoi polloi, being able to combine quick-and-dirty forms with quick-and-dirty ORM would be a godsend. And fits that RAD notion that CF is so fond of espousing, too.Also see discussion here: https://prerelease.adobe.com/project/forum/thread.html?cap=87529bda13744b3db718e841890b9240&forid={267a8bea-8d25-435c-a533-6c830dd686ca}&topid={747fe802-c16c-4e20-9d5e-b6b42cfc65f8}-- Adam
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3039312
External Customer Info:
External Company:
External Customer Name: Adam Cameron
External Customer Email: 17EB1A7649DA54C7992015A9
External Test Config: 07/16/2009
Attachments:
Comments: