Re: Language improvements

[Greg Dove]

"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 'This agreement proves that the original
implementation was not right'.
Firstly, I don't think Vector type was providing any benefit in this case
in the first place (but that alone is not a reason to change it, awareness
that it 'costs more' would however be a valid reason if there are no
benefits to using it).
Secondly, the collaborative outcome resulting in the use of explicit Array
and the goog.DEBUG check is better than the original Vector-as-Array output
because it offers the runtime type safety that was missing because it was
not behaving like a Vector - and it retains the advantage of zero-weight in
release build. Making these changes *is* a form of optimization based on
using options currently available, it just happens to be hand-coded and not
compiler-generated.
I know it's at least a little bit useful in its new form, because prior
testing with the branch level Vector implementation flagged a
non-conforming IBead in the 2nd app I tested it with, something that was
not found by the original 'Array' implementation.
SWF testing in parallel would have caught that too, but is not a realistic
assumption to have that as part of the workflow for checking runtime
behavior anymore, so this 'Array with debug-only typecheck' in javascript
is a good outcome.
In this case, going back to Vector-as-Array output without making the other
change would be a step backwards.

That is however just one specific case, and I needed to present what I
believe is a more balanced view of that... but I will not focus on it in
any further discussion.
I do understand that your point is intended to be more general.
In general, and *by definition*, the cases where you want Vector to be
Array without adverse consequences are always cases where it can also *be*
Array in the original as3 code. If the only justification for it being a
Vector in as3 code is 'compile-time type safety', then the proposed
alternative from Harbs and Josh is a better option because it retains the
benefits you seek and is a better quality cross-target representation for
this specific sort of requirement (it will also provide more benefits: most
Vector methods do not have compile-time type safety because most their
method signatures do not specify :T types, I hope the proposed alternative
might address that).
For the performance-oriented numeric types, which is another thing that has
been raised, maybe Josh can somehow include that with the typed Arrays
feature as he suggested, maybe not. If yes, then great, but if not, I am
happy to explore other options for that.

What I'd really like to hear are your thoughts about the concerns I raised
for the:
"new whateverclasstheconfigordirectivespecified()"
approach to doing any of this.

How do you propose to avoid risk to the community and potentially to
Royale's reputation with release of swcs that can have different
language-level variations in them (XML, Vector or anything that represents
a core as3 'type')?
Do we have to warn people not to do that, and then hope that they don't? A
user of that swc doesn't see the emulation class that the swc may expose
without investigating at runtime, they normally only see the type it
represents, and unless they are warned, they have no reason to assume it
won't do all the things it should. There could also be runtime conflict
implications when mixing swcs with different emulation decisions, and that
could even add weight overall compared to using one. None of this
represents stuff that can't be figured out and addressed by developers who
have to deal with it. But it seems to me to be something negative, which
would be better to avoid.

I think you are indicating the same desire to avoid this problem by saying
that you want to specify things by 'the swc' you add (e.g. XML
replacement)... but that can be too late, because even if an alternate
emulation class itself is not bundled into a swc's code, all the calls to
instantiate it are, which reflect its distinct package name and class name.
I can envisage ways to achieve optimization and to avoid risks for the
general case, but only if the instantiation calls for these language level
emulations can never vary throughout the entire codebase (all swcs
included), and the 'optimization' is therefore largely driven from the
application build, and not dictated at swc level. Maybe swc libraries could
be advertised as being compatible with some well-known optimizations in
this 

Re: Adding Jewel classes to Apache Royale AS3 reference

[Carlos Rovira]

Alex,

I'm seeing that a first load of link by ASDoc works ok. for example:

going directly to

https://royale.apache.org/asdoc/index.html#!org.apache.royale.jewel/Alert

shows

Packageorg.apache.royale.jewel
ClassApplication
Inheritance

(although seems ASDocs is failing in get more info, since only that is
showing)

So, I think the change I did are ok and the problem is something not
working ok in ASDoc. If your opinion is the same as mine, then I can
continue working in Royale-docs, and at sometime hope you could take a look
to what could be happening to ASDocs, or more later in time, if you can I
can take a look, although, since I didn't developed the app, it will be
more dficult to me to find what could be happening.

Thanks





El jue., 30 may. 2019 a las 20:10, Carlos Rovira ()
escribió:

> I was who added MX libraries just before. And what I removed was because
> was making build fail.
> I decided to get some few new working (Jewel and Icons) and then add others
> I reach to the middle point, where new libraries are showing in the lists,
> but when click it does not shows anything.
>
> El jue., 30 may. 2019 a las 20:05, Alex Harui ()
> escribió:
>
>> Did you revert the commenting out of some of the swcs and fix the asdoc
>> instead?  It is not fair to others to remove the mx libraries from the
>> ASDoc.
>>
>>
>>
>> -Alex
>>
>>
>>
>> *From: *Carlos Rovira 
>> *Date: *Thursday, May 30, 2019 at 6:51 AM
>> *To: *"dev@royale.apache.org" , Alex Harui <
>> aha...@adobe.com>
>> *Subject: *Re: Adding Jewel classes to Apache Royale AS3 reference
>>
>>
>>
>> Hi,
>>
>>
>>
>> @Alex Harui  , do you know why I click in for example
>> "Jewel Card" component in ASDoc I get "Loading..." but nothing is showing
>> up.
>>
>>
>>
>> https://royale.apache.org/asdoc/index.html#!org.apache.royale.jewel/Alert
>> 
>>
>>
>>
>> I need to solve this issue to get new Reference up in website, and to
>> avoid all new links to it fail (like here):
>>
>>
>>
>> https://apache.github.io/royale-docs/component-sets/jewel/jewel-alert.html
>> 
>>
>>
>>
>> (notice that in that page I need to put right urls since are linking to
>> html controls instead of jewel for now)
>>
>>
>>
>> any help here is very appreciated to make documentation completion task
>> progress
>>
>>
>>
>> Thanks!
>>
>>
>>
>> Carlos
>>
>>
>>
>>
>>
>> El mar., 28 may. 2019 a las 19:55, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>> I mean the rest of ASDoc is showing as before, but not Jewel
>>
>>
>>
>> El mar., 28 may. 2019 a las 19:52, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>> Ok,
>>
>>
>>
>> I tried (we always can revert).
>>
>> And I get Jewel showing in ASDoc.
>>
>> But, If I click in for example "Card" component I get "Loading..." but
>> nothing is showing up
>>
>>
>>
>> what could be happening?
>>
>>
>>
>> Thanks
>>
>>
>>
>> Carlos
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> El mar., 28 may. 2019 a las 19:43, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>> Hi,
>>
>>
>>
>> I think I get ASDocs building and generating with ANT.
>>
>> Now I need to upload results to website, but this seems not direct.
>>
>> There's some guide, email or something to now what I should overlay in
>> "asdic" folder on the website?
>>
>>
>>
>> I was thinking it should be just upload "bin/bin-release", but I'm seeing
>> contents there seems not all what we have in website (maybe in website we
>> have files that are not needed anymore)
>>
>>
>>
>> Another thing I see in published site is:
>>
>>
>>
>>  - CordovaClasses.js.json <-- this file is not produced by ANT
>>
>>  - CordovaClasses.swf.json.  <-- this file is produced by ANT
>>
>>
>>
>> I always can publish and if things are not as expected revert the change,
>> but hope to be instructed in some basic steps.
>>
>>
>>
>> thanks
>>
>>
>>
>>
>>
>> El vie., 24 may. 2019 a las 20:37, Alex Harui ()
>> escribió:
>>
>> It appears that the CI build is failing but not reporting a failure.  So
>> that may also be why you are not getting JSON files on your computers.  A
>> volunteer is needed to clean up the files that are causing errors.
>>
>> I guess that means that nobody is using our ASDoc, since otherwise I
>> think this would be reported.
>>
>>
>> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/CI/job/Royale_ASDoc_Example/
>> 

Re: Language improvements

[Harbs]

To me there are (or rather will be) two kinds of “Vector”.

1. `Vector.` (which has the extra code)
2. `Foo[]` which would have no extra code.

Do you have a reason why you’d want to use `Vector.` rather than `Foo[]`? 
Having two completely different constructs seems like it would be much less 
confusing for users.

Harbs

> On May 30, 2019, at 9:36 PM, Alex Harui  wrote:
> 
> It is pretty simple to me.  The proposed Vector implementation is heavy 
> enough that we all agree that we don't want to use it for just one use case 
> in the Strand.  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 would be much better if Royale had a way for developers to specify that 
> the one use of Vector in the Strand should be converted to plain Array by the 
> compiler and other uses could use the proposed Vector.  That's how 
> optimization should be made available for all kinds of code in Royale, not 
> just for Vector.
> 
> The current Vector output in the develop branch is low cost and fully 
> functional for some uses cases.  As long as that output is still available as 
> a compiler option then having other output fine.
> 
> I still haven't found time to look at the actual proposed changes, but I 
> would strongly prefer that, instead of having to modify compiler output each 
> time someone proposes a different Vector implementation, that the changes can 
> all be done by which SWC you choose for your Vector implementation.  There 
> are other places in the compiler where you can choose the class to use for 
> Binding or ClassFactory.  Hopefully the same approach is being used for 
> Vector.  Ideally, the compile would just output "new 
> whateverclasstheconfigordirectivespecified()" and then just output the usual 
> push/pop/index calls and so it could just be plain Array where specified or 
> the proposed Vector and some other Vector someday.
> 
> This is a case were "there is no one right way".  And when we have those 
> situations, we must offer choices.
> 
> -Alex
> 
> On 5/30/19, 1:34 AM, "Carlos Rovira"  > wrote:
> 
>Hi,
> 
>@Alex Harui  I think you misunderstood me. I'm not saying
>we should "remove choices". What I say is that we have finally a more
>robust implementation and we can evolve to have more choices from that
>point. I think continue from that safe point will give us many benefits. So
>I want those choices. What I don't want is to wait to make it perfect to
>merge. As I said before perfection is enemy of the progress.
> 
>An important point I can't agree with you: Why we don't use Vector in our
>production App? Cause we can't. To do that we need: a) Greg changes merged,
>b) make AMF understand Vectors (still to be done to make Vector usable for
>us). Without both points Vectors are not an option for us. So I think the
>premise of "we have 2 apps in production without Vectors" are not right. We
>don't have still Jewel DataGrid, or Swiz Global Dispatcher, and that does
>not mean it's ok for us. Is just we still don't have it, but making us to
>make our product without all of that is a serious issue that we need to
>workaround in some way. But we can do that as something "temporal", due to
>current Royale limitations. But our goal is to have all that, Vector-AMF
>included :)
> 
>For this reason, I prefer to have Greg's Vector now, since it makes our
>production App be one step closer to remove current workarounds :)
>And I'm sure that not having a Vector solution like this, could be a reason
>why some people still didn't try Royale to migrate to this date.
>So if you ask me or those people for a "priority path", we will say "let's
>get Vector first, then evolve from that to have more choices".
>That's what I'm saying it's ok to merge now.
> 
>I'm ok with having Vector as we all know it from AS3 (since is that...AS3
>Vector, don't forget that, and is what people expect to have at first
>sight, then we can give them more choices and they will appreciate for
>sure), and have as well a new Typed Array too as other proposed too. That
>will be for me options. But we should not wait to make all that happen to
>merge current branch, right?, All that we'll be lots of time to make it
>perfect from day 0.
> 
>The key concept for me was what Harbs said in his response to the end. If
>you don't use it the impact is 0, not 2-3k, since people don't have Vector
>presence in their codes. So that's PAYG. For that reason it's ok for me to
>merge and continue from that safe point, since we really only get positive
>things and nothing negative, and since we all agree in the same terms, just
>we need more time to continue evolving it to get to that perfect final
>point.
> 
> 
> 
> 
>   

Re: Language improvements

[Alex Harui]

It is pretty simple to me.  The proposed Vector implementation is heavy enough 
that we all agree that we don't want to use it for just one use case in the 
Strand.  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 would be much better if Royale had a way for developers to specify that the 
one use of Vector in the Strand should be converted to plain Array by the 
compiler and other uses could use the proposed Vector.  That's how optimization 
should be made available for all kinds of code in Royale, not just for Vector.

The current Vector output in the develop branch is low cost and fully 
functional for some uses cases.  As long as that output is still available as a 
compiler option then having other output fine.

I still haven't found time to look at the actual proposed changes, but I would 
strongly prefer that, instead of having to modify compiler output each time 
someone proposes a different Vector implementation, that the changes can all be 
done by which SWC you choose for your Vector implementation.  There are other 
places in the compiler where you can choose the class to use for Binding or 
ClassFactory.  Hopefully the same approach is being used for Vector.  Ideally, 
the compile would just output "new 
whateverclasstheconfigordirectivespecified()" and then just output the usual 
push/pop/index calls and so it could just be plain Array where specified or the 
proposed Vector and some other Vector someday.

This is a case were "there is no one right way".  And when we have those 
situations, we must offer choices.

-Alex

On 5/30/19, 1:34 AM, "Carlos Rovira"  wrote:

Hi,

@Alex Harui  I think you misunderstood me. I'm not saying
we should "remove choices". What I say is that we have finally a more
robust implementation and we can evolve to have more choices from that
point. I think continue from that safe point will give us many benefits. So
I want those choices. What I don't want is to wait to make it perfect to
merge. As I said before perfection is enemy of the progress.

An important point I can't agree with you: Why we don't use Vector in our
production App? Cause we can't. To do that we need: a) Greg changes merged,
b) make AMF understand Vectors (still to be done to make Vector usable for
us). Without both points Vectors are not an option for us. So I think the
premise of "we have 2 apps in production without Vectors" are not right. We
don't have still Jewel DataGrid, or Swiz Global Dispatcher, and that does
not mean it's ok for us. Is just we still don't have it, but making us to
make our product without all of that is a serious issue that we need to
workaround in some way. But we can do that as something "temporal", due to
current Royale limitations. But our goal is to have all that, Vector-AMF
included :)

For this reason, I prefer to have Greg's Vector now, since it makes our
production App be one step closer to remove current workarounds :)
And I'm sure that not having a Vector solution like this, could be a reason
why some people still didn't try Royale to migrate to this date.
So if you ask me or those people for a "priority path", we will say "let's
get Vector first, then evolve from that to have more choices".
That's what I'm saying it's ok to merge now.

I'm ok with having Vector as we all know it from AS3 (since is that...AS3
Vector, don't forget that, and is what people expect to have at first
sight, then we can give them more choices and they will appreciate for
sure), and have as well a new Typed Array too as other proposed too. That
will be for me options. But we should not wait to make all that happen to
merge current branch, right?, All that we'll be lots of time to make it
perfect from day 0.

The key concept for me was what Harbs said in his response to the end. If
you don't use it the impact is 0, not 2-3k, since people don't have Vector
presence in their codes. So that's PAYG. For that reason it's ok for me to
merge and continue from that safe point, since we really only get positive
things and nothing negative, and since we all agree in the same terms, just
we need more time to continue evolving it to get to that perfect final
point.




El jue., 30 may. 2019 a las 7:56, Greg Dove ()
escribió:

> Harbs some quick comments inline...
>
> On Thu, May 30, 2019 at 4:27 PM Harbs  wrote:
>
> > The only niggle I have with my approach is that Vector in Flash is more
> > performant than array, while in JS, it’s going to be the other way
> around.
> > So if someone has a performance-sensitive piece of code, how should they
> > write it so it outputs as performant as possible on both platforms?

Re: Adding Jewel classes to Apache Royale AS3 reference

[Carlos Rovira]

I was who added MX libraries just before. And what I removed was because
was making build fail.
I decided to get some few new working (Jewel and Icons) and then add others
I reach to the middle point, where new libraries are showing in the lists,
but when click it does not shows anything.

El jue., 30 may. 2019 a las 20:05, Alex Harui () escribió:

> Did you revert the commenting out of some of the swcs and fix the asdoc
> instead?  It is not fair to others to remove the mx libraries from the
> ASDoc.
>
>
>
> -Alex
>
>
>
> *From: *Carlos Rovira 
> *Date: *Thursday, May 30, 2019 at 6:51 AM
> *To: *"dev@royale.apache.org" , Alex Harui <
> aha...@adobe.com>
> *Subject: *Re: Adding Jewel classes to Apache Royale AS3 reference
>
>
>
> Hi,
>
>
>
> @Alex Harui  , do you know why I click in for example
> "Jewel Card" component in ASDoc I get "Loading..." but nothing is showing
> up.
>
>
>
> https://royale.apache.org/asdoc/index.html#!org.apache.royale.jewel/Alert
> 
>
>
>
> I need to solve this issue to get new Reference up in website, and to
> avoid all new links to it fail (like here):
>
>
>
> https://apache.github.io/royale-docs/component-sets/jewel/jewel-alert.html
> 
>
>
>
> (notice that in that page I need to put right urls since are linking to
> html controls instead of jewel for now)
>
>
>
> any help here is very appreciated to make documentation completion task
> progress
>
>
>
> Thanks!
>
>
>
> Carlos
>
>
>
>
>
> El mar., 28 may. 2019 a las 19:55, Carlos Rovira ()
> escribió:
>
> I mean the rest of ASDoc is showing as before, but not Jewel
>
>
>
> El mar., 28 may. 2019 a las 19:52, Carlos Rovira ()
> escribió:
>
> Ok,
>
>
>
> I tried (we always can revert).
>
> And I get Jewel showing in ASDoc.
>
> But, If I click in for example "Card" component I get "Loading..." but
> nothing is showing up
>
>
>
> what could be happening?
>
>
>
> Thanks
>
>
>
> Carlos
>
>
>
>
>
>
>
>
>
> El mar., 28 may. 2019 a las 19:43, Carlos Rovira ()
> escribió:
>
> Hi,
>
>
>
> I think I get ASDocs building and generating with ANT.
>
> Now I need to upload results to website, but this seems not direct.
>
> There's some guide, email or something to now what I should overlay in
> "asdic" folder on the website?
>
>
>
> I was thinking it should be just upload "bin/bin-release", but I'm seeing
> contents there seems not all what we have in website (maybe in website we
> have files that are not needed anymore)
>
>
>
> Another thing I see in published site is:
>
>
>
>  - CordovaClasses.js.json <-- this file is not produced by ANT
>
>  - CordovaClasses.swf.json.  <-- this file is produced by ANT
>
>
>
> I always can publish and if things are not as expected revert the change,
> but hope to be instructed in some basic steps.
>
>
>
> thanks
>
>
>
>
>
> El vie., 24 may. 2019 a las 20:37, Alex Harui ()
> escribió:
>
> It appears that the CI build is failing but not reporting a failure.  So
> that may also be why you are not getting JSON files on your computers.  A
> volunteer is needed to clean up the files that are causing errors.
>
> I guess that means that nobody is using our ASDoc, since otherwise I think
> this would be reported.
>
>
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/CI/job/Royale_ASDoc_Example/
> 
>
> -Alex
>
> On 5/24/19, 9:38 AM, "Carlos Rovira"  wrote:
>
> Hi Alex, without doubt something for our todo list, but there's many
> things
> in the plate and maybe other bigger fish to fry for now.
> I'll try to run vía ant and see if I can get something generated that
> can
> be committed to ref site
> thanks!
>
> El vie., 24 may. 2019 a las 18:19, Alex Harui
> ()
> escribió:
>
> > Carlos,
> >
> > When I compare the Ant build to the Maven build, I can see that the
> Ant
> > build runs the ASDoc compiler to generate the JSON and the Maven
> build does
> > not.  We definitely need more committers to understand enough of
> both Ant
> > and Maven so I don't have to do these investigations and have 

Re: Adding Jewel classes to Apache Royale AS3 reference

[Alex Harui]

Did you revert the commenting out of some of the swcs and fix the asdoc 
instead?  It is not fair to others to remove the mx libraries from the ASDoc.

-Alex

From: Carlos Rovira 
Date: Thursday, May 30, 2019 at 6:51 AM
To: "dev@royale.apache.org" , Alex Harui 

Subject: Re: Adding Jewel classes to Apache Royale AS3 reference

Hi,

@Alex Harui , do you know why I click in for example 
"Jewel Card" component in ASDoc I get "Loading..." but nothing is showing up.

https://royale.apache.org/asdoc/index.html#!org.apache.royale.jewel/Alert

I need to solve this issue to get new Reference up in website, and to avoid all 
new links to it fail (like here):

https://apache.github.io/royale-docs/component-sets/jewel/jewel-alert.html

(notice that in that page I need to put right urls since are linking to html 
controls instead of jewel for now)

any help here is very appreciated to make documentation completion task progress

Thanks!

Carlos


El mar., 28 may. 2019 a las 19:55, Carlos Rovira 
(mailto:carlosrov...@apache.org>>) escribió:
I mean the rest of ASDoc is showing as before, but not Jewel

El mar., 28 may. 2019 a las 19:52, Carlos Rovira 
(mailto:carlosrov...@apache.org>>) escribió:
Ok,

I tried (we always can revert).
And I get Jewel showing in ASDoc.
But, If I click in for example "Card" component I get "Loading..." but nothing 
is showing up

what could be happening?

Thanks

Carlos




El mar., 28 may. 2019 a las 19:43, Carlos Rovira 
(mailto:carlosrov...@apache.org>>) escribió:
Hi,

I think I get ASDocs building and generating with ANT.
Now I need to upload results to website, but this seems not direct.
There's some guide, email or something to now what I should overlay in "asdic" 
folder on the website?

I was thinking it should be just upload "bin/bin-release", but I'm seeing 
contents there seems not all what we have in website (maybe in website we have 
files that are not needed anymore)

Another thing I see in published site is:

 - CordovaClasses.js.json <-- this file is not produced by ANT
 - CordovaClasses.swf.json.  <-- this file is produced by ANT

I always can publish and if things are not as expected revert the change, but 
hope to be instructed in some basic steps.

thanks


El vie., 24 may. 2019 a las 20:37, Alex Harui () 
escribió:
It appears that the CI build is failing but not reporting a failure.  So that 
may also be why you are not getting JSON files on your computers.  A volunteer 
is needed to clean up the files that are causing errors.

I guess that means that nobody is using our ASDoc, since otherwise I think this 
would be reported.

http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/CI/job/Royale_ASDoc_Example/

-Alex

On 5/24/19, 9:38 AM, "Carlos Rovira" 
mailto:carlosrov...@apache.org>> wrote:

Hi Alex, without doubt something for our todo list, but there's many things
in the plate and maybe other bigger fish to fry for now.
I'll try to run vía ant and see if I can get something generated that can
be committed to ref site
thanks!

El vie., 24 may. 2019 a las 18:19, Alex Harui ()
escribió:

> Carlos,
>
> When I compare the Ant build to the Maven build, I can see that the Ant
> build runs the ASDoc compiler to generate the JSON and the Maven build 
does
> not.  We definitely need more committers to understand enough of both Ant
> and Maven so I don't have to do these investigations and have folks 
waiting
> on me to do so.
>
> Volunteers are welcome to improve the Maven build by creating a way to
> call the ASDoc compiler from Maven.
>
> HTH,
> -Alex
>
> On 5/24/19, 3:54 AM, "Carlos Rovira" 
mailto:carlosrov...@apache.org>> wrote:
>
> Hi Alex,
>
> in my latest commit I added to the files you pointed in your email the
> missed libraries I detected.
> I build with maven ASDoc app, but I didn't get a delta output. I was
> expecting some files to 

Re: Adding Jewel classes to Apache Royale AS3 reference

[Carlos Rovira]

Hi,

@Alex Harui  , do you know why I click in for example
"Jewel Card" component in ASDoc I get "Loading..." but nothing is showing
up.

https://royale.apache.org/asdoc/index.html#!org.apache.royale.jewel/Alert

I need to solve this issue to get new Reference up in website, and to avoid
all new links to it fail (like here):

https://apache.github.io/royale-docs/component-sets/jewel/jewel-alert.html

(notice that in that page I need to put right urls since are linking to
html controls instead of jewel for now)

any help here is very appreciated to make documentation completion task
progress

Thanks!

Carlos


El mar., 28 may. 2019 a las 19:55, Carlos Rovira ()
escribió:

> I mean the rest of ASDoc is showing as before, but not Jewel
>
> El mar., 28 may. 2019 a las 19:52, Carlos Rovira ()
> escribió:
>
>> Ok,
>>
>> I tried (we always can revert).
>> And I get Jewel showing in ASDoc.
>> But, If I click in for example "Card" component I get "Loading..." but
>> nothing is showing up
>>
>> what could be happening?
>>
>> Thanks
>>
>> Carlos
>>
>>
>>
>>
>> El mar., 28 may. 2019 a las 19:43, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>>> Hi,
>>>
>>> I think I get ASDocs building and generating with ANT.
>>> Now I need to upload results to website, but this seems not direct.
>>> There's some guide, email or something to now what I should overlay in
>>> "asdic" folder on the website?
>>>
>>> I was thinking it should be just upload "bin/bin-release", but I'm
>>> seeing contents there seems not all what we have in website (maybe in
>>> website we have files that are not needed anymore)
>>>
>>> Another thing I see in published site is:
>>>
>>>  - CordovaClasses.js.json <-- this file is not produced by ANT
>>>  - CordovaClasses.swf.json.  <-- this file is produced by ANT
>>>
>>> I always can publish and if things are not as expected revert the
>>> change, but hope to be instructed in some basic steps.
>>>
>>> thanks
>>>
>>>
>>> El vie., 24 may. 2019 a las 20:37, Alex Harui ()
>>> escribió:
>>>
 It appears that the CI build is failing but not reporting a failure.
 So that may also be why you are not getting JSON files on your computers.
 A volunteer is needed to clean up the files that are causing errors.

 I guess that means that nobody is using our ASDoc, since otherwise I
 think this would be reported.


 http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/CI/job/Royale_ASDoc_Example/

 -Alex

 On 5/24/19, 9:38 AM, "Carlos Rovira"  wrote:

 Hi Alex, without doubt something for our todo list, but there's
 many things
 in the plate and maybe other bigger fish to fry for now.
 I'll try to run vía ant and see if I can get something generated
 that can
 be committed to ref site
 thanks!

 El vie., 24 may. 2019 a las 18:19, Alex Harui
 ()
 escribió:

 > Carlos,
 >
 > When I compare the Ant build to the Maven build, I can see that
 the Ant
 > build runs the ASDoc compiler to generate the JSON and the Maven
 build does
 > not.  We definitely need more committers to understand enough of
 both Ant
 > and Maven so I don't have to do these investigations and have
 folks waiting
 > on me to do so.
 >
 > Volunteers are welcome to improve the Maven build by creating a
 way to
 > call the ASDoc compiler from Maven.
 >
 > HTH,
 > -Alex
 >
 > On 5/24/19, 3:54 AM, "Carlos Rovira" 
 wrote:
 >
 > Hi Alex,
 >
 > in my latest commit I added to the files you pointed in your
 email the
 > missed libraries I detected.
 > I build with maven ASDoc app, but I didn't get a delta
 output. I was
 > expecting some files to commit to reference repo
 > Maybe I must run an ANT command line instruction? if so what
 should I
 > try?
 > can you point me to the next steps?
 >
 > thanks
 >
 > --
 > Carlos Rovira
 >
 https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cbceea294e0914d344f0508d6e06630d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636943126848010535sdata=wgsVAzxp5ofiT8V4C1s6F%2FZtozBM5O4yrMvvHXf72t8%3Dreserved=0
 >
 >
 >
 >



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

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

New apache-royale questions for May 30 - Stack Exchange

[Stack Exchange]

***1 new question in [ApacheRoyale Tag Notifications 
filter]()
 on stackexchange.com***


[Definition com.adobe.cairngorm.vo.IValueObject could not 
found]()

i am unable to include external ".swc" files in compilation time. Please help 
me? or suggest alternative ways? i am using sevaral 3rd party swc files , so is 
right choice to migrate my application to ...

Tagged: apache-royale

by [Naresh_Nalla]() on 






[Unsubscribe from this 
filter]()
 or change your email preferences by visitingyour [filter subscriptions page on 
stackexchange.com]().

If you no longer want to receive mail from Stack Exchange, unsubscribe from all 
stackexchange.com emails 

Questions? Comments? Let us know on our feedback site at 
.

Stack Exchange, Inc. 110 William St, 28th Floor, NY NY 10038

Re: Error on mailing list page

[Carlos Rovira]

Hi Just changed it

I see that we have an issue with http links.
Website has a plugin to remove http: and https:
this is to ensure chrome and the rest of browsers to show we have a safe
green address bar (with the lock icon)

since there's no "exception" rule, we need to post process before publish
to public site and fix this links:

the links that I identified are:

//apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/



//apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/



//apache-royale-users.20374.n8.nabble.com/



//apache-royale-development.20373.n8.nabble.com/



and add to all of this "http:"


I updated release manage website info here with this data:

https://github.com/apache/royale-asjs/wiki/Release-Manger-(Web-Site)





El jue., 30 may. 2019 a las 10:03, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Yes it will resolve the problem.
>
> czw., 30 maj 2019 o 09:50 Carlos Rovira 
> napisał(a):
>
> > So,
> >
> > should I change Nabble links in this page:
> >
> > https://royale.apache.org/mailing-lists/
> >
> > like this one:
> >
> > https://apache-royale-users.20374.n8.nabble.com/
> >
> > to
> >
> > http://apache-royale-users.20374.n8.nabble.com/
> >
> > ?
> >
> > this should solve the problem?
> >
> > thanks
> >
> >
> > El jue., 30 may. 2019 a las 7:47, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>)
> > escribió:
> >
> > > Hi Guys,
> > >
> > > -1 for removing babble from the list.
> > >
> > > +1 For switching to http.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Thu, May 30, 2019, 6:10 AM Harbs  wrote:
> > >
> > > > More details in this link:
> > > > http://support.nabble.com/HTTPS-SSL-urgent-td7594627.html#a7594635 <
> > > > http://support.nabble.com/HTTPS-SSL-urgent-td7594627.html#a7594635>
> > > >
> > > > Simply put: Nabble does not support https.
> > > >
> > > > We can either keep those links as http, or get rid of Nabble…
> > > >
> > > > Harbs
> > > >
> > > > > On May 30, 2019, at 6:26 AM, Harbs  wrote:
> > > > >
> > > > > Looks like a problem with https on Nabble:
> > > > >
> > > >
> > >
> >
> http://support.nabble.com/problem-with-security-certificate-with-nabble-forum-td7597896.html
> > > > <
> > > >
> > >
> >
> http://support.nabble.com/problem-with-security-certificate-with-nabble-forum-td7597896.html
> > > > >
> > > > >
> > > > >> On May 29, 2019, at 10:42 PM, QA   > > > flexcapaci...@gmail.com>> wrote:
> > > > >>
> > > > >> Is anyone else getting errors when viewing the mailing list from
> the
> > > > web page?
> > > > >>
> > > > >> https://royale.apache.org/mailing-lists/ <
> > > > https://royale.apache.org/mailing-lists/>
> > > > >>
> > > > >> This server could not prove that it is*
> > > > apache-royale-development.20373.n8.nabble.com*;
> > > > >>
> > > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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

Re: Language improvements

[Carlos Rovira]

Hi,

@Alex Harui  I think you misunderstood me. I'm not saying
we should "remove choices". What I say is that we have finally a more
robust implementation and we can evolve to have more choices from that
point. I think continue from that safe point will give us many benefits. So
I want those choices. What I don't want is to wait to make it perfect to
merge. As I said before perfection is enemy of the progress.

An important point I can't agree with you: Why we don't use Vector in our
production App? Cause we can't. To do that we need: a) Greg changes merged,
b) make AMF understand Vectors (still to be done to make Vector usable for
us). Without both points Vectors are not an option for us. So I think the
premise of "we have 2 apps in production without Vectors" are not right. We
don't have still Jewel DataGrid, or Swiz Global Dispatcher, and that does
not mean it's ok for us. Is just we still don't have it, but making us to
make our product without all of that is a serious issue that we need to
workaround in some way. But we can do that as something "temporal", due to
current Royale limitations. But our goal is to have all that, Vector-AMF
included :)

For this reason, I prefer to have Greg's Vector now, since it makes our
production App be one step closer to remove current workarounds :)
And I'm sure that not having a Vector solution like this, could be a reason
why some people still didn't try Royale to migrate to this date.
So if you ask me or those people for a "priority path", we will say "let's
get Vector first, then evolve from that to have more choices".
That's what I'm saying it's ok to merge now.

I'm ok with having Vector as we all know it from AS3 (since is that...AS3
Vector, don't forget that, and is what people expect to have at first
sight, then we can give them more choices and they will appreciate for
sure), and have as well a new Typed Array too as other proposed too. That
will be for me options. But we should not wait to make all that happen to
merge current branch, right?, All that we'll be lots of time to make it
perfect from day 0.

The key concept for me was what Harbs said in his response to the end. If
you don't use it the impact is 0, not 2-3k, since people don't have Vector
presence in their codes. So that's PAYG. For that reason it's ok for me to
merge and continue from that safe point, since we really only get positive
things and nothing negative, and since we all agree in the same terms, just
we need more time to continue evolving it to get to that perfect final
point.




El jue., 30 may. 2019 a las 7:56, Greg Dove ()
escribió:

> Harbs some quick comments inline...
>
> On Thu, May 30, 2019 at 4:27 PM Harbs  wrote:
>
> > The only niggle I have with my approach is that Vector in Flash is more
> > performant than array, while in JS, it’s going to be the other way
> around.
> > So if someone has a performance-sensitive piece of code, how should they
> > write it so it outputs as performant as possible on both platforms?
> >
> > Vector in flash is only substantially faster for its 3 numeric types
> which
> are optimized. It is (slightly) slower than Array in other cases - I think
> it is normal that the extra type checking takes time even in native code.
> I remember seeing some data which said it was 30% slower for some methods
> with the non-primitive types, but that may be old.
>
> In terms of the emulation version, you can get javascript Array speed with
> the index access and assignment, which should be a direct copy of the same
> parts of code that are heavily optimized in flash I think.
>
> I was running performance tests on the non-debug flash player alongside
> javascript. I actually see the regular native javascript Array beating
> flash numeric Vectors in Chrome on windows, for the same tasks. Perhaps the
> pepper plugin is getting less cpu resource than the browser or something
> like that, not sure. I had assumed TypedArrays would be faster, but
> recently you said you weren't sure because of js engine smarts. I will
> still check that.
>
>
>
> > I have not spent the time looking into the implementation, but I think
> > there might be some cross-communication. My understanding from what Greg
> > wrote is that if Vector is not used in an application, there will be no
> > extra code due to dead code removal. If that’s correct, I think we’re in
> > agreement that the implementation is fine. Do I understand correctly?
> >
>
> That is correct.
>
>
> >
> > Harbs
> >
> > > On May 30, 2019, at 1:26 AM, Josh Tynjala 
> > wrote:
> > >
> > > I definitely want the default choice to have as few surprises as
> > possible when it comes to how ActionScript behaves in Royale. We'll never
> > have a perfect emulation, of course, but there are things that I think
> can
> > still be improved. At the same time, I think it's perfectly valid for
> > someone to want to opt into a typed Array that doesn't have the runtime
> > overhead of Vector and isn't as heavy in file size. I'm wary of 

Re: Error on mailing list page

[Piotr Zarzycki]

Yes it will resolve the problem.

czw., 30 maj 2019 o 09:50 Carlos Rovira 
napisał(a):

> So,
>
> should I change Nabble links in this page:
>
> https://royale.apache.org/mailing-lists/
>
> like this one:
>
> https://apache-royale-users.20374.n8.nabble.com/
>
> to
>
> http://apache-royale-users.20374.n8.nabble.com/
>
> ?
>
> this should solve the problem?
>
> thanks
>
>
> El jue., 30 may. 2019 a las 7:47, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Hi Guys,
> >
> > -1 for removing babble from the list.
> >
> > +1 For switching to http.
> >
> > Thanks,
> > Piotr
> >
> > On Thu, May 30, 2019, 6:10 AM Harbs  wrote:
> >
> > > More details in this link:
> > > http://support.nabble.com/HTTPS-SSL-urgent-td7594627.html#a7594635 <
> > > http://support.nabble.com/HTTPS-SSL-urgent-td7594627.html#a7594635>
> > >
> > > Simply put: Nabble does not support https.
> > >
> > > We can either keep those links as http, or get rid of Nabble…
> > >
> > > Harbs
> > >
> > > > On May 30, 2019, at 6:26 AM, Harbs  wrote:
> > > >
> > > > Looks like a problem with https on Nabble:
> > > >
> > >
> >
> http://support.nabble.com/problem-with-security-certificate-with-nabble-forum-td7597896.html
> > > <
> > >
> >
> http://support.nabble.com/problem-with-security-certificate-with-nabble-forum-td7597896.html
> > > >
> > > >
> > > >> On May 29, 2019, at 10:42 PM, QA  > > flexcapaci...@gmail.com>> wrote:
> > > >>
> > > >> Is anyone else getting errors when viewing the mailing list from the
> > > web page?
> > > >>
> > > >> https://royale.apache.org/mailing-lists/ <
> > > https://royale.apache.org/mailing-lists/>
> > > >>
> > > >> This server could not prove that it is*
> > > apache-royale-development.20373.n8.nabble.com*;
> > > >>
> > > >
> > >
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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

Re: Error on mailing list page

[Carlos Rovira]

So,

should I change Nabble links in this page:

https://royale.apache.org/mailing-lists/

like this one:

https://apache-royale-users.20374.n8.nabble.com/

to

http://apache-royale-users.20374.n8.nabble.com/

?

this should solve the problem?

thanks


El jue., 30 may. 2019 a las 7:47, Piotr Zarzycki ()
escribió:

> Hi Guys,
>
> -1 for removing babble from the list.
>
> +1 For switching to http.
>
> Thanks,
> Piotr
>
> On Thu, May 30, 2019, 6:10 AM Harbs  wrote:
>
> > More details in this link:
> > http://support.nabble.com/HTTPS-SSL-urgent-td7594627.html#a7594635 <
> > http://support.nabble.com/HTTPS-SSL-urgent-td7594627.html#a7594635>
> >
> > Simply put: Nabble does not support https.
> >
> > We can either keep those links as http, or get rid of Nabble…
> >
> > Harbs
> >
> > > On May 30, 2019, at 6:26 AM, Harbs  wrote:
> > >
> > > Looks like a problem with https on Nabble:
> > >
> >
> http://support.nabble.com/problem-with-security-certificate-with-nabble-forum-td7597896.html
> > <
> >
> http://support.nabble.com/problem-with-security-certificate-with-nabble-forum-td7597896.html
> > >
> > >
> > >> On May 29, 2019, at 10:42 PM, QA  > flexcapaci...@gmail.com>> wrote:
> > >>
> > >> Is anyone else getting errors when viewing the mailing list from the
> > web page?
> > >>
> > >> https://royale.apache.org/mailing-lists/ <
> > https://royale.apache.org/mailing-lists/>
> > >>
> > >> This server could not prove that it is*
> > apache-royale-development.20373.n8.nabble.com*;
> > >>
> > >
> >
> >
>


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

Re: New apache-royale questions for May 29 - Stack Exchange

[Piotr Zarzycki]

Cool! It looks like tag notifier is working ;)

czw., 30 maj 2019 o 09:27 Stack Exchange
 napisał(a):

> ***1 new question in [ApacheRoyale Tag Notifications filter](<
> https://stackexchange.com/filters/368073/apacheroyale-tag-notifications>)
> on stackexchange.com***
>
>
> [what is the equivalent concept in apache royale for flexmdi.swc ,
> flexlib.swc](<
> https://stackoverflow.com/questions/56367416/what-is-the-equivalent-concept-in-apache-royale-for-flexmdi-swc-flexlib-swc
> >)
>
> when i am migrating the flex to royale application , i am unable to
> implement the concept MDIWindow Concept in royale. i am able to find in
> Visual Studio Code IDE the implementation //Generated from: ...
>
> Tagged: flex
>
> by [Naresh_Nalla]()
> on 
>
> 
>
>
>
> [Unsubscribe from this filter](<
> https://stackexchange.com/email/unsubscribe-filter/840884/851118678?code=8lXsEHhI9I9JRuj20Ovh2SoyxUtn0WUQp%2bSJLerBHhA%3d>)
> or change your email preferences by visitingyour [filter subscriptions page
> on stackexchange.com](<
> https://stackexchange.com/users/15455638?tab=subscriptions>).
>
> If you no longer want to receive mail from Stack Exchange, unsubscribe
> from all stackexchange.com emails <
> https://stackexchange.com/email/manage/1558066/15f7d9cde7a7a685bf80f41600ebb4c7e80eaaa66cc8f3032cea1082f1dfb25d
> >
> Questions? Comments? Let us know on our feedback site at <
> https://meta.stackexchange.com>.
>
> Stack Exchange, Inc. 110 William St, 28th Floor, NY NY 10038
>
>

-- 

Piotr Zarzycki

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

New apache-royale questions for May 29 - Stack Exchange

[Stack Exchange]

***1 new question in [ApacheRoyale Tag Notifications 
filter]()
 on stackexchange.com***


[what is the equivalent concept in apache royale for flexmdi.swc , 
flexlib.swc]()

when i am migrating the flex to royale application , i am unable to implement 
the concept MDIWindow Concept in royale. i am able to find in Visual Studio 
Code IDE the implementation //Generated from: ...

Tagged: flex

by [Naresh_Nalla]() on 






[Unsubscribe from this 
filter]()
 or change your email preferences by visitingyour [filter subscriptions page on 
stackexchange.com]().

If you no longer want to receive mail from Stack Exchange, unsubscribe from all 
stackexchange.com emails 

Questions? Comments? Let us know on our feedback site at 
.

Stack Exchange, Inc. 110 William St, 28th Floor, NY NY 10038