Hi, I have gotten fckeditor to work fine using the cfc approach then I noticed that when enabling a url rewriter that the cfc was returning an url that the editors destination page passed into some js - the editor instance name.
Then I remembered the demos and looked through them again and found that the html demos worked just fine. Didn't have much changing over to this means of invoking fckeditor.
So my question is what am I really losing with this approach? Is this a really bad idea? It would seem that the browser check will happen in js and maybe there is a little fiddling with instances...but what is it I am losing... or put another way, what is the bennefit to using the cfc component approach?
Thanks,
John
Then I remembered the demos and looked through them again and found that the html demos worked just fine. Didn't have much changing over to this means of invoking fckeditor.
So my question is what am I really losing with this approach? Is this a really bad idea? It would seem that the browser check will happen in js and maybe there is a little fiddling with instances...but what is it I am losing... or put another way, what is the bennefit to using the cfc component approach?
Thanks,
John