I am not an expert there, but I see in the SWCs that ship from Adobe that the source path (to the /projects/ folder) is in fact coded "inside" the SWCs. When I open the SWCs from the Royale binaries, the source path points to some absolute Jenkins source folder that is not part of the distribution.
So, my suggestion has nothing to do with FB in particular : it is about "how does the IDE find the source files" ? We are not in love with FB, and wish to use VSCode instead (in fact, as soon the as plugin is completely adapted for Royale). But still, the question remains : how does the IDE find the source files ? If that information is already embedded inside the SWCs, isn't it cleaner ? Nicolas Granon > -----Message d'origine----- > De : Alex Harui [mailto:aha...@adobe.com] > Envoyé : mardi 7 novembre 2017 18:41 > À : dev@royale.apache.org; ngra...@idylog.com > Objet : Re: Source path in framework SWCs > > AFAIK, there is no way to link the source-path "out-of-the-box". It is > a limitation of Flash Builder. We might provide a script that injects > the links into a project's files. That's about the best we can do, > short of monkey-patching FB. > > Long-term, the newer IDEs (VSCode, Moonshine) and older IDEs that have > active support (FDT, possibly) will eventually replace FB. I am only > maintaining FB so there is one less thing to have to change to get > started with Royale, but you may want to move off of FB before you > finish. > > -Alex > > On 11/7/17, 5:37 AM, "Idylog - Nicolas Granon" <ngra...@idylog.com> > wrote: > > >Is it possible to have the framework's SWCs compiled in such a way > that > >the "source path" is automatically attached (/projects folder and > >subfolder) ? > >Or maybe it is rather something to specify in a config file (and not > >when compiling the SWCs) ? > > > >It would really help to have the "go to definition" feature to work > >without having to manually link all those source files (and doing it > >again at each new version of the SDK !) > > > >Nicolas Granon > > > > > > > > > >
