On 5/17/17, 3:24 AM, "yishayw" <yishayj...@hotmail.com> wrote:
>It's actually working. I just needed to clean the test project, as well as >the framework where I made changes. That's good news. Does that mean you are all set for your demo? Having to clean to see new files and changes to CSS files may be required for this release. The FB integration used to always request a full rebuild, but with dual mode that can be expensive so we now build up the list of sources and look for the modified dates to change. We should also be watching the parent folders as well, but I don't know if new files are detectable that way. And for a CSS file change in a SWC, the CSS file is not compiled (it is just packaged in the SWC) so it currently isn't in the list of files to watch. There is a note in the compiler source comments that watching 'everything' was also expensive. Hopefully, actually changing an existing source file will trigger a rebuild (it does for me in a test app). I will try to verify that it works in a library project as well. The compile usually takes long enough that you can see the "Building Workspace" progress bar in lower right in FB. And then, to see changes to SWCs in the test apps that use them, because we don't overwrite JS files in the output folder, you may always have to clean the test app project as well. Maybe there should be a way to force an overwrite. We also need to verify that cleaning a project from an IDE cleans out the bin/js-debug folder. For me, I created a whole new workspace and imported all of the FB project and it will not build for me, and in looking at the project files, it probably shouldn't. So I'm fixing up project files and the FB integration today. So if your demo is working for you, you may have gotten lucky so be careful about refreshing your workspace. I hope to fix this today so if new folks try bringing in these projects that the workspace does build correctly. Thanks for working on this, -Alex
