Stefan, IMHO, there isn't much of a Witango App that you can "port" to CF. You have the html code, of course, but Cold Fusion lacks the central TAF structure, no actions. Everything has to be coded in the Web page itself. I view CF as being "page-centric", and Witango is not, allowing it to be much more flexible.
One more thing to be aware of: The newest CF is MX and I'd suggest before someone goes this direction, that they spend some time in the Macromedia forums and read about the problems. There are plenty. my $.02 Tom Ferguson > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Stefan Gonick > Sent: Wednesday, December 04, 2002 3:41 PM > To: Multiple recipients of list witango-talk > Subject: Witango-Talk: Conversion to ColdFusion Estimate > > > > > Hi All, > > I have an interesting question for you all. I have a potential client for > a large project. We have been discussing the merits of using Witango > versus something less risky. I mean risky in the sense that Witango > may not survive as a product in the long run. Of course, I hope that > Witango lives forever. > > My client asked me the question of what it would cost to convert > my large Witango program to ColdFusion in the worst case scenario. > I have learned some ColdFusion, but I have never tried to convert > a large Witango program to CF. I was wondering if anyone has > much experience with that and could give a relative estimate of > how long that would take. In other words, something like: "in my > experience it would take approximately 50% of the original > development time to convert the program to CF." The answer should > assume that I have become proficient in CF. > > Thanks in advance, > Stefan > ======================================================== > Database WebWorks: Dynamic web sites through database integration > http://www.DatabaseWebWorks.com > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
