royale-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] aharui commented on issue #57: Dependency error when extending class and implementing interface from "external" SWC library
Date Sun, 18 Nov 2018 07:21:17 GMT
aharui commented on issue #57: Dependency error when extending class and implementing interface
from "external" SWC library
URL: https://github.com/apache/royale-compiler/issues/57#issuecomment-439673123
 
 
   IMO, it will make the SWCs really fat to additionally pack Externs in them.  And it will
take longer to compile the SWC because we will have to transpile not only to JS but transpile
again to Externs.  My thinking is that a whole bunch of SWCs may never be used as external
libraries, so SWC developers would be faced with packing externs just-in-case.
   
   Also, Google Closure Compiler doesn't run when building a SWC, it only runs when creating
an application or module, and the Flex workflow for kicking classes out of the model is probably
well-known to those migrating.  So teaching the Royale application compiler to generate the
externs based on what classes from all SWCs were actually put in the output that will be loaded
to provide those external dependencies.
   
   Or maybe I'm not understanding what you are trying to do with your SWCs.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message