Hi Andrew, When Dec, 31th arrives, Flex will be out of browsers, so just allowed using AIR. Maybe AIR could have an option to bundle Apache Flex with each version that ensures all work right. I mean, in 2021, Apache Flex will not have sense with AIR right? so why not to think in something that ease even more AIR+Flex marriage? Of course a version without Flex should have sense too for people that does not use Flex at all.
Make that sense? Thanks Carlos El lun., 9 mar. 2020 a las 14:45, Frost, Andrew (<andrew.fr...@harman.com>) escribió: > Hi > > We'd be happy to add things like this geometry API change - but it's then > going to be version-dependent so it would need to be compiled against the > later AIR SDK and would only run on the later AIR runtime.. > > I'm not sure whether there are other changes that would really impact the > Flex SDK itself. So perhaps we can consider these on a case-by-case basis. > > The one thing I keep coming back to though, is that it seems to be a very > painful process for (a) people to download and start using a new AIR SDK, > and (b) people who then have to combine a Flex SDK with an AIR SDK! So we > should perhaps address this in the first instance (and from our QA folk, > having a simple way to ensure you get back to a clean version of one/both > of these SDKs would be good too!) > > Any other thoughts on missing features or things that would be useful, > please send them in! > > thanks > > Andrew > > > -----Original Message----- > From: Piotr Zarzycki <piotrzarzyck...@gmail.com> > Sent: 09 March 2020 13:01 > To: users@flex.apache.org > Subject: [EXTERNAL] Re: Flex 4.16.1 broken for AIR33.1? > > Hi Andrew, > > This kind of situation may occur more often in the future if Air would > have more and more features. Is there any plan to someone from your Team > simply add missing stuff to Flex? Any thoughts on this approach? > > Thanks, > Piotr > > On Mon, Mar 9, 2020, 1:49 PM Frost, Andrew <andrew.fr...@harman.com> > wrote: > > > Hi Olaf > > > > > I think it would be nice if any AIR updates would be compatible with > > > the > > latest Flex SDK > > Yes completely agree, this was an error on our part to not consider > > the fact that overrides of the APIs that we were changing would have > > been affected. The changes were reverted, and we have re-implemented > > the new functionality within additional APIs/methods so that existing > > apps will now compile/run without any changes on the 33.1.1.63 release. > > > > We definitely intend that there is still full compatibility between > > Flex and any changes we make with AIR.. so thanks to leokan23 and Alex > > for bringing this to our attention! > > > > thanks > > > > Andrew > > > > > > -----Original Message----- > > From: Olaf Krueger <m...@olafkrueger.net> > > Sent: 06 March 2020 20:30 > > To: users@flex.apache.org > > Subject: [EXTERNAL] RE: Flex 4.16.1 broken for AIR33.1? > > > > Hi, > > > > I didn't follow the entire discussion, but I'd like to mention that I > > am not sure if we still have enough volunteers which are willing to > > work on a new Flex release. > > > > That said, I think it would be nice if any AIR updates would be > > compatible with the latest Flex SDK... as long as it's possible. > > > > Thanks, > > Olaf > > > > > > > > -- > > Sent from: > > https://clicktime.symantec.com/3T23VtMr4Dz6j6DqBbgaf5T7Vc?u=http%3A%2F > > %2Fapache-flex-users.2333346.n4.nabble.com%2F > > > -- Carlos Rovira http://about.me/carlosrovira
