Staying with Flex until I see what happens with it during its first year as an Apache project. I expect big improvements and many new and cool features, it will only depend on Adobe if it will follow with the player.
Haykel Ben Jemia Allmas Web & RIA Development http://www.allmas-tn.com On Thu, Jan 12, 2012 at 3:16 AM, <michael_reg...@dell.com> wrote: > ** > > > Staying with Flex. Not looking elsewhere.**** > > ** ** > > *Michael***** > > ** ** > > *From:* email@example.com [mailto:firstname.lastname@example.org] *On > Behalf Of *Ron G > *Sent:* Wednesday, January 11, 2012 8:15 PM > *To:* email@example.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 firstname.lastname@example.org, "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. > >**** > > **** > > >