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/03 14:30:11 UTC
FB : Strange side effects of -js-output argument
(my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9 binaries)
In some of my previous posts, I have tried to explain how to setup FB and
also the problems I got with code-assist (auto-complete) not working
properly.
I also suggested a "working" setup of FB.
Now, I have a *very* strange issue :
If I add "-js-output=somepath" to the compiler arguments (from "Project >
Properties > Flex compiler" tab), code-assist is lost !!!! (almost
entirely). (side note : the project compiles without errors, and output is
in fact directed to (somepath)).
If I remove the argument, code-assist is back ! (of course, output is
directed to the bin/js-debug inside the project folder as it should)
My flex-config.xml is the one that ships with the binaries distribution.
The project is a basic "hello world" project (one view, one label).
The js-output folder name has no spaces in it.
Note that when *adding" the -js-output parameter and validating the dialog,
I get a "realtime error processor" from FB. After closing and restrarting
FB, that error disappears, but it clearly shows that some active process get
lost in the dark... I suspect the active "realtime" process is code-assist.
Is it possible that the handling of this argument changes something inside
the internal paths used by FB for the current project ??? Maybe it is just a
matter of "restoring" the changed values after the compiler runs ???
And while I am at it, what are the *current* (0.9) values for -targets
argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex ???)
Nicolas Granon
RE: FB : Strange side effects of -js-output argument
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
As I said, it is not such a big deal for now (for us!).
Also, there was a small but important typo in my message.
We tried :
<js-output>
<path-element>/myoutputdir</path-element>
</js-output>
with a closing </path-element>, of course...
When you are at it, it seems that royale specific arguments are not listed when executing :
Mxmlc -help list (with or without "advanced" param)
Except "compiler.info.royale" (undocumented ?)
Finally, it seems that when compiling for JSRoyale target, the :
<js:valuesImpl>
<js:SimpleCSSValuesImpl/>
</js:valuesImpl>
tag must be present is the root file, otherwise we get nothing displayed in the browser (but compile is ok).
Maybe, for js output, additional warnings would be useful ? (like proper succession of <Application/>, <valuesImpl/>, <initialView/> tags...?
At this time, if the developer messes those, compiler outputs very cryptic errors... (like "generated byte code contains an operand stack underflow"...not very helpful !)
That is probably not "top priority", though.
Regarding code-assist, if FB setup is correctly made (left alone the js compiler arguments issue), code assist seems to work almost fine.
Nicolas Granon
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com]
> Envoyé : dimanche 5 novembre 2017 08:21
> À : ngranon@idylog.com; dev@royale.apache.org
> Objet : Re: FB : Strange side effects of -js-output argument
>
> Bummer, I think -js-output is currently broken. We'll have to look
> into fixing it.
>
> Sorry about that,
> -Alex
>
> On 11/4/17, 9:55 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
> wrote:
>
> >It's not such a big issue for now : what I have done is, I have a
> small
> >eclipse plug-in that can copy files from workspace to another
> >destination after compile.
> >
> >Since we have other (non Royale) files to copy to the http server
> >anyway...
> >
> >Your suggestion (adding the js-output argument in flex-config.xml) is
> >interesting, but what is the proper syntax ???
> >
> >I have tried :
> >
> > <js-output>
> > <path-element>/myoutputdir<path-element>
> > </js-output>
> >
> >But it does not work. Should there be a <path-element/> subtag ? Or
> >maybe it should have another name ? (or no subtag at all ?)...
> >
> >Nicolas Granon
> >
> >
> >
> >
> >> -----Message d'origine-----
> >> De : Alex Harui [mailto:aharui@adobe.com] Envoyé : samedi 4 novembre
> >> 2017 15:26 À : dev@royale.apache.org; ngranon@idylog.com Objet : Re:
> >> FB : Strange side effects of -js-output argument
> >>
> >> Piotr, Nicolas,
> >>
> >> As I said a few posts ago, I will look into it next week (probably
> >> Thursday), when I can try to set up a debug environment with the FB
> >> source code. I'm not able to do it now. The code-hinting system
> >> seems to not care that the default flex-config.xml has these new
> >> options, so you might be able to add your new options there as a
> >> workaround for now.
> >>
> >> Thanks,
> >> -Alex
> >>
> >> On 11/4/17, 1:12 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
> >> wrote:
> >>
> >> >Nope. It is not a casing problem.
> >> >
> >> >I can confirm that any additional "royale" argument in the "flex
> >> >compiler" panel breaks code-assist (it also triggers the realtime
> >> >processor error when you "apply" the settings).
> >> >
> >> >I also tried to use an additional config file (using -load-config
> >> >argument with the += syntax) but if the additional config file
> >> contains
> >> >a Royale argument (js-output, for example) it triggers an "uncaught
> >> >compiler exception".
> >> >
> >> >Nicolas Granon
> >> >
> >> >
> >> >
> >> >> -----Message d'origine-----
> >> >> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
> >> >> Envoyé : samedi 4 novembre 2017 03:32 À : dev@royale.apache.org;
> >> >> ngranon@idylog.com Objet : Re: FB : Strange side effects of
> >> >> -js-output argument
> >> >>
> >> >> Nicolas,
> >> >>
> >> >> Try to write exactly as I provide you -targets=JSRoyale or -
> >> >> compiler.targets=JSRoyale
> >> >>
> >> >> Piotr
> >> >>
> >> >> On Fri, Nov 3, 2017, 23:34 Idylog - Nicolas Granon
> >> >> <ng...@idylog.com>
> >> >> wrote:
> >> >>
> >> >> > Even more :
> >> >> >
> >> >> > When you add *any* royale argument to the "compiler arguments"
> >> >> dialog,
> >> >> > it breaks code-assist !!
> >> >> >
> >> >> > I just added -targets=jsroyale to the compiler arguments (no
> >> >> > -js-output
> >> >> > argument) and it also breaks code-assist !!!
> >> >> > (moreover, it does not seem to work : the swf is output as
> >> >> > well..)
> >> >> >
> >> >> > Something out there really needs a fix...
> >> >> >
> >> >> > Nicolas Granon
> >> >> >
> >> >> >
> >> >> >
> >> >> > > -----Message d'origine-----
> >> >> > > De : Alex Harui [mailto:aharui@adobe.com.INVALID] Envoyé :
> >> >> > > vendredi
> >> >> > > 3 novembre 2017 18:01 À : dev@royale.apache.org;
> >> >> > > ngranon@idylog.com Objet : Re: FB : Strange side effects of
> >> >> > > -js-output argument
> >> >> > >
> >> >> > > Yeah, I noticed that too. I think FB is running its own
> >> compiler
> >> >> > > for code-assist and new compiler options break that internal
> >> >> > > compiler. I'm planning to dig into it more next week. It
> >> >> > > might be that some compiler options have to be specified
> >> >> > > inside -config.xml
> >> >> files.
> >> >> > >
> >> >> > > -Alex
> >> >> > >
> >> >> > > On 11/3/17, 7:59 AM, "Idylog - Nicolas Granon"
> >> >> > > <ng...@idylog.com>
> >> >> > > wrote:
> >> >> > >
> >> >> > > >Ok, thanks.
> >> >> > > >
> >> >> > > >Nicolas Granon
> >> >> > > >
> >> >> > > >
> >> >> > > >
> >> >> > > >
> >> >> > > >> -----Message d'origine----- De : Piotr Zarzycki
> >> >> > > >> [mailto:piotrzarzycki21@gmail.com]
> >> >> > > >> Envoyé : vendredi 3 novembre 2017 15:40 À :
> >> >> dev@royale.apache.org
> >> >> > > >> Objet : Re: FB : Strange side effects of -js-output
> >> >> > > >> argument
> >> >> > > >>
> >> >> > > >> Hi Nicolas,
> >> >> > > >>
> >> >> > > >> Current compiler targets is "JSRoyale" for JS only output.
> >> >> > > >>
> >> >> > > >> Piotr
> >> >> > > >>
> >> >> > > >>
> >> >> > > >> 2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon
> >> >> > > >> <ng...@idylog.com>:
> >> >> > > >>
> >> >> > > >> > (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9
> >> >> > > >> > binaries)
> >> >> > > >> >
> >> >> > > >> > In some of my previous posts, I have tried to explain
> how
> >> to
> >> >> > > >> > setup FB and also the problems I got with code-assist
> >> >> > > >> > (auto-complete)
> >> >> > > not
> >> >> > > >> > working properly.
> >> >> > > >> > I also suggested a "working" setup of FB.
> >> >> > > >> >
> >> >> > > >> > Now, I have a *very* strange issue :
> >> >> > > >> >
> >> >> > > >> > If I add "-js-output=somepath" to the compiler arguments
> >> >> > > >> > (from "Project > Properties > Flex compiler" tab),
> >> >> > > >> > code-assist is lost
> >> >> > > !!!!
> >> >> > > >> > (almost entirely). (side note : the project compiles
> >> without
> >> >> > > >> > errors, and output is in fact directed to (somepath)).
> >> >> > > >> >
> >> >> > > >> > If I remove the argument, code-assist is back ! (of
> >> >> > > >> > course, output is directed to the bin/js-debug inside
> the
> >> >> > > >> > project folder as it
> >> >> > > >> > should)
> >> >> > > >> >
> >> >> > > >> > My flex-config.xml is the one that ships with the
> >> >> > > >> > binaries
> >> >> > > >> distribution.
> >> >> > > >> >
> >> >> > > >> > The project is a basic "hello world" project (one view,
> >> >> > > >> > one
> >> >> > > label).
> >> >> > > >> > The js-output folder name has no spaces in it.
> >> >> > > >> >
> >> >> > > >> > Note that when *adding" the -js-output parameter and
> >> >> validating
> >> >> > > the
> >> >> > > >> > dialog, I get a "realtime error processor" from FB.
> After
> >> >> > > >> > closing and restrarting FB, that error disappears, but
> it
> >> >> > > >> > clearly shows that some active process get lost in the
> >> dark...
> >> >> > > >> > I suspect the active
> >> >> > > >> "realtime"
> >> >> > > >> > process is code-assist.
> >> >> > > >> >
> >> >> > > >> > Is it possible that the handling of this argument
> changes
> >> >> > > something
> >> >> > > >> > inside the internal paths used by FB for the current
> >> project
> >> >> ???
> >> >> > > >> Maybe
> >> >> > > >> > it is just a matter of "restoring" the changed values
> >> >> > > >> > after
> >> >> the
> >> >> > > >> > compiler runs ???
> >> >> > > >> >
> >> >> > > >> > And while I am at it, what are the *current* (0.9)
> values
> >> >> > > >> > for
> >> >> -
> >> >> > > >> targets
> >> >> > > >> > argument for js output ? (JS ? RoyaleJS ? JSRoyale ?
> >> >> > > >> > JSFlex
> >> >> > > >> > ???)
> >> >> > > >> >
> >> >> > > >> > Nicolas Granon
> >> >> > > >> >
> >> >> > > >> >
> >> >> > > >> >
> >> >> > > >> >
> >> >> > > >> >
> >> >> > > >> >
> >> >> > > >>
> >> >> > > >>
> >> >> > > >> --
> >> >> > > >>
> >> >> > > >> Piotr Zarzycki
> >> >> > > >>
> >> >> > > >> mobile: +48 880 859 557
> >> >> > > >> skype: zarzycki10
> >> >> > > >>
> >> >> > > >> LinkedIn:
> >> >> > >
> >> >>
> >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F
> >> >> >>ww
> >> >> > > >>w.l
> >> >> > > i
> >> >> > > >>nke
> >> >> > >
> >> >>
> >>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Caa45f87d335d49441da608
> >> >> >>d5
> >> >> > > >>22c
> >> >> > > b
> >> >> > > >>958
> >> >> > >
> >> >>
> >>7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63645318014075480
> >> >> >>7&
> >> >> > > >>sda
> >> >> > > t
> >> >> > > >>a=u
> >> >> > > >>7DZ4xxyJZls0CwbS8Tx6sI3uDn5p26h4c99xv4vuTk%3D&reserved=0
> >> >> > > >>
> >> >> > >
> >> >>
> >>
> >><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.
> >> >> > > l
> >> >> > > >>ink
> >> >> > > >>edin.com%2Fin%2Fpiotr-zarzycki-
> >> >> > > 92a53552&data=02%7C01%7C%7Caa45f87d335d
> >> >> > > >>494
> >> >> > >
> >> >>
> >>41da608d522cb9587%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6
> >> >> >>36
> >> >> > > >>453
> >> >> > > 1
> >> >> > > >>801
> >> >> > >
> >> >>
> >>40911063&sdata=FEbuvYXGHKlY4nXGjXgo4t7W4HwKtdM9A7gMHfxM%2BKU%3D&
> >> >> >>re
> >> >> > > >>ser
> >> >> > > v
> >> >> > > >>ed=
> >> >> > > >>0>
> >> >> > > >>
> >> >> > > >> GitHub:
> >> >> > >
> >> >>
> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2
> >> >> >>Fg
> >> >> > > >>ith
> >> >> > > u
> >> >> > > >>b.c
> >> >> > >
> >> >>
> >>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Caa45f87d335d49441da608d52
> >> >> >>2c
> >> >> > > >>b95
> >> >> > > 8
> >> >> > > >>7%7
> >> >> > >
> >> >>
> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140911063&s
> >> >> >>da
> >> >> > > >>ta=
> >> >> > > G
> >> >> > > >>TnQ
> >> >> > > >>7nenut8qnMUFTbA53QR6nVmRXsdpvPlb0D%2FSqtU%3D&reserved=0
> >> >> > > >
> >> >> >
> >> >> >
> >> >> >
> >> >
> >
> >
Re: FB : Strange side effects of -js-output argument
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Bummer, I think -js-output is currently broken. We'll have to look into
fixing it.
Sorry about that,
-Alex
On 11/4/17, 9:55 AM, "Idylog - Nicolas Granon" <ng...@idylog.com> wrote:
>It's not such a big issue for now : what I have done is, I have a small
>eclipse plug-in that can copy files from workspace to another destination
>after compile.
>
>Since we have other (non Royale) files to copy to the http server
>anyway...
>
>Your suggestion (adding the js-output argument in flex-config.xml) is
>interesting, but what is the proper syntax ???
>
>I have tried :
>
> <js-output>
> <path-element>/myoutputdir<path-element>
> </js-output>
>
>But it does not work. Should there be a <path-element/> subtag ? Or maybe
>it should have another name ? (or no subtag at all ?)...
>
>Nicolas Granon
>
>
>
>
>> -----Message d'origine-----
>> De : Alex Harui [mailto:aharui@adobe.com]
>> Envoyé : samedi 4 novembre 2017 15:26
>> À : dev@royale.apache.org; ngranon@idylog.com
>> Objet : Re: FB : Strange side effects of -js-output argument
>>
>> Piotr, Nicolas,
>>
>> As I said a few posts ago, I will look into it next week (probably
>> Thursday), when I can try to set up a debug environment with the FB
>> source code. I'm not able to do it now. The code-hinting system seems
>> to not care that the default flex-config.xml has these new options, so
>> you might be able to add your new options there as a workaround for
>> now.
>>
>> Thanks,
>> -Alex
>>
>> On 11/4/17, 1:12 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
>> wrote:
>>
>> >Nope. It is not a casing problem.
>> >
>> >I can confirm that any additional "royale" argument in the "flex
>> >compiler" panel breaks code-assist (it also triggers the realtime
>> >processor error when you "apply" the settings).
>> >
>> >I also tried to use an additional config file (using -load-config
>> >argument with the += syntax) but if the additional config file
>> contains
>> >a Royale argument (js-output, for example) it triggers an "uncaught
>> >compiler exception".
>> >
>> >Nicolas Granon
>> >
>> >
>> >
>> >> -----Message d'origine-----
>> >> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
>> >> Envoyé : samedi 4 novembre 2017 03:32 À : dev@royale.apache.org;
>> >> ngranon@idylog.com Objet : Re: FB : Strange side effects of
>> >> -js-output argument
>> >>
>> >> Nicolas,
>> >>
>> >> Try to write exactly as I provide you -targets=JSRoyale or -
>> >> compiler.targets=JSRoyale
>> >>
>> >> Piotr
>> >>
>> >> On Fri, Nov 3, 2017, 23:34 Idylog - Nicolas Granon
>> >> <ng...@idylog.com>
>> >> wrote:
>> >>
>> >> > Even more :
>> >> >
>> >> > When you add *any* royale argument to the "compiler arguments"
>> >> dialog,
>> >> > it breaks code-assist !!
>> >> >
>> >> > I just added -targets=jsroyale to the compiler arguments (no
>> >> > -js-output
>> >> > argument) and it also breaks code-assist !!!
>> >> > (moreover, it does not seem to work : the swf is output as well..)
>> >> >
>> >> > Something out there really needs a fix...
>> >> >
>> >> > Nicolas Granon
>> >> >
>> >> >
>> >> >
>> >> > > -----Message d'origine-----
>> >> > > De : Alex Harui [mailto:aharui@adobe.com.INVALID] Envoyé :
>> >> > > vendredi
>> >> > > 3 novembre 2017 18:01 À : dev@royale.apache.org;
>> >> > > ngranon@idylog.com Objet : Re: FB : Strange side effects of
>> >> > > -js-output argument
>> >> > >
>> >> > > Yeah, I noticed that too. I think FB is running its own
>> compiler
>> >> > > for code-assist and new compiler options break that internal
>> >> > > compiler. I'm planning to dig into it more next week. It might
>> >> > > be that some compiler options have to be specified inside
>> >> > > -config.xml
>> >> files.
>> >> > >
>> >> > > -Alex
>> >> > >
>> >> > > On 11/3/17, 7:59 AM, "Idylog - Nicolas Granon"
>> >> > > <ng...@idylog.com>
>> >> > > wrote:
>> >> > >
>> >> > > >Ok, thanks.
>> >> > > >
>> >> > > >Nicolas Granon
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > >> -----Message d'origine-----
>> >> > > >> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
>> >> > > >> Envoyé : vendredi 3 novembre 2017 15:40 À :
>> >> dev@royale.apache.org
>> >> > > >> Objet : Re: FB : Strange side effects of -js-output argument
>> >> > > >>
>> >> > > >> Hi Nicolas,
>> >> > > >>
>> >> > > >> Current compiler targets is "JSRoyale" for JS only output.
>> >> > > >>
>> >> > > >> Piotr
>> >> > > >>
>> >> > > >>
>> >> > > >> 2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon
>> >> > > >> <ng...@idylog.com>:
>> >> > > >>
>> >> > > >> > (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9
>> >> > > >> > binaries)
>> >> > > >> >
>> >> > > >> > In some of my previous posts, I have tried to explain how
>> to
>> >> > > >> > setup FB and also the problems I got with code-assist
>> >> > > >> > (auto-complete)
>> >> > > not
>> >> > > >> > working properly.
>> >> > > >> > I also suggested a "working" setup of FB.
>> >> > > >> >
>> >> > > >> > Now, I have a *very* strange issue :
>> >> > > >> >
>> >> > > >> > If I add "-js-output=somepath" to the compiler arguments
>> >> > > >> > (from "Project > Properties > Flex compiler" tab),
>> >> > > >> > code-assist is lost
>> >> > > !!!!
>> >> > > >> > (almost entirely). (side note : the project compiles
>> without
>> >> > > >> > errors, and output is in fact directed to (somepath)).
>> >> > > >> >
>> >> > > >> > If I remove the argument, code-assist is back ! (of course,
>> >> > > >> > output is directed to the bin/js-debug inside the project
>> >> > > >> > folder as it
>> >> > > >> > should)
>> >> > > >> >
>> >> > > >> > My flex-config.xml is the one that ships with the binaries
>> >> > > >> distribution.
>> >> > > >> >
>> >> > > >> > The project is a basic "hello world" project (one view, one
>> >> > > label).
>> >> > > >> > The js-output folder name has no spaces in it.
>> >> > > >> >
>> >> > > >> > Note that when *adding" the -js-output parameter and
>> >> validating
>> >> > > the
>> >> > > >> > dialog, I get a "realtime error processor" from FB. After
>> >> > > >> > closing and restrarting FB, that error disappears, but it
>> >> > > >> > clearly shows that some active process get lost in the
>> dark...
>> >> > > >> > I suspect the active
>> >> > > >> "realtime"
>> >> > > >> > process is code-assist.
>> >> > > >> >
>> >> > > >> > Is it possible that the handling of this argument changes
>> >> > > something
>> >> > > >> > inside the internal paths used by FB for the current
>> project
>> >> ???
>> >> > > >> Maybe
>> >> > > >> > it is just a matter of "restoring" the changed values after
>> >> the
>> >> > > >> > compiler runs ???
>> >> > > >> >
>> >> > > >> > And while I am at it, what are the *current* (0.9) values
>> >> > > >> > for
>> >> -
>> >> > > >> targets
>> >> > > >> > argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex
>> >> > > >> > ???)
>> >> > > >> >
>> >> > > >> > Nicolas Granon
>> >> > > >> >
>> >> > > >> >
>> >> > > >> >
>> >> > > >> >
>> >> > > >> >
>> >> > > >> >
>> >> > > >>
>> >> > > >>
>> >> > > >> --
>> >> > > >>
>> >> > > >> Piotr Zarzycki
>> >> > > >>
>> >> > > >> mobile: +48 880 859 557
>> >> > > >> skype: zarzycki10
>> >> > > >>
>> >> > > >> LinkedIn:
>> >> > >
>> >> >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fww
>> >> > > >>w.l
>> >> > > i
>> >> > > >>nke
>> >> > >
>> >> >>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Caa45f87d335d49441da608d5
>> >> > > >>22c
>> >> > > b
>> >> > > >>958
>> >> > >
>> >> >>7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140754807&
>> >> > > >>sda
>> >> > > t
>> >> > > >>a=u
>> >> > > >>7DZ4xxyJZls0CwbS8Tx6sI3uDn5p26h4c99xv4vuTk%3D&reserved=0
>> >> > > >>
>> >> > >
>> >>
>> >><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.
>> >> > > l
>> >> > > >>ink
>> >> > > >>edin.com%2Fin%2Fpiotr-zarzycki-
>> >> > > 92a53552&data=02%7C01%7C%7Caa45f87d335d
>> >> > > >>494
>> >> > >
>> >> >>41da608d522cb9587%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636
>> >> > > >>453
>> >> > > 1
>> >> > > >>801
>> >> > >
>> >> >>40911063&sdata=FEbuvYXGHKlY4nXGjXgo4t7W4HwKtdM9A7gMHfxM%2BKU%3D&re
>> >> > > >>ser
>> >> > > v
>> >> > > >>ed=
>> >> > > >>0>
>> >> > > >>
>> >> > > >> GitHub:
>> >> > >
>> >> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
>> >> > > >>ith
>> >> > > u
>> >> > > >>b.c
>> >> > >
>> >> >>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Caa45f87d335d49441da608d522c
>> >> > > >>b95
>> >> > > 8
>> >> > > >>7%7
>> >> > >
>> >> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140911063&sda
>> >> > > >>ta=
>> >> > > G
>> >> > > >>TnQ
>> >> > > >>7nenut8qnMUFTbA53QR6nVmRXsdpvPlb0D%2FSqtU%3D&reserved=0
>> >> > > >
>> >> >
>> >> >
>> >> >
>> >
>
>
RE: FB : Strange side effects of -js-output argument
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
It's not such a big issue for now : what I have done is, I have a small eclipse plug-in that can copy files from workspace to another destination after compile.
Since we have other (non Royale) files to copy to the http server anyway...
Your suggestion (adding the js-output argument in flex-config.xml) is interesting, but what is the proper syntax ???
I have tried :
<js-output>
<path-element>/myoutputdir<path-element>
</js-output>
But it does not work. Should there be a <path-element/> subtag ? Or maybe it should have another name ? (or no subtag at all ?)...
Nicolas Granon
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com]
> Envoyé : samedi 4 novembre 2017 15:26
> À : dev@royale.apache.org; ngranon@idylog.com
> Objet : Re: FB : Strange side effects of -js-output argument
>
> Piotr, Nicolas,
>
> As I said a few posts ago, I will look into it next week (probably
> Thursday), when I can try to set up a debug environment with the FB
> source code. I'm not able to do it now. The code-hinting system seems
> to not care that the default flex-config.xml has these new options, so
> you might be able to add your new options there as a workaround for
> now.
>
> Thanks,
> -Alex
>
> On 11/4/17, 1:12 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
> wrote:
>
> >Nope. It is not a casing problem.
> >
> >I can confirm that any additional "royale" argument in the "flex
> >compiler" panel breaks code-assist (it also triggers the realtime
> >processor error when you "apply" the settings).
> >
> >I also tried to use an additional config file (using -load-config
> >argument with the += syntax) but if the additional config file
> contains
> >a Royale argument (js-output, for example) it triggers an "uncaught
> >compiler exception".
> >
> >Nicolas Granon
> >
> >
> >
> >> -----Message d'origine-----
> >> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
> >> Envoyé : samedi 4 novembre 2017 03:32 À : dev@royale.apache.org;
> >> ngranon@idylog.com Objet : Re: FB : Strange side effects of
> >> -js-output argument
> >>
> >> Nicolas,
> >>
> >> Try to write exactly as I provide you -targets=JSRoyale or -
> >> compiler.targets=JSRoyale
> >>
> >> Piotr
> >>
> >> On Fri, Nov 3, 2017, 23:34 Idylog - Nicolas Granon
> >> <ng...@idylog.com>
> >> wrote:
> >>
> >> > Even more :
> >> >
> >> > When you add *any* royale argument to the "compiler arguments"
> >> dialog,
> >> > it breaks code-assist !!
> >> >
> >> > I just added -targets=jsroyale to the compiler arguments (no
> >> > -js-output
> >> > argument) and it also breaks code-assist !!!
> >> > (moreover, it does not seem to work : the swf is output as well..)
> >> >
> >> > Something out there really needs a fix...
> >> >
> >> > Nicolas Granon
> >> >
> >> >
> >> >
> >> > > -----Message d'origine-----
> >> > > De : Alex Harui [mailto:aharui@adobe.com.INVALID] Envoyé :
> >> > > vendredi
> >> > > 3 novembre 2017 18:01 À : dev@royale.apache.org;
> >> > > ngranon@idylog.com Objet : Re: FB : Strange side effects of
> >> > > -js-output argument
> >> > >
> >> > > Yeah, I noticed that too. I think FB is running its own
> compiler
> >> > > for code-assist and new compiler options break that internal
> >> > > compiler. I'm planning to dig into it more next week. It might
> >> > > be that some compiler options have to be specified inside
> >> > > -config.xml
> >> files.
> >> > >
> >> > > -Alex
> >> > >
> >> > > On 11/3/17, 7:59 AM, "Idylog - Nicolas Granon"
> >> > > <ng...@idylog.com>
> >> > > wrote:
> >> > >
> >> > > >Ok, thanks.
> >> > > >
> >> > > >Nicolas Granon
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >> -----Message d'origine-----
> >> > > >> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
> >> > > >> Envoyé : vendredi 3 novembre 2017 15:40 À :
> >> dev@royale.apache.org
> >> > > >> Objet : Re: FB : Strange side effects of -js-output argument
> >> > > >>
> >> > > >> Hi Nicolas,
> >> > > >>
> >> > > >> Current compiler targets is "JSRoyale" for JS only output.
> >> > > >>
> >> > > >> Piotr
> >> > > >>
> >> > > >>
> >> > > >> 2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon
> >> > > >> <ng...@idylog.com>:
> >> > > >>
> >> > > >> > (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9
> >> > > >> > binaries)
> >> > > >> >
> >> > > >> > In some of my previous posts, I have tried to explain how
> to
> >> > > >> > setup FB and also the problems I got with code-assist
> >> > > >> > (auto-complete)
> >> > > not
> >> > > >> > working properly.
> >> > > >> > I also suggested a "working" setup of FB.
> >> > > >> >
> >> > > >> > Now, I have a *very* strange issue :
> >> > > >> >
> >> > > >> > If I add "-js-output=somepath" to the compiler arguments
> >> > > >> > (from "Project > Properties > Flex compiler" tab),
> >> > > >> > code-assist is lost
> >> > > !!!!
> >> > > >> > (almost entirely). (side note : the project compiles
> without
> >> > > >> > errors, and output is in fact directed to (somepath)).
> >> > > >> >
> >> > > >> > If I remove the argument, code-assist is back ! (of course,
> >> > > >> > output is directed to the bin/js-debug inside the project
> >> > > >> > folder as it
> >> > > >> > should)
> >> > > >> >
> >> > > >> > My flex-config.xml is the one that ships with the binaries
> >> > > >> distribution.
> >> > > >> >
> >> > > >> > The project is a basic "hello world" project (one view, one
> >> > > label).
> >> > > >> > The js-output folder name has no spaces in it.
> >> > > >> >
> >> > > >> > Note that when *adding" the -js-output parameter and
> >> validating
> >> > > the
> >> > > >> > dialog, I get a "realtime error processor" from FB. After
> >> > > >> > closing and restrarting FB, that error disappears, but it
> >> > > >> > clearly shows that some active process get lost in the
> dark...
> >> > > >> > I suspect the active
> >> > > >> "realtime"
> >> > > >> > process is code-assist.
> >> > > >> >
> >> > > >> > Is it possible that the handling of this argument changes
> >> > > something
> >> > > >> > inside the internal paths used by FB for the current
> project
> >> ???
> >> > > >> Maybe
> >> > > >> > it is just a matter of "restoring" the changed values after
> >> the
> >> > > >> > compiler runs ???
> >> > > >> >
> >> > > >> > And while I am at it, what are the *current* (0.9) values
> >> > > >> > for
> >> -
> >> > > >> targets
> >> > > >> > argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex
> >> > > >> > ???)
> >> > > >> >
> >> > > >> > Nicolas Granon
> >> > > >> >
> >> > > >> >
> >> > > >> >
> >> > > >> >
> >> > > >> >
> >> > > >> >
> >> > > >>
> >> > > >>
> >> > > >> --
> >> > > >>
> >> > > >> Piotr Zarzycki
> >> > > >>
> >> > > >> mobile: +48 880 859 557
> >> > > >> skype: zarzycki10
> >> > > >>
> >> > > >> LinkedIn:
> >> > >
> >> >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fww
> >> > > >>w.l
> >> > > i
> >> > > >>nke
> >> > >
> >> >>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Caa45f87d335d49441da608d5
> >> > > >>22c
> >> > > b
> >> > > >>958
> >> > >
> >> >>7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140754807&
> >> > > >>sda
> >> > > t
> >> > > >>a=u
> >> > > >>7DZ4xxyJZls0CwbS8Tx6sI3uDn5p26h4c99xv4vuTk%3D&reserved=0
> >> > > >>
> >> > >
> >>
> >><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.
> >> > > l
> >> > > >>ink
> >> > > >>edin.com%2Fin%2Fpiotr-zarzycki-
> >> > > 92a53552&data=02%7C01%7C%7Caa45f87d335d
> >> > > >>494
> >> > >
> >> >>41da608d522cb9587%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636
> >> > > >>453
> >> > > 1
> >> > > >>801
> >> > >
> >> >>40911063&sdata=FEbuvYXGHKlY4nXGjXgo4t7W4HwKtdM9A7gMHfxM%2BKU%3D&re
> >> > > >>ser
> >> > > v
> >> > > >>ed=
> >> > > >>0>
> >> > > >>
> >> > > >> GitHub:
> >> > >
> >> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
> >> > > >>ith
> >> > > u
> >> > > >>b.c
> >> > >
> >> >>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Caa45f87d335d49441da608d522c
> >> > > >>b95
> >> > > 8
> >> > > >>7%7
> >> > >
> >> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140911063&sda
> >> > > >>ta=
> >> > > G
> >> > > >>TnQ
> >> > > >>7nenut8qnMUFTbA53QR6nVmRXsdpvPlb0D%2FSqtU%3D&reserved=0
> >> > > >
> >> >
> >> >
> >> >
> >
Re: FB : Strange side effects of -js-output argument
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Piotr, Nicolas,
As I said a few posts ago, I will look into it next week (probably
Thursday), when I can try to set up a debug environment with the FB source
code. I'm not able to do it now. The code-hinting system seems to not
care that the default flex-config.xml has these new options, so you might
be able to add your new options there as a workaround for now.
Thanks,
-Alex
On 11/4/17, 1:12 AM, "Idylog - Nicolas Granon" <ng...@idylog.com> wrote:
>Nope. It is not a casing problem.
>
>I can confirm that any additional "royale" argument in the "flex
>compiler" panel breaks code-assist (it also triggers the realtime
>processor error when you "apply" the settings).
>
>I also tried to use an additional config file (using -load-config
>argument with the += syntax) but if the additional config file contains a
>Royale argument (js-output, for example) it triggers an "uncaught
>compiler exception".
>
>Nicolas Granon
>
>
>
>> -----Message d'origine-----
>> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
>> Envoyé : samedi 4 novembre 2017 03:32
>> À : dev@royale.apache.org; ngranon@idylog.com
>> Objet : Re: FB : Strange side effects of -js-output argument
>>
>> Nicolas,
>>
>> Try to write exactly as I provide you -targets=JSRoyale or -
>> compiler.targets=JSRoyale
>>
>> Piotr
>>
>> On Fri, Nov 3, 2017, 23:34 Idylog - Nicolas Granon <ng...@idylog.com>
>> wrote:
>>
>> > Even more :
>> >
>> > When you add *any* royale argument to the "compiler arguments"
>> dialog,
>> > it breaks code-assist !!
>> >
>> > I just added -targets=jsroyale to the compiler arguments (no
>> > -js-output
>> > argument) and it also breaks code-assist !!!
>> > (moreover, it does not seem to work : the swf is output as well..)
>> >
>> > Something out there really needs a fix...
>> >
>> > Nicolas Granon
>> >
>> >
>> >
>> > > -----Message d'origine-----
>> > > De : Alex Harui [mailto:aharui@adobe.com.INVALID] Envoyé : vendredi
>> > > 3 novembre 2017 18:01 À : dev@royale.apache.org; ngranon@idylog.com
>> > > Objet : Re: FB : Strange side effects of -js-output argument
>> > >
>> > > Yeah, I noticed that too. I think FB is running its own compiler
>> > > for code-assist and new compiler options break that internal
>> > > compiler. I'm planning to dig into it more next week. It might be
>> > > that some compiler options have to be specified inside -config.xml
>> files.
>> > >
>> > > -Alex
>> > >
>> > > On 11/3/17, 7:59 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
>> > > wrote:
>> > >
>> > > >Ok, thanks.
>> > > >
>> > > >Nicolas Granon
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >> -----Message d'origine-----
>> > > >> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
>> > > >> Envoyé : vendredi 3 novembre 2017 15:40 À :
>> dev@royale.apache.org
>> > > >> Objet : Re: FB : Strange side effects of -js-output argument
>> > > >>
>> > > >> Hi Nicolas,
>> > > >>
>> > > >> Current compiler targets is "JSRoyale" for JS only output.
>> > > >>
>> > > >> Piotr
>> > > >>
>> > > >>
>> > > >> 2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon
>> > > >> <ng...@idylog.com>:
>> > > >>
>> > > >> > (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9
>> > > >> > binaries)
>> > > >> >
>> > > >> > In some of my previous posts, I have tried to explain how to
>> > > >> > setup FB and also the problems I got with code-assist
>> > > >> > (auto-complete)
>> > > not
>> > > >> > working properly.
>> > > >> > I also suggested a "working" setup of FB.
>> > > >> >
>> > > >> > Now, I have a *very* strange issue :
>> > > >> >
>> > > >> > If I add "-js-output=somepath" to the compiler arguments (from
>> > > >> > "Project > Properties > Flex compiler" tab), code-assist is
>> > > >> > lost
>> > > !!!!
>> > > >> > (almost entirely). (side note : the project compiles without
>> > > >> > errors, and output is in fact directed to (somepath)).
>> > > >> >
>> > > >> > If I remove the argument, code-assist is back ! (of course,
>> > > >> > output is directed to the bin/js-debug inside the project
>> > > >> > folder as it
>> > > >> > should)
>> > > >> >
>> > > >> > My flex-config.xml is the one that ships with the binaries
>> > > >> distribution.
>> > > >> >
>> > > >> > The project is a basic "hello world" project (one view, one
>> > > label).
>> > > >> > The js-output folder name has no spaces in it.
>> > > >> >
>> > > >> > Note that when *adding" the -js-output parameter and
>> validating
>> > > the
>> > > >> > dialog, I get a "realtime error processor" from FB. After
>> > > >> > closing and restrarting FB, that error disappears, but it
>> > > >> > clearly shows that some active process get lost in the dark...
>> > > >> > I suspect the active
>> > > >> "realtime"
>> > > >> > process is code-assist.
>> > > >> >
>> > > >> > Is it possible that the handling of this argument changes
>> > > something
>> > > >> > inside the internal paths used by FB for the current project
>> ???
>> > > >> Maybe
>> > > >> > it is just a matter of "restoring" the changed values after
>> the
>> > > >> > compiler runs ???
>> > > >> >
>> > > >> > And while I am at it, what are the *current* (0.9) values for
>> -
>> > > >> targets
>> > > >> > argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex
>> > > >> > ???)
>> > > >> >
>> > > >> > Nicolas Granon
>> > > >> >
>> > > >> >
>> > > >> >
>> > > >> >
>> > > >> >
>> > > >> >
>> > > >>
>> > > >>
>> > > >> --
>> > > >>
>> > > >> Piotr Zarzycki
>> > > >>
>> > > >> mobile: +48 880 859 557
>> > > >> skype: zarzycki10
>> > > >>
>> > > >> LinkedIn:
>> > >
>> >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fww
>> > > >>w.l
>> > > i
>> > > >>nke
>> > >
>> >>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Caa45f87d335d49441da608d5
>> > > >>22c
>> > > b
>> > > >>958
>> > >
>> >>7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140754807&
>> > > >>sda
>> > > t
>> > > >>a=u
>> > > >>7DZ4xxyJZls0CwbS8Tx6sI3uDn5p26h4c99xv4vuTk%3D&reserved=0
>> > > >>
>> > >
>> >><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.
>> > > l
>> > > >>ink
>> > > >>edin.com%2Fin%2Fpiotr-zarzycki-
>> > > 92a53552&data=02%7C01%7C%7Caa45f87d335d
>> > > >>494
>> > >
>> >>41da608d522cb9587%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636
>> > > >>453
>> > > 1
>> > > >>801
>> > >
>> >>40911063&sdata=FEbuvYXGHKlY4nXGjXgo4t7W4HwKtdM9A7gMHfxM%2BKU%3D&re
>> > > >>ser
>> > > v
>> > > >>ed=
>> > > >>0>
>> > > >>
>> > > >> GitHub:
>> > >
>> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
>> > > >>ith
>> > > u
>> > > >>b.c
>> > >
>> >>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Caa45f87d335d49441da608d522c
>> > > >>b95
>> > > 8
>> > > >>7%7
>> > >
>> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140911063&sda
>> > > >>ta=
>> > > G
>> > > >>TnQ
>> > > >>7nenut8qnMUFTbA53QR6nVmRXsdpvPlb0D%2FSqtU%3D&reserved=0
>> > > >
>> >
>> >
>> >
>
RE: FB : Strange side effects of -js-output argument
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
Nope. It is not a casing problem.
I can confirm that any additional "royale" argument in the "flex compiler" panel breaks code-assist (it also triggers the realtime processor error when you "apply" the settings).
I also tried to use an additional config file (using -load-config argument with the += syntax) but if the additional config file contains a Royale argument (js-output, for example) it triggers an "uncaught compiler exception".
Nicolas Granon
> -----Message d'origine-----
> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
> Envoyé : samedi 4 novembre 2017 03:32
> À : dev@royale.apache.org; ngranon@idylog.com
> Objet : Re: FB : Strange side effects of -js-output argument
>
> Nicolas,
>
> Try to write exactly as I provide you -targets=JSRoyale or -
> compiler.targets=JSRoyale
>
> Piotr
>
> On Fri, Nov 3, 2017, 23:34 Idylog - Nicolas Granon <ng...@idylog.com>
> wrote:
>
> > Even more :
> >
> > When you add *any* royale argument to the "compiler arguments"
> dialog,
> > it breaks code-assist !!
> >
> > I just added -targets=jsroyale to the compiler arguments (no
> > -js-output
> > argument) and it also breaks code-assist !!!
> > (moreover, it does not seem to work : the swf is output as well..)
> >
> > Something out there really needs a fix...
> >
> > Nicolas Granon
> >
> >
> >
> > > -----Message d'origine-----
> > > De : Alex Harui [mailto:aharui@adobe.com.INVALID] Envoyé : vendredi
> > > 3 novembre 2017 18:01 À : dev@royale.apache.org; ngranon@idylog.com
> > > Objet : Re: FB : Strange side effects of -js-output argument
> > >
> > > Yeah, I noticed that too. I think FB is running its own compiler
> > > for code-assist and new compiler options break that internal
> > > compiler. I'm planning to dig into it more next week. It might be
> > > that some compiler options have to be specified inside -config.xml
> files.
> > >
> > > -Alex
> > >
> > > On 11/3/17, 7:59 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
> > > wrote:
> > >
> > > >Ok, thanks.
> > > >
> > > >Nicolas Granon
> > > >
> > > >
> > > >
> > > >
> > > >> -----Message d'origine-----
> > > >> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
> > > >> Envoyé : vendredi 3 novembre 2017 15:40 À :
> dev@royale.apache.org
> > > >> Objet : Re: FB : Strange side effects of -js-output argument
> > > >>
> > > >> Hi Nicolas,
> > > >>
> > > >> Current compiler targets is "JSRoyale" for JS only output.
> > > >>
> > > >> Piotr
> > > >>
> > > >>
> > > >> 2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon
> > > >> <ng...@idylog.com>:
> > > >>
> > > >> > (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9
> > > >> > binaries)
> > > >> >
> > > >> > In some of my previous posts, I have tried to explain how to
> > > >> > setup FB and also the problems I got with code-assist
> > > >> > (auto-complete)
> > > not
> > > >> > working properly.
> > > >> > I also suggested a "working" setup of FB.
> > > >> >
> > > >> > Now, I have a *very* strange issue :
> > > >> >
> > > >> > If I add "-js-output=somepath" to the compiler arguments (from
> > > >> > "Project > Properties > Flex compiler" tab), code-assist is
> > > >> > lost
> > > !!!!
> > > >> > (almost entirely). (side note : the project compiles without
> > > >> > errors, and output is in fact directed to (somepath)).
> > > >> >
> > > >> > If I remove the argument, code-assist is back ! (of course,
> > > >> > output is directed to the bin/js-debug inside the project
> > > >> > folder as it
> > > >> > should)
> > > >> >
> > > >> > My flex-config.xml is the one that ships with the binaries
> > > >> distribution.
> > > >> >
> > > >> > The project is a basic "hello world" project (one view, one
> > > label).
> > > >> > The js-output folder name has no spaces in it.
> > > >> >
> > > >> > Note that when *adding" the -js-output parameter and
> validating
> > > the
> > > >> > dialog, I get a "realtime error processor" from FB. After
> > > >> > closing and restrarting FB, that error disappears, but it
> > > >> > clearly shows that some active process get lost in the dark...
> > > >> > I suspect the active
> > > >> "realtime"
> > > >> > process is code-assist.
> > > >> >
> > > >> > Is it possible that the handling of this argument changes
> > > something
> > > >> > inside the internal paths used by FB for the current project
> ???
> > > >> Maybe
> > > >> > it is just a matter of "restoring" the changed values after
> the
> > > >> > compiler runs ???
> > > >> >
> > > >> > And while I am at it, what are the *current* (0.9) values for
> -
> > > >> targets
> > > >> > argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex
> > > >> > ???)
> > > >> >
> > > >> > Nicolas Granon
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >> --
> > > >>
> > > >> Piotr Zarzycki
> > > >>
> > > >> mobile: +48 880 859 557
> > > >> skype: zarzycki10
> > > >>
> > > >> LinkedIn:
> > >
> >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fww
> > > >>w.l
> > > i
> > > >>nke
> > >
> >>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Caa45f87d335d49441da608d5
> > > >>22c
> > > b
> > > >>958
> > >
> >>7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140754807&
> > > >>sda
> > > t
> > > >>a=u
> > > >>7DZ4xxyJZls0CwbS8Tx6sI3uDn5p26h4c99xv4vuTk%3D&reserved=0
> > > >>
> > >
> >><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.
> > > l
> > > >>ink
> > > >>edin.com%2Fin%2Fpiotr-zarzycki-
> > > 92a53552&data=02%7C01%7C%7Caa45f87d335d
> > > >>494
> > >
> >>41da608d522cb9587%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636
> > > >>453
> > > 1
> > > >>801
> > >
> >>40911063&sdata=FEbuvYXGHKlY4nXGjXgo4t7W4HwKtdM9A7gMHfxM%2BKU%3D&re
> > > >>ser
> > > v
> > > >>ed=
> > > >>0>
> > > >>
> > > >> GitHub:
> > >
> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
> > > >>ith
> > > u
> > > >>b.c
> > >
> >>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Caa45f87d335d49441da608d522c
> > > >>b95
> > > 8
> > > >>7%7
> > >
> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140911063&sda
> > > >>ta=
> > > G
> > > >>TnQ
> > > >>7nenut8qnMUFTbA53QR6nVmRXsdpvPlb0D%2FSqtU%3D&reserved=0
> > > >
> >
> >
> >
Re: FB : Strange side effects of -js-output argument
Posted by Piotr Zarzycki <pi...@gmail.com>.
Nicolas,
Try to write exactly as I provide you -targets=JSRoyale or
-compiler.targets=JSRoyale
Piotr
On Fri, Nov 3, 2017, 23:34 Idylog - Nicolas Granon <ng...@idylog.com>
wrote:
> Even more :
>
> When you add *any* royale argument to the "compiler arguments" dialog, it
> breaks code-assist !!
>
> I just added -targets=jsroyale to the compiler arguments (no -js-output
> argument) and it also breaks code-assist !!!
> (moreover, it does not seem to work : the swf is output as well..)
>
> Something out there really needs a fix...
>
> Nicolas Granon
>
>
>
> > -----Message d'origine-----
> > De : Alex Harui [mailto:aharui@adobe.com.INVALID]
> > Envoyé : vendredi 3 novembre 2017 18:01
> > À : dev@royale.apache.org; ngranon@idylog.com
> > Objet : Re: FB : Strange side effects of -js-output argument
> >
> > Yeah, I noticed that too. I think FB is running its own compiler for
> > code-assist and new compiler options break that internal compiler. I'm
> > planning to dig into it more next week. It might be that some compiler
> > options have to be specified inside -config.xml files.
> >
> > -Alex
> >
> > On 11/3/17, 7:59 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
> > wrote:
> >
> > >Ok, thanks.
> > >
> > >Nicolas Granon
> > >
> > >
> > >
> > >
> > >> -----Message d'origine-----
> > >> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
> > >> Envoyé : vendredi 3 novembre 2017 15:40 À : dev@royale.apache.org
> > >> Objet : Re: FB : Strange side effects of -js-output argument
> > >>
> > >> Hi Nicolas,
> > >>
> > >> Current compiler targets is "JSRoyale" for JS only output.
> > >>
> > >> Piotr
> > >>
> > >>
> > >> 2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon
> > >> <ng...@idylog.com>:
> > >>
> > >> > (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9 binaries)
> > >> >
> > >> > In some of my previous posts, I have tried to explain how to setup
> > >> > FB and also the problems I got with code-assist (auto-complete)
> > not
> > >> > working properly.
> > >> > I also suggested a "working" setup of FB.
> > >> >
> > >> > Now, I have a *very* strange issue :
> > >> >
> > >> > If I add "-js-output=somepath" to the compiler arguments (from
> > >> > "Project > Properties > Flex compiler" tab), code-assist is lost
> > !!!!
> > >> > (almost entirely). (side note : the project compiles without
> > >> > errors, and output is in fact directed to (somepath)).
> > >> >
> > >> > If I remove the argument, code-assist is back ! (of course, output
> > >> > is directed to the bin/js-debug inside the project folder as it
> > >> > should)
> > >> >
> > >> > My flex-config.xml is the one that ships with the binaries
> > >> distribution.
> > >> >
> > >> > The project is a basic "hello world" project (one view, one
> > label).
> > >> > The js-output folder name has no spaces in it.
> > >> >
> > >> > Note that when *adding" the -js-output parameter and validating
> > the
> > >> > dialog, I get a "realtime error processor" from FB. After closing
> > >> > and restrarting FB, that error disappears, but it clearly shows
> > >> > that some active process get lost in the dark... I suspect the
> > >> > active
> > >> "realtime"
> > >> > process is code-assist.
> > >> >
> > >> > Is it possible that the handling of this argument changes
> > something
> > >> > inside the internal paths used by FB for the current project ???
> > >> Maybe
> > >> > it is just a matter of "restoring" the changed values after the
> > >> > compiler runs ???
> > >> >
> > >> > And while I am at it, what are the *current* (0.9) values for -
> > >> targets
> > >> > argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex ???)
> > >> >
> > >> > Nicolas Granon
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >>
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> mobile: +48 880 859 557
> > >> skype: zarzycki10
> > >>
> > >> LinkedIn:
> > >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.l
> > i
> > >>nke
> > >>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Caa45f87d335d49441da608d522c
> > b
> > >>958
> > >>7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140754807&sda
> > t
> > >>a=u
> > >>7DZ4xxyJZls0CwbS8Tx6sI3uDn5p26h4c99xv4vuTk%3D&reserved=0
> > >>
> > >><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.
> > l
> > >>ink
> > >>edin.com%2Fin%2Fpiotr-zarzycki-
> > 92a53552&data=02%7C01%7C%7Caa45f87d335d
> > >>494
> > >>41da608d522cb9587%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453
> > 1
> > >>801
> > >>40911063&sdata=FEbuvYXGHKlY4nXGjXgo4t7W4HwKtdM9A7gMHfxM%2BKU%3D&reser
> > v
> > >>ed=
> > >>0>
> > >>
> > >> GitHub:
> > >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> > u
> > >>b.c
> > >>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Caa45f87d335d49441da608d522cb95
> > 8
> > >>7%7
> > >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140911063&sdata=
> > G
> > >>TnQ
> > >>7nenut8qnMUFTbA53QR6nVmRXsdpvPlb0D%2FSqtU%3D&reserved=0
> > >
>
>
>
RE: FB : Strange side effects of -js-output argument
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
Even more :
When you add *any* royale argument to the "compiler arguments" dialog, it breaks code-assist !!
I just added -targets=jsroyale to the compiler arguments (no -js-output argument) and it also breaks code-assist !!!
(moreover, it does not seem to work : the swf is output as well..)
Something out there really needs a fix...
Nicolas Granon
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com.INVALID]
> Envoyé : vendredi 3 novembre 2017 18:01
> À : dev@royale.apache.org; ngranon@idylog.com
> Objet : Re: FB : Strange side effects of -js-output argument
>
> Yeah, I noticed that too. I think FB is running its own compiler for
> code-assist and new compiler options break that internal compiler. I'm
> planning to dig into it more next week. It might be that some compiler
> options have to be specified inside -config.xml files.
>
> -Alex
>
> On 11/3/17, 7:59 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
> wrote:
>
> >Ok, thanks.
> >
> >Nicolas Granon
> >
> >
> >
> >
> >> -----Message d'origine-----
> >> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
> >> Envoyé : vendredi 3 novembre 2017 15:40 À : dev@royale.apache.org
> >> Objet : Re: FB : Strange side effects of -js-output argument
> >>
> >> Hi Nicolas,
> >>
> >> Current compiler targets is "JSRoyale" for JS only output.
> >>
> >> Piotr
> >>
> >>
> >> 2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon
> >> <ng...@idylog.com>:
> >>
> >> > (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9 binaries)
> >> >
> >> > In some of my previous posts, I have tried to explain how to setup
> >> > FB and also the problems I got with code-assist (auto-complete)
> not
> >> > working properly.
> >> > I also suggested a "working" setup of FB.
> >> >
> >> > Now, I have a *very* strange issue :
> >> >
> >> > If I add "-js-output=somepath" to the compiler arguments (from
> >> > "Project > Properties > Flex compiler" tab), code-assist is lost
> !!!!
> >> > (almost entirely). (side note : the project compiles without
> >> > errors, and output is in fact directed to (somepath)).
> >> >
> >> > If I remove the argument, code-assist is back ! (of course, output
> >> > is directed to the bin/js-debug inside the project folder as it
> >> > should)
> >> >
> >> > My flex-config.xml is the one that ships with the binaries
> >> distribution.
> >> >
> >> > The project is a basic "hello world" project (one view, one
> label).
> >> > The js-output folder name has no spaces in it.
> >> >
> >> > Note that when *adding" the -js-output parameter and validating
> the
> >> > dialog, I get a "realtime error processor" from FB. After closing
> >> > and restrarting FB, that error disappears, but it clearly shows
> >> > that some active process get lost in the dark... I suspect the
> >> > active
> >> "realtime"
> >> > process is code-assist.
> >> >
> >> > Is it possible that the handling of this argument changes
> something
> >> > inside the internal paths used by FB for the current project ???
> >> Maybe
> >> > it is just a matter of "restoring" the changed values after the
> >> > compiler runs ???
> >> >
> >> > And while I am at it, what are the *current* (0.9) values for -
> >> targets
> >> > argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex ???)
> >> >
> >> > Nicolas Granon
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> mobile: +48 880 859 557
> >> skype: zarzycki10
> >>
> >> LinkedIn:
> >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.l
> i
> >>nke
> >>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Caa45f87d335d49441da608d522c
> b
> >>958
> >>7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140754807&sda
> t
> >>a=u
> >>7DZ4xxyJZls0CwbS8Tx6sI3uDn5p26h4c99xv4vuTk%3D&reserved=0
> >>
> >><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.
> l
> >>ink
> >>edin.com%2Fin%2Fpiotr-zarzycki-
> 92a53552&data=02%7C01%7C%7Caa45f87d335d
> >>494
> >>41da608d522cb9587%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453
> 1
> >>801
> >>40911063&sdata=FEbuvYXGHKlY4nXGjXgo4t7W4HwKtdM9A7gMHfxM%2BKU%3D&reser
> v
> >>ed=
> >>0>
> >>
> >> GitHub:
> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> u
> >>b.c
> >>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Caa45f87d335d49441da608d522cb95
> 8
> >>7%7
> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140911063&sdata=
> G
> >>TnQ
> >>7nenut8qnMUFTbA53QR6nVmRXsdpvPlb0D%2FSqtU%3D&reserved=0
> >
Re: FB : Strange side effects of -js-output argument
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Yeah, I noticed that too. I think FB is running its own compiler for
code-assist and new compiler options break that internal compiler. I'm
planning to dig into it more next week. It might be that some compiler
options have to be specified inside -config.xml files.
-Alex
On 11/3/17, 7:59 AM, "Idylog - Nicolas Granon" <ng...@idylog.com> wrote:
>Ok, thanks.
>
>Nicolas Granon
>
>
>
>
>> -----Message d'origine-----
>> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
>> Envoyé : vendredi 3 novembre 2017 15:40
>> À : dev@royale.apache.org
>> Objet : Re: FB : Strange side effects of -js-output argument
>>
>> Hi Nicolas,
>>
>> Current compiler targets is "JSRoyale" for JS only output.
>>
>> Piotr
>>
>>
>> 2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon
>> <ng...@idylog.com>:
>>
>> > (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9 binaries)
>> >
>> > In some of my previous posts, I have tried to explain how to setup FB
>> > and also the problems I got with code-assist (auto-complete) not
>> > working properly.
>> > I also suggested a "working" setup of FB.
>> >
>> > Now, I have a *very* strange issue :
>> >
>> > If I add "-js-output=somepath" to the compiler arguments (from
>> > "Project > Properties > Flex compiler" tab), code-assist is lost !!!!
>> > (almost entirely). (side note : the project compiles without errors,
>> > and output is in fact directed to (somepath)).
>> >
>> > If I remove the argument, code-assist is back ! (of course, output is
>> > directed to the bin/js-debug inside the project folder as it should)
>> >
>> > My flex-config.xml is the one that ships with the binaries
>> distribution.
>> >
>> > The project is a basic "hello world" project (one view, one label).
>> > The js-output folder name has no spaces in it.
>> >
>> > Note that when *adding" the -js-output parameter and validating the
>> > dialog, I get a "realtime error processor" from FB. After closing and
>> > restrarting FB, that error disappears, but it clearly shows that some
>> > active process get lost in the dark... I suspect the active
>> "realtime"
>> > process is code-assist.
>> >
>> > Is it possible that the handling of this argument changes something
>> > inside the internal paths used by FB for the current project ???
>> Maybe
>> > it is just a matter of "restoring" the changed values after the
>> > compiler runs ???
>> >
>> > And while I am at it, what are the *current* (0.9) values for -
>> targets
>> > argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex ???)
>> >
>> > Nicolas Granon
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> mobile: +48 880 859 557
>> skype: zarzycki10
>>
>> LinkedIn:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linke
>>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Caa45f87d335d49441da608d522cb958
>>7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140754807&sdata=u
>>7DZ4xxyJZls0CwbS8Tx6sI3uDn5p26h4c99xv4vuTk%3D&reserved=0
>>
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.link
>>edin.com%2Fin%2Fpiotr-zarzycki-92a53552&data=02%7C01%7C%7Caa45f87d335d494
>>41da608d522cb9587%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364531801
>>40911063&sdata=FEbuvYXGHKlY4nXGjXgo4t7W4HwKtdM9A7gMHfxM%2BKU%3D&reserved=
>>0>
>>
>> GitHub:
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Caa45f87d335d49441da608d522cb9587%7
>>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453180140911063&sdata=GTnQ
>>7nenut8qnMUFTbA53QR6nVmRXsdpvPlb0D%2FSqtU%3D&reserved=0
>
RE: FB : Strange side effects of -js-output argument
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
Ok, thanks.
Nicolas Granon
> -----Message d'origine-----
> De : Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com]
> Envoyé : vendredi 3 novembre 2017 15:40
> À : dev@royale.apache.org
> Objet : Re: FB : Strange side effects of -js-output argument
>
> Hi Nicolas,
>
> Current compiler targets is "JSRoyale" for JS only output.
>
> Piotr
>
>
> 2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon
> <ng...@idylog.com>:
>
> > (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9 binaries)
> >
> > In some of my previous posts, I have tried to explain how to setup FB
> > and also the problems I got with code-assist (auto-complete) not
> > working properly.
> > I also suggested a "working" setup of FB.
> >
> > Now, I have a *very* strange issue :
> >
> > If I add "-js-output=somepath" to the compiler arguments (from
> > "Project > Properties > Flex compiler" tab), code-assist is lost !!!!
> > (almost entirely). (side note : the project compiles without errors,
> > and output is in fact directed to (somepath)).
> >
> > If I remove the argument, code-assist is back ! (of course, output is
> > directed to the bin/js-debug inside the project folder as it should)
> >
> > My flex-config.xml is the one that ships with the binaries
> distribution.
> >
> > The project is a basic "hello world" project (one view, one label).
> > The js-output folder name has no spaces in it.
> >
> > Note that when *adding" the -js-output parameter and validating the
> > dialog, I get a "realtime error processor" from FB. After closing and
> > restrarting FB, that error disappears, but it clearly shows that some
> > active process get lost in the dark... I suspect the active
> "realtime"
> > process is code-assist.
> >
> > Is it possible that the handling of this argument changes something
> > inside the internal paths used by FB for the current project ???
> Maybe
> > it is just a matter of "restoring" the changed values after the
> > compiler runs ???
> >
> > And while I am at it, what are the *current* (0.9) values for -
> targets
> > argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex ???)
> >
> > Nicolas Granon
> >
> >
> >
> >
> >
> >
>
>
> --
>
> Piotr Zarzycki
>
> mobile: +48 880 859 557
> skype: zarzycki10
>
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> <https://pl.linkedin.com/in/piotr-zarzycki-92a53552>
>
> GitHub: https://github.com/piotrzarzycki21
Re: FB : Strange side effects of -js-output argument
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Nicolas,
Current compiler targets is "JSRoyale" for JS only output.
Piotr
2017-11-03 15:30 GMT+01:00 Idylog - Nicolas Granon <ng...@idylog.com>:
> (my setup : FlashBuilder 4.7, Windows, Apache Royale 0.9 binaries)
>
> In some of my previous posts, I have tried to explain how to setup FB and
> also the problems I got with code-assist (auto-complete) not working
> properly.
> I also suggested a "working" setup of FB.
>
> Now, I have a *very* strange issue :
>
> If I add "-js-output=somepath" to the compiler arguments (from "Project >
> Properties > Flex compiler" tab), code-assist is lost !!!! (almost
> entirely). (side note : the project compiles without errors, and output is
> in fact directed to (somepath)).
>
> If I remove the argument, code-assist is back ! (of course, output is
> directed to the bin/js-debug inside the project folder as it should)
>
> My flex-config.xml is the one that ships with the binaries distribution.
>
> The project is a basic "hello world" project (one view, one label).
> The js-output folder name has no spaces in it.
>
> Note that when *adding" the -js-output parameter and validating the dialog,
> I get a "realtime error processor" from FB. After closing and restrarting
> FB, that error disappears, but it clearly shows that some active process
> get
> lost in the dark... I suspect the active "realtime" process is code-assist.
>
> Is it possible that the handling of this argument changes something inside
> the internal paths used by FB for the current project ??? Maybe it is just
> a
> matter of "restoring" the changed values after the compiler runs ???
>
> And while I am at it, what are the *current* (0.9) values for -targets
> argument for js output ? (JS ? RoyaleJS ? JSRoyale ? JSFlex ???)
>
> Nicolas Granon
>
>
>
>
>
>
--
Piotr Zarzycki
mobile: +48 880 859 557
skype: zarzycki10
LinkedIn: http://www.linkedin.com/piotrzarzycki
<https://pl.linkedin.com/in/piotr-zarzycki-92a53552>
GitHub: https://github.com/piotrzarzycki21