On 10/3/12 7:38 AM, "christofer.d...@c-ware.de" <christofer.d...@c-ware.de>
wrote:
> Oh ... let me thow in a little more weight for the Catalyst ;-)
>
> I invested quite some time in setting up a project structure that allowed me
> to concentrate on developing (Using an ugly but functional developer Skin) and
> having professional Designers use Catalyst to Skin the application.
> Unfortunately it seemed that the designers available on the market were all
> even less "finished" than the Catalyst project, but as soon as the designers
> got the hang of it, the results were pretty sattisfying and I had what I was
> allways dreaming about: Being able to concentrate on the functionality and
> have a designer do all the stuff that sells the application (cool buttons,
> even greater effects and animated transitions, ...) :-)
>
> I would be really happy if Adobe didn't entirely drop this tool, and if they
> did, If they would somehow open-source it.
>
It is essentially "dropped". See [1]. There are no plans to opensource
it. It too had a lot of "baggage" that made it difficult to implement. For
example, it really wasn't extensible as to what components it could handle.
The principle behind it (that you can take designer art and break it down
into components) is compelling, but I question whether it remains valid in a
world of dynamic UI.
It is also interesting to note that you used it in completely different way
than it was intended. It was for a design-first-then-develop workflow and
you did it the other way (which is what I do when I have a choice as well).
[1] http://www.adobe.com/devnet/flex/whitepapers/roadmap.html
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
