Re: Language improvements

2019-06-03 Thread Greg Dove
Hi Alex, this will be my last message in this thread.

"The whole point of giving choices is to avoid having to spend so many
emails trying to reach a decision.  "
Alex, I really don't understand your stance. The focus of the recent
discussion has been on the choices themselves... concerns about their
potential risks, along with ideas for improvements and code quality.
It sounds like you are saying that we can't talk about improving the
choices we already had, because if they exist that is all that matters.
As far as I understand, the point of these email discussions is to reach
the best quality collaborative decisions.
I don't enjoy the process myself. It's inefficient. But we have an
obligation to be collaborative (I think?). Expressing something along the
lines of 'just do it and move on' does not seem to be that.
I don't care about any of these things in terms of how it affects me
personally, I have only pursued the topic in relation to what I think will
help Royale be successful.

The only way I can interpret your replies thus far is:
More options for optimization are always better, even if they might present
possible risks that could harm the community. We deal with those risks by
issuing warnings.
Specifically, in this case, a library developer being able to dictate
certain optimization(s) that should be used by (and any associated risks
that should be accepted by) the application developer is not unacceptable.

-Your approach to mitigation of the above risks will be for us to warn
people not to do the specific things that could cause the problems in the
first place (from your comment about tools, risks, and documentation).
Something like:
'Don't use any emulation classes in library code unless your emulation
class is Array, and if it is Array, don't expose the Vector type on any
public or protected api surface because it will be a misleading
representation of the type to the user of that api'

Is that a fair summary?

It should be not surprise to you that I personally think the above is
confusing and avoidable, because I consider that there are (and will be)
better options that achieve the same optimization results. But I understand
that you don't, and I can accept that. So I will make one last attempt to
find something that I think is middle ground...

Vector-as-Array is just a special case of the emulationClass approach.
The only middle ground I can think of with regard to reducing the risk is
to have the 'emulationClass' approach is to actually re-map the type in the
javascript output, so the swc typing actually represents the type it has
been transformed to.
This means if people don't follow the above instructions and the type is
exposed on an api surface then it is not misrepresented to unsuspecting
users via the swc that has the optimization. Does that make any sense?
I have no idea at this point if this is easy to do or not. But it would
address the main things that worry me about this (again, not for me, for
royale in general). I only got to this idea out of frustration, although
perhaps it could be considered obvious in retrospect.
I'm not able to tackle this in the near term but I will be happy to pursue
it at some point if you can agree it is a good compromise ( I hope it might
be). As I said, I won't continue any more in this thread. If you like it
please let me know, otherwise I officially give up.

For now, I will try to find time to add the Vector-as-Array back in
sometime later this week. I will do it inside the vectorEmulationClass code
branches in the compiler as a special case of ' vectorEmulationClass '.
Once I have that done and working I will merge.


On Sat, Jun 1, 2019 at 8:26 AM Alex Harui  wrote:

> Greg, you are still trying to use the language conformance argument.  This
> is not an issue of language conformance, it is an issue of optimization.
> Code paths not needed should not be downloaded.  Every app development tool
> I've used that offers optimizations offers optimization levels and
> documentation of risks.
>
> There is a disagreement on how to implement Vector in JS as well.  The
> whole point of giving choices is to avoid having to spend so many emails
> trying to reach a decision.  Just provide choices so we can move on.  Every
> argument you make below is an argument for giving choices.
>
> -Alex
>
> On 5/30/19, 9:03 PM, "Greg Dove"  wrote:
>
> "And so we will stop using Vector and migrate to using a plain Array.
> That
> agreement proves that the proposed changes are not right."  We will
> effectively encourage others to do the same.
>
> It does not prove that at all, Alex. It depends on the criteria, and we
> have no commonly accepted guiding principles for what is 'right' here.
> At least one of us believes that it is more correct that (in the
> absence of
> other proposed options) it be an Array in the original code.
> If you take a step back and look at it from a broader perspective, it
> can
> be equally true to say '

Build failed in Jenkins: royale-asjs_jsonly #3050

2019-06-03 Thread Apache Royale CI Server
See 


--
[...truncated 2.12 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


Build failed in Jenkins: royale-asjs_jsonly #3049

2019-06-03 Thread Apache Royale CI Server
See 


--
[...truncated 2.12 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


Build failed in Jenkins: royale-asjs_jsonly #3048

2019-06-03 Thread Apache Royale CI Server
See 


Changes:

[noreply] Update README.txt

--
[...truncated 2.12 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Carlos Rovira
Hi Jude!

El lun., 3 jun. 2019 a las 22:32, QA () escribió:

> Great job! :) I have a few comments:
>

thanks!


>
> In the introduction I would add at the end, "It also allows an IDE to
> provide code completion, type checking, etc." You mention the advantages
> later in the post.
>
>
added! :)


> />Note: Currently the inject_html injection only works if your @externs
> class is located in a Royale library. It will not work if is located in
> the application project./
>
> Does that mean my externs class in my project directory, src, will work
> but it cannot add html to the template? Do I need to move my AS class
> somewhere else, or manually add the script tags to my template or is
> this a temporary issue that will be fixed in the future?
>

I think this is a temporary issue that will be fixed sometime. I asked for
help
so I can know where I could look to fix it, since it's not clear to me.
Maybe others like Alex or Josh could give a hand here or take directly a
look.


>
> In the example, the *hljs* class is not declared locally in the project
> because it is declared already in Royale. Does that mean it is available
> via code hinting automatically?
>

Is available in Jewel, so if you have Jewel added (that use to be since is
an official Royale lib)
you'll have it.


>
> When I create my extern classes for my own project where do I put them?
>

in a library project, like a did in jewel library project


>
> What is the code component? Does that a code tag?
>

I don't understand that question... the code of hljs.as is posted in the
example text.
and for code tag, it can't be used that way since it doesn't implement the
IMXMLDocument interface
you need to make a component that support that feature.


>
> Is it possible in the example code you use to remove the large comment
> at the top? :)
>

I prefer not to do it since is official Royale project, and it's been
shared there as is, so
I think I should not do it, sorry :(

Thanks! :)


>
> Jude
>
> On 6/3/19 1:25 PM, Carlos Rovira wrote:
> > Hi Andrew!
> >
> > just finished the last blog example, could you please take a look and fix
> > whatever aggression against the English language that may have been
> > committed? :)
> >
> >
> https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/
> >
> > To the rest of folks: please let me know if you thing something is wrong
> or
> > must be modified in some way.
> >
> > thanks in advance
> >
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira


Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread QA

Great job! :) I have a few comments:

In the introduction I would add at the end, "It also allows an IDE to 
provide code completion, type checking, etc." You mention the advantages 
later in the post.


/>Note: Currently the inject_html injection only works if your @externs 
class is located in a Royale library. It will not work if is located in 
the application project./


Does that mean my externs class in my project directory, src, will work 
but it cannot add html to the template? Do I need to move my AS class 
somewhere else, or manually add the script tags to my template or is 
this a temporary issue that will be fixed in the future?


In the example, the *hljs* class is not declared locally in the project 
because it is declared already in Royale. Does that mean it is available 
via code hinting automatically?


When I create my extern classes for my own project where do I put them?

What is the code component? Does that a code tag?

Is it possible in the example code you use to remove the large comment 
at the top? :)


Jude

On 6/3/19 1:25 PM, Carlos Rovira wrote:

Hi Andrew!

just finished the last blog example, could you please take a look and fix
whatever aggression against the English language that may have been
committed? :)

https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/

To the rest of folks: please let me know if you thing something is wrong or
must be modified in some way.

thanks in advance




Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Kenny Lerma
Thank you Josh, that's just the information I was looking for.  I'm getting
away with currently because I'm using "WHITESPACE_ONLY" currently, so no
re-naming.

I'm using WHITESPACE_ONLY since I'm loading multiple different apps at
runtime that share the same base code in a separate JS file.  Basically,
just like loading swf files at runtime only with JS files instead.

Kenny

On Mon, Jun 3, 2019 at 3:00 PM Josh Tynjala  wrote:

> COMPILE::JS should not be necessary, but if you're targeting JS, you
> should add the doc comment with the @externs tag. By default, Royale uses
> the Google Closure compiler, which aggressively renames properties and
> methods to make the generated code smaller. The @externs tag tells it not
> to rename any of the APIs on that particular class. If you have an external
> JS library included with 

Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Josh Tynjala
COMPILE::JS should not be necessary, but if you're targeting JS, you should add 
the doc comment with the @externs tag. By default, Royale uses the Google 
Closure compiler, which aggressively renames properties and methods to make the 
generated code smaller. The @externs tag tells it not to rename any of the APIs 
on that particular class. If you have an external JS library included with 

Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Carlos Rovira
Great Andrew!

Many thanks, I'll be pushing to public in the next hours or so. :)

El lun., 3 jun. 2019 a las 20:40, Andrew Wetmore ()
escribió:

> @Carlos Rovira   I have updated the blog entry
> with a few teeny tiny corrections. It seems very clear, and is a useful
> guide!
>
> On Mon, Jun 3, 2019 at 3:19 PM Kenny Lerma  wrote:
>
>> Thank Piotr.  I am only working with JS so that makes sense.  I just
>> wanted
>> to make sure I didn't need to add these for some other reason.
>>
>> Thanks,
>> Kenny
>>
>> On Mon, Jun 3, 2019 at 1:07 PM Piotr Zarzycki 
>> wrote:
>>
>> > Hi Kenny,
>> >
>> > I think it may not be necessary in your app when you build to JS only.
>> >
>> > If there is any different type of compilation - now to swf - you need to
>> > surround your JS related code with COMPILE::JS
>> >
>> > Thanks,
>> > Piotr
>> >
>> >
>> > On Mon, Jun 3, 2019, 7:37 PM Kenny Lerma  wrote:
>> >
>> > > Looking at the demo, I noticed you added @externs and COMPILE::JS?  Is
>> > this
>> > > necessary?
>> > > I'm just curious since the ActionsScript I've done for creating
>> external
>> > JS
>> > > code completion and SWC files too, I'm not adding these.
>> > >
>> > > Kenny
>> > >
>> > > On Mon, Jun 3, 2019 at 12:25 PM Carlos Rovira <
>> carlosrov...@apache.org>
>> > > wrote:
>> > >
>> > > > Hi Andrew!
>> > > >
>> > > > just finished the last blog example, could you please take a look
>> and
>> > fix
>> > > > whatever aggression against the English language that may have been
>> > > > committed? :)
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/
>> > > >
>> > > > To the rest of folks: please let me know if you thing something is
>> > wrong
>> > > or
>> > > > must be modified in some way.
>> > > >
>> > > > thanks in advance
>> > > >
>> > > >
>> > > > --
>> > > > Carlos Rovira
>> > > > http://about.me/carlosrovira
>> > > >
>> > >
>> >
>>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira


Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Andrew Wetmore
@Carlos Rovira   I have updated the blog entry
with a few teeny tiny corrections. It seems very clear, and is a useful
guide!

On Mon, Jun 3, 2019 at 3:19 PM Kenny Lerma  wrote:

> Thank Piotr.  I am only working with JS so that makes sense.  I just wanted
> to make sure I didn't need to add these for some other reason.
>
> Thanks,
> Kenny
>
> On Mon, Jun 3, 2019 at 1:07 PM Piotr Zarzycki 
> wrote:
>
> > Hi Kenny,
> >
> > I think it may not be necessary in your app when you build to JS only.
> >
> > If there is any different type of compilation - now to swf - you need to
> > surround your JS related code with COMPILE::JS
> >
> > Thanks,
> > Piotr
> >
> >
> > On Mon, Jun 3, 2019, 7:37 PM Kenny Lerma  wrote:
> >
> > > Looking at the demo, I noticed you added @externs and COMPILE::JS?  Is
> > this
> > > necessary?
> > > I'm just curious since the ActionsScript I've done for creating
> external
> > JS
> > > code completion and SWC files too, I'm not adding these.
> > >
> > > Kenny
> > >
> > > On Mon, Jun 3, 2019 at 12:25 PM Carlos Rovira  >
> > > wrote:
> > >
> > > > Hi Andrew!
> > > >
> > > > just finished the last blog example, could you please take a look and
> > fix
> > > > whatever aggression against the English language that may have been
> > > > committed? :)
> > > >
> > > >
> > > >
> > >
> >
> https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/
> > > >
> > > > To the rest of folks: please let me know if you thing something is
> > wrong
> > > or
> > > > must be modified in some way.
> > > >
> > > > thanks in advance
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Kenny Lerma
Thank Piotr.  I am only working with JS so that makes sense.  I just wanted
to make sure I didn't need to add these for some other reason.

Thanks,
Kenny

On Mon, Jun 3, 2019 at 1:07 PM Piotr Zarzycki 
wrote:

> Hi Kenny,
>
> I think it may not be necessary in your app when you build to JS only.
>
> If there is any different type of compilation - now to swf - you need to
> surround your JS related code with COMPILE::JS
>
> Thanks,
> Piotr
>
>
> On Mon, Jun 3, 2019, 7:37 PM Kenny Lerma  wrote:
>
> > Looking at the demo, I noticed you added @externs and COMPILE::JS?  Is
> this
> > necessary?
> > I'm just curious since the ActionsScript I've done for creating external
> JS
> > code completion and SWC files too, I'm not adding these.
> >
> > Kenny
> >
> > On Mon, Jun 3, 2019 at 12:25 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Andrew!
> > >
> > > just finished the last blog example, could you please take a look and
> fix
> > > whatever aggression against the English language that may have been
> > > committed? :)
> > >
> > >
> > >
> >
> https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/
> > >
> > > To the rest of folks: please let me know if you thing something is
> wrong
> > or
> > > must be modified in some way.
> > >
> > > thanks in advance
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>


Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Carlos Rovira
Hi Kenny,

I understand that you are not using "window" object, but you're talking
about "tags" in htjs.as. You refer to ?

ITOH, for example If I remove the stub as3 classes for hljs and
dialogPolyfill in Jewel library and try to compile I get this:

/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Jewel/src/main/royale/org/apache/royale/jewel/Alert.as(225):
col: 7 Access of possibly undefined property dialogPolyfill.


dialogPolyfill.registerDialog(dialog);

So in Alert.as this is failing:

if (!("showModal" in dialog))
{
dialogPolyfill.registerDialog(dialog); <- line
225
}





El lun., 3 jun. 2019 a las 20:07, Piotr Zarzycki ()
escribió:

> Hi Kenny,
>
> I think it may not be necessary in your app when you build to JS only.
>
> If there is any different type of compilation - now to swf - you need to
> surround your JS related code with COMPILE::JS
>
> Thanks,
> Piotr
>
>
> On Mon, Jun 3, 2019, 7:37 PM Kenny Lerma  wrote:
>
> > Looking at the demo, I noticed you added @externs and COMPILE::JS?  Is
> this
> > necessary?
> > I'm just curious since the ActionsScript I've done for creating external
> JS
> > code completion and SWC files too, I'm not adding these.
> >
> > Kenny
> >
> > On Mon, Jun 3, 2019 at 12:25 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Andrew!
> > >
> > > just finished the last blog example, could you please take a look and
> fix
> > > whatever aggression against the English language that may have been
> > > committed? :)
> > >
> > >
> > >
> >
> https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/
> > >
> > > To the rest of folks: please let me know if you thing something is
> wrong
> > or
> > > must be modified in some way.
> > >
> > > thanks in advance
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira


Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Piotr Zarzycki
Hi Kenny,

I think it may not be necessary in your app when you build to JS only.

If there is any different type of compilation - now to swf - you need to
surround your JS related code with COMPILE::JS

Thanks,
Piotr


On Mon, Jun 3, 2019, 7:37 PM Kenny Lerma  wrote:

> Looking at the demo, I noticed you added @externs and COMPILE::JS?  Is this
> necessary?
> I'm just curious since the ActionsScript I've done for creating external JS
> code completion and SWC files too, I'm not adding these.
>
> Kenny
>
> On Mon, Jun 3, 2019 at 12:25 PM Carlos Rovira 
> wrote:
>
> > Hi Andrew!
> >
> > just finished the last blog example, could you please take a look and fix
> > whatever aggression against the English language that may have been
> > committed? :)
> >
> >
> >
> https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/
> >
> > To the rest of folks: please let me know if you thing something is wrong
> or
> > must be modified in some way.
> >
> > thanks in advance
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Kenny Lerma
I was referencing the tags you are adding to the ActionScript class "hljs.as".
I personally never use the window[""] route.

I'm just wondering why you need those specific tags in you actionscript.  I
don't use those tags and it still works.

On Mon, Jun 3, 2019 at 12:49 PM Carlos Rovira 
wrote:

> Hi Kenny,
>
> I added two options:
>
> 1 .- through @externs
> 2 .- through bracket access.
>
> Maybe you're using 2 instead of 1?
> I was using that until now though windows js object, but I think is not
> what we want to expose or advertise in Apache Royale right?
>
> Please let me know, if I'm missing something, or there's more options that
> I'm not aware of. If that's the case, I can update the post to reflect
> that.
> If so please let me know some example so I can try it.
>
> thanks!
>
>
>
> El lun., 3 jun. 2019 a las 19:37, Kenny Lerma ()
> escribió:
>
> > Looking at the demo, I noticed you added @externs and COMPILE::JS?  Is
> this
> > necessary?
> > I'm just curious since the ActionsScript I've done for creating external
> JS
> > code completion and SWC files too, I'm not adding these.
> >
> > Kenny
> >
> > On Mon, Jun 3, 2019 at 12:25 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Andrew!
> > >
> > > just finished the last blog example, could you please take a look and
> fix
> > > whatever aggression against the English language that may have been
> > > committed? :)
> > >
> > >
> > >
> >
> https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/
> > >
> > > To the rest of folks: please let me know if you thing something is
> wrong
> > or
> > > must be modified in some way.
> > >
> > > thanks in advance
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Carlos Rovira
Hi Kenny,

I added two options:

1 .- through @externs
2 .- through bracket access.

Maybe you're using 2 instead of 1?
I was using that until now though windows js object, but I think is not
what we want to expose or advertise in Apache Royale right?

Please let me know, if I'm missing something, or there's more options that
I'm not aware of. If that's the case, I can update the post to reflect that.
If so please let me know some example so I can try it.

thanks!



El lun., 3 jun. 2019 a las 19:37, Kenny Lerma ()
escribió:

> Looking at the demo, I noticed you added @externs and COMPILE::JS?  Is this
> necessary?
> I'm just curious since the ActionsScript I've done for creating external JS
> code completion and SWC files too, I'm not adding these.
>
> Kenny
>
> On Mon, Jun 3, 2019 at 12:25 PM Carlos Rovira 
> wrote:
>
> > Hi Andrew!
> >
> > just finished the last blog example, could you please take a look and fix
> > whatever aggression against the English language that may have been
> > committed? :)
> >
> >
> >
> https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/
> >
> > To the rest of folks: please let me know if you thing something is wrong
> or
> > must be modified in some way.
> >
> > thanks in advance
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira


Re: Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Kenny Lerma
Looking at the demo, I noticed you added @externs and COMPILE::JS?  Is this
necessary?
I'm just curious since the ActionsScript I've done for creating external JS
code completion and SWC files too, I'm not adding these.

Kenny

On Mon, Jun 3, 2019 at 12:25 PM Carlos Rovira 
wrote:

> Hi Andrew!
>
> just finished the last blog example, could you please take a look and fix
> whatever aggression against the English language that may have been
> committed? :)
>
>
> https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/
>
> To the rest of folks: please let me know if you thing something is wrong or
> must be modified in some way.
>
> thanks in advance
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Last blog example: Using external javascript libraries in Apache Royale

2019-06-03 Thread Carlos Rovira
Hi Andrew!

just finished the last blog example, could you please take a look and fix
whatever aggression against the English language that may have been
committed? :)

https://royale.codeoscopic.com/using-external-javascript-libraries-in-apache-royale/

To the rest of folks: please let me know if you thing something is wrong or
must be modified in some way.

thanks in advance


-- 
Carlos Rovira
http://about.me/carlosrovira


Build failed in Jenkins: royale-asjs_jsonly #3040

2019-06-03 Thread Apache Royale CI Server
See 


Changes:

[carlosrovira] B012: simplifiy code adding binding

[carlosrovira] add hljs.as to Jewel

[carlosrovira] tourdejewel: remove HighlighCode and use new hljs code that 
injects the

[carlosrovira] B012: remove highlightcode and hljs classes and use new hljs 
@externs

--
[...truncated 2.12 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


Re: Using @extrens ( RE: Example of access external JS using Apache Royale)

2019-06-03 Thread Carlos Rovira
I put hljs.as class in a library, and in doing that hljs.as is
processed in GoogDepsWriter
and inject_html is pulled from that @externs class. This solve the problem
from that point.

So the real problem here is: If users has @externs classes in the
Application project, then they will get another processing different to
have this one in a library. And inject_html is not processed and, another
thing: source map file is generated when the externs class is in
Application project (while I removed creating in a recent commit).

Do you know some way to fix this problem in the best way?

thanks



El lun., 3 jun. 2019 a las 16:13, Carlos Rovira ()
escribió:

> Hi Alex,
>
> trying  to make inject_html work for @externs classes.
> I'm seeing that GoogDepsWriter are not processing hljs.as extern class in
> my B012 example, that is located directly in top level package.
> I output with println all getFileInfo() classes there and hljs is not part
> of that set. Maybe is only processing @extern classes inside libraries?
> in this case the @externs class is located in the Application project.
>
> I'm going to see if I can get it's processed in other part and try to read
> from there the inject_html
>
> Just want to inform since could be something by design or not wanted effect
>
> thanks
>
> Carlos
>
>
> El sáb., 4 may. 2019 a las 5:36, Alex Harui ()
> escribió:
>
>> I just searched the compiler code.  Current inject_html handling appears
>> to be in GoogDepsWriter.java.
>>
>> On 5/3/19, 2:04 PM, "Carlos Rovira"  wrote:
>>
>> Hi,
>>
>> I now Greg is busy now with an important update
>> I can try to do it myself if Alex point me to the code I should look,
>> for
>> me it would be part of the task to make this blog example in the best
>> way
>> possible.
>> thanks
>>
>> El vie., 3 may. 2019 a las 22:58, Greg Dove ()
>> escribió:
>>
>> > 'I'm pretty sure externs are not scanned for inject_html.
>> Volunteers are
>> > welcome to teach the compiler to do so.'
>> > I am happy to look into this sometime in the next few days. Just
>> trying to
>> > finish up something else first...
>> >
>> >
>> >
>> > On Sat, May 4, 2019 at 8:54 AM Alex Harui > >
>> > wrote:
>> >
>> > > Hi Carlos,
>> > >
>> > > I'm pretty sure externs are not scanned for inject_html.
>> Volunteers are
>> > > welcome to teach the compiler to do so.
>> > >
>> > > -Alex
>> > >
>> > > On 5/3/19, 1:50 PM, "Carlos Rovira" 
>> wrote:
>> > >
>> > > Hi,
>> > >
>> > > while putting the pieces together for the blog example I'm
>> finding
>> > the
>> > > following.
>> > >
>> > > For classes that wraps a js code that is an intrinsic file
>> needed to
>> > > make
>> > > the code function I think inject_html should work but I'm
>> trying it
>> > and
>> > > seems this is not working. The code is like this:
>> > >
>> > > package
>> > > {
>> > > /**
>> > >  * @externs
>> > >  */
>> > > public class hljs
>> > > {
>> > > /**
>> > >  * 
>> > >  * https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fhighlight.js%2F9.12.0%2Fhighlight.min.js&data=02%7C01%7Caharui%40adobe.com%7C922752ecb7bf4513718208d6d00ae5fb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636925142602102439&sdata=ubvldliTsViH69h%2FGeKby02C8H%2BKJ7HtblUo7dCnbrk%3D&reserved=0
>> > > ">
>> > > * https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fhighlight.js%2F9.12.0%2Fstyles%2Fatom-one-dark.min.css&data=02%7C01%7Caharui%40adobe.com%7C922752ecb7bf4513718208d6d00ae5fb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636925142602102439&sdata=uBI0vW721xJqBH2I%2FuUrq92KIu2Vgf6YzcrOXEFGLHM%3D&reserved=0
>> > > ">
>> > >  * 
>> > >  */
>> > > public function hljs()
>> > > {
>> > > }
>> > >
>> > > public static function
>> highlightBlock(block:Element):void {}
>> > > }
>> > > }
>> > >
>> > > So instead of add the inject_html in the code that calls the
>> methods
>> > in
>> > > this step, I think it should  be here
>> > >
>> > > Make this sense?
>> > >
>> > >
>> > >
>> > > El vie., 3 may. 2019 a las 9:38, Carlos Rovira (<
>> > > carlosrov...@apache.org>)
>> > > escribió:
>> > >
>> > > > Hi Alex,
>> > > >
>> > > > for me is difficult right now think about what would be
>> better for
>> > > > TypeScript. I think all will depend on how people interact
>> in the
>> > > following
>> > > > months/years to show us what't the best for Royale in the
>> long
>> > term.
>

Re: VSCode, Moonshine, go_to_definition_help

2019-06-03 Thread Josh Tynjala
VScode and Moonshine use go_to_definition_help, and I've observed it doesn't 
always go to the correct location. I knew it had something to do with line 
endings, but I never quite figured out exactly what was wrong. You're changes 
probably won't make anything worse.

> if you pull up an AS source file packaged with Flash Builder in Notepad on 
> Windows it is unreadable

It is worth mentioning that Notepad in Windows 10 has recently been updated to 
support files with Unix line endings.

- Josh

On 2019/06/02 14:56:38, Alex Harui  wrote: 
> Folks working on the newer IDEs:
> 
> I discovered that Royale is building SWCs a bit differently than Flex 
> apparently did.  It appears that Flex assumed source code always had Unix 
> line-endings (just LF, not CRLF as on Windows) and thus that the 
> go_to_definition_help metadata in the SWCs (that is supposedly there for 
> code-intelligence) was set accordingly.
> 
> I am going to make the same changes for Royale.  I will probably just enable 
> those changes if I know we are building release artifacts unless folks think 
> it doesn't matter.  But these changes may affect how the 
> go_to_definition_help offsets on Windows match up against the source code.  
> It looks like Adobe Flash Builder packaged the source code with Unix 
> line-endings so it would match the go_to_definition_help metadata but if you 
> pull up an AS source file packaged with Flash Builder in Notepad on Windows 
> it is unreadable.  Flash Builder itself is smart enough to handle Unix 
> line-endings in source on Windows.
> 
> Thoughts?
> -Alex
> 
> 


Re: Using @extrens ( RE: Example of access external JS using Apache Royale)

2019-06-03 Thread Carlos Rovira
Hi Alex,

trying  to make inject_html work for @externs classes.
I'm seeing that GoogDepsWriter are not processing hljs.as extern class in
my B012 example, that is located directly in top level package.
I output with println all getFileInfo() classes there and hljs is not part
of that set. Maybe is only processing @extern classes inside libraries?
in this case the @externs class is located in the Application project.

I'm going to see if I can get it's processed in other part and try to read
from there the inject_html

Just want to inform since could be something by design or not wanted effect

thanks

Carlos


El sáb., 4 may. 2019 a las 5:36, Alex Harui ()
escribió:

> I just searched the compiler code.  Current inject_html handling appears
> to be in GoogDepsWriter.java.
>
> On 5/3/19, 2:04 PM, "Carlos Rovira"  wrote:
>
> Hi,
>
> I now Greg is busy now with an important update
> I can try to do it myself if Alex point me to the code I should look,
> for
> me it would be part of the task to make this blog example in the best
> way
> possible.
> thanks
>
> El vie., 3 may. 2019 a las 22:58, Greg Dove ()
> escribió:
>
> > 'I'm pretty sure externs are not scanned for inject_html.
> Volunteers are
> > welcome to teach the compiler to do so.'
> > I am happy to look into this sometime in the next few days. Just
> trying to
> > finish up something else first...
> >
> >
> >
> > On Sat, May 4, 2019 at 8:54 AM Alex Harui 
> > wrote:
> >
> > > Hi Carlos,
> > >
> > > I'm pretty sure externs are not scanned for inject_html.
> Volunteers are
> > > welcome to teach the compiler to do so.
> > >
> > > -Alex
> > >
> > > On 5/3/19, 1:50 PM, "Carlos Rovira" 
> wrote:
> > >
> > > Hi,
> > >
> > > while putting the pieces together for the blog example I'm
> finding
> > the
> > > following.
> > >
> > > For classes that wraps a js code that is an intrinsic file
> needed to
> > > make
> > > the code function I think inject_html should work but I'm
> trying it
> > and
> > > seems this is not working. The code is like this:
> > >
> > > package
> > > {
> > > /**
> > >  * @externs
> > >  */
> > > public class hljs
> > > {
> > > /**
> > >  * 
> > >  * https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fhighlight.js%2F9.12.0%2Fhighlight.min.js&data=02%7C01%7Caharui%40adobe.com%7C922752ecb7bf4513718208d6d00ae5fb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636925142602102439&sdata=ubvldliTsViH69h%2FGeKby02C8H%2BKJ7HtblUo7dCnbrk%3D&reserved=0
> > > ">
> > > * https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdnjs.cloudflare.com%2Fajax%2Flibs%2Fhighlight.js%2F9.12.0%2Fstyles%2Fatom-one-dark.min.css&data=02%7C01%7Caharui%40adobe.com%7C922752ecb7bf4513718208d6d00ae5fb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636925142602102439&sdata=uBI0vW721xJqBH2I%2FuUrq92KIu2Vgf6YzcrOXEFGLHM%3D&reserved=0
> > > ">
> > >  * 
> > >  */
> > > public function hljs()
> > > {
> > > }
> > >
> > > public static function
> highlightBlock(block:Element):void {}
> > > }
> > > }
> > >
> > > So instead of add the inject_html in the code that calls the
> methods
> > in
> > > this step, I think it should  be here
> > >
> > > Make this sense?
> > >
> > >
> > >
> > > El vie., 3 may. 2019 a las 9:38, Carlos Rovira (<
> > > carlosrov...@apache.org>)
> > > escribió:
> > >
> > > > Hi Alex,
> > > >
> > > > for me is difficult right now think about what would be
> better for
> > > > TypeScript. I think all will depend on how people interact
> in the
> > > following
> > > > months/years to show us what't the best for Royale in the
> long
> > term.
> > > > I think bringing TS to Royale as a first citizen language
> will make
> > > us
> > > > more accesible and people will considere us more since TS is
> the
> > > language
> > > > people choose over AS3 (although I for example like AS3 more
> and if
> > > we get
> > > > few things like generics we'll be great to compete with TS),
> but
> > > this is a
> > > > very complex task, so I know this hardly be done unless
> someone
> > > comes with
> > > > time and knowledge to make it happen. And if we think about
> things
> > > that are
> > > > complex and hard to add and see the importance/value it will
> bring
> > to
> > > > Royale I think a WebAssembly target will be over TS since it
> > clearly

Build failed in Jenkins: royale-asjs_jsonly #3039

2019-06-03 Thread Apache Royale CI Server
See 


Changes:

[carlosrovira] Add B012 blog example to examples maven build and change theme 
color

--
[...truncated 2.12 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


Build failed in Jenkins: royale-asjs_jsonly #3038

2019-06-03 Thread Apache Royale CI Server
See 


--
[...truncated 2.12 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


Re: Build failed in Jenkins: royale-asjs_jsonly #3027

2019-06-03 Thread Carlos Rovira
Could be something related to selenium?

C:\Users\apacheroyale\AppData\Local\Temp\2\anonymous8220624574578606825webdriver-profile\extensions\webdriver-staging
 [java] 1559535801478   addons.xpi  DEBUG   Existing add-on
formautof...@mozilla.org in app-system-defaults
 [java] 1559535801478   addons.xpi  DEBUG   Existing add-on
fxmoni...@mozilla.org in app-system-defaults
 [java] 1559535801478   addons.xpi  DEBUG   Existing add-on
screensh...@mozilla.org in app-system-defaults
 [java] 1559535801478   addons.xpi  DEBUG   Existing add-on
webcompat-repor...@mozilla.org in app-system-defaults
 [java] 1559535801478   addons.xpi  DEBUG   Existing add-on
webcom...@mozilla.org in app-system-defaults
 [java] 1559535801479   addons.xpi  DEBUG   scanForChanges changed:
false, state: {}
 [java] JavaScript error:
resource://gre/modules/addons/XPIProvider.jsm, line 2706: TypeError:
addon is null
 [java] 1559535816710   addons.productaddonsINFOsending request
to: 
https://aus5.mozilla.org/update/3/GMP/67.0/20190516215225/WINNT_x86_64-msvc-x64/en-US/release/Windows_NT%2010.0.0.0.14393.2999%20(x64)/default/default/update.xml
 [java] 1559535816783   addons.productaddonsINFOCompleted
downloading document
 [java] 1559535817196   addons.productaddonsINFOdownloadXHR File
download. status=200
 [java] 1559535817226   addons.productaddonsINFODownloaded file
will be saved to C:\Users\APACHE~1\AppData\Local\Temp\2\tmpaddon-e8ec0
 [java] 1559535817846   addons.productaddonsINFOdownloadXHR File
download. status=200
 [java] 1559535817848   addons.productaddonsINFODownloaded file
will be saved to
C:\Users\APACHE~1\AppData\Local\Temp\2\tmpaddon-cebd63
 [java]
 [java] at
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:112)
 [java] ... 7 more
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g
BUILD FAILEDc:\jenkins\workspace\royale-asjs_jsonly\build.xml:1249:
Java returned: 1

Total time: 18 minutes 35 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g
Build step 'Invoke Ant' marked build as failure
Archiving artifacts
Sending e-mails to: dev@royale.apache.org
Finished: FAILURE



El lun., 3 jun. 2019 a las 14:13, Carlos Rovira ()
escribió:

> HI Piotr,
>
> I can confirm that I build all from scratch with unit test included and
> all goes ok.
>
> El lun., 3 jun. 2019 a las 14:03, Carlos Rovira ()
> escribió:
>
>> going to check again with unit test
>> report soon
>>
>> El lun., 3 jun. 2019 a las 13:51, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>>
>>> It's been 2 days since it happening, so this is not coincidence ->
>>>
>>> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
>>>
>>> pon., 3 cze 2019 o 13:50 Piotr Zarzycki 
>>> napisał(a):
>>>
>>> > Did you run all the unit stests ?
>>> >
>>> > pon., 3 cze 2019 o 13:45 Carlos Rovira 
>>> > napisał(a):
>>> >
>>> >> Hi Piotr,
>>> >>
>>> >> I fixed yesterday the problem with @externs and source maps.
>>> >> I rebuild all from scratch locally (included examples) and all is
>>> working
>>> >> fine.
>>> >> If this is something caused by my changes in the CI, I'm a bit
>>> confused
>>> >> and
>>> >> hope others could give some light on what could be the problem, or if
>>> is
>>> >> not related at all (maybe is just coincidence).
>>> >>
>>> >> thanks
>>> >>
>>> >>
>>> >> El lun., 3 jun. 2019 a las 13:33, Piotr Zarzycki (<
>>> >> piotrzarzyck...@gmail.com>)
>>> >> escribió:
>>> >>
>>> >> > Is it the results of some kind of changes lately ?
>>> >> >
>>> >> > --
>>> >> > Carlos Rovira
>>> >> > http://about.me/carlosrovira
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >>
>>> >
>>> >
>>> > --
>>> >
>>> > Piotr Zarzycki
>>> >
>>> > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > *
>>> >
>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> *
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira


Re: Build failed in Jenkins: royale-asjs_jsonly #3027

2019-06-03 Thread Carlos Rovira
HI Piotr,

I can confirm that I build all from scratch with unit test included and all
goes ok.

El lun., 3 jun. 2019 a las 14:03, Carlos Rovira ()
escribió:

> going to check again with unit test
> report soon
>
> El lun., 3 jun. 2019 a las 13:51, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> It's been 2 days since it happening, so this is not coincidence ->
>>
>> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
>>
>> pon., 3 cze 2019 o 13:50 Piotr Zarzycki 
>> napisał(a):
>>
>> > Did you run all the unit stests ?
>> >
>> > pon., 3 cze 2019 o 13:45 Carlos Rovira 
>> > napisał(a):
>> >
>> >> Hi Piotr,
>> >>
>> >> I fixed yesterday the problem with @externs and source maps.
>> >> I rebuild all from scratch locally (included examples) and all is
>> working
>> >> fine.
>> >> If this is something caused by my changes in the CI, I'm a bit confused
>> >> and
>> >> hope others could give some light on what could be the problem, or if
>> is
>> >> not related at all (maybe is just coincidence).
>> >>
>> >> thanks
>> >>
>> >>
>> >> El lun., 3 jun. 2019 a las 13:33, Piotr Zarzycki (<
>> >> piotrzarzyck...@gmail.com>)
>> >> escribió:
>> >>
>> >> > Is it the results of some kind of changes lately ?
>> >> >
>> >> > --
>> >> > Carlos Rovira
>> >> > http://about.me/carlosrovira
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > *
>> >
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira


Re: Build failed in Jenkins: royale-asjs_jsonly #3027

2019-06-03 Thread Carlos Rovira
going to check again with unit test
report soon

El lun., 3 jun. 2019 a las 13:51, Piotr Zarzycki ()
escribió:

> It's been 2 days since it happening, so this is not coincidence ->
>
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
>
> pon., 3 cze 2019 o 13:50 Piotr Zarzycki 
> napisał(a):
>
> > Did you run all the unit stests ?
> >
> > pon., 3 cze 2019 o 13:45 Carlos Rovira 
> > napisał(a):
> >
> >> Hi Piotr,
> >>
> >> I fixed yesterday the problem with @externs and source maps.
> >> I rebuild all from scratch locally (included examples) and all is
> working
> >> fine.
> >> If this is something caused by my changes in the CI, I'm a bit confused
> >> and
> >> hope others could give some light on what could be the problem, or if is
> >> not related at all (maybe is just coincidence).
> >>
> >> thanks
> >>
> >>
> >> El lun., 3 jun. 2019 a las 13:33, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>)
> >> escribió:
> >>
> >> > Is it the results of some kind of changes lately ?
> >> >
> >> > --
> >> > Carlos Rovira
> >> > http://about.me/carlosrovira
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 
Carlos Rovira
http://about.me/carlosrovira


Re: Build failed in Jenkins: royale-asjs_jsonly #3027

2019-06-03 Thread Piotr Zarzycki
Did you run all the unit stests ?

pon., 3 cze 2019 o 13:45 Carlos Rovira  napisał(a):

> Hi Piotr,
>
> I fixed yesterday the problem with @externs and source maps.
> I rebuild all from scratch locally (included examples) and all is working
> fine.
> If this is something caused by my changes in the CI, I'm a bit confused and
> hope others could give some light on what could be the problem, or if is
> not related at all (maybe is just coincidence).
>
> thanks
>
>
> El lun., 3 jun. 2019 a las 13:33, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Is it the results of some kind of changes lately ?
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
> >
> >
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*


Re: Build failed in Jenkins: royale-asjs_jsonly #3027

2019-06-03 Thread Piotr Zarzycki
It's been 2 days since it happening, so this is not coincidence ->
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/

pon., 3 cze 2019 o 13:50 Piotr Zarzycki 
napisał(a):

> Did you run all the unit stests ?
>
> pon., 3 cze 2019 o 13:45 Carlos Rovira 
> napisał(a):
>
>> Hi Piotr,
>>
>> I fixed yesterday the problem with @externs and source maps.
>> I rebuild all from scratch locally (included examples) and all is working
>> fine.
>> If this is something caused by my changes in the CI, I'm a bit confused
>> and
>> hope others could give some light on what could be the problem, or if is
>> not related at all (maybe is just coincidence).
>>
>> thanks
>>
>>
>> El lun., 3 jun. 2019 a las 13:33, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>> escribió:
>>
>> > Is it the results of some kind of changes lately ?
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>> >
>> >
>> >
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*


Re: Build failed in Jenkins: royale-asjs_jsonly #3027

2019-06-03 Thread Carlos Rovira
Hi Piotr,

I fixed yesterday the problem with @externs and source maps.
I rebuild all from scratch locally (included examples) and all is working
fine.
If this is something caused by my changes in the CI, I'm a bit confused and
hope others could give some light on what could be the problem, or if is
not related at all (maybe is just coincidence).

thanks


El lun., 3 jun. 2019 a las 13:33, Piotr Zarzycki ()
escribió:

> Is it the results of some kind of changes lately ?
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>
>


Re: Build failed in Jenkins: royale-asjs_jsonly #3027

2019-06-03 Thread Piotr Zarzycki
Is it the results of some kind of changes lately ?

niedz., 2 cze 2019 o 20:58 Apache Royale CI Server 
napisał(a):

> See <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/3027/display/redirect?page=changes
> >
>
> Changes:
>
> [carlosrovira] fix @externs example
>
> --
> [...truncated 1.94 MB...]
>[delete] Deleting: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/themes/JewelThemeJS/JewelThemeJS.swc.properties
> >
>
> clean:
>
> check-compiler-home:
>
> check-transpiler-home:
>
> check-compiler:
>
> compile:
>  [echo] Cross-compiling JewelThemeJS.swc
>  [echo] ROYALE_COMPILER_HOME: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/js
> >
> [mkdir] Created dir: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/themes/JewelThemeJS/target/generated-sources/royale
> >
>  [java] args:
>  [java] +royalelib=<
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks
> >
>  [java] -compiler.strict-xml=true
>  [java] -compiler.targets=SWF,JSRoyale
>  [java] -output=<
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/themes/JewelThemeJS/target/JewelThemeJS.swc
> >
>  [java] -load-config=<
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js-config.xml
> >
>  [java] -load-config+=<
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/themes/JewelThemeJS/src/main/config/compile-js-config.xml
> >
>  [java] target:SWF
>  [java] target:JSRoyale
>  [java] COMPC
>  [java] Loading configuration: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js-config.xml
> >
>  [java] Loading configuration: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/themes/JewelThemeJS/src/main/config/compile-js-config.xml
> >
>  [java]
>  [java] 1740 bytes written to
> C:\jenkins\workspace\royale-asjs_jsonly\frameworks\js\themes\JewelThemeJS\target\JewelThemeJS.swc
> in 0.744 seconds
>  [java] COMPCJSCRoyale
>  [java] Copy library.swf
>  [java] Compiling file: JewelThemeClasses
>  [java] Writing file: js\out\JewelThemeClasses.js
>  [java] 1.9935572 seconds
>  [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m
> -Xmx1g
>
> main:
>  [copy] Copying 1 file to <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/libs
> >
>
> copy-swc:
>
> check-for-tests:
>
> test:
>
> main:
>
> Icons:
>
> clean:
>
> check-for-tests:
>
> clean-tests:
>
> check-compiler-home:
>
> check-transpiler-home:
>
> check-compiler:
>
> compile:
>
> compile-js:
>[delete] Deleting: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties
> >
>
> clean:
>[delete] Deleting: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties
> >
>
> check-for-tests:
>
> clean-tests:
>
> check-compiler-home:
>
> check-transpiler-home:
>
> check-compiler:
>
> compile:
>  [echo] Cross-compiling IconsJS.swc
>  [echo] ROYALE_COMPILER_HOME: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/js
> >
> [mkdir] Created dir: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/target/generated-sources/royale
> >
>  [java] args:
>  [java] +royalelib=<
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks
> >
>  [java] -compiler.strict-xml=true
>  [java] -compiler.targets=SWF,JSRoyale
>  [java] -output=<
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/target/IconsJS.swc
> >
>  [java] -load-config=<
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js-config.xml
> >
>  [java] -load-config+=<
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/src/main/config/compile-js-config.xml
> >
>  [java] target:SWF
>  [java] target:JSRoyale
>  [java] COMPC
>  [java] Loading configuration: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js-config.xml
> >
>  [java] Loading configuration: <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/src/main/config/compile-js-config.xml
> >
>  [java]
>  [java] 78950 bytes written to
> C:\jenkins\workspace\royale-asjs_jsonly\framewo