Flex is an awesome product.Period. Atleast until version 3. Then they bloated it. The new spark component makes it easy to do the skinning but it costs a big deal in download time.
I am not sure there is anything flex specific in the Flash Player Runtime. Flex is totally written with AS3 and the flash player runs AS3. The path I would suggest the Apache Flex guys to go is towards creating a Flex to JS/HTML5 Cross compiler. This would be something that would help them quite a lot. Write code with AS3 and output to JS. There are quite a lot of Flex apps out there ( especially in the corprate world ). Given that adobe has given up on Flex ( which means they wont have any premium support ) these guys will be looking for a solution that can work as good as their current applications. Ofcourse, the big players ( especially in the financial industry ) are going to be slow to move. They wont change something just because Adobe wont support it quite in the future. They would be looking to change. This is the point where the Apache Flex community needs to catch up on. Flex is currently the biggest load on a ship called Flash Player Runtime. There is a significantly large hole in this ship. That would not have been the case, if Adobe had not shot itself in the foot, but that is a different topic altogether. Now, if one of the biggest load happens to unload quite fast onto another boat the rest of the smaller entities on the ship can jump on. If not, the other smaller entities wont die. They will just become a fish :) . Everything evolves, the question is how do you want to evolve! On Thu, Jan 12, 2012 at 5:38 PM, Ron G <rgri...@sinclairoil.com> wrote: > ** > > > Hi James, > > I certainly respect the decision of those who are sticking with Flex, but > I would suggest that developers do so with the recognition that they may be > developing with a technology that isn't going to be around that long. > > I could write at length about this, but, in a nutshell, here's why. On the > one hand, you have an open-source project that is geared toward enterprise > application development, but it is completely dependent on a proprietary > runtime. That runtime is manufactured by a company who has stated its > future is "digital media and digital marketing", and that it believes the > future of enterprise web application development is HTML5. It then begs the > question, "How long will they bloat their Flashplayer to support an > open-source Flex community's enterprise web application development goals > and wishes?" > > To accommodate the Flex community, Adobe gets nothing in return for its > expenditure of time and money in designing, developing, testing the > features the Flex community requires now and in the future. It also means > that, by supporting Flex in their runtime, the Flashplayer has an > unnecessarily larger footprint than would otherwise be required. > > So, ask yourself if you truly believe Flex will be a supported product by > Adobe in 5-10 years from now. I highly doubt it. > > On the other hand, I think if a developer uses Flash Pro to develop > digital media for their applications, they can probably count on that being > around indefinitely. But, not Flex. > > Ron > > > --- In flexcoders@yahoogroups.com, James Ong <yanlilei64@...> wrote: > > > > Using ZK and Java is great. I'm still sticking to Flex for developing > > desktop applications and gaming. > > Of course, many will still using it for animations, there is no such > thing > > as "abandon", some developers > > are just over use Flash and end up hurting user experience than > necessary. > > > > When it comes to web application, I stick to PHP but will definitely use > > Flex for mobile, desktop and > > components within the web browser. > > > > > > On Thu, Jan 12, 2012 at 10:16 AM, <michael_regert@...> wrote: > > > > > ** > > > > > > > > > Staying with Flex. Not looking elsewhere.**** > > > > > > ** ** > > > > > > *Michael***** > > > > > > ** ** > > > > > > *From:* flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] > *On > > > Behalf Of *Ron G > > > *Sent:* Wednesday, January 11, 2012 8:15 PM > > > *To:* flexcoders@yahoogroups.com > > > *Subject:* [flexcoders] Re: Flex alternatives**** > > > > > > ** ** > > > > > > **** > > > > > > > Yes, we have also abandoned Flex in favor of ZKoss. Since we are > already a > > > Java shop, on the server side, it seemed logical to use a Java based > > > framework on the client-side. > > > > > > The thing I really like about ZK or ZKoss is that it has equivalent > > > components to Flex. In fact, it actually has more components than Flex. > > > > > > It implements an approach that I really like of separating the UI into > > > appearance and behavior - much like the Spark components of Flex. > Well, not > > > exactly, but sort of. :) Here's what I mean. For each UI object, it > has a > > > client side (widget) and server side (component). I won't go into > further > > > detail, but it gives you a nice separation of concerns that you can > avail > > > yourself of. This feature also greatly insulates the rendered pages > from > > > x-browser compatibility issues. > > > > > > Check it out for yourself at their site (zkoss.org). > > > > > > Ron > > > > > > --- In flexcoders@yahoogroups.com, "Sal" <sal.celli@> wrote: > > > > > > > > hi, > > > > as i can sadly see from the message history bottom grid, many > > > programmers are leaving flex. > > > > So this thread is to ask you all, if you have already found a valid > > > alternative to flex for RIA development. > > > >**** > > > > > > **** > > > > > > > > > > > > > > -- Regards, Ganaraj P R
