This content has been marked as final. Show 6 replies
I've tried to work with cfwindow before and I was getting lots of errors with IE, and then I found a perfect solution CF_WINDOW custom tag. I tell you it's awesome and on top of it its free! Also look into <cfpod/> tag, you might find some solutions in there!
First of all, thank you for this information (I am more confident about this now that I understand that I am not alone to deal with those problems).
I am trying to find the source of this custom tag from the web but in the meantime, could you post the link here?
You got it!
It is finally not a "so-good" solution for me at this moment as I am rushing about time and this solution is screwing the normal library of ColdFusion 8. It is better, I admit but will require a lot of work in order to replace what I am already use from CF8 (right now, the page has CFFORM, CFLAYOUT, CFWINDOW, CFGRID, and many Ajax functionalities). I do not know how many deep I will have to work if I decided to use this solution but right now, the system is not supporting TAB from CFLAYOUT and CF_WINDOW together.
I actually hope to have some time soon to take all the library (or at least all the basic elements I am often use in my web applications) of EXT2 and apply them as a central library for all my projects. But I was looking for a fast turn-around for the glitch I encountered. I have now to demolish what I've developing since 2 days and start a new way to do it (which is longer and not so kool as it was to have all steps joined together on a single page).
Thank you very much by the way!
I finally change my interface completely! I decided to go with step-by-step philosophy as I had to much problem to play with a single page to accommodate all the information and forms. The step-by-step method I decided to use is involving a CFLAYOUT which is change from simple AHREF link (where I use images instead of text to be more stylish for the user) click. This actually help me to finish that part of the application (after 2 intensive days of bugs investigation concerning the new features of CF8). I am not saying that the problem is CF8, in a contrary, but we have to be careful when using the new tags because some combinations can be a nightmare to figure out the proper way - to not say that is it not possible to be used in combination at all for some of them.
Please note that all datefield input are working perfectly now. I do not know what was the problem exactly but I suspected that it was concerning embedding tags into tags such as CFFORM within CFWINDOW within CFLAYOUT/CFLAYOURAREA within CFFORM. I still want to turn myself to the EXT2 library but the time, as I said before, is a big issue for me (as I miss the appropriate time to do it). Perhaps CF9 will be on a beta version soon and I will be able to figure out faster as they certainly expect to use the EXT2 in the next version.