Good question Stefan. :) I'm thinking about this question for a long time too, well, since I'v not seen Flash CS3 component set yet, and I'm not very familar with Flex 2 components(Although i'v read their source code a lot).
Here's some guessings: 0. AsWing is Open Source, AsWing A2 is in maintaining for 2 years, it is very stable now, there's successful commercial products based on it. AsWing community is active, you generally will get response in 24 hours for any question posted on the AsWing Mailling List. There's third party support too, Many LookAndFeels developed by Rustem and Igor, FvAsWing(a part of Fever framework) is based on AsWing A2 too. 1. The big advantage only come into existence when you are familiar with Java Swing and not familiar with Flex 2 components API, AsWing's architecture is based on java swing, most api is same to swing, so if you know how to use JXXX component and LayoutManagers like BorderLayout, FlowLayout, you'll feel at home when use AsWing, you can create your application interface at once with out long time study 2. I don't know whether this is a advantage for every one, but it is a advantage for me, it is that you can create your UI with AS3 directly without MXML, i know that we can't create Flex2 UI only with AS3 generally, right?. Well, can we use MXML to create AsWing UI? We can't right now, but this is a planned feature, we'll implement it in near future. 3. AsWing is light-weight than Flex 2 component set. From a friend of mine, he told me that Flex 2 Components is very heavy, he used serveral components, then got 300+ kb swf size, and from reading the source code of Flex 2 components, i can say that Flex 2 component is really very heavy. AsWing A3 is light-weight than it. For a general use of serveral components, you just got about 150+ kb. Hmm, that means AsWing is about half weight of Flex 2 components.And, i can't see that the ability less, so there is a maybe advantage of AsWing is that: It use half weight code to get almost same ability for components. 4. AsWing is well architectured, a well known in java world that Swing is some how bad, because it do a lot dirty thing to keep AWT components, and JComponent inherited from AWT Container too. But pure Swing is very well architectured, MVC supported very well. AsWing do not need to keep AWT, so, you can consider AsWing is like "Swing without AWT". 5. Easy skin, LookAndFeel system is powerful, you can change both Look(Skin) and Feel(control) for every component. However, write a full LookAndFeel is not easy, so we developed a especial LookAndFeel named SkinBuilderLAF, it embeded a series images to skin the components, so, you can change the component look by just replace image files and recompile. 6. For Flash CS3 component set, it is not out yet, so i can't say any thing, but i guess, it is a very light-weight component set, so it just with small ability, it may not have LayoutManager, may not have MVC support, may not have some advanced feature for complex UI. We can wait and see, i think Flash CS3 component set would be a very great component set, but it can't be best suitable for everywhere. 7. Why not try it, it is just a choice, it is bad or good only be felt after you deeply used it. :) Regards~~ /iiley 16 Apr 2007 05:12:44 -0700, Stefan Schmalhaus <[EMAIL PROTECTED]>:
--- In [email protected] <flexcoders%40yahoogroups.com>, iiley <[EMAIL PROTECTED]> wrote: > > *==========AsWing A3 0.8=========* What's the advantage of the "AsWing A3" component set over the Flex 2 components or the new Flash CS3 component set? Stefan
-- iiley AsWing http://www.aswing.org Personal http://www.iiley.com
