Ray, removing CF File support from Dreamweaver means the WHOLE PRODUCT is useless in ColdFusion sites. You can't use any of the Dreamweaver product to develop a ColdFusion site because you can't open the files. Unless you build a whole bunch of static html pages, lay them out and design them and do all that stuff, THEN convert them to ColdFusion pages, Dreamweaver's useless.
But not if you build them in the competitor's technology PHP instead. Why on earth would they retain support for the competitor, but not their own for pete's sake?? What sense does that make?? On Wed, Jun 19, 2013 at 12:16 PM, Raymond Camden <raymondcam...@gmail.com>wrote: > > On Tue, Jun 18, 2013 at 8:31 PM, Mike K <afpwebwo...@gmail.com> wrote: > > > > > Adobe really have no clue how to support and market any server products. > > I said that when i saw what a fiasco the forms product was for them, > now > > it looks like ColdFusion is 'deprecated' too. > > > > > *sigh* > > Let me repeat myself. > > The ColdFusion team is working on 11. Right now. > The ColdFusion team is working on an update to ColdFusion Builder. Right > now. > > If you want to consider the removal of *file* support from one product as > MORE IMPORTANT then the actual product itself - so be it. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:356002 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
