Comments on: Ext.CFC: Easing Integration with Ext and Adobe ColdFusion

By: Tribulus

Tribulus — Mon, 22 Sep 2008 17:42:59 +0000

thanks for that…

By: Jon Hartmann

Jon Hartmann — Tue, 11 Dec 2007 13:49:21 +0000

@JeffHowden: You’re right that Ext has a very complex data layer, in fact I’d argue that it might be the most important aspect of Ext, but it still lives in presentation land because it is limited to client side processing. If you use a CFC to abstract your Ext objects, its doing exactly the same thing as if you used custom tags to abstract it, because all the CFC or custom tag are doing is converting what you setup into a string of JS for the front end. If you were to write a CFC that Ext interacted with via asynchronous calls it would be different, but thats still the presentation layer communicating with your processing/data.

By: JeffHowden

JeffHowden — Tue, 11 Dec 2007 08:58:59 +0000

@Jon Hartmann: Ext also has a substantial data layer for working with data to and from the server making CFCs an excellent candidate for that portion of the transaction and making Ext not so solidly in presentation land as you originally described.

By: Jon Hartmann

Jon Hartmann — Mon, 10 Dec 2007 18:11:58 +0000

Thats a very nice setup, but for some reason I can’t help but want ext built into custom tags rather then CFCs, as I tend to equate in my mind that CFCs = processing, and Custom Tags = presentation. Ext lies solidly in presentation land, thus custom tags. Awesome work though, and don’ let CF8′s integration discourage you… Adobe didn’t port even half of Ext to tags, and didn’t do a perfect job at what it did.

By: Cutter

Cutter — Mon, 10 Dec 2007 17:53:00 +0000

I look forward to reviewing the code here. First glimpse, nice work.

By: Rey Bango

Rey Bango — Mon, 10 Dec 2007 17:10:38 +0000

@Dion: Thanks man. Great to see CF love on Ajaxian. :)

Ext.CFC was created by Brian Love and he’s pretty excited about extending it further out and updating it to use Ext 2.0