You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Michael Schmalle (JIRA)" <ji...@apache.org> on 2015/06/02 21:31:52 UTC

[jira] [Created] (FLEX-34869) FlexJS framework/projects need to be refactored to take into account shared public API

Michael Schmalle created FLEX-34869:
---------------------------------------

             Summary: FlexJS framework/projects need to be refactored to take into account shared public API
                 Key: FLEX-34869
                 URL: https://issues.apache.org/jira/browse/FLEX-34869
             Project: Apache Flex
          Issue Type: Improvement
          Components: FlexJS
    Affects Versions: Apache FlexJS 0.0.2
            Reporter: Michael Schmalle


>From dev list;

>5. The API now needs to be yanked out of Core/as/src into another
>directory
>like Core/api/src, so the as Flash and as HTML ActionScript can share the
>same interfaces, correct? What would be the plan?

You know, I went and moved everything into up to 3 folders (as, js, asjs),
then found out that FB only supports one folder path per source attachment
for a SWC.  So now, when debugging you sometimes have to switch source
attachments from as to asjs.   So, I’m totally up for another folder
restructuring.

So, not sure what files need to be yanked out and shared, but seems like
we have 3 different classes of source files;

1) AS for Flash
2) AS for JS
3) AS for both Flash and JS

I wonder if we need to plan ahead for any JS source for something we need
to hack in that can’t be described in AS.

Anyway, do you happen to know how IJ associates source with SWCs for
debugging?  FB would rather we put #1 and #3 in the same source folder,
but that makes describing what gets cross-compiled to JS more difficult.
We could make COMPJSC smarter and ignore files with some directive in it
so folks don’t need to keep adding to a list of files when adding new
files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)