On the original topic, it certainly seems easiest to release 4.16.2 with just fixes to the native function calls that are broken. Seems like it would be a small change for a developer familiar with the affected package. Then everyone who wants to milk the last few months from AIR 33.0 (prior to geom package breaking-changes) or older can just use Flex 4.16.1 and those who need AIR 33.1 starting with the geom breaking-changes just need 4.16.2.
We can consider all the other wonderful ideas in this thread, independent of getting started on this particular fix. Just my $.02 Erik On Mar 9, 2020, at 1:59 PM, Frost, Andrew <andrew.fr...@harman.com> wrote: Hi Responding to a few of these: 1) what's the actual support of Adobe for Flash Player, or if it will left to Harman as part of the AIR deal [AF] Yes we have certain rights around the licensing of Flash Player, as we have had since the days of the OSP many years ago! but there are limitations to this :-) 2) Flash will be just present on AIR [AF] This is where we need to clarify terminology: "Flash" as a rendering engine and ActionScript VM, yes it's in AIR. "Flash Player" as a browser plug-in, no that's not in AIR and hasn't been for several years. 3) donating to Apache has no sense at all, since Flash Player has many licensed closed source parts that can't be open source [AF] Yes sadly this is very much true.. 4) Browser vendors are closing plugin doors [AF] and this is the crux of it. Doesn't matter if you're looking at Flash, Java, Silverlight, whatever .. plug-ins aren't going to be a viable solution longer term.. 5) Why couldn't Adobe/Harman changed Flash to use the methodology Flash uses for deployment? [AF] I'm assuming there's a typo, not quite sure what's meant, but the real issue is deployment via the web. If you can deploy a standalone application, then you can continue to use workarounds here, but if you need the app to be accessed via a standard browser then your best bet (for a Flex app) is likely to be Royale :-) thanks Andrew -----Original Message----- From: Paul Stearns <pa...@compuace.com.INVALID> Sent: 09 March 2020 19:47 To: Carlos Rovira <carlosrov...@apache.org>; users@flex.apache.org Subject: [EXTERNAL] Re: [Spam] :Re: Flex 4.16.1 broken for AIR33.1? I am investing Royale, but haven't seen any results yet. I am showing my ignorance here, but, my confusion is, will Java still be deployable via web browsers? If so, what is the difference between using a web browser to deploy a Java app, and a Flash app? Why couldn't Adobe/Harmon changed Flash to use the methodology Flash uses for deployment? Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 ---------------------------------------- From: Carlos Rovira <carlosrov...@apache.org> Sent: 3/9/20 3:31 PM To: users@flex.apache.org, Paul Stearns <pa...@compuace.com> Subject: [Spam] :Re: Flex 4.16.1 broken for AIR33.1? Hi Paul, must say don't know what's the actual support of Adobe for Flash Player, or if it will left to Harman as part of the AIR deal, maybe Andrew can give some light on this. Since Flash will be just present on AIR, and not in any other place, that could have sense. But that will mean more maintenance effort and people needed by Harman. Anyway, donating to Apache has no sense at all, since Flash Player has many licensed closed source parts that can't be open source, or at least that's what they always says. But again...donating Flash Player and making it OS, if it could be something doable at some point (let's go utopic ;), does not change anything, since Browser vendors are closing plugin doors. So even in that case, it continue to be a death end. I think Apache Royale is this days in a very good shape, and is better each day... so I maybe people should give a try and consider it as an option for the future. Thanks El lun., 9 mar. 2020 a las 20:04, Paul Stearns (<pa...@compuace.com.invalid>) escribió: Has Adobe stopped supporting it, and has not turned it over to Apache? Now that is just unconscionable. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 ---------------------------------------- From: Carlos Rovira <carlosrov...@apache.org> Sent: 3/9/20 1:28 PM To: users@flex.apache.org, Paul Stearns <pa...@compuace.com> Subject: Re: Flex 4.16.1 broken for AIR33.1? Hi Paul, not bad idea, but don't know a browser that will support Flash, and the problem is Adobe is stopping supporting flash player as a plugin, so I'm afraid that's not possible. El lun., 9 mar. 2020 a las 17:40, Paul Stearns () escribió: > Better yet, how about supporting a browser whose main feature is the > support of Flex? > > My applications are 99.9% flex. The main things I use the browser for > is application deployment, file upload/download and displaying PDF files.. > > Paul R. Stearns > Advanced Consulting Enterprises, Inc. > > 15280 NW 79th Ct. > Suite 250 > Miami Lakes, Fl 33016 > > Voice: (305)623-0360 x107 > Fax: (305)623-4588 > > ---------------------------------------- > From: Carlos Rovira > Sent: 3/9/20 10:09 AM > To: users@flex.apache.org > Subject: Re: Flex 4.16.1 broken for AIR33.1? > 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 > AIR+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 () > 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 >> 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 >> 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 >>> 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%3 >>> A%2F %2Fapache-flex-users.2333346.n4.nabble.com%2F >>> >> > > -- > Carlos Rovira > https://clicktime.symantec.com/3S7LLeTVcUpSCswuSwqZKry7Vc?u=http%3A%2F > %2Fabout.me%2Fcarlosrovira > > > -- Carlos Rovira https://clicktime.symantec.com/3S7LLeTVcUpSCswuSwqZKry7Vc?u=http%3A%2F%2Fabout.me%2Fcarlosrovira -- Carlos Rovira https://clicktime.symantec.com/3S7LLeTVcUpSCswuSwqZKry7Vc?u=http%3A%2F%2Fabout.me%2Fcarlosrovira
