I'm proposing to use what the SDK has to offer, mx and spark, and add
a thin wrapper class around each of those: goog. However, the goog
components don't add any functionality, they only provide support for
the JS workflow. From a developer point of view they'll look and act
just like their mx and
There is already precedence for mapping existing components to a new
namespace. Some spark components are just MX components also referenced
from the spark manifest (SWFLoader, ArrayCollection).
So yes, while I still have reservations about your approach and wish I could
convince you to join me
Alex,
So yes, while I still have reservations about your approach and wish I could
convince you to join me on my re-write, I think you are making a good
proposal for helping folks know the boundaries on what components you are
supporting.
I will join you with your work on FlexJS, don't
Something isn't clear to me.
Are you proposing that the AS3 code for Flex contains 3 groups of
components? (mx or it's equivilent, spark, and goog)
Or are you proposing that there are 2 groups of AS3 components, mx and
spark, and one set of JS components (goog) which have different levels
of
