On Thu, Nov 6, 2014 at 4:20 PM, DavidM <[email protected]> wrote: > > Justin, OmPrakash, Ronny, thanks so much for the replies. > > I tend to agree with you. At the time of Adobe's announcements re Flex, I > was fairly certain that it would continue to be maintained. A plugin with a > presence in hundreds of millions of browsers just can't disappear that > easily. Certainly not with the manpower invested in the framework. > > I even tried to convince Jens Halms, the developer of Parsley, that he > should continue to support it for these reasons - though I must have failed > because I see that the project is in 'read-only' mode, and has been for > several years. I'm have a question about IOC containers, but will post that > in a separate thread. > > In terms of this thread: I'm going to use SDK 4.13, but, for now, will > target the same version that our current software runs on, 11.3, I believe. > > Simultaneously, we will record the flash players of our customers and > decide > what to do. > > It might be that we release 2 versions, one targeting 11.3 and another > targeting 14.0, and let the browser decide which one to load. I don't want > to force all of our customers to upgrade their players just for our > application. > > Thanks again for your responses - if you need to support IE 8, need a > datagrid with fixed headers and columns, and don't need to support tablets > or phones, then it seems that Flex is still the way to go. > > You can still compile your Flex app to create native iOS and Android apps. Please take a look at the Apache Flex Showcase [1] which has several examples of native iOS and Android apps built with Flex.
Thanks, Om [1] http://flex.apache.org/community-showcase.html David > > > > > -- > View this message in context: > http://apache-flex-users.2333346.n4.nabble.com/State-of-Flex-tp8616p8620.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
