After Alex mentioned FXG, one important question comes to light:
should Apache Flex keep use FXG as skining tool?
as FXG is tightly linked to Adobe and its tools, can we count on Adobe
to continue to maintain the use of it? especially in Creative suite tools?
by the way, why Adobe chose to use new FXG, instead of SVG? (i bet the
answer as already been given a few times, sorry for asking again)
Alex, can you please enlighten us on that subject?
Thanks
Le 03/10/2012 19:37, Alex Harui a écrit :
On 10/3/12 10:21 AM, "christofer.d...@c-ware.de" <christofer.d...@c-ware.de>
wrote:
Well isn't it usually that way around?
I create some general UI scetches using some tools like blamiq mockups and
deal with negoitating the functionallity with my customers. As soon as the
component works as desired I go "pimp my app" and give it to a designer to
have it pimped.
I rarely ever "finish" an app, but that would be my preferred workflow as
well.
Using Catalyst this was really easy (As soon as you had a desiger at hand that
was used to it and it's concepts). I was even able to let the designer skin a
running application deployed by me somewhere on the web, so I didn't have give
away the code of the application itself or setup the environment at the
designers office. This workflow was the major breakthrough for me and was one
of the major things that made me shift allmost entirely to the Flex road.
I doubt you need Catalyst to implement this workflow. What would really be
the best way to implement it? Wouldn't it be using PS/FF and exporting to
FXG and then having a way to inject FXG into your app? That sounds much
more possible.
