|
|
|
|
|
|
by ebiester
5408 days ago
|
|
|
I thought that the CFML was the tag language and CFscript was considered separate, and this particular project didn't take advantage of CFscript, but looking around, people aren't too keen on the interfaces given to CFscript, even today. http://www.clearcrystalmedia.com/pm/full-cfscript-cfcs-not-w... http://www.forta.com/blog/index.cfm/2011/2/4/I-Am-Not-A-Fan-... I can speak to a similar adobe product, Flex (and MXML/ActionScript) and at least there, Adobe tried to figure out what would make most sense in MXML, and then the ActionScript interface fell out of that, rather than what made sense for an ActionScript interface. Then, Adobe pointed everyone to the MXML as documentation, rather than having a separate documentation for ActionScript. However, things didn't work exactly the same. Perhaps life is better in CFland, but Adobe has seemed to have "good enough? Then ship! Our devs will figure out workarounds." in their DNA. Looking at this thread -- http://forums.adobe.com/thread/507720 -- it seems ColdFusion is no exception. |
|
|