Re: Publishing royale to npm

Sounds good. > On Nov 13, 2017, at 10:41 AM, OmPrakash Muppirala > wrote: > > BTW, I just realized that we don't have a royale-utilities git repo. I am > tempted to simply put the npm related code into royale-asjs/npm directory > and add it as an exclude in the

Re: Publishing royale to npm

BTW, I just realized that we don't have a royale-utilities git repo. I am tempted to simply put the npm related code into royale-asjs/npm directory and add it as an exclude in the build.xml. Any objections? Thanks, Om On Sun, Nov 12, 2017 at 1:58 PM, Harbs wrote: > If

Re: Release Philosophy (was Re: [Website] Getting content ready to publish)

Hi Piotr, ok, as we are still in preview site, not published, I think is better to wait for the final link. One thing is confusing me is that status link is more legit ( builds.apache.org) than the nightly links (apacheflexbuild.cloudapp.net) I think in a final stage we should not have

Re: Release Philosophy (was Re: [Website] Getting content ready to publish)

That's what I think so. I was trying to also login into account, but when I'm going to admin page it doesn't ask me for a new password, but rather redirect me to the login page. I tried to reset password, but it didn't help. Piotr 2017-11-13 13:11 GMT+01:00 Carlos Rovira

Re: Release Philosophy (was Re: [Website] Getting content ready to publish)

Hi Piotr, I'm fine with the decisions you would like to take regarding that links. I just setup an initial layout. So, if I understand well I must to remove only the status link? 2017-11-13 12:42 GMT+01:00 Piotr Zarzycki : > Carlos, > > I'm not convinced that we

Re: Release Philosophy (was Re: [Website] Getting content ready to publish)

Carlos, I'm not convinced that we should move framework build from Alex's Azure PC. It is really convenient if something went wrong to just connect with the PC. If you would like to have distribution build under Apache umbrella you will need to fight with Infra about that. Maven is building on

Re: Apache Royale Examples Blog Category

Hi Alex, both sites are possible since both allows code to be posted. But I think our own blog could be better for the following points: * We can embed the result App in the same page for each example. * The plugin I use support code coloring for MXML and AS3, don't know if GitHub will represent

Re: Release Philosophy (was Re: [Website] Getting content ready to publish)

Hi Piotr, I removed that part, please, check. As well I sent you private for access info thanks 2017-11-13 13:21 GMT+01:00 Piotr Zarzycki : > That's what I think so. > > I was trying to also login into account, but when I'm going to admin page > it doesn't ask me for

Re: Royale ASDoc Reference link

Hi Carlos, There is an application which Alex build ASDoc in the examples. [1] You can link to Alex's server, but maybe it is worth to deploy somewhere that example ? [1]

Re: Royale ASDoc Reference link

Good plan. It would be great if we could automatically update the json files on the website repo automatically so the app is always up to date. We can figure out how to do that afterwards. > On Nov 13, 2017, at 4:22 PM, Carlos Rovira wrote: > > Thanks, > > we can

Re: [royale-asjs] 01/01: First (non-working) version

I need some help here. The code should be working, but the bead is added before the children are added, so the styles and attributes are not applied. Any ideas on how to delay the execution until after the full tree of children are added? Thanks, Harbs > On Nov 13, 2017, at 2:57 PM,

RE: [royale-asjs] 01/01: First (non-working) version

Why not listen to the container’s ‘initComplete’? Also, doesn’t DisableBead work for containers as is? From: Piotr Zarzycki Sent: Monday, November 13, 2017 3:15:54 PM To: dev@royale.apache.org Subject: Re: [royale-asjs] 01/01: First

Royale ASDoc Reference link

Hi, could someone provide the link to ASDoc for Royale? (if we have something already up) Is to link in the website thanks -- Carlos Rovira http://about.me/carlosrovira

Apache Royale Team Page

Hi, I have an initial draft of the team page. Please review it and request changes: http://royale.codeoscopic.com/team/ * I get the list of PMCs from here: https://projects.apache.org/committee.html?royale, we have no committers. * For Mentors, I assume Dave is the only one. * I get the photos

RE: [royale-asjs] 01/01: First (non-working) version

It looks like initComplete is called after children are initialized [1] I would add the focus disable behavior as a separate bead as Piotr suggested (similar to DisabledAlphaBead). [1] https://github.com/yishayw/Examples/tree/initComplete From: Harbs

Re: Apache Royale Team Page

Hi Carlos, It looks nice :) I see that you are mentioning "JIRA" should be GitHub. I will send you my photo off list. We should have at least clickable names if someone would like to know about us more. Thoughts ? Piotr 2017-11-13 15:33 GMT+01:00 Carlos Rovira : >

Re: [royale-asjs] 01/01: First (non-working) version

Yishay, Thanks for the info! Precious! :) Piotr 2017-11-13 16:03 GMT+01:00 Yishay Weiss : > It looks like initComplete is called after children are initialized [1] > > > > I would add the focus disable behavior as a separate bead as Piotr > suggested (similar to

Re: [royale-asjs] 01/01: First (non-working) version

I don’t think it’s after children are added. That’s why I asked. I’ll try to check later. > On Nov 13, 2017, at 3:36 PM, Piotr Zarzycki wrote: > > Maybe it's even should be split into two separate bead. > > As for your question - initComplete is fired in

Re: Royale ASDoc Reference link

Thanks, we can put that link for now, but I state in the website that is temporal. I think we could host in with the website in royale.apache.org For styling, we can go through as a next step in put all documentation organized and usable with a good looking. Since this website is easy to update

Re: [royale-asjs] 01/01: First (non-working) version

Is initComplete fired after all the children are added? > Also, doesn’t DisableBead work for containers as is? No. DisableBead helps in so far as you can’t select using the mouse, but you can still select using the keyboard by tabbing though controls. For that to work, you need to disable

Re: Royale ASDoc Reference link

I just tried to improve the styling of the app, but it’s not working locally, when I build. Is there a trick to get it to work? > On Nov 13, 2017, at 3:25 PM, Piotr Zarzycki wrote: > > Hi Carlos, > > There is an application which Alex build ASDoc in the examples.

Re: Royale ASDoc Reference link

Sounds Great Harbs :) 2017-11-13 15:26 GMT+01:00 Harbs : > Good plan. > > It would be great if we could automatically update the json files on the > website repo automatically so the app is always up to date. We can figure > out how to do that afterwards. > > > On Nov 13,

Re: [royale-asjs] 01/01: First (non-working) version

You might be better off using childrenAdded. It should fire once for the entire set of children specified in MXML, and once for each child added via AS, which you might need if a child is added "later". My 2 cents, -Alex On 11/13/17, 7:09 AM, "Piotr Zarzycki" wrote:

Re: [royale-asjs] branch develop updated: [WAST] batch script for WASTC and an early example project

I'm so so happy that you back to us! :) <3 Piotr 2017-11-13 19:16 GMT+01:00 Erik de Bruin : > My status and plans in short: > > There is now a separate and independent transpiler, WASTC, (in the > 'feature/wast' branch), which is addressed through the >

Re: Apache Royale Examples Blog Category

IMO, the most important piece is to make sure all examples are under Apache license so they can be shared, updated, PR'd, tracked, etc, the same way any other code and documentation is handled. Building a useful site from assets stored in a GH repo sounds like a great Royale app, including a

Re: [royale-asjs] branch develop updated: [WAST] batch script for WASTC and an early example project

My status and plans in short: There is now a separate and independent transpiler, WASTC, (in the 'feature/wast' branch), which is addressed through the 'royale-asjs/wast/bin/wastc' script. There is no specific visitors yet for the transpilation, so it's putting out what you put in, but hey, the

Re: [royale-asjs] 01/01: First (non-working) version

I would like to add that "childrenAdded" is the first event which is fire, "initComplete" may happen a bit later. If someone override addedToParent in the sub class of UIBase will probably dispatch "initComplete" once do some other stuff. You should use childrenAdded as long as you are do not

Re: [royale-asjs] 01/01: First (non-working) version

That’s what I was looking for. Thanks! > On Nov 13, 2017, at 6:42 PM, Alex Harui wrote: > > You might be better off using childrenAdded. It should fire once for the > entire set of children specified in MXML, and once for each child added > via AS, which you might

Re: [royale-asjs] 01/01: First (non-working) version

Maybe. That’s probably more PAYG. https://github.com/apache/royale-asjs/issues/80 > On Nov 13, 2017, at 5:03 PM, Yishay Weiss wrote: > > I would add the focus disable behavior as a separate bead as Piotr suggested >

Re: [royale-asjs] 01/01: First (non-working) version

Sure. Nitpick away! ;-) > On Nov 13, 2017, at 8:37 PM, Piotr Zarzycki wrote: > > Harbs, > > I shout you couple of question in the commit. I hope you are not > overwhelming by my constant Code Inspection! > > Thanks, Piotr > > 2017-11-13 19:29 GMT+01:00 Harbs

Re: [royale-asjs] 01/01: First (non-working) version

Harbs, I shout you couple of question in the commit. I hope you are not overwhelming by my constant Code Inspection! Thanks, Piotr 2017-11-13 19:29 GMT+01:00 Harbs : > That’s what I was looking for. > > Thanks! > > > On Nov 13, 2017, at 6:42 PM, Alex Harui

Re: [royale-asjs] branch develop updated: [WAST] batch script for WASTC and an early example project

Hi Erik, seems like a reliable roadmap. Wish you luck on the trip :) 2017-11-13 19:20 GMT+01:00 Piotr Zarzycki : > I'm so so happy that you back to us! :) <3 > > Piotr > > > 2017-11-13 19:16 GMT+01:00 Erik de Bruin : > > > My status and plans in

Re: [royale-asjs] 01/01: First (non-working) version

Harbs, First thought is register to "initComplete" for each children ? But does each of our children emit such event ? Piotr 2017-11-13 14:01 GMT+01:00 Harbs : > I need some help here. > > The code should be working, but the bead is added before the children are >

Re: [royale-asjs] 01/01: First (non-working) version

Maybe it's even should be split into two separate bead. As for your question - initComplete is fired in addedToParent, after all stuff which is done related to current component. Not sure if it's include children, but I would check and give the feedback cause it will be precious information.

Re: Apache Royale Team Page

Hi! 2017-11-13 15:40 GMT+01:00 Piotr Zarzycki : > Hi Carlos, > > It looks nice :) I see that you are mentioning "JIRA" should be GitHub. Thanks for seeing that! just update it :) > I > will send you my photo off list. We should have at least clickable names if >

Re: Apache Royale Examples Blog Category

Hi Alex, that sounds good to me. The main problem is as always timing. For me the "try it now" Royale App is a must and as well look-an-feel and a UI set that work flawlessly. With that in place, I think we can rework other things with Royale. But, for example, I'm starting on that path trying to