Coldfusion UI Tags Suggestion
Coldfusion, SuggestionA Rob Brooks-Bilson post touched a nerve of mine regarding Coldfusion's UI tags, like cfform and cfwindow. As well as its integration with third party libraries, such as Verity. In short, they're great if you can live within their limits. But, if you need to go beyond it's a big can't-get-there-from-here.
Take cfform for instance, great idea, but what happens when you start to need things like related select boxes? Little challenging. Or in the more recent case, the issue is the libraries continue to advance, such as Ext and FCKEdit, but the Coldfusion tags lag behind.
My suggestions:
- divorce the release cycles between UI/third-party integration tags and Coldfusion
- open source the UI tags with a license that requires changes be made freely available
Ben Davies said:
Its unfortunate, but the example you chose - Relating select lists - is now insanely easy with CF8. The binding features make this trivial.
But in general I agree whole-heartedly that this is a problem. I believe the CF tags should be abstracted from the implementation - sort of like the Java API. Adobe would supply an implementation but should make integrating your own implementation easy - as lonq as you implement the interface.
This implies an overhaul of some of the tags to make them consistent (attribute-wise) and vendor-neutral (someone suggested CFPIM instead of CFEXCHANGE, for example).
This abstraction of the implementation from the interface would probably make the whole platform somewhat more testable and force the CF-team to take a long-term approach to language development.
From my perspective I see too many developers 'out-grow' Coldfusion when they hit these limits in flexibility and extensibility - its definately worthwhile solving.
Cheers
But in general I agree whole-heartedly that this is a problem. I believe the CF tags should be abstracted from the implementation - sort of like the Java API. Adobe would supply an implementation but should make integrating your own implementation easy - as lonq as you implement the interface.
This implies an overhaul of some of the tags to make them consistent (attribute-wise) and vendor-neutral (someone suggested CFPIM instead of CFEXCHANGE, for example).
This abstraction of the implementation from the interface would probably make the whole platform somewhat more testable and force the CF-team to take a long-term approach to language development.
From my perspective I see too many developers 'out-grow' Coldfusion when they hit these limits in flexibility and extensibility - its definately worthwhile solving.
Cheers
Loading....