PastaPrimavera,
It is frustrating sometimes!
Flex has a larger file size than Flash because it has much more overhead in
its framework. But that framework is what enables us to move way beyond Flash
in terms of data manipulation. Flex can easily work with data and application
servers with its RPC components. Flash can do this, but it is neither as
intuitive or as simple IMO.
Flex code is compatible with code management systems; Flash code is not.
A Flash "application" will not scale like a Flex application will. Working
with a timeline is not suited for applications which need to work with lots of
different types of changing data. I use After Effects extensively for timeline
animation to create Flash video for my Flex applications. but I cannot imagine
building a business application within a timeline!
So we pay a bit of a price in file size just to get started using Flex with
all its components and features, in comparison to Flash. But I think it is
better in scenarios where we work with data and need the ability to scale and
expand the manipulation of that data. Flex applications are much easier to
debug, modify and expand than Flash apps as they really are full-blown
applications.
And don't forget the ability to turn your Flex app into a desktop app using
AIR.
Hang in there and pick your development "battles" wisely. Since you obviously
have a good grasp on Flash development, you will be able to transfer those
skills into Flex and become a killer RIA developer. Don't get frustrated, but
try to see the advantages of both worlds and leverage your existing Flash
skills into Flex development. Speaking for myself, I wish I had more knowledge
of Flash which I could apply to Flex, but Flash has always been rather
mysterious to me. So, you have a great advantage here... use it and don't give
up on Flex!!!

Thanks, i just got so excited when i started to learn Flash, because it opened
up a whole new world for us embedded guys. Think of all the networked stuff you
use that could benefit from a nice user interface such as your router, NAS,
printer....

I suppose like many new Flash programmers it leaves you rolling your eyes on
how to do something. No so intuitive... So when a bud of mine told me about
Flex, I tried the demo and GOT INSTANTLY HOOKED!!! I love the crap out of it.
The only downfall is that the dam file sizes are so friken large compared to
Flash that it limits me on the types of microprocessors I can use due to the
internal storage, which has to hold the web page & the system code as well.

I just figured that since I am new to Flex I must have been doing something
wrong and importing more than I needed to.

For instance when I define import flash.events.*;
To me ".*" Would mean the whole dam thing, all files for events.
When lets say I was just using a button. Then I would simply just use: import
flash.events.button.
I know that is not correct, but I hope it shows my point.
So rather than brining in the whole library using ".*" I could be more
specific in what I use from the library.

You're correct about the import statements. Importing just what you need will
reduce the file size. Using: import flash.events.MouseEvent is more efficient
than: import flash.events.*

Now I understand better what you're trying to do regarding embedding a web
page in a hardware device. Never done that. Please share any solutions you come
up with!

I sure will share, what I have to figure out is what I am using and to only import those. I have no idea where to start looking for that.

"PastaPrimavera" <webforumsuser@macromedia.com> wrote in message
news:gea656$lmu$1@forums.macromedia.com...
> Thanks, i just got so excited when i started to learn Flash, because it
> opened
> up a whole new world for us embedded guys. Think of all the networked
> stuff you
> use that could benefit from a nice user interface such as your router,
> NAS,
> printer....
>
> I suppose like many new Flash programmers it leaves you rolling your eyes
> on
> how to do something. No so intuitive... So when a bud of mine told me
> about
> Flex, I tried the demo and GOT INSTANTLY HOOKED!!! I love the crap out of
> it.
> The only downfall is that the dam file sizes are so friken large compared
> to
> Flash that it limits me on the types of microprocessors I can use due to
> the
> internal storage, which has to hold the web page & the system code as
> well.
>
> I just figured that since I am new to Flex I must have been doing
> something
> wrong and importing more than I needed to.
>
> For instance when I define import flash.events.*;
> To me ".*" Would mean the whole dam thing, all files for events.
> When lets say I was just using a button. Then I would simply just use:
> import
> flash.events.button.
> I know that is not correct, but I hope it shows my point.
> So rather than brining in the whole library using ".*" I could be more
> specific in what I use from the library.

Everything that is in the same swc with anything you import with it.

HTH;

Amy