To be clear, would the intention here to be a limited subset for multi-platform, with everything maintained for swf legacy? Perhaps dumping mx and keeping spark, or some subtler equiv? Or to have mx as an additional module only available on swf?
- Ian -----Original Message----- From: Kessler CTR Mark J [mailto:mark.kessler....@usmc.mil] Sent: 16 November 2012 14:07 To: flex-dev@incubator.apache.org Subject: RE: [POLL] - Must Flex 5 be a complete rewrite or can flex code base be re-architecture? I would say it's possible given how it's compiled. So having a robust compiler or different compilers for different target environments could be possible. -----Original Message----- From: sébastien Paturel [mailto:sebpatu.f...@gmail.com] Sent: Friday, November 16, 2012 8:54 To: flex-dev@incubator.apache.org Subject: Re: [POLL] - Must Flex 5 be a complete rewrite or can flex code base be re-architecture? "Having more deployed targets based on what we have currently" But is it possible? thats the question... Le 16/11/2012 14:50, Kessler CTR Mark J a écrit : > Option 2 ... +1 > > I would think the community is already based around the current framework. Having more deployed targets based on what we have currently sounds like a way to broaden our target audience. > > How about we continue to correct and fix the current Flex framework. Could we start a new namespace that we could use to build up a partial new framework for a future transition to? It just feels like rewriting everything from scratch would take a long time and would basically be a separate project. > > I'm also envisioning the amount of work the developers using Flex will have to go through to convert to a completely new framework. > > -Mark >
