I was actually just trying to follow the instructions on the wiki. I don’t remember right now exactly what I did, but I did create a new project and just copied the source files. For some reason that did not work. I’m using FB 4.5. Could that be the problem?
I had some urgent things to take care of the last few days, but I’ll probably be back at this tomorrow… Here’s my plan to get up to speed in FlexJS: 1) Get myself setup so I can code (with code hinting), build and debug any project. (either in FB or IntelliJ) 2) Get that to work from the source folder (so I’m able to fix and add to the develop branch and debug changes). 3) Setup my own project and get that working. 4) Setup a project that can do bi-directional handling of XML. (this is a really important feature for me) I’m thinking of creating some classes which will act as proxies for Flash XML and DOM XMLDocument. I’m hoping to be able to reproduce the basics of E4X in a more normal syntax. 5) Get EaselJS working. Once I get to step 5, I think I’ll be very comfortable with FlexJS... On Oct 26, 2015, at 7:43 PM, Alex Harui <aha...@adobe.com> wrote: > 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 >> >
