On 9/17/13 9:21 PM, "Justin Mclean" wrote:
>Hi,
>
>> Seems like the options are (at least):
>> 1) The release notes say that Falcon only works with 4.11 and greater so
>> 'too bad' if you try against an older SDK
>> 2) Hard-code Spark as the default theme
>> 3) Have Falcon report an warning if
Hi,
> Seems like the options are (at least):
> 1) The release notes say that Falcon only works with 4.11 and greater so
> 'too bad' if you try against an older SDK
> 2) Hard-code Spark as the default theme
> 3) Have Falcon report an warning if no theme is found in any config file.
> 4) Have Falcon
On 9/17/13 5:12 PM, "Justin Mclean" wrote:
>Hi,
>
>> If Erik doesn't want to upgrade to 4.11, he can add a tag to
>>his SDK's
>> air-config.xml. Are we ok with that?
>-1 to that, sorry but it's just going to confuse people.
Seems like the options are (at least):
1) The release notes say that
On 9/17/13 6:50 PM, "Justin Mclean" wrote:
>Hi,
>
>Also depending on how AIR is added to the Flex SDK, it may use the air
>config file from the AIR SDK which will be missing the now required theme
>line.
I looked in my AIR 3.4 SDK and didn't see an air-config, so I thought the
only copy was our
Hi,
Also depending on how AIR is added to the Flex SDK, it may use the air config
file from the AIR SDK which will be missing the now required theme line.
Justin
Hi,
> If Erik doesn't want to upgrade to 4.11, he can add a tag to his SDK's
> air-config.xml. Are we ok with that?
-1 to that, sorry but it's just going to confuse people.
> My internal customer's app specifies a long list of locales, including
> en_GB. But they don't have custom resource bun
On Sep 17, 2013 12:22 PM, "Erik de Bruin" wrote:
>
> >>> Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then
> >>>uses
> >>> Falcon and gets a bunch of errors about styles only supported in Spark
> >>> theme. The root cause is that the air-config.xml in every shipping
> >>> vers
On 9/17/13 12:38 PM, "OmPrakash Muppirala" wrote:
>I am not sure what exactly the benefits are when switching to the new
>Falcon compiler. Why exactly would I go through the hassle of modifying
>all these?
>
>I think Alex mentioned a while ago that we cannot expect compile times to
>improve a
t seems acceptable to me
to agree with.
-Fred
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 17 septembre 2013 21:10
À : dev@flex.apache.org
Objet : Re: [FALCON] Should Falcon compile older SDKs?
On 9/17/13 11:36 AM, "Erik de Bruin" wro
Yeah, there is an option for version hell there... On the other hand,
if the libs were updated to work with Falcon, they would still work
with the old compiler, if I'm not mistaken?
EdB
On Tue, Sep 17, 2013 at 7:00 PM, OmPrakash Muppirala
wrote:
> On Tue, Sep 17, 2013 at 9:30 AM, Erik de Bruin
>>> Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then
>>>uses
>>> Falcon and gets a bunch of errors about styles only supported in Spark
>>> theme. The root cause is that the air-config.xml in every shipping
>>> version of Flex doesn't have a tag and MXMLC is hard-coded to
>>>
On 9/17/13 11:36 AM, "Erik de Bruin" wrote:
>> Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then
>>uses
>> Falcon and gets a bunch of errors about styles only supported in Spark
>> theme. The root cause is that the air-config.xml in every shipping
>> version of Flex doesn't
> Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then uses
> Falcon and gets a bunch of errors about styles only supported in Spark
> theme. The root cause is that the air-config.xml in every shipping
> version of Flex doesn't have a tag and MXMLC is hard-coded to
> assume Spark
: Tuesday, September 17, 2013 1:50 PM
To: dev@flex.apache.org
Subject: RE: [FALCON] Should Falcon compile older SDKs?
Well if it's overall improvement, wouldn't it be worth the time to correct the
issues anyways?
What is the volume we are talking about?
-Mark
ailto:mark.kessler@usmc.mil]
>Sent: Tuesday, September 17, 2013 1:50 PM
>To: dev@flex.apache.org
>Subject: RE: [FALCON] Should Falcon compile older SDKs?
>
>Well if it's overall improvement, wouldn't it be worth the time to
>correct the issues anyways?
>
>What is the volume we are talking about?
>
>
>
>-Mark
apache.org
Subject: Re: [FALCON] Should Falcon compile older SDKs?
Yeah, there is an option for version hell there... On the other hand,
if the libs were updated to work with Falcon, they would still work
with the old compiler, if I'm not mistaken?
EdB
I say don't worry too much about backwards compatibility, that is
always a sure road to over complicating a piece of software. What I do
think should happen is to make the compiler 'selectable'... So you
compile with either the old one (default for some time), or the new
one. That way people can ev
On Tue, Sep 17, 2013 at 9:30 AM, Erik de Bruin wrote:
> I say don't worry too much about backwards compatibility, that is
> always a sure road to over complicating a piece of software. What I do
> think should happen is to make the compiler 'selectable'... So you
> compile with either the old one
Falcon is catching subtle coding issues that MXMLC didn't catch like duplicate
variable declarations, ambigous definitions and more. Therefore, there is a
good chance that when you compile an existing app with Falcon you might have to
fix some of your code. So far, I haven't seen anyone want t
19 matches
Mail list logo
