The cool thing is the future :)
Adobe wants to correct this bias; Flash Builder will happen, and the
distinction between Flex Builder and Flex framework will melt. There
we will be happy and everything :)
The IDE is about to get all dressed up for a sexy evening ;)
Now, if one could, he/she can reinvent its wheel, developping his/her
own framework, handling data processes and liquid layouts and more
all with Flash, that's not a problem.
The current really nice thing about the flex framework is how simple
it is to build up something **quickly**; the current downside of the
flex framework is that some people do not know that everything under
it is a Flash Player thing.
Next, people won't even know how to build their own buttons :(
(the last paragraph is optional and not intended to pun anyone)
As Paul says, the crucial part is to know when to use the Flex
Framework, because as all frameworks, it *can* have its downside.
Anyways, the easier way to build up applications is to use Flex
Builder and Flex Framework. But we all know that good Flex
applications are all customized and built upon strong knowledge of
Flash.
Cedric
Henrik Andersson wrote:
Paul Andrews wrote:
Stuff
Allow me to summarize your post:
You think that Flash is good for graphical projects, such as
animations. You also think that Flex builder is better for
creating software.
You like the Flex components and how they are data driven.
You acknowledge that Flex projects end up larger, due to having
more code doing stuff instead of the authoring tool.
My opinion:
I think that Flash is better for anything that isn't strictly code
only, and that is more or less all projects, since it's quite
boring to design graphics using code.
I would disagree with that statement since it implies that Flex
doesn't support IDE based graphical design - which it does - but
only for components and not general design work. Your statement
also forgets the tedium of building complex layout management of
the kind that comes with Flex.
The upcoming code completion in Flash CS 5 seems to take care of
most coding needs in my opinion. It's not going to give you any
fancy class feature listing panels or profilers, but those are
rarely needed.
I would say I can't really comment on CS5, but it seems to be a
catchup game with Flex and coding support. A lot of developers
would strongly disagree with the idea that class documentation
support or profiling is rarely needed - it's more a question of
project scale and coding emphasis perhaps.
If I had to chose what to use, I would use Flash, because I want
to use the full swf format. I do not think that Flex alone can do
that.
Anything that the swf format supports can be achieved using Flex
(albeit via actionscript, than perhaps IDE support).
I'm not knocking Flash - it's far better for many tasks than Flex
and vice-versa.
Paul
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
