It’s working pretty well for me. I’d be interesting in knowing what’s not working for you.
> On Nov 9, 2017, at 11:55 PM, Carlos Rovira <carlosrov...@apache.org> wrote: > > Hi Harbs, > > I did that, and see that code is referring the SDK ok now (Apache Royale > 0.9.0-SNAPSHOT), I created the SDK with maven from sources. > but intelligence seems not going very accurate. I didn't test it too much. > > hope Josh release is soon since I think this extension is very important. > > Thanks > > > > 2017-11-09 20:15 GMT+01:00 Harbs <harbs.li...@gmail.com > <mailto:harbs.li...@gmail.com>>: > >> I imagine Josh will release it soon, but it’s pretty easy to build if you >> don’t want to wait. >> >> I’m using the snapshot right now. The current release does not work with >> Royale. >> >> To use the snapshot: >> >> 1. Remove the release extension if it’s installed. >> 2. Run: mvn clean package >> 3. In the Extensions tab click the “more” button and click “Install from >> VSIX…” >> 4. Navigate to distribution/target/vscode-nextgenas/vscode-nextgenas/ >> vscode-nextgenas-0.8.0-SNAPSHOT.vsix >> >> HTH, >> Harbs >> >>> On Nov 9, 2017, at 8:13 PM, Carlos Rovira <carlosrov...@apache.org> >> wrote: >>> >>> Hi Harbs, >>> so following the issue I suppose that we need to build our own extension >>> right? >>> (I mean we still can't use released version with Royale right now?) >>> >>> 2017-11-09 17:09 GMT+01:00 Harbs <harbs.li...@gmail.com >>> <mailto:harbs.li...@gmail.com> <mailto: >> harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>>: >>> >>>> OK. >>>> >>>> I think I’m done fixing up the asconfigc files. Currently, the only >>>> problems being reported are in the GoogleMaps project. (not sure how to >> fix >>>> those), and some .pbj files in GRaphics. Hopefully Josh will make those >>>> errors go away. >>>> >>>> FYI, the first target in the targets list is the one which triggers the >>>> code assist. [1] >>>> >>>> I tried to set the order of the targets to what generally makes sense >> in a >>>> specific project. >>>> >>>> I’ll try to fix up the asconfigc files in the examples later. >>>> >>>> This is going to make it much easier to work on framework files. :-) >>>> >>>> Harbs >>>> >>>> [1]https://github.com/BowlerHatLLC/vscode-nextgenas/issues/155 >>>> <https://github.com/BowlerHatLLC/vscode-nextgenas/issues/155> < >>>> https://github.com/BowlerHatLLC/vscode-nextgenas/issues/155 >>>> <https://github.com/BowlerHatLLC/vscode-nextgenas/issues/155> < >> https://github.com/BowlerHatLLC/vscode-nextgenas/issues/155 >> <https://github.com/BowlerHatLLC/vscode-nextgenas/issues/155>>> >>>> >>>>> On Nov 9, 2017, at 9:24 AM, Harbs <harbs.li...@gmail.com >>>>> <mailto:harbs.li...@gmail.com> <mailto: >> harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote: >>>>> >>>>> I fixed up the asconfig file in the projects folder. >>>>> >>>>> Opening the projects folder give code intelligence on all the projects. >>>>> >>>>> Harbs >>>> >>>> >>> >>> >>> -- >>> Carlos Rovira >>> http://about.me/carlosrovira <http://about.me/carlosrovira> >>> <http://about.me/carlosrovira <http://about.me/carlosrovira>> >> > > > > -- > Carlos Rovira > http://about.me/carlosrovira <http://about.me/carlosrovira>
