After seeing Luke’s email on a related topic, it occurred to me that you are probably trying to get each SWC to work as an FB AS library project, and then your app as a FlexJS application that relies on these library projects. TBH, I haven’t really worked that way, but I think it should be possible. I avoided this workflow so far because I didn’t want to deal with any issues with FB caching SWCs and handling MXML manifests.
I poked at it a bit this morning and discovered that Om tried to check in FB library project files for the SWCs, but the .gitignore ignored the .project files so the repo doesn’t have everything you need. Maybe Om can force commit those files and we can see how far that gets you. The project files are not in the source package, so any changes here don’t affect the proposed release. I would prefer that we get this release out without worrying about making the FB workflow better. One thing to note is that these project files will likely change significantly again once we finish up the back-port from JS to AS, so I’d rather defer work on the FB workflow until after we finish the port (which is also not part of this release). Is that ok? Thanks, -Alex On 10/25/15, 7:14 AM, "Alex Harui" <aha...@adobe.com> wrote: >I can’t help much with IntelliJ, but see below for FB. > >On 10/25/15, 2:22 AM, "Harbs" <harbs.li...@gmail.com> wrote: > >>Some more hitches: >> >>I’m following the instructions on the wiki[1] >> >>1) It seems that building the source does not produce a recognized SDK. I >>cannot add it as an SDK in Flash Builder. > >That has historically been true for all of our repo builds. I believe it >is because we do not want to copy the AIR SDK into the repo folder tree. >Instead, we have an “ant release” target that builds the release packages >the Installer can use. I have a custom sdk-installer-config-4.0.xml that >points to my repo’s out folder and tell the Installer to use that, or I >more often just copy the swcs over the install of the latest nightly >build. > >>2) The installation of FlexJS Nightly does produce a recognized SDK, and >>I was able to add that. >>3) I followed the instructions for adding the project, but FB is acting >>kind of funny. It’s not showing all the files in the Package Explorer. I >>used the Navigator to open the DataBinding example in the editor, but >>some classes are not recognized. For example: >>org.apache.flex.events.EventDispatcher > >For these issues, are these occurring after you have run the installer on >the nightly and added the results as a Flex SDK and are using that as the >project’s Flex SDK? >>4) I’m not getting any kind of code hinting at all. I have a feeling it’s >>related to the error below. >>5) When I added the develop build as a build configuration it did not >>work at all. When I added the nightly build, I get the following error >>when trying to run: > >I’m not sure what you mean by “adding the develop build as a build >configuration”. It sounds like you are trying a workflow I haven’t tried. > I would need more details about what steps you are trying. > >-Alex >
