Today I had to start work on the "JS resources on the classpath" feature. In order to get VF2JS working, I had to somehow provide the closure-library which is downloaded using maven so the compiler can copy the static resources to the bin/js-debug directory. So I guess if I get this working with VF2JS we're a good step closer to adding a similar feature to FlexJS. Another Idea I had that could help prevent classpath clashes would be to locate all JS resources in a js (or ".js", or "_js" directory inside the swc)
Currently I somehow need to scann the classpath for resources. I was planning on using this library for this task: https://code.google.com/p/reflections/ are there any objections against this? Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Dienstag, 11. November 2014 17:08 An: dev@flex.apache.org Betreff: Re: AW: AW: [FLEX-JS] Streamlining the packaging On 11/11/14, 3:37 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi Alex, > >well I don't see a reason why FlashBuilder should have a problem with >this. >After all you are setting the command line manually now too (If I'm not >mistaken) My concern is about FlashBuilder opening the SWCs to do code-hinting in the IDE. I just want to make sure it doesn’t choke on js files in there. > >My suggestion would probably need a little modification cause in this >case it wouldn't take a js-root-path but look inside all the SWC files >that is was provided with and use the resources in there. I guess >currently Falcon wouldn't be able to work that way. But with this option >I even guess that it should be possible to build a FlexJS application >with the default build configs. Right, FalconJX would learn to use the library-path to find JS files so there wouldn’t be any additional options. We could have different clients like FlexJSMXMLC instead of the js-output-type option if that makes life easier for folks. -Alex
