royale-confie.xml wasn't in distribution folder, so it was not copied. I think the way Chris made distribution was copy a version of some file-template.xml and a duplicate without "-template" in the name. So I added those files, but still don't get VSCode works ok
regarding "royale-asjs" folder, I tried to run "ant -f InstallAdobeSDKs.xml" in royale-asjs folder and this added AIR sdk to this folder, but VSCode doesn't recognize Royale-asjs folder as a SDK. I'm a but loose here or maybe I'm not understanding how you create your local SDK to feed VSCode :? thanks El mar., 4 sept. 2018 a las 12:56, Harbs (<[email protected]>) escribió: > Yes. royale-asjs. > > Does Maven copy the royale-config.xml file? That’s required and is done by > the ant build. > > > On Sep 4, 2018, at 1:30 PM, Carlos Rovira <[email protected]> > wrote: > > > > mmm.... "asjs" folder is "royale-asjs" ? > > If I try to click in VSCode the SDK button (bottom-right) and click then > > "Add more SDKs to this list..." (button on top of VSCode) and go to > > "royale-asjs" it's not recognized as a valid SDK. Or are you talking > about > > other asjs folder? > > > > El mar., 4 sept. 2018 a las 12:24, Harbs (<[email protected]>) > escribió: > > > >> I’m not totally sure what you’re asking. > >> > >> I have VS Code pointed to my asjs folder. > >> > >> The only thing you need to do to make it a valid SDK is copying > >> playerglobal to frameworks/libs/player/11.1/playerglobal.swc: > >> > >> Thanks, > >> Harbs > >> > >>> On Sep 4, 2018, at 1:16 PM, Carlos Rovira <[email protected]> > >> wrote: > >>> > >>> Harbs, > >>> > >>> I suppose you create a SDK from develop to use with VSCode. Do you > create > >>> it with ANT? > >>> Can you post here how do you build it? > >>> I guess that we are very near to get a valid SDK build with maven, so > if > >> is > >>> few time, I'll try to fix this for this release, since I think it could > >> be > >>> a good improvement for people trying new release. If I see is not as > >> easy, > >>> I'll be dropping for next release. > >>> > >>> Thanks > >>> > >>> > >>> > >>> El mar., 4 sept. 2018 a las 11:18, Harbs (<[email protected]>) > >> escribió: > >>> > >>>> Cool. Thanks. > >>>> > >>>> I merged in all new commits in MXRoyale and develop. > >>>> > >>>>> On Sep 4, 2018, at 12:05 PM, Piotr Zarzycki < > [email protected] > >>> > >>>> wrote: > >>>>> > >>>>> Harbs, > >>>>> > >>>>> I will start checking tour De Flex in couple of hours. > >>>>> > >>>>> I saw yesterday new Pull Requests accepted from Pashmina in MXRoyale > >>>>> branch. Could make sure that is included in integration branch? > >>>>> > >>>>> Thanks, > >>>>> Piotr > >>>>> > >>>>> On Tue, Sep 4, 2018, 10:23 AM Harbs <[email protected]> wrote: > >>>>> > >>>>>> If we’re going to have “compatible sets”, we’re going to need some > way > >>>> of > >>>>>> organizing them (naming or otherwise) to indicate which sets of > >> layouts > >>>> are > >>>>>> compatible with each other. > >>>>>> > >>>>>>> On Sep 4, 2018, at 10:28 AM, Alex Harui <[email protected]> > >>>>>> wrote: > >>>>>>> > >>>>>>> It seems to me that there are going to be incompatible sets of > >> layouts. > >>>>>> IOW, if you want to use flexbox, you may have to use flexbox layouts > >> in > >>>> all > >>>>>> parents. And not use percentages in the children (IIRC). And not > nest > >>>>>> flexboxes, etc. > >>>>>> > >>>>>> > >>>> > >>>> > >>> > >>> -- > >>> Carlos Rovira > >>> http://about.me/carlosrovira > >> > >> > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > -- Carlos Rovira http://about.me/carlosrovira
