Fc was a failure from the begining. It never had momentum because never was integrated with the Fb main enviroment. It's a pitty, but when Adobe announced the dead of Fc few people complain since it was not the right way. The Fc fail resembles the fail of Macromedia Brady the first Flex Builder based on Dreamweaver. It was clear that the product not had any sense at all but it was developed. Fc was the same history and here Adobe was not listening to the community so the product never was of real use...
For something like this to succed should be a real eclipse plugin to integrate with Eclipse and Fb and although both were sell separately should work seamless. Bu this is another story and have no sense to talk much more about it. 2012/1/10 Dimitri k. <k...@noos.fr> > This is a quick reminder of a petition I started a few weeks ago: >> Please sign it and enjoy designing nice looking Spark components with >> Flash Catalyst CS5.5 >> -- Sebastian >> > > Sorry, but it's clearly a lost battle from the start. > Adobe had to make difficult decisions with its reorientation toward > digital marketing/ digital media, but the abandon of Flash Catalyst must > have been one of its easier one. > Sales were poor. People already voted with their wallets. > It could have been a great tool for all of us, I know it was for a few > ones, but it's gone. > And also don't forget: Adobe won't developp the Design View in Flash > Builder anymore, because of the tight integration with the Apache Flex SDK > it would have required. Flash Catalyst would be worse, because part of the > SDK was in fact written to help FC compatibility. Without real control over > the SDK, FC is now almost impossible to handle for Adobe, in a ROI kind of > way anyway. > > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 CODEOSCOPIC S.A. <http://www.codeoscopic.com> Avd. del General Perón, 32 Planta 10, Puertas P-Q 28020 Madrid
