Re: Flex 4.16.1 broken for AIR33.1?

[Alex Harui]

FWIW, there used to be (not sure now), a fair number of folks who for some 
reason could not upgrade to the latest version of Flash/AIR.

The APIs in Flash/AIR apparently have historically only changed by adding new 
methods to classes, not by changing the parameter list.  There is still a risk 
that a newly added API will cause a problem to an existing app, but I believe 
that Harman is doing the right thing by refactoring to not change the parameter 
list and add a new method.

Then the Flex SDK will work for a wider range of versions just in case someone 
is still out there wanting an older one.

My 2 cents,
-Alex

On 3/10/20, 4:34 AM, "Piotr Zarzycki"  wrote:

Hi Leo,

There is nothing more than showing proper documentation to anyone who
wanted to release sdk - however only as far as I know committers can
finalize release process. Fix can submit anyone by pull request. Do that
and I bet someone take care of the rest of the process - even if it takes
more time.

Thanks,
Piotr

pon., 9 mar 2020 o 21:53 leokan23  napisał(a):

> Going back on topic, how easy would be for current volunteers to show how
> to
> update Flex / make a release, to someone from Harman?
>
>
>
> --
> Sent from: 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.246.n4.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C65959989d39e4c10c12e08d7c4e70ed0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637194368975848136sdata=e0pRVlHMrb8Y1z44yiH%2FF5lbgAfF3Vdxw%2FLVC10uKAU%3Dreserved=0
>


-- 

Piotr Zarzycki

Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C65959989d39e4c10c12e08d7c4e70ed0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637194368975848136sdata=NdLsrJ1UtlVrDBS6nd8378peXnaZAMDGgkU8MK3p2PQ%3Dreserved=0

*

Re: Flex 4.16.1 broken for AIR33.1?

[Piotr Zarzycki]

Hi Leo,

There is nothing more than showing proper documentation to anyone who
wanted to release sdk - however only as far as I know committers can
finalize release process. Fix can submit anyone by pull request. Do that
and I bet someone take care of the rest of the process - even if it takes
more time.

Thanks,
Piotr

pon., 9 mar 2020 o 21:53 leokan23  napisał(a):

> Going back on topic, how easy would be for current volunteers to show how
> to
> update Flex / make a release, to someone from Harman?
>
>
>
> --
> Sent from: http://apache-flex-users.246.n4.nabble.com/
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: [Spam] :Re: Flex 4.16.1 broken for AIR33.1?

[Carlos Rovira]

Hi Paul,

many years ago I must say that was completely true, for that reason I
started trying to introduce in my clients and projects Flash and AMF in
early 2000, first with Flash authoring tool, then with MTASC (someone
remember it? ;)), and then Flex was really what we just needed. That was
very disruptive compared with the html/js/css stack at that time.

Currently that's not true. Near 2020, js is like the bytecode in Flash and
Royale is the current Flex. So it's clear that you don't need to go very
"low level", but if you needed, you can do it! (and that's good). But
Royale should allow you to develop without the need to go that route. and
just use good proven patterns like Flex did. We're working towards
that...and I think we're already got it. :)

About GUI IDE, although I think is something very cool to have something
like that, I abandoned that kind of tools many years ago. Maybe in the
future I could be working in something like that, just for pleasure, but
for now there's still many work to do in Royale in things more needed.
Maybe others could drive that effort... But I really think the current
Royale coding is very straight forward to do. As well examples like Tour De
Jewel has a lot of code to see how things should be used and learn from it
a lot of good practices.



El lun., 9 mar. 2020 a las 22:48, Paul Stearns ()
escribió:

> What attracted me to Flex initially was that it ran in its own
> environment, completely separate from the html, web browser and their
> multitude of DOMs. I used to write apps in ASP/HTML, and every other week a
> new version of a browser would break something.
>
> For the type of applications I write & support, having a GUI IDE, a
> defined language (like as3 & mxml) and an engine which which provides
> consistent results across platforms are the most important features. At
> this point the weakness I see in Royale is there isn't a GUI IDE, and since
> it doesn't have its own engine, it relies on the vicissitudes of javascript
> and how the particular browser it is running in implements its DOM.
>
> This is why I shied away from .NET, and PHP in the past except for more
> traditional websites with a bit of user interaction. Javascript frameworks
> just hide the ugliness, they don't make it go away.
>
> Having said all of the above, I am taking a chance on Royale to see what
> the level of effort will be to convert to it.
>
> 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 4:55 PM
> To: Paul Stearns 
> Cc: users@flex.apache.org
> Subject: Re: [Spam] :Re: Flex 4.16.1 broken for AIR33.1?
> Hi Paul,
>
> I suppose you refer to Java Applets, hope other could give more info about
> this, but although you're in part right, I think Flash Player is more well
> integrated in Browsers and Applets never had the power of Flash. But it's
> ok, you can enable in browsers... anyway, we 're in 2020 and seems things
> will continue its course, so nothing we can do to revert that.
>
> I always be a great advocate of the Flash platform, but I found in Royale
> something better that what we had with Flash. IMHO, we have the best of
> both worlds. From Flex/Flash I wanted the "development productivity",
> languages (AS3, MXML), compiler, AMF, and many other things. From web I
> always liked things like CSS (that's far superior than what we had in Flex
> for sure), and the fact that we are not constraint to a plugin and a
> sandbox, so it's more easy to do things for the web.
>
> We have both combined now in Royale, and that's for me amazing. As we get
> components with clear API definitions, and access to latest browsers
> features, we are getting the same productivity that we had in Flex, and as
> well we are removing the complexity in Browsers where you need to test in
> each browsers or lost time solving browser compatibility problems. We
> finally can have things like IoC (Inversion of Control), DI (Dependency
> Injection), Metadata, MXML, Routing (Deep Linking), LocalStorage (like old
> Local SharedObject), just to name a few.
>
> But even more, since the bead/strand Arquitecture is really powerful, and
> Apps build with royale are more easy to build that even was in Royale. And
> the most important: Performance: The apps built with Royale has an
> outstanding performance. Apps migrated from Flex use to be many XX% faster
> in Royale.
>
> I must say, I'm very happy with what we're getting with Apache Royale :)
>
> Carlos
>
> El lun., 9 mar. 2020 a las 20:46, Paul Stearns ()
> escribió:
>
> > I am investing Royale, but haven't seen a

Re: [Spam] :Re: Flex 4.16.1 broken for AIR33.1?

[Paul Stearns]

What attracted me to Flex initially was that it ran in its own environment, 
completely separate from the html, web browser and their multitude of DOMs. I 
used to write apps in ASP/HTML, and every other week a new version of a browser 
would break something.

For the type of applications I write & support, having a GUI IDE, a defined 
language (like as3 & mxml) and an engine which which provides consistent 
results across platforms are the most important features. At this point the 
weakness I see in Royale is there isn't a GUI IDE, and since it doesn't have 
its own engine, it relies on the vicissitudes of javascript and how the 
particular browser it is running in implements its DOM.

This is why I shied away from .NET, and PHP in the past except for more 
traditional websites with a bit of user interaction. Javascript frameworks just 
hide the ugliness, they don't make it go away.

Having said all of the above, I am taking a chance on Royale to see what the 
level of effort will be to convert to it.

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 4:55 PM
To: Paul Stearns 
Cc: users@flex.apache.org
Subject: Re: [Spam] :Re: Flex 4.16.1 broken for AIR33.1?
Hi Paul,

I suppose you refer to Java Applets, hope other could give more info about
this, but although you're in part right, I think Flash Player is more well
integrated in Browsers and Applets never had the power of Flash. But it's
ok, you can enable in browsers... anyway, we 're in 2020 and seems things
will continue its course, so nothing we can do to revert that.

I always be a great advocate of the Flash platform, but I found in Royale
something better that what we had with Flash. IMHO, we have the best of
both worlds. From Flex/Flash I wanted the "development productivity",
languages (AS3, MXML), compiler, AMF, and many other things. From web I
always liked things like CSS (that's far superior than what we had in Flex
for sure), and the fact that we are not constraint to a plugin and a
sandbox, so it's more easy to do things for the web.

We have both combined now in Royale, and that's for me amazing. As we get
components with clear API definitions, and access to latest browsers
features, we are getting the same productivity that we had in Flex, and as
well we are removing the complexity in Browsers where you need to test in
each browsers or lost time solving browser compatibility problems. We
finally can have things like IoC (Inversion of Control), DI (Dependency
Injection), Metadata, MXML, Routing (Deep Linking), LocalStorage (like old
Local SharedObject), just to name a few.

But even more, since the bead/strand Arquitecture is really powerful, and
Apps build with royale are more easy to build that even was in Royale. And
the most important: Performance: The apps built with Royale has an
outstanding performance. Apps migrated from Flex use to be many XX% faster
in Royale.

I must say, I'm very happy with what we're getting with Apache Royale :)

Carlos

El lun., 9 mar. 2020 a las 20:46, Paul Stearns ()
escribió:

> 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
> *Sent*: 3/9/20 3:31 PM
> *To*: users@flex.apache.org, Paul Stearns
> *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 c

Re: Flex 4.16.1 broken for AIR33.1?

[Erik Thomas]

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  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  
Sent: 09 March 2020 19:47
To: Carlos Rovira ; 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 
Sent: 3/9/20 3:31 PM
To: users@flex.apache.org, Paul Stearns 
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 () 
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 
Sent: 3/9/20 1:28 PM
To: users@flex.apache.org, Paul Stearns 
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 La

Re: Flex 4.16.1 broken for AIR33.1?

[Frost, Andrew]

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  
Sent: 09 March 2020 19:47
To: Carlos Rovira ; 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 
Sent: 3/9/20 3:31 PM
To: users@flex.apache.org, Paul Stearns 
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 () 
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 
Sent: 3/9/20 1:28 PM
To: users@flex.apache.org, Paul Stearns 
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 versio

Re: [Spam] :Re: Flex 4.16.1 broken for AIR33.1?

[Carlos Rovira]

Hi Paul,

I suppose you refer to Java Applets, hope other could give more info about
this, but although you're in part right, I think Flash Player is more well
integrated in Browsers and Applets never had the power of Flash. But it's
ok, you can enable in browsers... anyway, we 're in 2020 and seems things
will continue its course, so nothing we can do to revert that.

I always be a great advocate of the Flash platform, but I found in Royale
something better that what we had with Flash.  IMHO, we have the best of
both worlds. From Flex/Flash I wanted the "development productivity",
languages (AS3, MXML), compiler, AMF, and many other things. From web I
always liked things like CSS (that's far superior than what we had in Flex
for sure), and the fact that we are not constraint to a plugin and a
sandbox, so it's more easy to do things for the web.

We have both combined now in Royale, and that's for me amazing. As we get
components with clear API definitions, and access to latest browsers
features, we are getting the same productivity that we had in Flex, and as
well we are removing the complexity in Browsers where you need to test in
each browsers or lost time solving browser compatibility problems. We
finally can have things like IoC (Inversion of Control), DI (Dependency
Injection), Metadata, MXML, Routing (Deep Linking), LocalStorage (like old
Local SharedObject), just to name a few.

But even more, since the bead/strand Arquitecture is really powerful, and
Apps build with royale are more easy to build that even was in Royale. And
the most important: Performance: The apps built with Royale has an
outstanding performance. Apps migrated from Flex use to be many XX% faster
in Royale.

I must say, I'm very happy with what we're getting with Apache Royale :)

Carlos




El lun., 9 mar. 2020 a las 20:46, Paul Stearns ()
escribió:

> 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 
> *Sent*: 3/9/20 3:31 PM
> *To*: users@flex.apache.org, Paul Stearns 
> *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 ()
> 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 
>> Sent: 3/9/20 1:28 PM
>> To: users@flex.apache.org, Paul Stearns 
>> 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..
>>

Re: Flex 4.16.1 broken for AIR33.1?

[leokan23]

Going back on topic, how easy would be for current volunteers to show how to
update Flex / make a release, to someone from Harman? 



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: [Spam] :Re: Flex 4.16.1 broken for AIR33.1?

[Paul Stearns]

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 
Sent: 3/9/20 3:31 PM
To: users@flex.apache.org, Paul Stearns 
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 () 
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 
Sent: 3/9/20 1:28 PM
To: users@flex.apache.org, Paul Stearns 
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 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

Re: Flex 4.16.1 broken for AIR33.1?

[Carlos Rovira]

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 ()
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 
> Sent: 3/9/20 1:28 PM
> To: users@flex.apache.org, Paul Stearns 
> 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 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
>

Re: Flex 4.16.1 broken for AIR33.1?

[Paul Stearns]

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 
Sent: 3/9/20 1:28 PM
To: users@flex.apache.org, Paul Stearns 
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 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%3A%2F
> > > %2Fapache-flex-users.246.n4.nabble.com%2F
> > >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>

--
Carlos Rovira
http://about.me/carlosrovira

Re: Flex 4.16.1 broken for AIR33.1?

[Carlos Rovira]

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 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%3A%2F
> > > %2Fapache-flex-users.246.n4.nabble.com%2F
> > >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Flex 4.16.1 broken for AIR33.1?

[Paul Stearns]

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 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%3A%2F
> > %2Fapache-flex-users.246.n4.nabble.com%2F
> >
>

--
Carlos Rovira
http://about.me/carlosrovira

Re: Flex 4.16.1 broken for AIR33.1?

[leokan23]

There is a free tier for v33. Although 32 is more or less stable, it doesnt
support Android, in less than a month it wont support iOS, it doesnt support
Mac so it is pretty much outdated.  



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Flex 4.16.1 broken for AIR33.1?

[Frost, Andrew]

To add to this (and responding to one of the earlier messages) - you need AIR 
33 (soon) if you publish to mobiles, due to the changes that Google and Apple 
keep imposing. But on desktops there's no real reason to update things; even 
with Catalina, you can still use AIR 32 if you take a few extra steps to avoid 
some of the quarantine issues etc.

We're in a bit of a transition period currently, I'm uncomfortably aware that 
there are still teething issues with the AIR SDK versions that we're putting 
out at the moment, but the goal is to end up with a more sustainable version of 
AIR that can be used for the next 10 years. Ultimately though, yes everyone has 
a choice of technologies, and they all come with a risk of obsolescence..

I don't really see Flex or AIR as 'sinking ships', but then I probably see a 
lot more of the activity that goes on and the large number of very big 
companies who are still dependent on it and who are going to still be dependent 
on it post 2020..!

cheers


-Original Message-
From: Hans Nuecke  
Sent: 09 March 2020 15:55
To: users@flex.apache.org
Subject: [EXTERNAL] Re: Flex 4.16.1 broken for AIR33.1?

I do: You have to pay for the new version if I want to publish it as captive 
runtime version.
That's why I test with v33, but use v32 for the final delivery.

I still love Air and Flex. It is a perfect solution for my desktop based 
product (Windows and maOS).

But I feel more and more uncomfortable and might start a new development soon; 
based on an actual mainstream  framework. Which for me
(unfortunately) isn't Royale neither ;-(

For the browser based part of my product we already made the switch to 
JavaScript (hic!) and vue. So it might be a good advice to leave the sinking 
AIR/Flex ship in time?!

I really appreciate all your work, but at the end I need a secure and 
comfortable base that takes me through the coming 10 years... And emails like 
these ones don't give me the level of comfort I'm seeking...

Just my 2 cts.


Regards

Hans


Am 09.03.2020 um 16:34 schrieb Erik Thomas:
> On Mar 9, 2020, at 7:14 AM, leokan23  wrote:
>
>>> "I don't see a reason to keep Flex working with old AIR versions."
> +1
>
> Erik

Re: Flex 4.16.1 broken for AIR33.1?

[Hans Nuecke]

I do: You have to pay for the new version if I want to publish it as 
captive runtime version.

That's why I test with v33, but use v32 for the final delivery.

I still love Air and Flex. It is a perfect solution for my desktop based 
product (Windows and maOS).


But I feel more and more uncomfortable and might start a new development 
soon; based on an actual mainstream  framework. Which for me 
(unfortunately) isn't Royale neither ;-(


For the browser based part of my product we already made the switch to 
JavaScript (hic!) and vue. So it might be a good advice to leave the 
sinking AIR/Flex ship in time?!


I really appreciate all your work, but at the end I need a secure and 
comfortable base that takes me through the coming 10 years... And emails 
like these ones don't give me the level of comfort I'm seeking...


Just my 2 cts.


Regards

Hans


Am 09.03.2020 um 16:34 schrieb Erik Thomas:

On Mar 9, 2020, at 7:14 AM, leokan23  wrote:


"I don't see a reason to keep Flex working with old AIR versions."

+1

Erik

Re: Flex 4.16.1 broken for AIR33.1?

[Erik Thomas]

On Mar 9, 2020, at 7:14 AM, leokan23  wrote:

>> "I don't see a reason to keep Flex working with old AIR versions."

+1

Erik

Re: Flex 4.16.1 broken for AIR33.1?

[leokan23]

Do we really need Flex to work with older AIR SDK versions? 

- Web distribution is not relevant any more and it will be EOLed in a few
months. 
- Android needs AIR33 or higher (to support Android 64bit restriction).
- iOS currently needs AIR32 or higher (this will change soon as in April
2020 Apple will force iOS 13 sdk so I guess this will be bumped to AIR33 as
well).
- Mac,if not mistaken, needs AIR33 to work in the latest os version
(catalina).
- Windows is the only thing not affected. 

So with all the above, I dont see a reason to keep Flex working with old AIR
versions. This is my experience so I might miss something that makes it
crucial to keep Flex working with the old versions (right now you can even
download AIR3.7 from Flex installer).



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Flex 4.16.1 broken for AIR33.1?

[Carlos Rovira]

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 ()
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%3A%2F
> > %2Fapache-flex-users.246.n4.nabble.com%2F
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Flex 4.16.1 broken for AIR33.1?

[Frost, Andrew]

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%3A%2F
> %2Fapache-flex-users.246.n4.nabble.com%2F
>

Re: Flex 4.16.1 broken for AIR33.1?

[Piotr Zarzycki]

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%3A%2F%2Fapache-flex-users.246.n4.nabble.com%2F
>

RE: Flex 4.16.1 broken for AIR33.1?

[Frost, Andrew]

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%3A%2F%2Fapache-flex-users.246.n4.nabble.com%2F

RE: Flex 4.16.1 broken for AIR33.1?

[Olaf Krueger]

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: http://apache-flex-users.246.n4.nabble.com/

RE: Flex 4.16.1 broken for AIR33.1?

[agm65]

Hi,

yes please update the Flex version to run with the new AIR SDK 33.1. We need
64 Bit support in our apps. Is it also possible to fix the Flex SDK
installer that we can download an nightly build with that fix?

KR



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

RE: Flex 4.16.1 broken for AIR33.1?

[leokan23]

To me it looks like the best option would be updating Flex SDK to 4.16.2 and
implementing the new changes. However, as this might take a while, Andrew's
idea of using different function names, looks like the most feasible option
right now. 



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

RE: Flex 4.16.1 broken for AIR33.1?

[Frost, Andrew]

Thanks; so I think if the mx.geom.Transform APIs were updated, it would mean 
that apps built using that would then only work on AIR 33.1 and above..

Currently then:
a) if you have a Flex app and Flex SDK, you can use up to/including AIR 33.0 
SDK to build your application. Everything will work fine (once we've made the 
change to the runtime i.e. 33.1.1.50 is the only version that will fail to load 
this but our next release would be okay).
b) if you are using AIR 33.1 SDK to build, then you need to update to a later 
Flex SDK (4.16.2?) with these new mx.geom.* APIs in them. A SWF built with this 
would then only run on versions above AIR 33.1.1.50..

I'm actually starting to lean towards the idea of reverting the change and just 
adding the new APIs alongside the old ones with different function names. Hence:
public native function getRelativeMatrix3D(relativeTo:DisplayObject, 
output:Matrix3D=null):Matrix3D;
would become:
// the original API:
public native function 
getRelativeMatrix3D(relativeTo:DisplayObject):Matrix3D;
// the new API as well:
[API(CONFIG::SWF_44)]
public native function 
getRelativeMatrix3DToOutput(relativeTo:DisplayObject, output:Matrix3D):Matrix3D;

So this one must be called deliberately and needs the output parameter to be 
provided (but can be null). Then actually internally our first function could 
just be calling the second one with a null input..

Feedback welcomed (particularly on what we should call these functions!) but we 
need to make a decision today really to get this into our next release!

thanks

   Andrew



-Original Message-
From: leokan23  
Sent: 04 March 2020 10:37
To: users@flex.apache.org
Subject: [EXTERNAL] RE: Flex 4.16.1 broken for AIR33.1?

I think Flex libs (mx.geom.Transform) should be updated to work with the latest 
versions of AIR. From the mobile perspective, it doesn't make much sense to 
support older ones as you can't publish apps if you are lower than AIR 32 for 
iOS or AIR 33 for Android.

I am not sure if there is any similar issue for desktops and web.



--
Sent from: 
https://clicktime.symantec.com/3HjCESjpMQXstAAUHQ7kAfa7Vc?u=http%3A%2F%2Fapache-flex-users.246.n4.nabble.com%2F

RE: Flex 4.16.1 broken for AIR33.1?

[leokan23]

I think Flex libs (mx.geom.Transform) should be updated to work with the
latest versions of AIR. From the mobile perspective, it doesn't make much
sense to support older ones as you can't publish apps if you are lower than
AIR 32 for iOS or AIR 33 for Android.

I am not sure if there is any similar issue for desktops and web.



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

RE: Flex 4.16.1 broken for AIR33.1?

[Frost, Andrew]

Hi

Yes I've just checked and Array.insertAt() is just specified for SWF version 30 
and upward. There's no version with different parameters that I can see. I will 
check with the Flash engineering team though..
See https://github.com/adobe/avmplus/blob/master/core/Array.as

In terms of a workaround here: we're going to make a small change to allow the 
runtime to work with the old APIs or the new ones. So no more VerifyError 
problems if you're running an older Flex app on the new runtime.

What we can't change though is the compiler, so compiling against the new 
airglobals.swc file will require the Flex APIs to be updated to the new 
function signatures.

The alternative would be to revert the APIs and provide them instead under a 
"flash.geom2" namespace (or preferably, "air.geom"..) - I'd be interested in 
your opinions, I'm not really sure how many people would be impacted by this. 
Happy to contribute the necessary changes into the Flex SDK, it's not a huge 
number of changes.. 

thanks

   Andrew


-Original Message-
From: Alex Harui  
Sent: 04 March 2020 08:31
To: users@flex.apache.org
Subject: [EXTERNAL] Re: Flex 4.16.1 broken for AIR33.1?

Hi Andrew,

I don't know about additional parameters, but have you looked at how 
Array.insertAt is handled in the runtime?  It was added in AIR 19, and I'm 
pretty sure you will get different compiler results from compiling against AIR 
18, and different runtime behavior based on the swfversion as well.

I thought there have been parameter changes as well, but I can't remember any 
right now.

HTH,
-Alex

On 3/3/20, 10:13 PM, "Frost, Andrew"  wrote:

Hi 

Apologies for causing the extra hassle here. There doesn't appear to be a 
way for us to specify an API to be removed from the AS3 definitions at a 
particular SWF version, which actually meant we couldn't add the changes in a 
version-checked manner (i.e. our initial aim was to adjust the API based on the 
-swf-version value but we can only add new APIs in this way, rather than 
changing an existing one).

We've investigated the impact here a little further, and it looks like (for 
overriding the functions):
1) when you build the existing code (without the new parameters) then you 
need to use the old airglobal.swc file for this
2) an app built using the old airglobal.swc then won't run on the new AIR 
runtime
3) an app built using the new airglobal.swc then won't run on an older AIR 
runtime

Part 3 here is what would also be the case if you were just using the new 
APIs: our original intent was that if you chose to use the new API then of 
course you need to compile with AIR 33.1 SDK and run it on AIR 33.1.

I was going to suggest that the Flex code could be updated to add in the 
extra parameters for these overrides but I think we would still have an issue 
with #2, i.e. existing Flex applications will not work if run on AIR 33.1... 
That's definitely not a good thing, in my opinion!

So I think we need to rethink this one; I would suggest holding off making 
any code changes here (i.e. don't use AIR 33.1!) as there may be some other 
options here (the obvious one being, revert the APIs...)

thanks

   Andrew


-Original Message-
From: Greg Dove  
Sent: 03 March 2020 20:32
To: users@flex.apache.org
    Subject: [EXTERNAL] Re: Flex 4.16.1 broken for AIR33.1?

That sounds like there might be a few of these. Any classes that extend the 
native ones inside mx.geom will likely need attention for the affected 
overridden methods.


On Wed, Mar 4, 2020 at 9:00 AM leokan23  wrote:

> Changing the -swf-version didn't do the trick. This is the change they 
did:
>
> /Update geometry APIs to allow object pooling, so for example, rather 
> than creating and returning new Point, Matrix, Vector3D etc objects, 
> functions within the flash.geom.* classes will take an optional 
> parameter that can be an object to reuse and return. /
>
> I will try messing around with Transform.as next.
>
>
>
>
>
>
> --
> Sent from: 
> 
https://clicktime.symantec.com/38NMYfbFR4zB7vN47iJqKvF7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F3PG82YtwHLcZuLsBDbCLtTt7Vc%253Fu%253Dhttp%25253A%25252F%25252Fapache-flex-users.246.n4.nabble.com%25252F%26data%3D02%257C01%257Caharui%2540adobe.com%257Ca072ee5deed341a30e5f08d7c0032a5e%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C637188992144497184%26sdata%3DcCJ7uNX7G%252F47zmorxixVID4UN3InK83f%252BhYNMyMHLFU%253D%26reserved%3D0
>

Re: Flex 4.16.1 broken for AIR33.1?

[agm65]

Hi,

did you find a solution? Same issued here..



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Flex 4.16.1 broken for AIR33.1?

[Alex Harui]

Hi Andrew,

I don't know about additional parameters, but have you looked at how 
Array.insertAt is handled in the runtime?  It was added in AIR 19, and I'm 
pretty sure you will get different compiler results from compiling against AIR 
18, and different runtime behavior based on the swfversion as well.

I thought there have been parameter changes as well, but I can't remember any 
right now.

HTH,
-Alex

On 3/3/20, 10:13 PM, "Frost, Andrew"  wrote:

Hi 

Apologies for causing the extra hassle here. There doesn't appear to be a 
way for us to specify an API to be removed from the AS3 definitions at a 
particular SWF version, which actually meant we couldn't add the changes in a 
version-checked manner (i.e. our initial aim was to adjust the API based on the 
-swf-version value but we can only add new APIs in this way, rather than 
changing an existing one).

We've investigated the impact here a little further, and it looks like (for 
overriding the functions):
1) when you build the existing code (without the new parameters) then you 
need to use the old airglobal.swc file for this
2) an app built using the old airglobal.swc then won't run on the new AIR 
runtime
3) an app built using the new airglobal.swc then won't run on an older AIR 
runtime

Part 3 here is what would also be the case if you were just using the new 
APIs: our original intent was that if you chose to use the new API then of 
course you need to compile with AIR 33.1 SDK and run it on AIR 33.1.

I was going to suggest that the Flex code could be updated to add in the 
extra parameters for these overrides but I think we would still have an issue 
with #2, i.e. existing Flex applications will not work if run on AIR 33.1... 
That's definitely not a good thing, in my opinion!

So I think we need to rethink this one; I would suggest holding off making 
any code changes here (i.e. don't use AIR 33.1!) as there may be some other 
options here (the obvious one being, revert the APIs...)

thanks

   Andrew


-Original Message-
From: Greg Dove  
Sent: 03 March 2020 20:32
To: users@flex.apache.org
Subject: [EXTERNAL] Re: Flex 4.16.1 broken for AIR33.1?

That sounds like there might be a few of these. Any classes that extend the 
native ones inside mx.geom will likely need attention for the affected 
overridden methods.


On Wed, Mar 4, 2020 at 9:00 AM leokan23  wrote:

> Changing the -swf-version didn't do the trick. This is the change they 
did:
>
> /Update geometry APIs to allow object pooling, so for example, rather 
> than creating and returning new Point, Matrix, Vector3D etc objects, 
> functions within the flash.geom.* classes will take an optional 
> parameter that can be an object to reuse and return. /
>
> I will try messing around with Transform.as next.
>
>
>
>
>
>
> --
> Sent from: 
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fclicktime.symantec.com%2F3PG82YtwHLcZuLsBDbCLtTt7Vc%3Fu%3Dhttp%253A%252F%252Fapache-flex-users.246.n4.nabble.com%252Fdata=02%7C01%7Caharui%40adobe.com%7Ca072ee5deed341a30e5f08d7c0032a5e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637188992144497184sdata=cCJ7uNX7G%2F47zmorxixVID4UN3InK83f%2BhYNMyMHLFU%3Dreserved=0
>

Re: Flex 4.16.1 broken for AIR33.1?

[Frost, Andrew]

Hi 

Apologies for causing the extra hassle here. There doesn't appear to be a way 
for us to specify an API to be removed from the AS3 definitions at a particular 
SWF version, which actually meant we couldn't add the changes in a 
version-checked manner (i.e. our initial aim was to adjust the API based on the 
-swf-version value but we can only add new APIs in this way, rather than 
changing an existing one).

We've investigated the impact here a little further, and it looks like (for 
overriding the functions):
1) when you build the existing code (without the new parameters) then you need 
to use the old airglobal.swc file for this
2) an app built using the old airglobal.swc then won't run on the new AIR 
runtime
3) an app built using the new airglobal.swc then won't run on an older AIR 
runtime

Part 3 here is what would also be the case if you were just using the new APIs: 
our original intent was that if you chose to use the new API then of course you 
need to compile with AIR 33.1 SDK and run it on AIR 33.1.

I was going to suggest that the Flex code could be updated to add in the extra 
parameters for these overrides but I think we would still have an issue with 
#2, i.e. existing Flex applications will not work if run on AIR 33.1... That's 
definitely not a good thing, in my opinion!

So I think we need to rethink this one; I would suggest holding off making any 
code changes here (i.e. don't use AIR 33.1!) as there may be some other options 
here (the obvious one being, revert the APIs...)

thanks

   Andrew


-Original Message-
From: Greg Dove  
Sent: 03 March 2020 20:32
To: users@flex.apache.org
Subject: [EXTERNAL] Re: Flex 4.16.1 broken for AIR33.1?

That sounds like there might be a few of these. Any classes that extend the 
native ones inside mx.geom will likely need attention for the affected 
overridden methods.


On Wed, Mar 4, 2020 at 9:00 AM leokan23  wrote:

> Changing the -swf-version didn't do the trick. This is the change they did:
>
> /Update geometry APIs to allow object pooling, so for example, rather 
> than creating and returning new Point, Matrix, Vector3D etc objects, 
> functions within the flash.geom.* classes will take an optional 
> parameter that can be an object to reuse and return. /
>
> I will try messing around with Transform.as next.
>
>
>
>
>
>
> --
> Sent from: 
> https://clicktime.symantec.com/3PG82YtwHLcZuLsBDbCLtTt7Vc?u=http%3A%2F%2Fapache-flex-users.246.n4.nabble.com%2F
>

Re: Flex 4.16.1 broken for AIR33.1?

[Greg Dove]

That sounds like there might be a few of these. Any classes that extend the
native ones inside mx.geom will likely need attention for the affected
overridden methods.


On Wed, Mar 4, 2020 at 9:00 AM leokan23  wrote:

> Changing the -swf-version didn't do the trick. This is the change they did:
>
> /Update geometry APIs to allow object pooling, so for example, rather than
> creating and returning
> new Point, Matrix, Vector3D etc objects, functions within the flash.geom.*
> classes will take an
> optional parameter that can be an object to reuse and return. /
>
> I will try messing around with Transform.as next.
>
>
>
>
>
>
> --
> Sent from: http://apache-flex-users.246.n4.nabble.com/
>

Re: Flex 4.16.1 broken for AIR33.1?

[leokan23]

Changing the -swf-version didn't do the trick. This is the change they did:

/Update geometry APIs to allow object pooling, so for example, rather than
creating and returning
new Point, Matrix, Vector3D etc objects, functions within the flash.geom.*
classes will take an
optional parameter that can be an object to reuse and return. /

I will try messing around with Transform.as next.






--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Flex 4.16.1 broken for AIR33.1?

[Alex Harui]

If you don't need the new APIs in 33.1 and are just looking for the runtime 
improvements, you can set the -swf-version and maybe -target-player to a lower 
number.  (AIR 32 is swf-version 43, not sure what 33 and 33.1 are using)

HTH,
-Alex

On 3/3/20, 11:10 AM, "Greg Dove"  wrote:

sorry, that should have been:

It sounds like an extra optonal parameter was added to

flash.geom.Transform.getRelativeMatrix3D

You could try monkey patching

mx.geom.Transform

by adding the source package for that to your local project, and then look
at the overridden method for 'getRelativeMatrix3D' and add the second
missing parameter for the latest version of that method

On Wed, Mar 4, 2020 at 8:08 AM Greg Dove  wrote:

>
> It sounds like an extra optonal parameter was added to
>
> mx.geom.Transform.getRelativeMatrix3D
>
> You could try monkey patching
>
> mx.geom.Transform
>
> by adding the source package for that to your local project, and then look
> at the overridden method for 'getRelativeMatrix3D' and add the second
> missing parameter for the latest version of that method
>
>
>
>
>
> On Wed, Mar 4, 2020 at 7:49 AM leokan23  wrote:
>
>> It looks like there is an issue with the latest AIR version, after they
>> updated the geometry APIs.
>>
>> I am trying to run some projects and i get the following errors:
>>
>> param count mismatch
>> virt params=2 optional=1 flash.geom::Transform/getRelativeMatrix3D()
>> over params=1 optional=0 flash.geom::Transform/getRelativeMatrix3D()
>> VerifyError: Error #1053: Illegal override of Transform in
>> mx.geom.Transform.
>>
>> at
>>
>> 
spark.primitives.supportClasses::GraphicElement/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\spark\src\spark\primitives\supportClasses\GraphicElement.as:3546]
>> at
>>
>> 
spark.components::Group/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\spark\src\spark\components\Group.as:938]
>> at
>>
>> 
mx.managers::LayoutManager/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:601]
>> at
>>
>> 
mx.managers::LayoutManager/doPhasedInstantiation()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:787]
>> at
>>
>> 
mx.managers::LayoutManager/doPhasedInstantiationCallback()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1191]
>>
>>
>> Any ideas?
>>
>>
>>
>> --
>> Sent from: 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.246.n4.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Cbc451ca69fde46a1143b08d7bfa676a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637188594003806409sdata=ihY9KFQMn0Q7T5ImEIMtN3Q1TB%2Fod6l%2FL6di635NdUA%3Dreserved=0
>>
>

Re: Flex 4.16.1 broken for AIR33.1?

[Greg Dove]

sorry, that should have been:

It sounds like an extra optonal parameter was added to

flash.geom.Transform.getRelativeMatrix3D

You could try monkey patching

mx.geom.Transform

by adding the source package for that to your local project, and then look
at the overridden method for 'getRelativeMatrix3D' and add the second
missing parameter for the latest version of that method

On Wed, Mar 4, 2020 at 8:08 AM Greg Dove  wrote:

>
> It sounds like an extra optonal parameter was added to
>
> mx.geom.Transform.getRelativeMatrix3D
>
> You could try monkey patching
>
> mx.geom.Transform
>
> by adding the source package for that to your local project, and then look
> at the overridden method for 'getRelativeMatrix3D' and add the second
> missing parameter for the latest version of that method
>
>
>
>
>
> On Wed, Mar 4, 2020 at 7:49 AM leokan23  wrote:
>
>> It looks like there is an issue with the latest AIR version, after they
>> updated the geometry APIs.
>>
>> I am trying to run some projects and i get the following errors:
>>
>> param count mismatch
>> virt params=2 optional=1 flash.geom::Transform/getRelativeMatrix3D()
>> over params=1 optional=0 flash.geom::Transform/getRelativeMatrix3D()
>> VerifyError: Error #1053: Illegal override of Transform in
>> mx.geom.Transform.
>>
>> at
>>
>> spark.primitives.supportClasses::GraphicElement/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\spark\src\spark\primitives\supportClasses\GraphicElement.as:3546]
>> at
>>
>> spark.components::Group/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\spark\src\spark\components\Group.as:938]
>> at
>>
>> mx.managers::LayoutManager/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:601]
>> at
>>
>> mx.managers::LayoutManager/doPhasedInstantiation()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:787]
>> at
>>
>> mx.managers::LayoutManager/doPhasedInstantiationCallback()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1191]
>>
>>
>> Any ideas?
>>
>>
>>
>> --
>> Sent from: http://apache-flex-users.246.n4.nabble.com/
>>
>

Re: Flex 4.16.1 broken for AIR33.1?

[Greg Dove]

It sounds like an extra optonal parameter was added to

mx.geom.Transform.getRelativeMatrix3D

You could try monkey patching

mx.geom.Transform

by adding the source package for that to your local project, and then look
at the overridden method for 'getRelativeMatrix3D' and add the second
missing parameter for the latest version of that method





On Wed, Mar 4, 2020 at 7:49 AM leokan23  wrote:

> It looks like there is an issue with the latest AIR version, after they
> updated the geometry APIs.
>
> I am trying to run some projects and i get the following errors:
>
> param count mismatch
> virt params=2 optional=1 flash.geom::Transform/getRelativeMatrix3D()
> over params=1 optional=0 flash.geom::Transform/getRelativeMatrix3D()
> VerifyError: Error #1053: Illegal override of Transform in
> mx.geom.Transform.
>
> at
>
> spark.primitives.supportClasses::GraphicElement/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\spark\src\spark\primitives\supportClasses\GraphicElement.as:3546]
> at
>
> spark.components::Group/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\spark\src\spark\components\Group.as:938]
> at
>
> mx.managers::LayoutManager/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:601]
> at
>
> mx.managers::LayoutManager/doPhasedInstantiation()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:787]
> at
>
> mx.managers::LayoutManager/doPhasedInstantiationCallback()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1191]
>
>
> Any ideas?
>
>
>
> --
> Sent from: http://apache-flex-users.246.n4.nabble.com/
>

Flex 4.16.1 broken for AIR33.1?

[leokan23]

It looks like there is an issue with the latest AIR version, after they
updated the geometry APIs.

I am trying to run some projects and i get the following errors:

param count mismatch
virt params=2 optional=1 flash.geom::Transform/getRelativeMatrix3D()
over params=1 optional=0 flash.geom::Transform/getRelativeMatrix3D()
VerifyError: Error #1053: Illegal override of Transform in
mx.geom.Transform.

at
spark.primitives.supportClasses::GraphicElement/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\spark\src\spark\primitives\supportClasses\GraphicElement.as:3546]
at
spark.components::Group/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\spark\src\spark\components\Group.as:938]
at
mx.managers::LayoutManager/validateProperties()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:601]
at
mx.managers::LayoutManager/doPhasedInstantiation()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:787]
at
mx.managers::LayoutManager/doPhasedInstantiationCallback()[D:\flex_sdk\Sources\flex-sdk\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1191]


Any ideas?



--
Sent from: http://apache-flex-users.246.n4.nabble.com/