the front end
of the Falcon compiler, but has undergone a lot of evolution in that process.
- Gordon
-Original Message-
From: Clint Modien [mailto:cmod...@gmail.com]
Sent: Monday, August 06, 2012 10:11 AM
To: flex-dev@incubator.apache.org
Subject: Re: New namespaces and Flash Bu
it's probably worth mentioning that flash builder has its own compiler
implementation... while it might make sense to support it for this release...
it will be pretty difficult to continue to do so. Hopefully falcon was flash
builders plan to solve this problem.
Sent from my iPhone
On Aug 6,
Hi,
> That is baked into the compiler. It is the constant MXML_2009_NAMESPACE
> in MxmlNamespaces.java. I also see constants for SPARK_NAMESPACE and
> MX_NAMESPACE in that file but I didn't follow thru and see how they were
> used.
Well that's something we can change at least.
Thanks,
Justin
On 8/6/12 4 :41AM, "Justin Mclean" wrote:
>Hi,
>
>As suggested in another thread I thought I'd try replacing the existing
>Adode namespaces with Apache namespaces to see what would happen.
>
>It's easy enough to add them to the flex-config.xml like so, pointing to
>the existing manifest files:
Hi,
> This is newly a vendor tooling issue to be worked with people at adobe. But
> again, I think that tool should be framework compliant and not the
> inverse...
In a perfect world sure I would agree. However there a lot of people still
using Flash Builder 4.6 and to encourage them to move to A
This is newly a vendor tooling issue to be worked with people at adobe. But
again, I think that tool should be framework compliant and not the
inverse... (as this was discussed in packaing sdk for flash builder...)
2012/8/6 Justin Mclean
> Hi,
>
> As suggested in another thread I thought I'd t
Hi,
As suggested in another thread I thought I'd try replacing the existing Adode
namespaces with Apache namespaces to see what would happen.
It's easy enough to add them to the flex-config.xml like so, pointing to the
existing manifest files:
http://flex.apache.org/mxml/
