Hi Alex, I thought Maven build was now the preferred way of building FlexJS over ant With Maven all this complicated recipe will be over (thank to god) and will only need to pass maven to build in his local repository and the create a pom based on some of the examples (Maybe this last part is dependent on some last work Chris is making this days, at least I'm waiting anxiously for that and laready build with maven)
Thanks 2016-07-07 7:40 GMT+02:00 Alex Harui <aha...@adobe.com>: > In theory, there is a better way. Try the following and report where it > doesn't work and we'll see if we can figure out how to make it work. > > First, run ant in the repo. This should generate all of the JS files. > > There should be Flash Builder project files in the repo in each > frameworks/projects folder and frameworks/js/FlexJS/projects folders. > Create a new workspace, add the nightly as a Flex SDK, import all of the > projects. You will probably have to fix up the projects to use the > nightly SDK. > > Now add/create a test application. The test application should select the > nightly as its SDK. From the Project menu, choose Properties, then choose > Flex Build Path from the left-side list and make sure library path is > shown on the right. > > Expand the SDK entry in the list. > Click on each SWC other than playerglobal.swc and choose Remove to remove > it from the list. > Click on Add Project and add each of the projects it needs. > > At this point, changing an AS file in any project should result in a new > SWF with the changes. However, for me, changes to Core.swc cause FB to > hang and I have to restart FB (sometimes twice) to get back to working > again. That might be a good reason to make SWC changes in a SWC other > than Core. > > To build the JS version, you should be able to run the FlexJS (JS CompC) > on the project with the changes. This should generate a fresh set of JS > files. Double-check to make sure they are going in the correct folder. > > Then, from the Run menu, choose External Tools then External Tools > Configuration. Make a copy of FlexJS (FalconJX Debug Build). In that > copy, in the arguments before the -fb option, add sdk-js-lib=<path to > generated-source folder> for each of the SWCs you need in your app. Then, > when you run that config, it should use the newly generated-source folders. > > HTH, > -Alex > > > On 7/6/16, 8:59 PM, "yishayw" <yishayj...@hotmail.com> wrote: > > >I'd like to optimize my SDK development workflow. Currently I have a > >folder > >which contains the nightly build, and a separate folder which has the > >latest > >develop branch of flex-asjs. My main FlashBuilder project is configured to > >use the nightly build as the SDK. > > > > > >When I make changes to flex-asjs develop, I clean my project from > >FlashBuilder, compile from the command line, and use the following > >(windows) > >commands to copy the compiled files: > > > >---- > >copy C:\dev\flexjs\flex-asjs\frameworks\js\FlexJS\libs\*.swc > >C:\dev\flexjs_builds\nightly_07\frameworks\js\FlexJS\libs > > > >copy C:\dev\flexjs\flex-asjs\frameworks\libs\*.swc > >C:\dev\flexjs_builds\nightly_07\frameworks\libs > > > >xcopy /E /Y C:\dev\flexjs\flex-asjs\frameworks\js\FlexJS\generated-sources > >C:\dev\flexjs_builds\nightly_07\frameworks\js\FlexJS\generated-sources > >----- > > > >Then I can see the SDK changes in my main project. > > > >Is there a better way to do this? Ideally, I'd like to edit a file from > >the > >SDK in FlashBuilder and have my main project recognize the changes > >immediately. > > > > > > > > > >-- > >View this message in context: > > > http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Developer-Setu > >p-tp53729.html > >Sent from the Apache Flex Development mailing list archive at Nabble.com. > > -- Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la prestación del servicio o información solicitados, teniendo usted derecho de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación necesaria.
