Re: Publishing royale to npm

[Harbs]

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 build.xml.  Any objections?
> 
> Thanks,
> Om
> 
> On Sun, Nov 12, 2017 at 1:58 PM, Harbs  wrote:
> 
>> If you call it 0.10.0, I think it’s pretty clear.
>> 
>>> On Nov 12, 2017, at 11:46 PM, Idylog - Nicolas Granon <
>> ngra...@idylog.com> wrote:
>>> 
>>> In developer's eyes, "0.10" is "lower" than "0.9".
>>> 
>>> You'd better number it as "0.91".
>>> 
>>> Nicolas Granon
>>> 
>>> 
>>> 
 -Message d'origine-
 De : Harbs [mailto:harbs.li...@gmail.com]
 Envoyé : dimanche 12 novembre 2017 10:15
 À : dev@royale.apache.org
 Objet : Re: Publishing royale to npm
 
 We’ve fixed a lot of things since 0.8.
 
 0.9 does not need to jump to 1.0. We can have 0.10 (and 0.11…)
 
 I’d really like to streamline the release process so it’s painless
 enough to release every couple/few weeks.
 
 Harbs
 
> On Nov 12, 2017, at 10:35 AM, Carlos Rovira 
 wrote:
> 
> Hi,
> 
> about version number, I'll feel more happy with 0.8 than 0.9 My point
> is that we are getting a first release of Royale and is the same that
> FlexJS 0.8 but with some new fixes and little things.
> As well I can see many things to do to reach 1.0, and would be great
> to have still an intermediate release 0.9
> 
> 
> 
> 2017-11-11 22:10 GMT+01:00 OmPrakash Muppirala
 :
> 
>> On Thu, Nov 9, 2017 at 6:41 PM, Alex Harui
 
>> wrote:
>> 
>>> That might work.  One question:  we want the same bits that were
>> published
>>> as 0.9.0-rc1 to become the final bits where you would do:
>>> 
>>> npm install -g apache-royale
>>> 
>>> We aren't supposed to rebuild anything.  For Maven the same bits
>>> from staging get copied to Maven central, for Ant/IDE the same bits
>>> are moved (not copied) from dist/dev to dist/release.  So is it
 true
>>> that the RM
>> can
>>> publish the final bits by taking the same bits that were once
>>> published via
>> 
>> 
>>> 
>>> npm publish --tag 0.9.0-rc1
>>> 
>>> as the final release?  What does the RM to do make that happen?
 Just:
>>> 
>>> 
>>> npm publish
>>> 
>>> without any tag?
>>> 
>> 
>> The rc1 would be in the /dev/ area of the dist site.  We will use a
>> useMirror=false flag while attempting to download the specified sdk.
>> This will bypass the mirror urls and directly load it from the dist
 site.
>> 
>> For the nightlies, it would be similar, except we can use the direct
>> url of the lastSuccessfulArtifact directory in Jenkins.
>> 
>> When the release candidate artifacts get promoted to GA, they will
 be
>> available via mirrors.  So, we will push a new release to npm with
>> the new version number, which simply is new package.json file with
>> the correct paths to the sdk artifacts.
>> 
>> I plan to write a script called: publish-to-npm which can be invoked
>> like
>> this:
>> 
>> ./publish-to-npm -- -nightly=true version=0.9.0 ./publish-to-npm --
>> -rc=true version=0.9.0 ./publish-to-npm -- -ga=true version=0.9.0
>> 
>> The script will take care of setting up the correct values in
>> package.json and will publish it to npmjs.org.
>> 
>> The values would be:
>> Nightly:
>> "royale_path_binary": "
>> http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jsonly/
>> lastSuccessfulBuild/artifact/out/
>> ",
>> "royale_file_name": "apache-royale-jsonly-0.9.0-bin.zip",
>> "useMirror": false
>> 
>> This will be published as: npm publish --tag nightly
>> 
>> RC:
>> "royale_path_binary": "
>> https://dist.apache.org/repos/dist/dev/royale/sdk/0.9.0/rc1/;,
>> "royale_file_name": "apache-royale-jsonly-0.9.0-bin.zip",
>> "useMirror": false
>> 
>> This will be published as: npm publish --tag 0.9.0-rc1
>> 
>> GA:
>> "royale_path_binary": "/dist/release/royale/sdk/0.9.0/",
>> "royale_file_name": "apache-royale-jsonly-0.9.0-bin.zip",
>> "useMirror": true
>> 
>> This will be published as: npm publish
>> 
>> When we move to the next version, we need to up the version number
 to
>> the next one and push a nightly tag out.
>> P.S.  All this assumes that there are no changes in the packaging
 logic.
>> 
>> Thanks,
>> Om
>> 
>> 
>>> 
>>> Seems reasonable for the RM to have Node.js and npm installed.
>>> 
>>> Thanks,
>>> -Alex
>>> 
>>> On 11/9/17, 

Re: Publishing royale to npm

[OmPrakash Muppirala]

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 you call it 0.10.0, I think it’s pretty clear.
>
> > On Nov 12, 2017, at 11:46 PM, Idylog - Nicolas Granon <
> ngra...@idylog.com> wrote:
> >
> > In developer's eyes, "0.10" is "lower" than "0.9".
> >
> > You'd better number it as "0.91".
> >
> > Nicolas Granon
> >
> >
> >
> >> -Message d'origine-
> >> De : Harbs [mailto:harbs.li...@gmail.com]
> >> Envoyé : dimanche 12 novembre 2017 10:15
> >> À : dev@royale.apache.org
> >> Objet : Re: Publishing royale to npm
> >>
> >> We’ve fixed a lot of things since 0.8.
> >>
> >> 0.9 does not need to jump to 1.0. We can have 0.10 (and 0.11…)
> >>
> >> I’d really like to streamline the release process so it’s painless
> >> enough to release every couple/few weeks.
> >>
> >> Harbs
> >>
> >>> On Nov 12, 2017, at 10:35 AM, Carlos Rovira 
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> about version number, I'll feel more happy with 0.8 than 0.9 My point
> >>> is that we are getting a first release of Royale and is the same that
> >>> FlexJS 0.8 but with some new fixes and little things.
> >>> As well I can see many things to do to reach 1.0, and would be great
> >>> to have still an intermediate release 0.9
> >>>
> >>>
> >>>
> >>> 2017-11-11 22:10 GMT+01:00 OmPrakash Muppirala
> >> :
> >>>
>  On Thu, Nov 9, 2017 at 6:41 PM, Alex Harui
> >> 
>  wrote:
> 
> > That might work.  One question:  we want the same bits that were
>  published
> > as 0.9.0-rc1 to become the final bits where you would do:
> >
> > npm install -g apache-royale
> >
> > We aren't supposed to rebuild anything.  For Maven the same bits
> > from staging get copied to Maven central, for Ant/IDE the same bits
> > are moved (not copied) from dist/dev to dist/release.  So is it
> >> true
> > that the RM
>  can
> > publish the final bits by taking the same bits that were once
> > published via
> 
> 
> >
> > npm publish --tag 0.9.0-rc1
> >
> > as the final release?  What does the RM to do make that happen?
> >> Just:
> >
> >
> > npm publish
> >
> > without any tag?
> >
> 
>  The rc1 would be in the /dev/ area of the dist site.  We will use a
>  useMirror=false flag while attempting to download the specified sdk.
>  This will bypass the mirror urls and directly load it from the dist
> >> site.
> 
>  For the nightlies, it would be similar, except we can use the direct
>  url of the lastSuccessfulArtifact directory in Jenkins.
> 
>  When the release candidate artifacts get promoted to GA, they will
> >> be
>  available via mirrors.  So, we will push a new release to npm with
>  the new version number, which simply is new package.json file with
>  the correct paths to the sdk artifacts.
> 
>  I plan to write a script called: publish-to-npm which can be invoked
>  like
>  this:
> 
>  ./publish-to-npm -- -nightly=true version=0.9.0 ./publish-to-npm --
>  -rc=true version=0.9.0 ./publish-to-npm -- -ga=true version=0.9.0
> 
>  The script will take care of setting up the correct values in
>  package.json and will publish it to npmjs.org.
> 
>  The values would be:
>  Nightly:
>  "royale_path_binary": "
>  http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jsonly/
>  lastSuccessfulBuild/artifact/out/
>  ",
>  "royale_file_name": "apache-royale-jsonly-0.9.0-bin.zip",
>  "useMirror": false
> 
>  This will be published as: npm publish --tag nightly
> 
>  RC:
>  "royale_path_binary": "
>  https://dist.apache.org/repos/dist/dev/royale/sdk/0.9.0/rc1/;,
>  "royale_file_name": "apache-royale-jsonly-0.9.0-bin.zip",
>  "useMirror": false
> 
>  This will be published as: npm publish --tag 0.9.0-rc1
> 
>  GA:
>  "royale_path_binary": "/dist/release/royale/sdk/0.9.0/",
>  "royale_file_name": "apache-royale-jsonly-0.9.0-bin.zip",
>  "useMirror": true
> 
>  This will be published as: npm publish
> 
>  When we move to the next version, we need to up the version number
> >> to
>  the next one and push a nightly tag out.
>  P.S.  All this assumes that there are no changes in the packaging
> >> logic.
> 
>  Thanks,
>  Om
> 
> 
> >
> > Seems reasonable for the RM to have Node.js and npm installed.
> >
> > Thanks,
> > -Alex
> >
> > On 11/9/17, 6:28 PM, "omup...@gmail.com on behalf of OmPrakash
>  Muppirala"
> >  wrote:
> >
> >> For staging 

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

[Carlos Rovira]

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 "apacheflexbuild" right?
But status seems ok to me at first sight

thanks

2017-11-12 20:04 GMT+01:00 Piotr Zarzycki :

> Another thing is: "Apache Royale Jenkings Job Status" - This status showing
> the state of Maven build which is hosted on builds.apache.org. Since we
> are
> using Alex's machine for producing ditribution package for developers we
> should not have it this link on the website.
>
> Maven is able to build distribution package, but so far it's missing some
> things and you can use that package only for code completion purposes in
> your IDE either Moonshine or VSCode. If I find resources I hope I will fix
> it and we can then linking to Maven build.
>
> Thanks Carslo for that website! :)
> Piotr
>
>
> 2017-11-12 18:42 GMT+01:00 Piotr Zarzycki :
>
> > Hi Carlos,
> >
> > Here you go links to Royale. I see proper names. Royale [1] JS Only [2].
> I
> > did just quick look and when I came to the website I started to search
> this
> > information that Nightly is not for production. After w while I have
> found
> > this red rectangle. I think font size could be a bit bigger there.
> >
> > [1] http://apacheflexbuild.cloudapp.net:8080/job/royale-
> > asjs/lastSuccessfulBuild/artifact/out/
> > [2] http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jsonly/
> > lastSuccessfulBuild/artifact/out/
> >
> > Piotr
> >
> >
> >
> > 2017-11-12 18:30 GMT+01:00 Carlos Rovira :
> >
> >> Hi,
> >>
> >> here's the download page for you to review.
> >>
> >> http://royale.codeoscopic.com/download/
> >>
> >> Some things to mention:
> >>
> >> * As we already don't have release binaries, the first section could be
> >> consider under construction
> >> * For nightly builds I use the links posted by Alex in October. I think
> >> those links are somewhat temporal since are labeled in "FlexJS" instead
> of
> >> "RoyaleJS" or something and he mentions the to rename in the future.
> >>
> >> You can check if links are the expected, or we need to put something
> more.
> >>
> >> Take into account that the info is what I found navigating through the
> >> mailing list and since I'm not a user of that links, although we will
> need
> >> to update as we get final names, they can be wrong links at this time.
> >>
> >> Hope you guys could let me know what is right and wrong
> >>
> >> Thanks
> >>
> >> Carlos
> >>
> >>
> >>
> >>
> >>
> >> 2017-11-11 11:35 GMT+01:00 Carlos Rovira :
> >>
> >> > Hi Alex,
> >> >
> >> > as in lots of things in life I think we should get to some point in
> the
> >> > middle. I think it would be bad if we try to make lots of components
> in
> >> few
> >> > time, since as you said, we don't know what things people will need
> >> > nowadays. I like your point about "we don't need to mimic Flex 4.x",
> for
> >> > example, a cool Date component should work seamlessly in mobile and
> >> > desktop, so better to create a royale one than try to get Flex 4
> >> > DateChooser and DateSpinner, since we have in flex both due to the way
> >> Flex
> >> > was evolving through the years. They worked great for the web and
> >> desktop,
> >> > but suddenly a new mobile world emerge and they must respect the old
> >> way to
> >> > do things.
> >> >
> >> > In the other hand, I think it would be very bad for us to left things
> >> > completely to users demand. We know right now that some components are
> >> > needed and we can propose others as well.
> >> >
> >> > I think I'll better create a new thread since I think this one was
> more
> >> > about releases and nightly builds so we can stay on focus
> >> >
> >> >
> >> > Thanks
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > 2017-11-11 8:04 GMT+01:00 Alex Harui :
> >> >
> >> >> Well, I would love to be wrong about "few years", but I know I
> wouldn't
> >> >> bet any money on knowing what components and features our users who
> are
> >> >> migrating from Flex are going to need.  And I would hope we don't
> have
> >> to
> >> >> say to any users "well, we don't have that component/feature so too
> >> bad",
> >> >> unless it is a really extensive and expensive component that we don't
> >> have
> >> >> the committer-power to reproduce.   Maybe we do have the ability to
> >> gather
> >> >> that list of components/features up front, but I am expecting that we
> >> are
> >> >> going to have to be demand-driven.  Whoever signs up to migrate to
> >> Royale
> >> >> will have my priority just like Harbs and Yishay did.  I did not ask
> >> them
> >> >> to commit up front to what they needed, they started migrating and
> >> asked
> >> >> for stuff and we made it happen.  I 

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

[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 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 :

> 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 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 Apache
> > servers, Chris handle that. I would rather not invest the time in that
> > since we have working everything on Alex PC, but that's just mine
> > convenient and save time view. :)
> >
> > Piotr
> >
> >
> > 2017-11-13 12:36 GMT+01:00 Carlos Rovira :
> >
> > > 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 "apacheflexbuild" right?
> > > But status seems ok to me at first sight
> > >
> > > thanks
> > >
> > > 2017-11-12 20:04 GMT+01:00 Piotr Zarzycki :
> > >
> > > > Another thing is: "Apache Royale Jenkings Job Status" - This status
> > > showing
> > > > the state of Maven build which is hosted on builds.apache.org. Since
> > we
> > > > are
> > > > using Alex's machine for producing ditribution package for developers
> > we
> > > > should not have it this link on the website.
> > > >
> > > > Maven is able to build distribution package, but so far it's missing
> > some
> > > > things and you can use that package only for code completion purposes
> > in
> > > > your IDE either Moonshine or VSCode. If I find resources I hope I
> will
> > > fix
> > > > it and we can then linking to Maven build.
> > > >
> > > > Thanks Carslo for that website! :)
> > > > Piotr
> > > >
> > > >
> > > > 2017-11-12 18:42 GMT+01:00 Piotr Zarzycki  >:
> > > >
> > > > > Hi Carlos,
> > > > >
> > > > > Here you go links to Royale. I see proper names. Royale [1] JS Only
> > > [2].
> > > > I
> > > > > did just quick look and when I came to the website I started to
> > search
> > > > this
> > > > > information that Nightly is not for production. After w while I
> have
> > > > found
> > > > > this red rectangle. I think font size could be a bit bigger there.
> > > > >
> > > > > [1] http://apacheflexbuild.cloudapp.net:8080/job/royale-
> > > > > asjs/lastSuccessfulBuild/artifact/out/
> > > > > [2] http://apacheflexbuild.cloudapp.net:8080/job/royale-
> asjs-jsonly/
> > > > > lastSuccessfulBuild/artifact/out/
> > > > >
> > > > > Piotr
> > > > >
> > > > >
> > > > >
> > > > > 2017-11-12 18:30 GMT+01:00 Carlos Rovira  >:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> here's the download page for you to review.
> > > > >>
> > > > >> http://royale.codeoscopic.com/download/
> > > > >>
> > > > >> Some things to mention:
> > > > >>
> > > > >> * As we already don't have release binaries, the first section
> could
> > > be
> > > > >> consider under construction
> > > > >> * For nightly builds I use the links posted by Alex in October. I
> > > think
> > > > >> those links are somewhat temporal since are labeled in "FlexJS"
> > > instead
> > > > of
> > > > >> "RoyaleJS" or something and he mentions the to rename in the
> future.
> > > > >>
> > > > >> You can check if links are the expected, or we need to put
> something
> > > > more.
> > > > >>
> > > > >> Take into account that the info is what I found navigating through
> > the
> > > > >> mailing list and since I'm not a user of that links, although we
> > will
> > > > need
> > > > >> to update as we get final names, they can be wrong links at this
> > time.
> > > > >>
> > > > >> Hope you guys could let me know what is right and wrong
> > > > >>
> > > > >> Thanks
> > > > >>
> > > > >> Carlos
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> 2017-11-11 11:35 GMT+01:00 Carlos Rovira  >:
> > > > >>
> > > > >> > Hi Alex,
> > > > >> >
> > > > >> > as in lots of things in life I think we should get to some point
> > in
> > > > the
> > > > >> > middle. I think it would be bad if we try to make lots of
> > components
> > > > in
> > > > >> few
> > > > >> > time, since as you said, we don't know what things people will
> > need
> > > > >> > nowadays. I like your point about "we don't need to 

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

[Carlos Rovira]

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 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 Apache
> servers, Chris handle that. I would rather not invest the time in that
> since we have working everything on Alex PC, but that's just mine
> convenient and save time view. :)
>
> Piotr
>
>
> 2017-11-13 12:36 GMT+01:00 Carlos Rovira :
>
> > 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 "apacheflexbuild" right?
> > But status seems ok to me at first sight
> >
> > thanks
> >
> > 2017-11-12 20:04 GMT+01:00 Piotr Zarzycki :
> >
> > > Another thing is: "Apache Royale Jenkings Job Status" - This status
> > showing
> > > the state of Maven build which is hosted on builds.apache.org. Since
> we
> > > are
> > > using Alex's machine for producing ditribution package for developers
> we
> > > should not have it this link on the website.
> > >
> > > Maven is able to build distribution package, but so far it's missing
> some
> > > things and you can use that package only for code completion purposes
> in
> > > your IDE either Moonshine or VSCode. If I find resources I hope I will
> > fix
> > > it and we can then linking to Maven build.
> > >
> > > Thanks Carslo for that website! :)
> > > Piotr
> > >
> > >
> > > 2017-11-12 18:42 GMT+01:00 Piotr Zarzycki :
> > >
> > > > Hi Carlos,
> > > >
> > > > Here you go links to Royale. I see proper names. Royale [1] JS Only
> > [2].
> > > I
> > > > did just quick look and when I came to the website I started to
> search
> > > this
> > > > information that Nightly is not for production. After w while I have
> > > found
> > > > this red rectangle. I think font size could be a bit bigger there.
> > > >
> > > > [1] http://apacheflexbuild.cloudapp.net:8080/job/royale-
> > > > asjs/lastSuccessfulBuild/artifact/out/
> > > > [2] http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jsonly/
> > > > lastSuccessfulBuild/artifact/out/
> > > >
> > > > Piotr
> > > >
> > > >
> > > >
> > > > 2017-11-12 18:30 GMT+01:00 Carlos Rovira :
> > > >
> > > >> Hi,
> > > >>
> > > >> here's the download page for you to review.
> > > >>
> > > >> http://royale.codeoscopic.com/download/
> > > >>
> > > >> Some things to mention:
> > > >>
> > > >> * As we already don't have release binaries, the first section could
> > be
> > > >> consider under construction
> > > >> * For nightly builds I use the links posted by Alex in October. I
> > think
> > > >> those links are somewhat temporal since are labeled in "FlexJS"
> > instead
> > > of
> > > >> "RoyaleJS" or something and he mentions the to rename in the future.
> > > >>
> > > >> You can check if links are the expected, or we need to put something
> > > more.
> > > >>
> > > >> Take into account that the info is what I found navigating through
> the
> > > >> mailing list and since I'm not a user of that links, although we
> will
> > > need
> > > >> to update as we get final names, they can be wrong links at this
> time.
> > > >>
> > > >> Hope you guys could let me know what is right and wrong
> > > >>
> > > >> Thanks
> > > >>
> > > >> Carlos
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> 2017-11-11 11:35 GMT+01:00 Carlos Rovira :
> > > >>
> > > >> > Hi Alex,
> > > >> >
> > > >> > as in lots of things in life I think we should get to some point
> in
> > > the
> > > >> > middle. I think it would be bad if we try to make lots of
> components
> > > in
> > > >> few
> > > >> > time, since as you said, we don't know what things people will
> need
> > > >> > nowadays. I like your point about "we don't need to mimic Flex
> 4.x",
> > > for
> > > >> > example, a cool Date component should work seamlessly in mobile
> and
> > > >> > desktop, so better to create a royale one than try to get Flex 4
> > > >> > DateChooser and DateSpinner, since we have in flex both due to the
> > way
> > > >> Flex
> > > >> > was evolving through the years. They worked great for the web and
> > > >> desktop,
> > > >> > but suddenly a new mobile world emerge and they must respect the
> old
> > > >> way to
> > > >> > do things.
> > > >> >
> > > >> > In the other hand, I think it would be very bad for us to left
> > things
> > > >> > 

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

[Piotr Zarzycki]

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 Apache
servers, Chris handle that. I would rather not invest the time in that
since we have working everything on Alex PC, but that's just mine
convenient and save time view. :)

Piotr


2017-11-13 12:36 GMT+01:00 Carlos Rovira :

> 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 "apacheflexbuild" right?
> But status seems ok to me at first sight
>
> thanks
>
> 2017-11-12 20:04 GMT+01:00 Piotr Zarzycki :
>
> > Another thing is: "Apache Royale Jenkings Job Status" - This status
> showing
> > the state of Maven build which is hosted on builds.apache.org. Since we
> > are
> > using Alex's machine for producing ditribution package for developers we
> > should not have it this link on the website.
> >
> > Maven is able to build distribution package, but so far it's missing some
> > things and you can use that package only for code completion purposes in
> > your IDE either Moonshine or VSCode. If I find resources I hope I will
> fix
> > it and we can then linking to Maven build.
> >
> > Thanks Carslo for that website! :)
> > Piotr
> >
> >
> > 2017-11-12 18:42 GMT+01:00 Piotr Zarzycki :
> >
> > > Hi Carlos,
> > >
> > > Here you go links to Royale. I see proper names. Royale [1] JS Only
> [2].
> > I
> > > did just quick look and when I came to the website I started to search
> > this
> > > information that Nightly is not for production. After w while I have
> > found
> > > this red rectangle. I think font size could be a bit bigger there.
> > >
> > > [1] http://apacheflexbuild.cloudapp.net:8080/job/royale-
> > > asjs/lastSuccessfulBuild/artifact/out/
> > > [2] http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jsonly/
> > > lastSuccessfulBuild/artifact/out/
> > >
> > > Piotr
> > >
> > >
> > >
> > > 2017-11-12 18:30 GMT+01:00 Carlos Rovira :
> > >
> > >> Hi,
> > >>
> > >> here's the download page for you to review.
> > >>
> > >> http://royale.codeoscopic.com/download/
> > >>
> > >> Some things to mention:
> > >>
> > >> * As we already don't have release binaries, the first section could
> be
> > >> consider under construction
> > >> * For nightly builds I use the links posted by Alex in October. I
> think
> > >> those links are somewhat temporal since are labeled in "FlexJS"
> instead
> > of
> > >> "RoyaleJS" or something and he mentions the to rename in the future.
> > >>
> > >> You can check if links are the expected, or we need to put something
> > more.
> > >>
> > >> Take into account that the info is what I found navigating through the
> > >> mailing list and since I'm not a user of that links, although we will
> > need
> > >> to update as we get final names, they can be wrong links at this time.
> > >>
> > >> Hope you guys could let me know what is right and wrong
> > >>
> > >> Thanks
> > >>
> > >> Carlos
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> 2017-11-11 11:35 GMT+01:00 Carlos Rovira :
> > >>
> > >> > Hi Alex,
> > >> >
> > >> > as in lots of things in life I think we should get to some point in
> > the
> > >> > middle. I think it would be bad if we try to make lots of components
> > in
> > >> few
> > >> > time, since as you said, we don't know what things people will need
> > >> > nowadays. I like your point about "we don't need to mimic Flex 4.x",
> > for
> > >> > example, a cool Date component should work seamlessly in mobile and
> > >> > desktop, so better to create a royale one than try to get Flex 4
> > >> > DateChooser and DateSpinner, since we have in flex both due to the
> way
> > >> Flex
> > >> > was evolving through the years. They worked great for the web and
> > >> desktop,
> > >> > but suddenly a new mobile world emerge and they must respect the old
> > >> way to
> > >> > do things.
> > >> >
> > >> > In the other hand, I think it would be very bad for us to left
> things
> > >> > completely to users demand. We know right now that some components
> are
> > >> > needed and we can propose others as well.
> > >> >
> > >> > I think I'll better create a new thread since I think this one was
> > more
> > >> > about releases and nightly builds so we can stay on focus
> > >> >
> > >> >
> > >> > Thanks
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > 2017-11-11 8:04 GMT+01:00 Alex Harui :
> > >> >
> > >> >> Well, I would love to be wrong about "few years", but I know I
> > wouldn't
> > >> >> 

Re: Apache Royale Examples Blog Category

[Carlos Rovira]

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 code in the same way
* Maybe organization is better since we use tags complementing search

I see Github good for the documentation and wiki but this part could work
better in our blog.

That's my opinion

Thanks



2017-11-13 9:03 GMT+01:00 Alex Harui :

> Is there an advantage to using a blog vs using a GitHub repo?
>
> -Alex
>
> On 11/11/17, 8:03 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi,
> >
> >we talked about committers and PMCs that want to contribute can get access
> >to the wordpress installation to collaborate.
> >Regarding other people we could setup wordpress for people to become
> >contributors and other committers and PMC could review content and
> >approve.
> >But don't know if this is allowed or people must sign first an ICLA to
> >declare that contributions are donated to Apache Royale.
> >
> >
> >
> >
> >
> >2017-11-11 15:54 GMT+01:00 gkk gb :
> >
> >> I completely agree. If it is open for more than one person to
> >>contribute,
> >> it should build up fairly quickly.
> >>
> >> > On November 10, 2017 at 2:30 PM Carlos Rovira wrote:
> >> >
> >> >
> >> > Hi,
> >> >
> >> > One thing I think it would be great would be to have something
> >>like
> >> Peter
> >> > deHaan blogs (Flex Examples, AIR Examples, ActionScript Examples)
> >> >
> >> > I made a test post and a hello world post in a blog category
> >>called
> >> "Royale
> >> > Examples"
> >> >
> >> >
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Froyale.co
> >>deoscopic.com%2Fcategory%2Froyale-examples%2F=02%
> 7C01%7C%7Cb7200a359
> >>8f04343d75608d5291dd6ce%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364
> >>60130496354658=Alojomc%2Fa%2BznHUyVP6OCuQpTuxGkhie%
> 2FvSb2d%2FI79wk%
> >>3D=0
> >> >
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Froyale.co
> >>deoscopic.com%2Fcreating-a-hello-world-in-=02%7C01%
> 7C%7Cb7200a3598f0
> >>4343d75608d5291dd6ce%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364601
> >>30496354658=laC5yIkV8DXIYron3q8YverGsg73Va
> %2FHvLIZM%2FkqMIU%3D
> >>rved=0
> >> apache-royale/
> >> >
> >> > One thing we need here is to complete this kind of post is to add
> >>the
> >> > working example so people could see final results.
> >> > Should we host in the same website? or maybe we should use another
> >> tool
> >> > (maybe JSFiddle could be used with Royale?, if so I think it can
> >>be
> >> > embedded in a post but then the content will be in JSFiddle and we
> >> need a
> >> > generic "apacheroyale" account there...)
> >> >
> >> > If we use tags like Peter did we can have an easy and fast way for
> >> people
> >> > to get to a concrete example.
> >> >
> >> > I think some of you want to have something like this. If this go
> >> forward, I
> >> > expect we all post examples
> >> >
> >> > Let me know what do you think.
> >> >
> >> > --
> >> > Carlos Rovira
> >> >
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%
> >>2Fcarlosrovira=02%7C01%7C%7Cb7200a3598f04343d75608d5291d
> d6ce%7Cfa7b1
> >>b5a7b34438794aed2c178decee1%7C0%7C0%7C636460130496354658&
> sdata=DNfktZJkOq
> >>xWmM7b0HrEC9ZFLU6T96MgeL4kziKObxQ%3D=0
> >> >
> >>
> >
> >
> >
> >--
> >Carlos Rovira
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2
> >Fcarlosrovira=02%7C01%7C%7Cb7200a3598f04343d75608d5291d
> d6ce%7Cfa7b1b5
> >a7b34438794aed2c178decee1%7C0%7C0%7C636460130496354658&
> sdata=DNfktZJkOqxWm
> >M7b0HrEC9ZFLU6T96MgeL4kziKObxQ%3D=0
>
>


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

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

[Carlos Rovira]

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 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 :
>
> > 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 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 Apache
> > > servers, Chris handle that. I would rather not invest the time in that
> > > since we have working everything on Alex PC, but that's just mine
> > > convenient and save time view. :)
> > >
> > > Piotr
> > >
> > >
> > > 2017-11-13 12:36 GMT+01:00 Carlos Rovira :
> > >
> > > > 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 "apacheflexbuild" right?
> > > > But status seems ok to me at first sight
> > > >
> > > > thanks
> > > >
> > > > 2017-11-12 20:04 GMT+01:00 Piotr Zarzycki  >:
> > > >
> > > > > Another thing is: "Apache Royale Jenkings Job Status" - This status
> > > > showing
> > > > > the state of Maven build which is hosted on builds.apache.org.
> Since
> > > we
> > > > > are
> > > > > using Alex's machine for producing ditribution package for
> developers
> > > we
> > > > > should not have it this link on the website.
> > > > >
> > > > > Maven is able to build distribution package, but so far it's
> missing
> > > some
> > > > > things and you can use that package only for code completion
> purposes
> > > in
> > > > > your IDE either Moonshine or VSCode. If I find resources I hope I
> > will
> > > > fix
> > > > > it and we can then linking to Maven build.
> > > > >
> > > > > Thanks Carslo for that website! :)
> > > > > Piotr
> > > > >
> > > > >
> > > > > 2017-11-12 18:42 GMT+01:00 Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> > >:
> > > > >
> > > > > > Hi Carlos,
> > > > > >
> > > > > > Here you go links to Royale. I see proper names. Royale [1] JS
> Only
> > > > [2].
> > > > > I
> > > > > > did just quick look and when I came to the website I started to
> > > search
> > > > > this
> > > > > > information that Nightly is not for production. After w while I
> > have
> > > > > found
> > > > > > this red rectangle. I think font size could be a bit bigger
> there.
> > > > > >
> > > > > > [1] http://apacheflexbuild.cloudapp.net:8080/job/royale-
> > > > > > asjs/lastSuccessfulBuild/artifact/out/
> > > > > > [2] http://apacheflexbuild.cloudapp.net:8080/job/royale-
> > asjs-jsonly/
> > > > > > lastSuccessfulBuild/artifact/out/
> > > > > >
> > > > > > Piotr
> > > > > >
> > > > > >
> > > > > >
> > > > > > 2017-11-12 18:30 GMT+01:00 Carlos Rovira <
> carlosrov...@apache.org
> > >:
> > > > > >
> > > > > >> Hi,
> > > > > >>
> > > > > >> here's the download page for you to review.
> > > > > >>
> > > > > >> http://royale.codeoscopic.com/download/
> > > > > >>
> > > > > >> Some things to mention:
> > > > > >>
> > > > > >> * As we already don't have release binaries, the first section
> > could
> > > > be
> > > > > >> consider under construction
> > > > > >> * For nightly builds I use the links posted by Alex in October.
> I
> > > > think
> > > > > >> those links are somewhat temporal since are labeled in "FlexJS"
> > > > instead
> > > > > of
> > > > > >> "RoyaleJS" or something and he mentions the to rename in the
> > future.
> > > > > >>
> > > > > >> You can check if links are the expected, or we need to put
> > something
> > > > > more.
> > > > > >>
> > > > > >> Take into account that the info is what I found navigating
> through
> > > the
> > > > > >> mailing list and since I'm not a user of that links, although we
> > > will
> > > > > need
> > > > > >> to update as we get final names, they can be wrong links at this
> > > time.
> > > > > >>
> > > > > >> Hope you guys could let me know what is right and wrong
> > > > > >>
> > > > > >> Thanks
> > > > > >>
> > > > > >> Carlos
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>

Re: Royale ASDoc Reference link

[Piotr Zarzycki]

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]
http://apacheflexbuild.cloudapp.net:8080/job/Royale_ASDoc_Example/lastSuccessfulBuild/artifact/examples/royale/ASDoc/bin/js-release/index.html

Piotr


2017-11-13 14:20 GMT+01:00 Carlos Rovira :

> 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
>



-- 

Piotr Zarzycki

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

Re: Royale ASDoc Reference link

[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, 2017, at 4:22 PM, Carlos Rovira  wrote:
> 
> 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 and modify, we can iterate as we need
> at any time.
> 
> Best,
> 
> Carlos
> 
> 
> 2017-11-13 14:45 GMT+01:00 Harbs :
> 
>> 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. [1] You
>> can
>>> link to Alex's server, but maybe it is worth to deploy somewhere that
>>> example ?
>>> 
>>> [1]
>>> http://apacheflexbuild.cloudapp.net:8080/job/Royale_ASDoc_Example/
>> lastSuccessfulBuild/artifact/examples/royale/ASDoc/bin/js-
>> release/index.html
>>> 
>>> Piotr
>>> 
>>> 
>>> 2017-11-13 14:20 GMT+01:00 Carlos Rovira :
>>> 
 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
 
>>> 
>>> 
>>> 
>>> --
>>> 
>>> Piotr Zarzycki
>>> 
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> *
>> 
>> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

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

[Harbs]

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, ha...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> harbs pushed a commit to branch feature/disable-children-bead
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> commit c1cc651a6f03cbcdb6792eed367140404adf7863
> Author: Harbs 
> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
> 
>First (non-working) version
> ---
> .../Basic/src/main/resources/basic-manifest.xml|   1 +
> .../royale/html/beads/DisableChildrenBead.as   | 152 +
> 2 files changed, 153 insertions(+)
> 
> diff --git a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml 
> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> index 90b72b3..02a8579 100644
> --- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> +++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> @@ -113,6 +113,7 @@
>  class="org.apache.royale.html.beads.UnselectableElementBead"/>
>  class="org.apache.royale.html.beads.DisableBead" />
>  class="org.apache.royale.html.beads.DisabledAlphaBead" />
> + class="org.apache.royale.html.beads.DisableChildrenBead" />
>  class="org.apache.royale.html.accessories.NumericOnlyTextInputBead" />
>  class="org.apache.royale.html.accessories.PasswordInputBead" />
>  class="org.apache.royale.html.accessories.PasswordInputRemovableBead" />
> diff --git 
> a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
>  
> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
> new file mode 100644
> index 000..ca4ffa1
> --- /dev/null
> +++ 
> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
> @@ -0,0 +1,152 @@
> +
> +//
> +//  Licensed to the Apache Software Foundation (ASF) under one or more
> +//  contributor license agreements.  See the NOTICE file distributed with
> +//  this work for additional information regarding copyright ownership.
> +//  The ASF licenses this file to You under the Apache License, Version 2.0
> +//  (the "License"); you may not use this file except in compliance with
> +//  the License.  You may obtain a copy of the License at
> +//
> +//  http://www.apache.org/licenses/LICENSE-2.0
> +//
> +//  Unless required by applicable law or agreed to in writing, software
> +//  distributed under the License is distributed on an "AS IS" BASIS,
> +//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> +//  See the License for the specific language governing permissions and
> +//  limitations under the License.
> +//
> +
> +package org.apache.royale.html.beads
> +{
> + COMPILE::SWF {
> + import flash.display.DisplayObjectContainer;
> + }
> + 
> + import org.apache.royale.core.IBead;
> + import org.apache.royale.core.IStrand;
> + import org.apache.royale.core.IUIBase;
> + import org.apache.royale.core.UIHTMLElementWrapper;
> + import org.apache.royale.events.Event;
> + import org.apache.royale.events.IEventDispatcher;
> + import org.apache.royale.events.ValueEvent;
> +
> + COMPILE::JS{
> + import org.apache.royale.core.WrappedHTMLElement;
> + import org.apache.royale.core.HTMLElementWrapper;
> + }
> + /**
> +  *  The DisableBead class is a specialty bead that can be used with
> +  *  any UIBase. When disabled is true, the bead prevents interaction 
> with the component.
> +  *  The appearance of the component when disabled is controlled by a 
> separate bead.
> +  *  
> +  *  @langversion 3.0
> +  *  @playerversion Flash 10.2
> +  *  @playerversion AIR 2.6
> +  *  @productversion Royale 0.0
> +  */
> + public class DisableChildrenBead implements IBead
> + {
> + /**
> +  *  constructor.
> +  *
> +  *  @langversion 3.0
> +  *  @playerversion Flash 10.2
> +  *  @playerversion AIR 2.6
> +  *  @productversion Royale 0.0
> +  */
> + public function DisableChildrenBead()
> + {
> + }
> + 
> + private var _strand:IStrand;
> + private var _disabled:Boolean;
> + 
> + /**
> +  *  @copy org.apache.royale.core.IBead#strand
> +  *  
> +  *  @langversion 3.0
> +  *  @playerversion Flash 10.2
> 

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

[Yishay Weiss]

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 (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
> 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, ha...@apache.org wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > harbs pushed a commit to branch feature/disable-children-bead
> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >
> > commit c1cc651a6f03cbcdb6792eed367140404adf7863
> > Author: Harbs 
> > AuthorDate: Mon Nov 13 14:57:34 2017 +0200
> >
> >First (non-working) version
> > ---
> > .../Basic/src/main/resources/basic-manifest.xml|   1 +
> > .../royale/html/beads/DisableChildrenBead.as   | 152
> +
> > 2 files changed, 153 insertions(+)
> >
> > diff --git a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> > index 90b72b3..02a8579 100644
> > --- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> > +++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> > @@ -113,6 +113,7 @@
> >  class="org.apache.royale.html.beads.UnselectableElementBead"/>
> >  > class="org.apache.royale.html.beads.DisableBead"
> />
> >  > class="org.apache.royale.html.beads.DisabledAlphaBead"
> />
> > + > class="org.apache.royale.html.beads.DisableChildrenBead"
> />
> >  class="org.apache.royale.html.accessories.NumericOnlyTextInputBead" />
> >  > class="org.apache.royale.html.accessories.PasswordInputBead"
> />
> >  class="org.apache.royale.html.accessories.PasswordInputRemovableBead" />
> > diff --git a/frameworks/projects/Basic/src/main/royale/org/apache/
> royale/html/beads/DisableChildrenBead.as b/frameworks/projects/Basic/
> src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
> > new file mode 100644
> > index 000..ca4ffa1
> > --- /dev/null
> > +++ b/frameworks/projects/Basic/src/main/royale/org/apache/
> royale/html/beads/DisableChildrenBead.as
> > @@ -0,0 +1,152 @@
> > +///
> /
> > +//
> > +//  Licensed to the Apache Software Foundation (ASF) under one or more
> > +//  contributor license agreements.  See the NOTICE file distributed
> with
> > +//  this work for additional information regarding copyright ownership.
> > +//  The ASF licenses this file to You under the Apache License, Version
> 2.0
> > +//  (the "License"); you may not use this file except in compliance with
> > +//  the License.  You may obtain a copy of the License at
> > +//
> > +//  http://www.apache.org/licenses/LICENSE-2.0
> > +//
> > +//  Unless required by applicable law or agreed to in writing, software
> > +//  distributed under the License is distributed on an "AS IS" BASIS,
> > +//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> > +//  See the License for the specific language governing permissions and
> > +//  limitations under the License.
> > +//
> > +///
> /
> > +package org.apache.royale.html.beads
> > +{
> > + COMPILE::SWF {
> > + import flash.display.DisplayObjectContainer;
> > + }
> > +
> > + import org.apache.royale.core.IBead;
> > + import org.apache.royale.core.IStrand;
> > + import org.apache.royale.core.IUIBase;
> > + import org.apache.royale.core.UIHTMLElementWrapper;
> > + import org.apache.royale.events.Event;
> > + import org.apache.royale.events.IEventDispatcher;
> > + import org.apache.royale.events.ValueEvent;
> > +
> > + COMPILE::JS{
> > + import org.apache.royale.core.WrappedHTMLElement;
> > + import org.apache.royale.core.HTMLElementWrapper;
> > + }
> > + /**
> > +  *  The DisableBead class is a specialty bead that can be used with
> > +  *  any UIBase. When disabled is true, the bead prevents
> interaction with the component.
> > +  *  The appearance of the component when disabled is controlled by
> a separate bead.
> > +  *
> > +  *  @langversion 3.0
> > +  *  @playerversion Flash 10.2
> > +  *  @playerversion AIR 2.6
> > +  *  @productversion Royale 0.0
> > +  */
> > + public class 

Royale ASDoc Reference link

[Carlos Rovira]

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

[Carlos Rovira]

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 from Apache Flex Team Page. I think we need to update
those photos with actual ones with more resolution (for example Alex's
photo has very poor resolution, Peter and Yishay does not have any).
Please sent it to me, or if you want to update your own card, ask me to get
credential access. It's up to you.
* For titles I put always PMC (and Harbs PMC Chair).
* for links I put the ones on Apache Flex Team Page (the ones the team card
allows to introduce).
* We can put a text with short bio if you like, but I thought this less is
more and clean.

Let me know if you want something more.

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

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

[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 DisabledAlphaBead).



[1] https://github.com/yishayw/Examples/tree/initComplete




From: Harbs 
Sent: Monday, November 13, 2017 3:26:58 PM
To: dev@royale.apache.org
Subject: 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 tabbing on all the descendants.

> On Nov 13, 2017, at 3:20 PM, Yishay Weiss  wrote:
>
> 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 (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
>> 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, ha...@apache.org wrote:
>>>
>>> This is an automated email from the ASF dual-hosted git repository.
>>>
>>> harbs pushed a commit to branch feature/disable-children-bead
>>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>>>
>>> commit c1cc651a6f03cbcdb6792eed367140404adf7863
>>> Author: Harbs 
>>> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
>>>
>>>   First (non-working) version
>>> ---
>>> .../Basic/src/main/resources/basic-manifest.xml|   1 +
>>> .../royale/html/beads/DisableChildrenBead.as   | 152
>> +
>>> 2 files changed, 153 insertions(+)
>>>
>>> diff --git a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>>> index 90b72b3..02a8579 100644
>>> --- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>>> +++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>>> @@ -113,6 +113,7 @@
>>>> class="org.apache.royale.html.beads.UnselectableElementBead"/>
>>>>> class="org.apache.royale.html.beads.DisableBead"
>> />
>>>>> class="org.apache.royale.html.beads.DisabledAlphaBead"
>> />
>>> +>> class="org.apache.royale.html.beads.DisableChildrenBead"
>> />
>>>> class="org.apache.royale.html.accessories.NumericOnlyTextInputBead" />
>>>>> class="org.apache.royale.html.accessories.PasswordInputBead"
>> />
>>>> class="org.apache.royale.html.accessories.PasswordInputRemovableBead" />
>>> diff --git a/frameworks/projects/Basic/src/main/royale/org/apache/
>> royale/html/beads/DisableChildrenBead.as b/frameworks/projects/Basic/
>> src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
>>> new file mode 100644
>>> index 000..ca4ffa1
>>> --- /dev/null
>>> +++ b/frameworks/projects/Basic/src/main/royale/org/apache/
>> royale/html/beads/DisableChildrenBead.as
>>> @@ -0,0 +1,152 @@
>>> +///
>> /
>>> +//
>>> +//  Licensed to the Apache Software Foundation (ASF) under one or more
>>> +//  contributor license agreements.  See the NOTICE file distributed
>> with
>>> +//  this work for additional information regarding copyright ownership.
>>> +//  The ASF licenses this file to You under the Apache License, Version
>> 2.0
>>> +//  (the "License"); you may not use this file except in compliance with
>>> +//  the License.  You may obtain a copy of the License at
>>> +//
>>> +//  http://www.apache.org/licenses/LICENSE-2.0
>>> +//
>>> +//  Unless required by applicable law or agreed to in writing, software
>>> +//  distributed under the License is distributed on an "AS IS" BASIS,
>>> +//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
>>> +//  See the License for the specific language governing permissions and
>>> +//  limitations under the License.
>>> +//
>>> +///
>> /
>>> +package org.apache.royale.html.beads
>>> +{
>>> + COMPILE::SWF {
>>> + import flash.display.DisplayObjectContainer;
>>> + }
>>> +
>>> + import org.apache.royale.core.IBead;
>>> + import org.apache.royale.core.IStrand;
>>> + import 

Re: Apache Royale Team Page

[Piotr Zarzycki]

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 :

> 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 from Apache Flex Team Page. I think we need to update
> those photos with actual ones with more resolution (for example Alex's
> photo has very poor resolution, Peter and Yishay does not have any).
> Please sent it to me, or if you want to update your own card, ask me to get
> credential access. It's up to you.
> * For titles I put always PMC (and Harbs PMC Chair).
> * for links I put the ones on Apache Flex Team Page (the ones the team card
> allows to introduce).
> * We can put a text with short bio if you like, but I thought this less is
> more and clean.
>
> Let me know if you want something more.
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 

Piotr Zarzycki

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

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

[Piotr Zarzycki]

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 DisabledAlphaBead).
>
>
>
> [1] https://github.com/yishayw/Examples/tree/initComplete
>
>
>
> 
> From: Harbs 
> Sent: Monday, November 13, 2017 3:26:58 PM
> To: dev@royale.apache.org
> Subject: 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 tabbing on all the descendants.
>
> > On Nov 13, 2017, at 3:20 PM, Yishay Weiss 
> wrote:
> >
> > 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 (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
> >> 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, ha...@apache.org wrote:
> >>>
> >>> This is an automated email from the ASF dual-hosted git repository.
> >>>
> >>> harbs pushed a commit to branch feature/disable-children-bead
> >>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >>>
> >>> commit c1cc651a6f03cbcdb6792eed367140404adf7863
> >>> Author: Harbs 
> >>> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
> >>>
> >>>   First (non-working) version
> >>> ---
> >>> .../Basic/src/main/resources/basic-manifest.xml|   1 +
> >>> .../royale/html/beads/DisableChildrenBead.as   | 152
> >> +
> >>> 2 files changed, 153 insertions(+)
> >>>
> >>> diff --git a/frameworks/projects/Basic/src/main/resources/basic-
> manifest.xml
> >> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >>> index 90b72b3..02a8579 100644
> >>> --- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >>> +++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >>> @@ -113,6 +113,7 @@
> >>> >> class="org.apache.royale.html.beads.UnselectableElementBead"/>
> >>> >> />
> >>> >> />
> >>> + >> />
> >>> >> class="org.apache.royale.html.accessories.NumericOnlyTextInputBead" />
> >>> >> />
> >>> >> class="org.apache.royale.html.accessories.PasswordInputRemovableBead"
> />
> >>> diff --git a/frameworks/projects/Basic/src/main/royale/org/apache/
> >> royale/html/beads/DisableChildrenBead.as b/frameworks/projects/Basic/
> >> src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
> >>> new file mode 100644
> >>> index 000..ca4ffa1
> >>> --- /dev/null
> >>> +++ b/frameworks/projects/Basic/src/main/royale/org/apache/
> >> royale/html/beads/DisableChildrenBead.as
> >>> @@ -0,0 +1,152 @@
> >>> +///
> >> /
> >>> +//
> >>> +//  Licensed to the Apache Software Foundation (ASF) under one or more
> >>> +//  contributor license agreements.  See the NOTICE file distributed
> >> with
> >>> +//  this work for additional information regarding copyright
> ownership.
> >>> +//  The ASF licenses this file to You under the Apache License,
> Version
> >> 2.0
> >>> +//  (the "License"); you may not use this file except in compliance
> with
> >>> +//  the License.  You may obtain a copy of the License at
> >>> +//
> >>> +//  http://www.apache.org/licenses/LICENSE-2.0
> >>> +//
> >>> +//  Unless required by applicable law or agreed to in writing,
> software
> >>> +//  distributed under the License is distributed on an "AS IS" BASIS,
> >>> +//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> >> implied.
> >>> +//  See the License for the specific language governing permissions
> and
> >>> +//  limitations under the License.
> >>> +//
> >>> +///
> >> /
> >>> +package org.apache.royale.html.beads
> >>> +{
> >>> + COMPILE::SWF {
> >>> + import flash.display.DisplayObjectContainer;
> >>> + 

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

[Harbs]

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 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.
> 
> Piotr
> 
> 
> 2017-11-13 14:26 GMT+01:00 Harbs :
> 
>> 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 tabbing on all the descendants.
>> 
>>> On Nov 13, 2017, at 3:20 PM, Yishay Weiss 
>> wrote:
>>> 
>>> 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 (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
 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, ha...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> harbs pushed a commit to branch feature/disable-children-bead
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> commit c1cc651a6f03cbcdb6792eed367140404adf7863
> Author: Harbs 
> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
> 
>  First (non-working) version
> ---
> .../Basic/src/main/resources/basic-manifest.xml|   1 +
> .../royale/html/beads/DisableChildrenBead.as   | 152
 +
> 2 files changed, 153 insertions(+)
> 
> diff --git a/frameworks/projects/Basic/src/main/resources/basic-
>> manifest.xml
 b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> index 90b72b3..02a8579 100644
> --- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> +++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> @@ -113,6 +113,7 @@
>   >>> class="org.apache.royale.html.beads.UnselectableElementBead"/>
>   >>> />
>   >>> />
> +>>> />
>   >>> class="org.apache.royale.html.accessories.NumericOnlyTextInputBead" />
>   >>> />
>   >>> class="org.apache.royale.html.accessories.PasswordInputRemovableBead"
>> />
> diff --git a/frameworks/projects/Basic/src/main/royale/org/apache/
 royale/html/beads/DisableChildrenBead.as b/frameworks/projects/Basic/
 src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
> new file mode 100644
> index 000..ca4ffa1
> --- /dev/null
> +++ b/frameworks/projects/Basic/src/main/royale/org/apache/
 royale/html/beads/DisableChildrenBead.as
> @@ -0,0 +1,152 @@
> +///
 /
> +//
> +//  Licensed to the Apache Software Foundation (ASF) under one or more
> +//  contributor license agreements.  See the NOTICE file distributed
 with
> +//  this work for additional information regarding copyright
>> ownership.
> +//  The ASF licenses this file to You under the Apache License,
>> Version
 2.0
> +//  (the "License"); you may not use this file except in compliance
>> with
> +//  the License.  You may obtain a copy of the License at
> +//
> +//  http://www.apache.org/licenses/LICENSE-2.0
> +//
> +//  Unless required by applicable law or agreed to in writing,
>> software
> +//  distributed under the License is distributed on an "AS IS" BASIS,
> +//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
 implied.
> +//  See the License for the specific language governing permissions
>> and
> +//  limitations under the License.
> +//
> +///
 /
> +package org.apache.royale.html.beads
> +{
> + COMPILE::SWF {
> + import flash.display.DisplayObjectContainer;
> +   

Re: Royale ASDoc Reference link

[Carlos Rovira]

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 and modify, we can iterate as we need
at any time.

Best,

Carlos


2017-11-13 14:45 GMT+01:00 Harbs :

> 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. [1] You
> can
> > link to Alex's server, but maybe it is worth to deploy somewhere that
> > example ?
> >
> > [1]
> > http://apacheflexbuild.cloudapp.net:8080/job/Royale_ASDoc_Example/
> lastSuccessfulBuild/artifact/examples/royale/ASDoc/bin/js-
> release/index.html
> >
> > Piotr
> >
> >
> > 2017-11-13 14:20 GMT+01:00 Carlos Rovira :
> >
> >> 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
> >>
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
>
>


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

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

[Harbs]

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 tabbing on all the descendants.

> On Nov 13, 2017, at 3:20 PM, Yishay Weiss  wrote:
> 
> 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 (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
>> 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, ha...@apache.org wrote:
>>> 
>>> This is an automated email from the ASF dual-hosted git repository.
>>> 
>>> harbs pushed a commit to branch feature/disable-children-bead
>>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>>> 
>>> commit c1cc651a6f03cbcdb6792eed367140404adf7863
>>> Author: Harbs 
>>> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
>>> 
>>>   First (non-working) version
>>> ---
>>> .../Basic/src/main/resources/basic-manifest.xml|   1 +
>>> .../royale/html/beads/DisableChildrenBead.as   | 152
>> +
>>> 2 files changed, 153 insertions(+)
>>> 
>>> diff --git a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>>> index 90b72b3..02a8579 100644
>>> --- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>>> +++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>>> @@ -113,6 +113,7 @@
>>>> class="org.apache.royale.html.beads.UnselectableElementBead"/>
>>>>> class="org.apache.royale.html.beads.DisableBead"
>> />
>>>>> class="org.apache.royale.html.beads.DisabledAlphaBead"
>> />
>>> +>> class="org.apache.royale.html.beads.DisableChildrenBead"
>> />
>>>> class="org.apache.royale.html.accessories.NumericOnlyTextInputBead" />
>>>>> class="org.apache.royale.html.accessories.PasswordInputBead"
>> />
>>>> class="org.apache.royale.html.accessories.PasswordInputRemovableBead" />
>>> diff --git a/frameworks/projects/Basic/src/main/royale/org/apache/
>> royale/html/beads/DisableChildrenBead.as b/frameworks/projects/Basic/
>> src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
>>> new file mode 100644
>>> index 000..ca4ffa1
>>> --- /dev/null
>>> +++ b/frameworks/projects/Basic/src/main/royale/org/apache/
>> royale/html/beads/DisableChildrenBead.as
>>> @@ -0,0 +1,152 @@
>>> +///
>> /
>>> +//
>>> +//  Licensed to the Apache Software Foundation (ASF) under one or more
>>> +//  contributor license agreements.  See the NOTICE file distributed
>> with
>>> +//  this work for additional information regarding copyright ownership.
>>> +//  The ASF licenses this file to You under the Apache License, Version
>> 2.0
>>> +//  (the "License"); you may not use this file except in compliance with
>>> +//  the License.  You may obtain a copy of the License at
>>> +//
>>> +//  http://www.apache.org/licenses/LICENSE-2.0
>>> +//
>>> +//  Unless required by applicable law or agreed to in writing, software
>>> +//  distributed under the License is distributed on an "AS IS" BASIS,
>>> +//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
>>> +//  See the License for the specific language governing permissions and
>>> +//  limitations under the License.
>>> +//
>>> +///
>> /
>>> +package org.apache.royale.html.beads
>>> +{
>>> + COMPILE::SWF {
>>> + import flash.display.DisplayObjectContainer;
>>> + }
>>> +
>>> + import org.apache.royale.core.IBead;
>>> + import org.apache.royale.core.IStrand;
>>> + import org.apache.royale.core.IUIBase;
>>> + import org.apache.royale.core.UIHTMLElementWrapper;
>>> + import org.apache.royale.events.Event;
>>> + import org.apache.royale.events.IEventDispatcher;
>>> + import org.apache.royale.events.ValueEvent;
>>> +
>>> + COMPILE::JS{
>>> + import org.apache.royale.core.WrappedHTMLElement;
>>> + import org.apache.royale.core.HTMLElementWrapper;
>>> + }
>>> + /**
>>> +  

Re: Royale ASDoc Reference link

[Harbs]

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. [1] You can
> link to Alex's server, but maybe it is worth to deploy somewhere that
> example ?
> 
> [1]
> http://apacheflexbuild.cloudapp.net:8080/job/Royale_ASDoc_Example/lastSuccessfulBuild/artifact/examples/royale/ASDoc/bin/js-release/index.html
> 
> Piotr
> 
> 
> 2017-11-13 14:20 GMT+01:00 Carlos Rovira :
> 
>> 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
>> 
> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> *

Re: Royale ASDoc Reference link

[Carlos Rovira]

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, 2017, at 4:22 PM, Carlos Rovira 
> wrote:
> >
> > 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 and modify, we can iterate as we
> need
> > at any time.
> >
> > Best,
> >
> > Carlos
> >
> >
> > 2017-11-13 14:45 GMT+01:00 Harbs :
> >
> >> 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. [1] You
> >> can
> >>> link to Alex's server, but maybe it is worth to deploy somewhere that
> >>> example ?
> >>>
> >>> [1]
> >>> http://apacheflexbuild.cloudapp.net:8080/job/Royale_ASDoc_Example/
> >> lastSuccessfulBuild/artifact/examples/royale/ASDoc/bin/js-
> >> release/index.html
> >>>
> >>> Piotr
> >>>
> >>>
> >>> 2017-11-13 14:20 GMT+01:00 Carlos Rovira :
> >>>
>  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
> 
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> Piotr Zarzycki
> >>>
> >>> Patreon: *https://www.patreon.com/piotrzarzycki
> >>> *
> >>
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>


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

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

[Alex Harui]

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:

>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 DisabledAlphaBead).
>>
>>
>>
>> [1] 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>om%2Fyishayw%2FExamples%2Ftree%2FinitComplete=02%7C01%7C%7Ca9d54724b
>>c9443dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364
>>61825737445515=gYDEhA2WwBvRPPQ6aOgyz5Cp4fIn3iluQhq9YbFtIdQ%3D
>>ved=0
>>
>>
>>
>> 
>> From: Harbs 
>> Sent: Monday, November 13, 2017 3:26:58 PM
>> To: dev@royale.apache.org
>> Subject: 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 tabbing on all the descendants.
>>
>> > On Nov 13, 2017, at 3:20 PM, Yishay Weiss 
>> wrote:
>> >
>> > 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 (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
>> >> 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, ha...@apache.org wrote:
>> >>>
>> >>> This is an automated email from the ASF dual-hosted git repository.
>> >>>
>> >>> harbs pushed a commit to branch feature/disable-children-bead
>> >>> in repository
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.a
>>pache.org%2Frepos%2Fasf%2Froyale-asjs.git=02%7C01%7C%7Ca9d54724bc944
>>3dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63646182
>>5737445515=KWwzVziEug3oAjzc2payBE947JUEv4GSWWPeoOtHd6w%3D=
>>0
>> >>>
>> >>> commit c1cc651a6f03cbcdb6792eed367140404adf7863
>> >>> Author: Harbs 
>> >>> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
>> >>>
>> >>>   First (non-working) version
>> >>> ---
>> >>> .../Basic/src/main/resources/basic-manifest.xml|   1 +
>> >>> .../royale/html/beads/DisableChildrenBead.as   | 152
>> >> +
>> >>> 2 files changed, 153 insertions(+)
>> >>>
>> >>> diff --git a/frameworks/projects/Basic/src/main/resources/basic-
>> manifest.xml
>> >> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>> >>> index 90b72b3..02a8579 100644
>> >>> --- 
>>a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>> >>> +++ 
>>b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>> >>> @@ -113,6 +113,7 @@
>> >>>> >> class="org.apache.royale.html.beads.UnselectableElementBead"/>
>> >>>> >> />
>> >>>> >> />
>> >>> +>class="org.apache.royale.html.
>> beads.DisableChildrenBead"
>> >> />
>> >>>> >> class="org.apache.royale.html.accessories.NumericOnlyTextInputBead"
>>/>
>> >>>> >> />
>> >>>> >> class="org.apache.royale.html.accessories.PasswordInputRemovableBead"
>> />
>> >>> diff --git a/frameworks/projects/Basic/src/main/royale/org/apache/
>> >> royale/html/beads/DisableChildrenBead.as b/frameworks/projects/Basic/
>> >> src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
>> >>> new file mode 100644
>> >>> index 000..ca4ffa1
>> >>> --- /dev/null
>> >>> +++ b/frameworks/projects/Basic/src/main/royale/org/apache/
>> >> royale/html/beads/DisableChildrenBead.as
>> >>> @@ -0,0 +1,152 @@
>> >>> +///
>> >> /
>> >>> +//
>> >>> +//  Licensed to the Apache Software Foundation (ASF) under one or
>>more
>> >>> +//  contributor license agreements.  See the NOTICE file
>>distributed
>> >> with
>> >>> +//  this work for 

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

[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 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
> transpiler compiles and runs ;-)
>
> Next up: complete the tool chain, mostly figure out how to automate the
> 'wat' (WebAssembly Text format) to 'wast' ("binary" WebAssembly format)
> conversion, publish full project with HTML 'template', put up some basic
> "setup and run" documentation, etc.
>
> Then I'll get started creating the first small steps on the visitors,
> getting a tiny AS application ("trace('Hello World')") to transpile to a
> functioning WAST project.
>
> From there: complete transpiling all AS core functionality, complete the
> glue script to make WAST -> JavaScript communication happen and do a bunch
> of other things (including some I don't know about yet, I'm sure, because
> I'm still learning WebAssembly).
>
> I hope to have the proof of concept (everything up to 'Hello World') done
> by the end of the week. Then I'll have to do some real work again :-P
>
> Thanks,
>
> EdB
>
>
>
> On Mon, Nov 13, 2017 at 5:51 PM, Harbs  wrote:
>
> > Awesome!
> >
> > Does this compile yet?
> >
> > > On Nov 13, 2017, at 6:27 PM, erikdebr...@apache.org wrote:
> > >
> > > This is an automated email from the ASF dual-hosted git repository.
> > >
> > > erikdebruin pushed a commit to branch develop
> > > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> > >
> > >
> > > The following commit(s) were added to refs/heads/develop by this push:
> > > new e036dd3  [WAST] batch script for WASTC and an early example
> > project
> > > e036dd3 is described below
> > >
> > > commit e036dd345ba0c37b80bef09798c9c957a6088ee7
> > > Author: Erik de Bruin 
> > > AuthorDate: Mon Nov 13 17:27:07 2017 +0100
> > >
> > >[WAST] batch script for WASTC and an early example project
> > >
> > >Signed-off-by: Erik de Bruin 
> > > ---
> > > wast/bin/wastc | 72
> > ++
> > > wast/examples/HelloWorld/src/HelloWorld.as | 29 
> > > 2 files changed, 101 insertions(+)
> > >
> > > diff --git a/wast/bin/wastc b/wast/bin/wastc
> > > new file mode 100755
> > > index 000..fd77d19
> > > --- /dev/null
> > > +++ b/wast/bin/wastc
> > > @@ -0,0 +1,72 @@
> > > +#!/bin/sh
> > > +
> > > +###
> > #
> > > +##
> > > +##  Licensed to the Apache Software Foundation (ASF) under one or more
> > > +##  contributor license agreements.  See the NOTICE file distributed
> > with
> > > +##  this work for additional information regarding copyright
> ownership.
> > > +##  The ASF licenses this file to You under the Apache License,
> Version
> > 2.0
> > > +##  (the "License"); you may not use this file except in compliance
> with
> > > +##  the License.  You may obtain a copy of the License at
> > > +##
> > > +##  http://www.apache.org/licenses/LICENSE-2.0
> > > +##
> > > +##  Unless required by applicable law or agreed to in writing,
> software
> > > +##  distributed under the License is distributed on an "AS IS" BASIS,
> > > +##  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> > implied.
> > > +##  See the License for the specific language governing permissions
> and
> > > +##  limitations under the License.
> > > +##
> > > +###
> > #
> > > +
> > > +
> > > +#
> > > +# wastc shell script to launch wastc.jar on OSX, Unix, or Cygwin.
> > > +#
> > > +
> > > +SCRIPT_HOME=`dirname "$0"`
> > > +
> > > +test "$FLEX_HOME" = "" && {
> > > +FLEX_HOME=`dirname "$0"`/../..
> > > +}
> > > +
> > > +for i in "$@"
> > > +do
> > > +case $i in
> > > +-t=*|--target-player=*)
> > > +TARGET_PLAYER="${i#*=}"
> > > +shift
> > > +;;
> > > +*) # unknown option
> > > +;;
> > > +esac
> > > +done
> > > +
> > > +test "$TARGET_PLAYER" = "" && {
> > > +TARGET_PLAYER=11.1
> > > +}
> > > +
> > > +case `uname` in
> > > + CYGWIN*)
> > > + OS="Windows"
> > > + ;;
> > > + *)
> > > + OS=Unix
> > > +esac
> > > +
> > > +D32=''
> > > +
> > > +if [ $OS = "Unix" ]; then
> > > +
> > > +check64="`java -version 2>&1 | grep -i 64-Bit`"
> > > +isOSX="`uname | grep -i Darwin`"
> > > +javaVersion="`java -version 2>&1 | awk -F '[ ".]+' 'NR==1 {print
> $3
> > "." $4}'`"
> > > +
> > > +if [ "$isOSX" != "" -a "$HOSTTYPE" = "x86_64" -a "$check64" != ""
> > -a "$javaVersion" = "1.6" ]; then
> > > +D32='-d32'
> > > +fi
> > > +fi
> > > +
> > > 

Re: Apache Royale Examples Blog Category

[Alex Harui]

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 component that can do code-coloring.

My 2 cents,
-Alex

On 11/13/17, 3:17 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>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 code in the same way
>* Maybe organization is better since we use tags complementing search
>
>I see Github good for the documentation and wiki but this part could work
>better in our blog.
>
>That's my opinion
>
>Thanks
>
>
>
>2017-11-13 9:03 GMT+01:00 Alex Harui :
>
>> Is there an advantage to using a blog vs using a GitHub repo?
>>
>> -Alex
>>
>> On 11/11/17, 8:03 AM, "carlos.rov...@gmail.com on behalf of Carlos
>>Rovira"
>>  wrote:
>>
>> >Hi,
>> >
>> >we talked about committers and PMCs that want to contribute can get
>>access
>> >to the wordpress installation to collaborate.
>> >Regarding other people we could setup wordpress for people to become
>> >contributors and other committers and PMC could review content and
>> >approve.
>> >But don't know if this is allowed or people must sign first an ICLA to
>> >declare that contributions are donated to Apache Royale.
>> >
>> >
>> >
>> >
>> >
>> >2017-11-11 15:54 GMT+01:00 gkk gb :
>> >
>> >> I completely agree. If it is open for more than one person to
>> >>contribute,
>> >> it should build up fairly quickly.
>> >>
>> >> > On November 10, 2017 at 2:30 PM Carlos Rovira wrote:
>> >> >
>> >> >
>> >> > Hi,
>> >> >
>> >> > One thing I think it would be great would be to have something
>> >>like
>> >> Peter
>> >> > deHaan blogs (Flex Examples, AIR Examples, ActionScript
>>Examples)
>> >> >
>> >> > I made a test post and a hello world post in a blog category
>> >>called
>> >> "Royale
>> >> > Examples"
>> >> >
>> >> >
>> >>https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Froyale.co
>> >>deoscopic.com%2Fcategory%2Froyale-examples%2F=02%
>> 7C01%7C%7Cb7200a359
>> >>8f04343d75608d5291dd6ce%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6364
>> >>60130496354658=Alojomc%2Fa%2BznHUyVP6OCuQpTuxGkhie%
>> 2FvSb2d%2FI79wk%
>> >>3D=0
>> >> >
>> >>https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Froyale.co
>> >>deoscopic.com%2Fcreating-a-hello-world-in-=02%7C01%
>> 7C%7Cb7200a3598f0
>> >>4343d75608d5291dd6ce%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6364601
>> >>30496354658=laC5yIkV8DXIYron3q8YverGsg73Va
>> %2FHvLIZM%2FkqMIU%3D
>> >>rved=0
>> >> apache-royale/
>> >> >
>> >> > One thing we need here is to complete this kind of post is to
>>add
>> >>the
>> >> > working example so people could see final results.
>> >> > Should we host in the same website? or maybe we should use
>>another
>> >> tool
>> >> > (maybe JSFiddle could be used with Royale?, if so I think it
>>can
>> >>be
>> >> > embedded in a post but then the content will be in JSFiddle
>>and we
>> >> need a
>> >> > generic "apacheroyale" account there...)
>> >> >
>> >> > If we use tags like Peter did we can have an easy and fast way
>>for
>> >> people
>> >> > to get to a concrete example.
>> >> >
>> >> > I think some of you want to have something like this. If this
>>go
>> >> forward, I
>> >> > expect we all post examples
>> >> >
>> >> > Let me know what do you think.
>> >> >
>> >> > --
>> >> > Carlos Rovira
>> >> >
>> >>https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fabout.me%
>> >>2Fcarlosrovira=02%7C01%7C%7Cb7200a3598f04343d75608d5291d
>> d6ce%7Cfa7b1
>> >>b5a7b34438794aed2c178decee1%7C0%7C0%7C636460130496354658&
>> sdata=DNfktZJkOq
>> >>xWmM7b0HrEC9ZFLU6T96MgeL4kziKObxQ%3D=0
>> >> >
>> >>
>> >
>> >
>> >
>> >--
>> >Carlos Rovira
>> >https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fabout.me%2
>> >Fcarlosrovira=02%7C01%7C%7Cb7200a3598f04343d75608d5291d
>> d6ce%7Cfa7b1b5
>> >a7b34438794aed2c178decee1%7C0%7C0%7C636460130496354658&
>> sdata=DNfktZJkOqxWm
>> >M7b0HrEC9ZFLU6T96MgeL4kziKObxQ%3D=0
>>
>>
>
>
>-- 
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira=02%7C01%7C%7C14685eac9e31498785f308d52a882990%7Cfa7b1b5
>a7b34438794aed2c178decee1%7C0%7C0%7C636461686658555281=%2BvDgg%2B4QJ
>Z6Gl4aNtviJKGSNMVAUFBpbWVaS02A%2F%2FSo%3D=0

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

[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
'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
transpiler compiles and runs ;-)

Next up: complete the tool chain, mostly figure out how to automate the
'wat' (WebAssembly Text format) to 'wast' ("binary" WebAssembly format)
conversion, publish full project with HTML 'template', put up some basic
"setup and run" documentation, etc.

Then I'll get started creating the first small steps on the visitors,
getting a tiny AS application ("trace('Hello World')") to transpile to a
functioning WAST project.

>From there: complete transpiling all AS core functionality, complete the
glue script to make WAST -> JavaScript communication happen and do a bunch
of other things (including some I don't know about yet, I'm sure, because
I'm still learning WebAssembly).

I hope to have the proof of concept (everything up to 'Hello World') done
by the end of the week. Then I'll have to do some real work again :-P

Thanks,

EdB



On Mon, Nov 13, 2017 at 5:51 PM, Harbs  wrote:

> Awesome!
>
> Does this compile yet?
>
> > On Nov 13, 2017, at 6:27 PM, erikdebr...@apache.org wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > erikdebruin pushed a commit to branch develop
> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >
> >
> > The following commit(s) were added to refs/heads/develop by this push:
> > new e036dd3  [WAST] batch script for WASTC and an early example
> project
> > e036dd3 is described below
> >
> > commit e036dd345ba0c37b80bef09798c9c957a6088ee7
> > Author: Erik de Bruin 
> > AuthorDate: Mon Nov 13 17:27:07 2017 +0100
> >
> >[WAST] batch script for WASTC and an early example project
> >
> >Signed-off-by: Erik de Bruin 
> > ---
> > wast/bin/wastc | 72
> ++
> > wast/examples/HelloWorld/src/HelloWorld.as | 29 
> > 2 files changed, 101 insertions(+)
> >
> > diff --git a/wast/bin/wastc b/wast/bin/wastc
> > new file mode 100755
> > index 000..fd77d19
> > --- /dev/null
> > +++ b/wast/bin/wastc
> > @@ -0,0 +1,72 @@
> > +#!/bin/sh
> > +
> > +###
> #
> > +##
> > +##  Licensed to the Apache Software Foundation (ASF) under one or more
> > +##  contributor license agreements.  See the NOTICE file distributed
> with
> > +##  this work for additional information regarding copyright ownership.
> > +##  The ASF licenses this file to You under the Apache License, Version
> 2.0
> > +##  (the "License"); you may not use this file except in compliance with
> > +##  the License.  You may obtain a copy of the License at
> > +##
> > +##  http://www.apache.org/licenses/LICENSE-2.0
> > +##
> > +##  Unless required by applicable law or agreed to in writing, software
> > +##  distributed under the License is distributed on an "AS IS" BASIS,
> > +##  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> > +##  See the License for the specific language governing permissions and
> > +##  limitations under the License.
> > +##
> > +###
> #
> > +
> > +
> > +#
> > +# wastc shell script to launch wastc.jar on OSX, Unix, or Cygwin.
> > +#
> > +
> > +SCRIPT_HOME=`dirname "$0"`
> > +
> > +test "$FLEX_HOME" = "" && {
> > +FLEX_HOME=`dirname "$0"`/../..
> > +}
> > +
> > +for i in "$@"
> > +do
> > +case $i in
> > +-t=*|--target-player=*)
> > +TARGET_PLAYER="${i#*=}"
> > +shift
> > +;;
> > +*) # unknown option
> > +;;
> > +esac
> > +done
> > +
> > +test "$TARGET_PLAYER" = "" && {
> > +TARGET_PLAYER=11.1
> > +}
> > +
> > +case `uname` in
> > + CYGWIN*)
> > + OS="Windows"
> > + ;;
> > + *)
> > + OS=Unix
> > +esac
> > +
> > +D32=''
> > +
> > +if [ $OS = "Unix" ]; then
> > +
> > +check64="`java -version 2>&1 | grep -i 64-Bit`"
> > +isOSX="`uname | grep -i Darwin`"
> > +javaVersion="`java -version 2>&1 | awk -F '[ ".]+' 'NR==1 {print $3
> "." $4}'`"
> > +
> > +if [ "$isOSX" != "" -a "$HOSTTYPE" = "x86_64" -a "$check64" != ""
> -a "$javaVersion" = "1.6" ]; then
> > +D32='-d32'
> > +fi
> > +fi
> > +
> > +VMARGS="-Xmx384m -Dsun.io.useCanonCaches=false"
> > +
> > +java $VMARGS $D32 -jar "${SCRIPT_HOME}/../lib/wastc.jar"
> -external-library-path="${FLEX_HOME}/frameworks/libs/
> player/${TARGET_PLAYER}/playerglobal.swc" "$@"
> > diff --git a/wast/examples/HelloWorld/src/HelloWorld.as
> b/wast/examples/HelloWorld/src/HelloWorld.as
> > new file mode 100644
> > index 000..b2d2c36
> > --- /dev/null
> > +++ 

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

[Piotr Zarzycki]

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 care about this
"other stuff".

Piotr


2017-11-13 17:42 GMT+01:00 Alex Harui :

> 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:
>
> >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 DisabledAlphaBead).
> >>
> >>
> >>
> >> [1]
> >>https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.c
> >>om%2Fyishayw%2FExamples%2Ftree%2FinitComplete=02%
> 7C01%7C%7Ca9d54724b
> >>c9443dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364
> >>61825737445515=gYDEhA2WwBvRPPQ6aOgyz5Cp4fIn3i
> luQhq9YbFtIdQ%3D
> >>ved=0
> >>
> >>
> >>
> >> 
> >> From: Harbs 
> >> Sent: Monday, November 13, 2017 3:26:58 PM
> >> To: dev@royale.apache.org
> >> Subject: 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 tabbing on all the descendants.
> >>
> >> > On Nov 13, 2017, at 3:20 PM, Yishay Weiss 
> >> wrote:
> >> >
> >> > 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 (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
> >> >> 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, ha...@apache.org wrote:
> >> >>>
> >> >>> This is an automated email from the ASF dual-hosted git repository.
> >> >>>
> >> >>> harbs pushed a commit to branch feature/disable-children-bead
> >> >>> in repository
> >>https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgitbox.a
> >>pache.org%2Frepos%2Fasf%2Froyale-asjs.git=02%
> 7C01%7C%7Ca9d54724bc944
> >>3dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C63646182
> >>5737445515=KWwzVziEug3oAjzc2payBE947JUEv4
> GSWWPeoOtHd6w%3D=
> >>0
> >> >>>
> >> >>> commit c1cc651a6f03cbcdb6792eed367140404adf7863
> >> >>> Author: Harbs 
> >> >>> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
> >> >>>
> >> >>>   First (non-working) version
> >> >>> ---
> >> >>> .../Basic/src/main/resources/basic-manifest.xml|   1 +
> >> >>> .../royale/html/beads/DisableChildrenBead.as   | 152
> >> >> +
> >> >>> 2 files changed, 153 insertions(+)
> >> >>>
> >> >>> diff --git a/frameworks/projects/Basic/src/main/resources/basic-
> >> manifest.xml
> >> >> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >> >>> index 90b72b3..02a8579 100644
> >> >>> ---
> >>a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >> >>> +++
> >>b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >> >>> @@ -113,6 +113,7 @@
> >> >>> >> >> class="org.apache.royale.html.beads.UnselectableElementBead"/>
> >> >>> >> >> />
> >> >>> >> >> />
> >> >>> + >>class="org.apache.royale.html.
> >> beads.DisableChildrenBead"
> >> >> />
> >> >>> >> >> class="org.apache.royale.html.accessories.NumericOnlyTextInputBead"
> >>/>
> >> >>> >> >> />
> >> >>> >> >> class="org.apache.royale.html.accessories.
> PasswordInputRemovableBead"
> >> />
> >> >>> diff --git 

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

[Harbs]

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 need if a child is added "later".
> 
> My 2 cents,
> -Alex
> 
> On 11/13/17, 7:09 AM, "Piotr Zarzycki"  > wrote:
> 
>> 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 DisabledAlphaBead).
>>> 
>>> 
>>> 
>>> [1] 
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c 
>>> 
>>> om%2Fyishayw%2FExamples%2Ftree%2FinitComplete=02%7C01%7C%7Ca9d54724b
>>> c9443dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364
>>> 61825737445515=gYDEhA2WwBvRPPQ6aOgyz5Cp4fIn3iluQhq9YbFtIdQ%3D
>>> ved=0
>>> 
>>> 
>>> 
>>> 
>>> From: Harbs >
>>> Sent: Monday, November 13, 2017 3:26:58 PM
>>> To: dev@royale.apache.org 
>>> Subject: 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 tabbing on all the descendants.
>>> 
 On Nov 13, 2017, at 3:20 PM, Yishay Weiss >
>>> wrote:
 
 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 (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
> 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, ha...@apache.org  
>> wrote:
>> 
>> This is an automated email from the ASF dual-hosted git repository.
>> 
>> harbs pushed a commit to branch feature/disable-children-bead
>> in repository
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.a 
>>> 
>>> pache.org 
>>> %2Frepos%2Fasf%2Froyale-asjs.git=02%7C01%7C%7Ca9d54724bc944
>>> 3dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63646182
>>> 5737445515=KWwzVziEug3oAjzc2payBE947JUEv4GSWWPeoOtHd6w%3D=
>>> 0
>> 
>> commit c1cc651a6f03cbcdb6792eed367140404adf7863
>> Author: Harbs >
>> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
>> 
>>  First (non-working) version
>> ---
>> .../Basic/src/main/resources/basic-manifest.xml|   1 +
>> .../royale/html/beads/DisableChildrenBead.as   | 152
> +
>> 2 files changed, 153 insertions(+)
>> 
>> diff --git a/frameworks/projects/Basic/src/main/resources/basic-
>>> manifest.xml
> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>> index 90b72b3..02a8579 100644
>> --- 
>>> a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>> +++ 
>>> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
>> @@ -113,6 +113,7 @@
>>    class="org.apache.royale.html.beads.UnselectableElementBead"/>
>>    />
>>    />
>> +>> class="org.apache.royale.html.
>>> beads.DisableChildrenBead"
> />
>>    class="org.apache.royale.html.accessories.NumericOnlyTextInputBead"
>>> />
>>    />
>>    class="org.apache.royale.html.accessories.PasswordInputRemovableBead"
>>> />
>> diff 

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

[Harbs]

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 
> (similar to DisabledAlphaBead).

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

[Harbs]

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 :
> 
>> 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 need if a child is added "later".
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> On 11/13/17, 7:09 AM, "Piotr Zarzycki" > > wrote:
>>> 
 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 DisabledAlphaBead).
> 
> 
> 
> [1]
> https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fgithub.c > protection.outlook.com/?url=https%3A%2F%2Fgithub.c>
> om%2Fyishayw%2FExamples%2Ftree%2FinitComplete=02%
>> 7C01%7C%7Ca9d54724b
> c9443dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6364
> 61825737445515=gYDEhA2WwBvRPPQ6aOgyz5Cp4fIn3i
>> luQhq9YbFtIdQ%3D
> ved=0
> 
> 
> 
> 
> From: Harbs >
> Sent: Monday, November 13, 2017 3:26:58 PM
> To: dev@royale.apache.org 
> Subject: 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 tabbing on all the descendants.
> 
>> On Nov 13, 2017, at 3:20 PM, Yishay Weiss > >
> wrote:
>> 
>> Why not listen to the container’s ‘initComplete’? Also, doesn’t
> DisableBead work for containers as is?
>> 
>> 
>> 
>> 
>> From: Piotr Zarzycki  piotrzarzyck...@gmail.com>>
>> Sent: Monday, November 13, 2017 3:15:54 PM
>> To: dev@royale.apache.org 
>> Subject: 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  harbs.li...@gmail.com>>:
>> 
>>> 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, ha...@apache.org > ha...@apache.org> wrote:
 
 This is an automated email from the ASF dual-hosted git repository.
 
 harbs pushed a commit to branch feature/disable-children-bead
 in repository
> https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fgitbox.a > protection.outlook.com/?url=https%3A%2F%2Fgitbox.a>
> pache.org %2Frepos%2Fasf%2Froyale-asjs.git=
>> 02%7C01%7C%7Ca9d54724bc944
> 3dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C63646182
> 5737445515=KWwzVziEug3oAjzc2payBE947JUEv4
>> GSWWPeoOtHd6w%3D=
> 0
 
 commit c1cc651a6f03cbcdb6792eed367140404adf7863
 Author: Harbs >
 AuthorDate: Mon Nov 13 14:57:34 2017 +0200
 
 First (non-working) version
 ---
 .../Basic/src/main/resources/basic-manifest.xml|   1 +
 .../royale/html/beads/DisableChildrenBead.as   | 152
>>> +
 2 files changed, 153 insertions(+)
 
 diff --git a/frameworks/projects/Basic/src/main/resources/basic-
> manifest.xml
>>> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
 index 90b72b3..02a8579 100644
 ---
> 

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

[Piotr Zarzycki]

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 
> 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 need if a child is added "later".
> >
> > My 2 cents,
> > -Alex
> >
> > On 11/13/17, 7:09 AM, "Piotr Zarzycki"  > wrote:
> >
> >> 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 DisabledAlphaBead).
> >>>
> >>>
> >>>
> >>> [1]
> >>> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.c  protection.outlook.com/?url=https%3A%2F%2Fgithub.c>
> >>> om%2Fyishayw%2FExamples%2Ftree%2FinitComplete=02%
> 7C01%7C%7Ca9d54724b
> >>> c9443dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364
> >>> 61825737445515=gYDEhA2WwBvRPPQ6aOgyz5Cp4fIn3i
> luQhq9YbFtIdQ%3D
> >>> ved=0
> >>>
> >>>
> >>>
> >>> 
> >>> From: Harbs >
> >>> Sent: Monday, November 13, 2017 3:26:58 PM
> >>> To: dev@royale.apache.org 
> >>> Subject: 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 tabbing on all the descendants.
> >>>
>  On Nov 13, 2017, at 3:20 PM, Yishay Weiss  >
> >>> wrote:
> 
>  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 (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
> > 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, ha...@apache.org  ha...@apache.org> wrote:
> >>
> >> This is an automated email from the ASF dual-hosted git repository.
> >>
> >> harbs pushed a commit to branch feature/disable-children-bead
> >> in repository
> >>> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgitbox.a  protection.outlook.com/?url=https%3A%2F%2Fgitbox.a>
> >>> pache.org %2Frepos%2Fasf%2Froyale-asjs.git=
> 02%7C01%7C%7Ca9d54724bc944
> >>> 3dcb42d08d52aa88b95%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C63646182
> >>> 5737445515=KWwzVziEug3oAjzc2payBE947JUEv4
> GSWWPeoOtHd6w%3D=
> >>> 0
> >>
> >> commit c1cc651a6f03cbcdb6792eed367140404adf7863
> >> Author: Harbs >
> >> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
> >>
> >>  First (non-working) version
> >> ---
> >> .../Basic/src/main/resources/basic-manifest.xml|   1 +
> >> .../royale/html/beads/DisableChildrenBead.as   | 152
> > +
> >> 2 files changed, 153 insertions(+)
> >>
> >> diff --git a/frameworks/projects/Basic/src/main/resources/basic-
> >>> manifest.xml
> > b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >> index 90b72b3..02a8579 100644
> >> ---
> >>> a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >> +++
> >>> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >> @@ -113,6 +113,7 @@
> >>> 

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

[Carlos Rovira]

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 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
> > transpiler compiles and runs ;-)
> >
> > Next up: complete the tool chain, mostly figure out how to automate the
> > 'wat' (WebAssembly Text format) to 'wast' ("binary" WebAssembly format)
> > conversion, publish full project with HTML 'template', put up some basic
> > "setup and run" documentation, etc.
> >
> > Then I'll get started creating the first small steps on the visitors,
> > getting a tiny AS application ("trace('Hello World')") to transpile to a
> > functioning WAST project.
> >
> > From there: complete transpiling all AS core functionality, complete the
> > glue script to make WAST -> JavaScript communication happen and do a
> bunch
> > of other things (including some I don't know about yet, I'm sure, because
> > I'm still learning WebAssembly).
> >
> > I hope to have the proof of concept (everything up to 'Hello World') done
> > by the end of the week. Then I'll have to do some real work again :-P
> >
> > Thanks,
> >
> > EdB
> >
> >
> >
> > On Mon, Nov 13, 2017 at 5:51 PM, Harbs  wrote:
> >
> > > Awesome!
> > >
> > > Does this compile yet?
> > >
> > > > On Nov 13, 2017, at 6:27 PM, erikdebr...@apache.org wrote:
> > > >
> > > > This is an automated email from the ASF dual-hosted git repository.
> > > >
> > > > erikdebruin pushed a commit to branch develop
> > > > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> > > >
> > > >
> > > > The following commit(s) were added to refs/heads/develop by this
> push:
> > > > new e036dd3  [WAST] batch script for WASTC and an early example
> > > project
> > > > e036dd3 is described below
> > > >
> > > > commit e036dd345ba0c37b80bef09798c9c957a6088ee7
> > > > Author: Erik de Bruin 
> > > > AuthorDate: Mon Nov 13 17:27:07 2017 +0100
> > > >
> > > >[WAST] batch script for WASTC and an early example project
> > > >
> > > >Signed-off-by: Erik de Bruin 
> > > > ---
> > > > wast/bin/wastc | 72
> > > ++
> > > > wast/examples/HelloWorld/src/HelloWorld.as | 29 
> > > > 2 files changed, 101 insertions(+)
> > > >
> > > > diff --git a/wast/bin/wastc b/wast/bin/wastc
> > > > new file mode 100755
> > > > index 000..fd77d19
> > > > --- /dev/null
> > > > +++ b/wast/bin/wastc
> > > > @@ -0,0 +1,72 @@
> > > > +#!/bin/sh
> > > > +
> > > > +###
> > > #
> > > > +##
> > > > +##  Licensed to the Apache Software Foundation (ASF) under one or
> more
> > > > +##  contributor license agreements.  See the NOTICE file distributed
> > > with
> > > > +##  this work for additional information regarding copyright
> > ownership.
> > > > +##  The ASF licenses this file to You under the Apache License,
> > Version
> > > 2.0
> > > > +##  (the "License"); you may not use this file except in compliance
> > with
> > > > +##  the License.  You may obtain a copy of the License at
> > > > +##
> > > > +##  http://www.apache.org/licenses/LICENSE-2.0
> > > > +##
> > > > +##  Unless required by applicable law or agreed to in writing,
> > software
> > > > +##  distributed under the License is distributed on an "AS IS"
> BASIS,
> > > > +##  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> > > implied.
> > > > +##  See the License for the specific language governing permissions
> > and
> > > > +##  limitations under the License.
> > > > +##
> > > > +###
> > > #
> > > > +
> > > > +
> > > > +#
> > > > +# wastc shell script to launch wastc.jar on OSX, Unix, or Cygwin.
> > > > +#
> > > > +
> > > > +SCRIPT_HOME=`dirname "$0"`
> > > > +
> > > > +test "$FLEX_HOME" = "" && {
> > > > +FLEX_HOME=`dirname "$0"`/../..
> > > > +}
> > > > +
> > > > +for i in "$@"
> > > > +do
> > > > +case $i in
> > > > +-t=*|--target-player=*)
> > > > +TARGET_PLAYER="${i#*=}"
> > > > +shift
> > > > +;;
> > > > +*) # unknown option
> > > > +;;
> > > > +esac
> > > > +done
> > > > +
> > > > +test "$TARGET_PLAYER" = "" && {
> > > > +TARGET_PLAYER=11.1
> > > > +}
> > > > +
> > > > +case `uname` in
> > > > + CYGWIN*)
> > > > + OS="Windows"
> > > > + ;;
> > > > + *)
> > > > + OS=Unix
> > > > +esac
> > > > +
> > > > +D32=''

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

[Piotr Zarzycki]

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
> 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, ha...@apache.org wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > harbs pushed a commit to branch feature/disable-children-bead
> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >
> > commit c1cc651a6f03cbcdb6792eed367140404adf7863
> > Author: Harbs 
> > AuthorDate: Mon Nov 13 14:57:34 2017 +0200
> >
> >First (non-working) version
> > ---
> > .../Basic/src/main/resources/basic-manifest.xml|   1 +
> > .../royale/html/beads/DisableChildrenBead.as   | 152
> +
> > 2 files changed, 153 insertions(+)
> >
> > diff --git a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> > index 90b72b3..02a8579 100644
> > --- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> > +++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> > @@ -113,6 +113,7 @@
> >  class="org.apache.royale.html.beads.UnselectableElementBead"/>
> >  > class="org.apache.royale.html.beads.DisableBead"
> />
> >  > class="org.apache.royale.html.beads.DisabledAlphaBead"
> />
> > + > class="org.apache.royale.html.beads.DisableChildrenBead"
> />
> >  class="org.apache.royale.html.accessories.NumericOnlyTextInputBead" />
> >  > class="org.apache.royale.html.accessories.PasswordInputBead"
> />
> >  class="org.apache.royale.html.accessories.PasswordInputRemovableBead" />
> > diff --git a/frameworks/projects/Basic/src/main/royale/org/apache/
> royale/html/beads/DisableChildrenBead.as b/frameworks/projects/Basic/
> src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
> > new file mode 100644
> > index 000..ca4ffa1
> > --- /dev/null
> > +++ b/frameworks/projects/Basic/src/main/royale/org/apache/
> royale/html/beads/DisableChildrenBead.as
> > @@ -0,0 +1,152 @@
> > +///
> /
> > +//
> > +//  Licensed to the Apache Software Foundation (ASF) under one or more
> > +//  contributor license agreements.  See the NOTICE file distributed
> with
> > +//  this work for additional information regarding copyright ownership.
> > +//  The ASF licenses this file to You under the Apache License, Version
> 2.0
> > +//  (the "License"); you may not use this file except in compliance with
> > +//  the License.  You may obtain a copy of the License at
> > +//
> > +//  http://www.apache.org/licenses/LICENSE-2.0
> > +//
> > +//  Unless required by applicable law or agreed to in writing, software
> > +//  distributed under the License is distributed on an "AS IS" BASIS,
> > +//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> > +//  See the License for the specific language governing permissions and
> > +//  limitations under the License.
> > +//
> > +///
> /
> > +package org.apache.royale.html.beads
> > +{
> > + COMPILE::SWF {
> > + import flash.display.DisplayObjectContainer;
> > + }
> > +
> > + import org.apache.royale.core.IBead;
> > + import org.apache.royale.core.IStrand;
> > + import org.apache.royale.core.IUIBase;
> > + import org.apache.royale.core.UIHTMLElementWrapper;
> > + import org.apache.royale.events.Event;
> > + import org.apache.royale.events.IEventDispatcher;
> > + import org.apache.royale.events.ValueEvent;
> > +
> > + COMPILE::JS{
> > + import org.apache.royale.core.WrappedHTMLElement;
> > + import org.apache.royale.core.HTMLElementWrapper;
> > + }
> > + /**
> > +  *  The DisableBead class is a specialty bead that can be used with
> > +  *  any UIBase. When disabled is true, the bead prevents
> interaction with the component.
> > +  *  The appearance of the component when disabled is controlled by
> a separate bead.
> > +  *
> > +  *  @langversion 3.0
> > +  *  @playerversion Flash 10.2
> > +  *  @playerversion AIR 2.6
> > +  *  @productversion Royale 0.0
> > +  */
> > + public class DisableChildrenBead implements IBead
> > + {
> > + /**
> > +  *  constructor.
> > +  *
> > +  *  @langversion 3.0
> > +  *  @playerversion Flash 10.2
> > +  *  @playerversion AIR 2.6
> > +  *  @productversion Royale 0.0
> > +  */
> > + 

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

[Piotr Zarzycki]

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.

Piotr


2017-11-13 14:26 GMT+01:00 Harbs :

> 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 tabbing on all the descendants.
>
> > On Nov 13, 2017, at 3:20 PM, Yishay Weiss 
> wrote:
> >
> > 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 (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
> >> 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, ha...@apache.org wrote:
> >>>
> >>> This is an automated email from the ASF dual-hosted git repository.
> >>>
> >>> harbs pushed a commit to branch feature/disable-children-bead
> >>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >>>
> >>> commit c1cc651a6f03cbcdb6792eed367140404adf7863
> >>> Author: Harbs 
> >>> AuthorDate: Mon Nov 13 14:57:34 2017 +0200
> >>>
> >>>   First (non-working) version
> >>> ---
> >>> .../Basic/src/main/resources/basic-manifest.xml|   1 +
> >>> .../royale/html/beads/DisableChildrenBead.as   | 152
> >> +
> >>> 2 files changed, 153 insertions(+)
> >>>
> >>> diff --git a/frameworks/projects/Basic/src/main/resources/basic-
> manifest.xml
> >> b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >>> index 90b72b3..02a8579 100644
> >>> --- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >>> +++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
> >>> @@ -113,6 +113,7 @@
> >>> >> class="org.apache.royale.html.beads.UnselectableElementBead"/>
> >>> >> />
> >>> >> />
> >>> + >> />
> >>> >> class="org.apache.royale.html.accessories.NumericOnlyTextInputBead" />
> >>> >> />
> >>> >> class="org.apache.royale.html.accessories.PasswordInputRemovableBead"
> />
> >>> diff --git a/frameworks/projects/Basic/src/main/royale/org/apache/
> >> royale/html/beads/DisableChildrenBead.as b/frameworks/projects/Basic/
> >> src/main/royale/org/apache/royale/html/beads/DisableChildrenBead.as
> >>> new file mode 100644
> >>> index 000..ca4ffa1
> >>> --- /dev/null
> >>> +++ b/frameworks/projects/Basic/src/main/royale/org/apache/
> >> royale/html/beads/DisableChildrenBead.as
> >>> @@ -0,0 +1,152 @@
> >>> +///
> >> /
> >>> +//
> >>> +//  Licensed to the Apache Software Foundation (ASF) under one or more
> >>> +//  contributor license agreements.  See the NOTICE file distributed
> >> with
> >>> +//  this work for additional information regarding copyright
> ownership.
> >>> +//  The ASF licenses this file to You under the Apache License,
> Version
> >> 2.0
> >>> +//  (the "License"); you may not use this file except in compliance
> with
> >>> +//  the License.  You may obtain a copy of the License at
> >>> +//
> >>> +//  http://www.apache.org/licenses/LICENSE-2.0
> >>> +//
> >>> +//  Unless required by applicable law or agreed to in writing,
> software
> >>> +//  distributed under the License is distributed on an "AS IS" BASIS,
> >>> +//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> >> implied.
> >>> +//  See the License for the specific language governing permissions
> and
> >>> +//  limitations under the License.
> >>> +//
> >>> +///
> >> /
> >>> +package org.apache.royale.html.beads
> >>> +{
> >>> + COMPILE::SWF {
> >>> + import flash.display.DisplayObjectContainer;
> >>> + }
> >>> +
> >>> + import org.apache.royale.core.IBead;
> >>> + import org.apache.royale.core.IStrand;
> >>> + import org.apache.royale.core.IUIBase;
> >>> + import org.apache.royale.core.UIHTMLElementWrapper;
> 

Re: Apache Royale Team Page

[Carlos Rovira]

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
> someone would like to know about us more.
>
> Thoughts ?
>
>
Right the cards support that. For example any member can use the click over
the card to go to his own site, or what they want.
For icons, that are limited to the ones provided (facebook, twitter,
linkedin,...)

Thanks!

Carlos



> Piotr
>
>
> 2017-11-13 15:33 GMT+01:00 Carlos Rovira :
>
> > 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 from Apache Flex Team Page. I think we need to update
> > those photos with actual ones with more resolution (for example Alex's
> > photo has very poor resolution, Peter and Yishay does not have any).
> > Please sent it to me, or if you want to update your own card, ask me to
> get
> > credential access. It's up to you.
> > * For titles I put always PMC (and Harbs PMC Chair).
> > * for links I put the ones on Apache Flex Team Page (the ones the team
> card
> > allows to introduce).
> > * We can put a text with short bio if you like, but I thought this less
> is
> > more and clean.
> >
> > Let me know if you want something more.
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>



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

Re: Apache Royale Examples Blog Category

[Carlos Rovira]

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
do a basic tool for the look and feel and I'm finding many problems to get
something very basic. For example, Js:Slider seems to work but thumb
appears with a huge offset and when click and drag does not work as
expected... This is to name only one thing.. If we want to do a UI Set to
do those things, I think we have a lot of work a head. So we need to
organize and prioritize things. IMHO, we can reach a Royale Examples Blog
or App without getting a minimal UI set state that be easy to work with.

But that's just my opinion. As always and the rest of the team has to be
pronouncing to take the best path we can.

Thanks



2017-11-13 17:39 GMT+01:00 Alex Harui :

> 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 component that can do code-coloring.
>
> My 2 cents,
> -Alex
>
> On 11/13/17, 3:17 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >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 code in the same way
> >* Maybe organization is better since we use tags complementing search
> >
> >I see Github good for the documentation and wiki but this part could work
> >better in our blog.
> >
> >That's my opinion
> >
> >Thanks
> >
> >
> >
> >2017-11-13 9:03 GMT+01:00 Alex Harui :
> >
> >> Is there an advantage to using a blog vs using a GitHub repo?
> >>
> >> -Alex
> >>
> >> On 11/11/17, 8:03 AM, "carlos.rov...@gmail.com on behalf of Carlos
> >>Rovira"
> >>  wrote:
> >>
> >> >Hi,
> >> >
> >> >we talked about committers and PMCs that want to contribute can get
> >>access
> >> >to the wordpress installation to collaborate.
> >> >Regarding other people we could setup wordpress for people to become
> >> >contributors and other committers and PMC could review content and
> >> >approve.
> >> >But don't know if this is allowed or people must sign first an ICLA to
> >> >declare that contributions are donated to Apache Royale.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >2017-11-11 15:54 GMT+01:00 gkk gb :
> >> >
> >> >> I completely agree. If it is open for more than one person to
> >> >>contribute,
> >> >> it should build up fairly quickly.
> >> >>
> >> >> > On November 10, 2017 at 2:30 PM Carlos Rovira wrote:
> >> >> >
> >> >> >
> >> >> > Hi,
> >> >> >
> >> >> > One thing I think it would be great would be to have something
> >> >>like
> >> >> Peter
> >> >> > deHaan blogs (Flex Examples, AIR Examples, ActionScript
> >>Examples)
> >> >> >
> >> >> > I made a test post and a hello world post in a blog category
> >> >>called
> >> >> "Royale
> >> >> > Examples"
> >> >> >
> >> >> >
> >> >>https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Froyale.co
> >> >>deoscopic.com%2Fcategory%2Froyale-examples%2F=02%
> >> 7C01%7C%7Cb7200a359
> >> >>8f04343d75608d5291dd6ce%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C6364
> >> >>60130496354658=Alojomc%2Fa%2BznHUyVP6OCuQpTuxGkhie%
> >> 2FvSb2d%2FI79wk%
> >> >>3D=0
> >> >> >
> >> >>https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Froyale.co
> >> >>deoscopic.com%2Fcreating-a-hello-world-in-=02%7C01%
> >> 7C%7Cb7200a3598f0
> >> >>4343d75608d5291dd6ce%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C6364601
> >> >>30496354658=laC5yIkV8DXIYron3q8YverGsg73Va
> >> %2FHvLIZM%2FkqMIU%3D
> >> >>rved=0
> >> >> apache-royale/
> >> >> >
> >> >> > One thing we need here is to complete this kind of post is to
> >>add
> >> >>the
> >> >> > working example so people could see final results.
> >> >> > Should we host in the same website? or maybe we should use
> >>another
> >> >> tool
> >> >> > (maybe JSFiddle could be used with Royale?, if so I think it
> >>can
> >> >>be
> >> >> > embedded in a post but then the content will be in JSFiddle
> >>and we
> >> >> need a
> >> >> > generic "apacheroyale" account there...)
> >> >> >
> >> >> > If we use tags like Peter did we can have an easy and fast way
> >>for
> >> >> people
> >> >> > to get to a concrete example.
> >> >> >
> >> >> > I