You mean the property is unknown to FalconJX (i.e. isn't handled yet),
or do you mean a property that isn't part of the MXML specification
(whatever that may be ;-))?
EdB
On Tue, Apr 23, 2013 at 8:32 AM, Tigran Najaryan tig...@gmail.com wrote:
I am trying to understand how to make FalconJX
From: Erik de Bruin [mailto:e...@ixsoftware.nl]
You mean the property is unknown to FalconJX (i.e. isn't handled yet), or
do
you mean a property that isn't part of the MXML specification
(whatever that may be ;-))?
EdB
Well, I tried property automationName which is part of the current
In short: compiler.jx (FalconJX) gets it's information from compiler
(Falcon). The AS/MXML source is compiled for use in compiler.jx by the
compiler (duh ;-)) into an AST (Abstract Syntax Table), which becomes
available to use in the JS production in 'MXMLBlockWalker.java ::
visitCompilationUnit
I think Tigran wants to know where the allowed set of attributes for a tag
come from. They come from the set of public variables and setters on the
class represented by the tag. To add automationName, you would add it to
UIBase.as (and UIBase.js)
However, it is my goal that things like
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
I think Tigran wants to know where the allowed set of attributes for a tag
come from. They come from the set of public variables and setters on the
class represented by the tag. To add automationName, you would add it
Currently, I have no plans to match every one of the properties in the
current Flex SDK. Erik has mentioned making the effort to try to do so, but
I still think that is too much work and the results will not be as optimal.
Which properties we keep from the current FlexSDK in FlexJS depends on
