You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Idylog - Nicolas Granon <ng...@idylog.com> on 2017/11/07 13:37:52 UTC
Source path in framework SWCs
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
RE: Source path in framework SWCs
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
We know that VSCode + Josh's extension is a very good setup.
We were just beginning to use it when the whole rename story came up...
That's why we went back to FB (plus we also had some maintenance going on and felt it would be quicker)
But as soon as VSCode allows code-assist + source debugging again, we will be back to it !
Nicolas Granon
> -----Message d'origine-----
> De : Harbs [mailto:harbs.lists@gmail.com]
> Envoyé : mardi 7 novembre 2017 14:52
> À : dev@royale.apache.org; ngranon@idylog.com
> Objet : Re: Source path in framework SWCs
>
> I know you’re trying to get FB working but:
>
> FWIW, Josh’s VS Code extension offers “go to definition”. I’m hoping
> we’ll get the functionality back really soon when it supports Royale.
>
> > On Nov 7, 2017, at 3:37 PM, Idylog - Nicolas Granon
> <ng...@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
> >
> >
> >
> >
> >
Re: Source path in framework SWCs
Posted by Harbs <ha...@gmail.com>.
I know you’re trying to get FB working but:
FWIW, Josh’s VS Code extension offers “go to definition”. I’m hoping we’ll get the functionality back really soon when it supports Royale.
> On Nov 7, 2017, at 3:37 PM, Idylog - Nicolas Granon <ng...@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
>
>
>
>
>
RE: Source path in framework SWCs
Posted by Yishay Weiss <yi...@hotmail.com>.
I think FDT still requires Eclipse 3 where language servers can’t be used, so they would need some major refactoring. I was thinking of a new plugin altogether that would leverage this [1] . But that would be an entire project…
[1] https://developers.redhat.com/blog/2016/11/24/deliver-support-for-new-languages-in-eclipse-ide-faster-with-generic-editor-and-language-servers/
________________________________
From: Piotr Zarzycki <pi...@gmail.com>
Sent: Wednesday, November 8, 2017 10:36:44 AM
To: dev@royale.apache.org
Subject: Re: Source path in framework SWCs
Hi Yishay,
We can raise ticket for FDT team and help them to have that support.
Moonshine successfully reuse Josh extension, so it may be possible.
Thanks, Piotr
2017-11-08 8:38 GMT+01:00 Yishay Weiss <yi...@hotmail.com>:
> Let’s hope FDT provides Royale support. We need a presence in Eclipse. New
> versions of Eclipse support generic editors that support language servers
> so maybe Josh’s work can be reused…
>
>
>
> ________________________________
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Tuesday, November 7, 2017 7:41:24 PM
> To: dev@royale.apache.org; ngranon@idylog.com
> Subject: 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" <ng...@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
> >
> >
> >
> >
> >
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Source path in framework SWCs
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Yishay,
We can raise ticket for FDT team and help them to have that support.
Moonshine successfully reuse Josh extension, so it may be possible.
Thanks, Piotr
2017-11-08 8:38 GMT+01:00 Yishay Weiss <yi...@hotmail.com>:
> Let’s hope FDT provides Royale support. We need a presence in Eclipse. New
> versions of Eclipse support generic editors that support language servers
> so maybe Josh’s work can be reused…
>
>
>
> ________________________________
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Tuesday, November 7, 2017 7:41:24 PM
> To: dev@royale.apache.org; ngranon@idylog.com
> Subject: 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" <ng...@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
> >
> >
> >
> >
> >
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
RE: Source path in framework SWCs
Posted by Yishay Weiss <yi...@hotmail.com>.
Let’s hope FDT provides Royale support. We need a presence in Eclipse. New versions of Eclipse support generic editors that support language servers so maybe Josh’s work can be reused…
________________________________
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Tuesday, November 7, 2017 7:41:24 PM
To: dev@royale.apache.org; ngranon@idylog.com
Subject: 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" <ng...@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
>
>
>
>
>
Re: RE: Source path in framework SWCs
Posted by Josh Tynjala <jo...@apache.org>.
The VSCode extension attempts to use the source path from the SWC, if possible. Basically, it checks the path for "/frameworks/projects/", and then, it tries to swap in the local path to the SDK on your computer.
- Josh
On 2017-11-07 13:12, "Idylog - Nicolas Granon" <ng...@idylog.com> wrote:
> 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:aharui@adobe.com]
> > Envoyé : mardi 7 novembre 2017 18:41
> > Ã : dev@royale.apache.org; ngranon@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" <ng...@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
> > >
> > >
> > >
> > >
> > >
>
>
>
RE: Source path in framework SWCs
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
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:aharui@adobe.com]
> Envoyé : mardi 7 novembre 2017 18:41
> À : dev@royale.apache.org; ngranon@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" <ng...@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
> >
> >
> >
> >
> >
Re: Source path in framework SWCs
Posted by Alex Harui <ah...@adobe.com.INVALID>.
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" <ng...@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
>
>
>
>
>