[
https://issues.apache.org/jira/browse/FLEX-34867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570960#comment-14570960
]
Alex Harui commented on FLEX-34867:
-----------------------------------
It is hard to know which demographic will find FlexJS most appealing: folks
creating new JS apps, or folks with existing Flex code bases looking for a way
to migrate off of Flash. For the latter, the more things we emulate from the
existing Flex SDK, the less painful migration will be although the output JS
might be fatter and slower. Lots of folks used application frameworks that
heavily relied on metadata accessed via describeType(). Emulating that may
make it possible for some of these application frameworks to be re-purposed for
FlexJS.
If you have 100,000 lines of AS code that has been running fine for several
years, the thought of porting it to any existing JS framework, or even a
language like TS and re-testing it all would make me nervous. My little test
of porting FlexStore to FlexJS showed that the AS "business logic" was almost
untouched. If someone were to write a more Spark-like component set (which
would be fatter and slower than the component set we've written so far) then
porting the MXML would be much less painful too, so eventually we might find
that folks want us to build out more of the introspection APIs they relied on
in Flash.
> Implement JavaScript metadata
> -----------------------------
>
> Key: FLEX-34867
> URL: https://issues.apache.org/jira/browse/FLEX-34867
> Project: Apache Flex
> Issue Type: New Feature
> Components: FalconJX
> Affects Versions: Apache FalconJX 0.0.2
> Reporter: Michael Schmalle
> Priority: Minor
>
> Allow for custom metadata;
> [JavaScript(export="true|false",mode=[global,prototype,json])]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
