Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
I hope the few people building from sources would try with actual instructions and if they have problems come to the list and try to solve it with our help, so we can improve scripts and build process learning from that kind of experiences. El lun., 23 sept. 2019 a las 14:05, Andrew Wetmore () escribió: > Yes: the PERFECT would be clear and simple instructions that work and do > not scare people away. We do not seem to have those. I thought the > discussion was whether to go forward with the release anyhow, since the > number of users who build from source is smaller than the number who use > the compiled binaries, or delay the release until we get the instructions > right. > > My suggestion related to the first option, to make sure that, if we go > ahead with the release including insufficient build instructions, that we > warn people about that. That way we show that we know it's an issue, rather > than looking like we don't know or, worse, don't care. > > a > > On Mon, Sep 23, 2019 at 8:28 AM Carlos Rovira > wrote: > > > Hi Andrew, > > > > ok I understand. > > > > IMHO, instructions should be as easy as possible. People that see steps > > depending on things that are not clear will be mostly lost and with high > > probability of never come back. Royale SDK is a complex technology with > > many pieces involved, we should make the install process as simple as > > possible hidding all that complexity if we want to succeed. The main > point > > that is running against us is that complexity. > > > > just my 2... > > > > > > > > > > > -- Carlos Rovira http://about.me/carlosrovira
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
Yes: the PERFECT would be clear and simple instructions that work and do not scare people away. We do not seem to have those. I thought the discussion was whether to go forward with the release anyhow, since the number of users who build from source is smaller than the number who use the compiled binaries, or delay the release until we get the instructions right. My suggestion related to the first option, to make sure that, if we go ahead with the release including insufficient build instructions, that we warn people about that. That way we show that we know it's an issue, rather than looking like we don't know or, worse, don't care. a On Mon, Sep 23, 2019 at 8:28 AM Carlos Rovira wrote: > Hi Andrew, > > ok I understand. > > IMHO, instructions should be as easy as possible. People that see steps > depending on things that are not clear will be mostly lost and with high > probability of never come back. Royale SDK is a complex technology with > many pieces involved, we should make the install process as simple as > possible hidding all that complexity if we want to succeed. The main point > that is running against us is that complexity. > > just my 2... > > > > >
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
Hi Andrew, ok I understand. IMHO, instructions should be as easy as possible. People that see steps depending on things that are not clear will be mostly lost and with high probability of never come back. Royale SDK is a complex technology with many pieces involved, we should make the install process as simple as possible hidding all that complexity if we want to succeed. The main point that is running against us is that complexity. just my 2... El lun., 23 sept. 2019 a las 13:01, Andrew Wetmore () escribió: > Oops: edited my proposed text and did not check it afterwards. What I meant > was this for the release page for 0.9.6:: > > "The current version of Apache Royale is 0.9.6, released in MONTH YEAR. It > is beta-quality. This means that Royale may not work entirely as you or we > want it to, and that certain standard components and functions are not yet > available. However, you can create and compile applications in Royale and > run them either in a browser window or on the Flash and AIR platforms. > Further: please note that the instructions for compiling Royale from the > source code may not work for you as they are written. You may need to set > additional environment variables, depending on your operating system. Send > an email to EMAIL ADDRESS if you run into difficulties and need further > instructions. You can, of course, use the compiled binaries of Royale and > get to work immediately." > > On Mon, Sep 23, 2019 at 7:57 AM Andrew Wetmore > wrote: > > > The question is whether we release 0.9.6 when the instructions for > > compiling from source are incomplete and/or inaccurate. > > > > For 0.9.4 the page says "The current version of *Apache Royale* is > *0.9.4*, > > released in *Diciembre, 2018*. It is *beta-quality*. This means that > > Royale may not work entirely as you or we want it to, and that certain > > “standard” components or functions are not yet available. However, you > can > > create applications in Royale and compile them to run either in a browser > > window or on the Flash/AIR platforms." > > > > For 0.9.6, why can we not say, "The current version of Apache Royale is > > 0.9.6, release in MONTH YEAR. It is beta-quality. This means that Royale > > may not work entirely as you or we want it to, and that certain > "standard" > > components or functions are not yet available. However, you can create > > applications and compile applications in Royale and run them either in a > > browser window or on the Flash and AIR platforms. > > Further: please note that the instructions for compiling Royale from the > > source code may not work for you as they are written. You may need to set > > additional environment variables, depending on your operating system. > Send > > an email to EMAIL ADDRESS if you run into difficulties and need further > > instructions. You can, of course, use the compiled binaries of Royale and > > get to work immediately." > > > > Andrew > > > > On Mon, Sep 23, 2019 at 6:57 AM Carlos Rovira > > wrote: > > > >> Hi Andrew, > >> > >> can you specify what you mean? Here's the download page with all > download > >> links: https://royale.apache.org/download/ > >> > >> El dom., 22 sept. 2019 a las 20:11, Andrew Wetmore (< > cottag...@gmail.com > >> >) > >> escribió: > >> > >> > Could it not also be posted on the website, where the link for > >> downloading > >> > the release is? > >> > > >> > On Sat, Sep 21, 2019 at 8:53 PM Alex Harui > >> > wrote: > >> > > >> > > The only place to include it without altering the release artifacts > >> is in > >> > > the RELEASE_NOTES addendum in our wiki. > >> > > > >> > > We could do that, but folks probably won't look there until after > they > >> > > have a problem. > >> > > > >> > > -Alex > >> > > > >> > > On 9/21/19, 4:44 AM, "Andrew Wetmore" wrote: > >> > > > >> > > Would it be acceptable to include some sort of explanation that > >> > > compiling > >> > > from source will require setting a number of environment > >> variables, > >> > not > >> > > just ANT_HOME, and that, if you really want to compile 0.9.6 > from > >> > > source, > >> > > you should contact [LIST EMAIL] for instructions on what to do? > It > >> > > sort of > >> > > dodges the issue, but permits moving forward with the release > with > >> > the > >> > > presumption that, as Alex says, most people will want and use > the > >> > > compiled > >> > > binaries. > >> > > > >> > > I guess I would rather acknowledge the problem than look like we > >> > don't > >> > > realize there is a problem. > >> > > > >> > > Andrew > >> > > > >> > > On Fri, Sep 20, 2019 at 2:10 AM Alex Harui > >> >> > > > >> > > wrote: > >> > > > >> > > > I think we all want to get a release out. > >> > > > > >> > > > My user experience was the equivalent of taking the source > >> package > >> > > and > >> > > > trying to build it without setting any environment variables > >> other > >> > > than > >> > > > ANT_HOME as
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
Oops: edited my proposed text and did not check it afterwards. What I meant was this for the release page for 0.9.6:: "The current version of Apache Royale is 0.9.6, released in MONTH YEAR. It is beta-quality. This means that Royale may not work entirely as you or we want it to, and that certain standard components and functions are not yet available. However, you can create and compile applications in Royale and run them either in a browser window or on the Flash and AIR platforms. Further: please note that the instructions for compiling Royale from the source code may not work for you as they are written. You may need to set additional environment variables, depending on your operating system. Send an email to EMAIL ADDRESS if you run into difficulties and need further instructions. You can, of course, use the compiled binaries of Royale and get to work immediately." On Mon, Sep 23, 2019 at 7:57 AM Andrew Wetmore wrote: > The question is whether we release 0.9.6 when the instructions for > compiling from source are incomplete and/or inaccurate. > > For 0.9.4 the page says "The current version of *Apache Royale* is *0.9.4*, > released in *Diciembre, 2018*. It is *beta-quality*. This means that > Royale may not work entirely as you or we want it to, and that certain > “standard” components or functions are not yet available. However, you can > create applications in Royale and compile them to run either in a browser > window or on the Flash/AIR platforms." > > For 0.9.6, why can we not say, "The current version of Apache Royale is > 0.9.6, release in MONTH YEAR. It is beta-quality. This means that Royale > may not work entirely as you or we want it to, and that certain "standard" > components or functions are not yet available. However, you can create > applications and compile applications in Royale and run them either in a > browser window or on the Flash and AIR platforms. > Further: please note that the instructions for compiling Royale from the > source code may not work for you as they are written. You may need to set > additional environment variables, depending on your operating system. Send > an email to EMAIL ADDRESS if you run into difficulties and need further > instructions. You can, of course, use the compiled binaries of Royale and > get to work immediately." > > Andrew > > On Mon, Sep 23, 2019 at 6:57 AM Carlos Rovira > wrote: > >> Hi Andrew, >> >> can you specify what you mean? Here's the download page with all download >> links: https://royale.apache.org/download/ >> >> El dom., 22 sept. 2019 a las 20:11, Andrew Wetmore (> >) >> escribió: >> >> > Could it not also be posted on the website, where the link for >> downloading >> > the release is? >> > >> > On Sat, Sep 21, 2019 at 8:53 PM Alex Harui >> > wrote: >> > >> > > The only place to include it without altering the release artifacts >> is in >> > > the RELEASE_NOTES addendum in our wiki. >> > > >> > > We could do that, but folks probably won't look there until after they >> > > have a problem. >> > > >> > > -Alex >> > > >> > > On 9/21/19, 4:44 AM, "Andrew Wetmore" wrote: >> > > >> > > Would it be acceptable to include some sort of explanation that >> > > compiling >> > > from source will require setting a number of environment >> variables, >> > not >> > > just ANT_HOME, and that, if you really want to compile 0.9.6 from >> > > source, >> > > you should contact [LIST EMAIL] for instructions on what to do? It >> > > sort of >> > > dodges the issue, but permits moving forward with the release with >> > the >> > > presumption that, as Alex says, most people will want and use the >> > > compiled >> > > binaries. >> > > >> > > I guess I would rather acknowledge the problem than look like we >> > don't >> > > realize there is a problem. >> > > >> > > Andrew >> > > >> > > On Fri, Sep 20, 2019 at 2:10 AM Alex Harui >> > > > >> > > wrote: >> > > >> > > > I think we all want to get a release out. >> > > > >> > > > My user experience was the equivalent of taking the source >> package >> > > and >> > > > trying to build it without setting any environment variables >> other >> > > than >> > > > ANT_HOME as specified in the README. It did not work for me. >> > > > >> > > > The question is: how many of our users are going to try to >> build >> > the >> > > > source package? And when it fails and the ask about it, will it >> > > bother >> > > > them to be told to go get the Adobe stuff and set environment >> > > variables? I >> > > > think it is a small number of people, almost everyone else is >> going >> > > to grab >> > > > binaries. However, it is bothering me because we are an open >> > source >> > > > project and our minimum configuration should work but doesn't. >> > > > >> > > > -Alex >> > > > >> > > > On 9/19/19, 9:20 PM, "Piotr Zarzycki" < >> piotrzarzyck...@gmail.com> >> > > wrote: >> > > > >> > > > I'm in
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
The question is whether we release 0.9.6 when the instructions for compiling from source are incomplete and/or inaccurate. For 0.9.4 the page says "The current version of *Apache Royale* is *0.9.4*, released in *Diciembre, 2018*. It is *beta-quality*. This means that Royale may not work entirely as you or we want it to, and that certain “standard” components or functions are not yet available. However, you can create applications in Royale and compile them to run either in a browser window or on the Flash/AIR platforms." For 0.9.6, why can we not say, "The current version of Apache Royale is 0.9.6, release in MONTH YEAR. It is beta-quality. This means that Royale may not work entirely as you or we want it to, and that certain "standard" components or functions are not yet available. However, you can create applications and compile applications in Royale and run them either in a browser window or on the Flash and AIR platforms. Further: please note that the instructions for compiling Royale from the source code may not work for you as they are written. You may need to set additional environment variables, depending on your operating system. Send an email to EMAIL ADDRESS if you run into difficulties and need further instructions. You can, of course, use the compiled binaries of Royale and get to work immediately." Andrew On Mon, Sep 23, 2019 at 6:57 AM Carlos Rovira wrote: > Hi Andrew, > > can you specify what you mean? Here's the download page with all download > links: https://royale.apache.org/download/ > > El dom., 22 sept. 2019 a las 20:11, Andrew Wetmore () > escribió: > > > Could it not also be posted on the website, where the link for > downloading > > the release is? > > > > On Sat, Sep 21, 2019 at 8:53 PM Alex Harui > > wrote: > > > > > The only place to include it without altering the release artifacts is > in > > > the RELEASE_NOTES addendum in our wiki. > > > > > > We could do that, but folks probably won't look there until after they > > > have a problem. > > > > > > -Alex > > > > > > On 9/21/19, 4:44 AM, "Andrew Wetmore" wrote: > > > > > > Would it be acceptable to include some sort of explanation that > > > compiling > > > from source will require setting a number of environment variables, > > not > > > just ANT_HOME, and that, if you really want to compile 0.9.6 from > > > source, > > > you should contact [LIST EMAIL] for instructions on what to do? It > > > sort of > > > dodges the issue, but permits moving forward with the release with > > the > > > presumption that, as Alex says, most people will want and use the > > > compiled > > > binaries. > > > > > > I guess I would rather acknowledge the problem than look like we > > don't > > > realize there is a problem. > > > > > > Andrew > > > > > > On Fri, Sep 20, 2019 at 2:10 AM Alex Harui > > > > > > wrote: > > > > > > > I think we all want to get a release out. > > > > > > > > My user experience was the equivalent of taking the source > package > > > and > > > > trying to build it without setting any environment variables > other > > > than > > > > ANT_HOME as specified in the README. It did not work for me. > > > > > > > > The question is: how many of our users are going to try to build > > the > > > > source package? And when it fails and the ask about it, will it > > > bother > > > > them to be told to go get the Adobe stuff and set environment > > > variables? I > > > > think it is a small number of people, almost everyone else is > going > > > to grab > > > > binaries. However, it is bothering me because we are an open > > source > > > > project and our minimum configuration should work but doesn't. > > > > > > > > -Alex > > > > > > > > On 9/19/19, 9:20 PM, "Piotr Zarzycki" > > > > wrote: > > > > > > > > I'm in favor of moving forward. I would like to finally > release > > > stuff. > > > > > > > > I can live with setting up env. Variables. I'm concern by the > > > user > > > > experience than mine. > > > > > > > > Thanks, > > > > Piotr > > > > > > > > On Thu, Sep 19, 2019, 10:36 PM Alex Harui > > > > > > > wrote: > > > > > > > > > Don't know. Judgement call. > > > > > > > > > > We've done a bunch of work since 0.9.4 to allow folks to be > > > able to > > > > > compile without the Adobe Flash and AIR SDKs. I've run > into > > a > > > > couple of > > > > > problems. ASDoc's JSON generator was failing if you didn't > > > have > > > > Flash > > > > > SDK. I mentioned it in the RC1 discuss thread. I think > > > because it > > > > is only > > > > > this one example it is probably ok. > > > > > > > > > > What is less ok is another commit I have pending which is > > that > > > the > > > > main > > > > > SWC build fails if you don't have Flash and AIR
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
Hi Andrew, can you specify what you mean? Here's the download page with all download links: https://royale.apache.org/download/ El dom., 22 sept. 2019 a las 20:11, Andrew Wetmore () escribió: > Could it not also be posted on the website, where the link for downloading > the release is? > > On Sat, Sep 21, 2019 at 8:53 PM Alex Harui > wrote: > > > The only place to include it without altering the release artifacts is in > > the RELEASE_NOTES addendum in our wiki. > > > > We could do that, but folks probably won't look there until after they > > have a problem. > > > > -Alex > > > > On 9/21/19, 4:44 AM, "Andrew Wetmore" wrote: > > > > Would it be acceptable to include some sort of explanation that > > compiling > > from source will require setting a number of environment variables, > not > > just ANT_HOME, and that, if you really want to compile 0.9.6 from > > source, > > you should contact [LIST EMAIL] for instructions on what to do? It > > sort of > > dodges the issue, but permits moving forward with the release with > the > > presumption that, as Alex says, most people will want and use the > > compiled > > binaries. > > > > I guess I would rather acknowledge the problem than look like we > don't > > realize there is a problem. > > > > Andrew > > > > On Fri, Sep 20, 2019 at 2:10 AM Alex Harui > > > wrote: > > > > > I think we all want to get a release out. > > > > > > My user experience was the equivalent of taking the source package > > and > > > trying to build it without setting any environment variables other > > than > > > ANT_HOME as specified in the README. It did not work for me. > > > > > > The question is: how many of our users are going to try to build > the > > > source package? And when it fails and the ask about it, will it > > bother > > > them to be told to go get the Adobe stuff and set environment > > variables? I > > > think it is a small number of people, almost everyone else is going > > to grab > > > binaries. However, it is bothering me because we are an open > source > > > project and our minimum configuration should work but doesn't. > > > > > > -Alex > > > > > > On 9/19/19, 9:20 PM, "Piotr Zarzycki" > > wrote: > > > > > > I'm in favor of moving forward. I would like to finally release > > stuff. > > > > > > I can live with setting up env. Variables. I'm concern by the > > user > > > experience than mine. > > > > > > Thanks, > > > Piotr > > > > > > On Thu, Sep 19, 2019, 10:36 PM Alex Harui > > > > > wrote: > > > > > > > Don't know. Judgement call. > > > > > > > > We've done a bunch of work since 0.9.4 to allow folks to be > > able to > > > > compile without the Adobe Flash and AIR SDKs. I've run into > a > > > couple of > > > > problems. ASDoc's JSON generator was failing if you didn't > > have > > > Flash > > > > SDK. I mentioned it in the RC1 discuss thread. I think > > because it > > > is only > > > > this one example it is probably ok. > > > > > > > > What is less ok is another commit I have pending which is > that > > the > > > main > > > > SWC build fails if you don't have Flash and AIR SDKs. In > > theory, > > > none of > > > > you should have been able to get the build to work without > > > environment > > > > variables for the Adobe stuff. So it depends a bit on how > > important > > > we > > > > think building from sources without the Adobe stuff is for > this > > > release. > > > > If you did get the build to work without the Adobe stuff, > > check your > > > > environment and post the console output. I was fooled by > > having a > > > > PLAYERGLOBAL_HOME still set. When I took it away, more > things > > broke. > > > > > > > > I'm testing building with Flash/AIR now to try to make sure > my > > > js-only > > > > changes didn't affect js-swf. > > > > > > > > -Alex > > > > > > > > On 9/19/19, 1:19 PM, "Piotr Zarzycki" < > > piotrzarzyck...@gmail.com> > > > wrote: > > > > > > > > Hi Alex, > > > > > > > > We need to have it in 0.9.6? > > > > > > > > Thanks, > > > > Piotr > > > > > > > > On Thu, Sep 19, 2019, 9:49 PM wrote: > > > > > > > > > This is an automated email from the ASF dual-hosted git > > > repository. > > > > > > > > > > aharui pushed a commit to branch release/0.9.6 > > > > > in repository > > > > > > > > > >
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
Could it not also be posted on the website, where the link for downloading the release is? On Sat, Sep 21, 2019 at 8:53 PM Alex Harui wrote: > The only place to include it without altering the release artifacts is in > the RELEASE_NOTES addendum in our wiki. > > We could do that, but folks probably won't look there until after they > have a problem. > > -Alex > > On 9/21/19, 4:44 AM, "Andrew Wetmore" wrote: > > Would it be acceptable to include some sort of explanation that > compiling > from source will require setting a number of environment variables, not > just ANT_HOME, and that, if you really want to compile 0.9.6 from > source, > you should contact [LIST EMAIL] for instructions on what to do? It > sort of > dodges the issue, but permits moving forward with the release with the > presumption that, as Alex says, most people will want and use the > compiled > binaries. > > I guess I would rather acknowledge the problem than look like we don't > realize there is a problem. > > Andrew > > On Fri, Sep 20, 2019 at 2:10 AM Alex Harui > wrote: > > > I think we all want to get a release out. > > > > My user experience was the equivalent of taking the source package > and > > trying to build it without setting any environment variables other > than > > ANT_HOME as specified in the README. It did not work for me. > > > > The question is: how many of our users are going to try to build the > > source package? And when it fails and the ask about it, will it > bother > > them to be told to go get the Adobe stuff and set environment > variables? I > > think it is a small number of people, almost everyone else is going > to grab > > binaries. However, it is bothering me because we are an open source > > project and our minimum configuration should work but doesn't. > > > > -Alex > > > > On 9/19/19, 9:20 PM, "Piotr Zarzycki" > wrote: > > > > I'm in favor of moving forward. I would like to finally release > stuff. > > > > I can live with setting up env. Variables. I'm concern by the > user > > experience than mine. > > > > Thanks, > > Piotr > > > > On Thu, Sep 19, 2019, 10:36 PM Alex Harui > > > wrote: > > > > > Don't know. Judgement call. > > > > > > We've done a bunch of work since 0.9.4 to allow folks to be > able to > > > compile without the Adobe Flash and AIR SDKs. I've run into a > > couple of > > > problems. ASDoc's JSON generator was failing if you didn't > have > > Flash > > > SDK. I mentioned it in the RC1 discuss thread. I think > because it > > is only > > > this one example it is probably ok. > > > > > > What is less ok is another commit I have pending which is that > the > > main > > > SWC build fails if you don't have Flash and AIR SDKs. In > theory, > > none of > > > you should have been able to get the build to work without > > environment > > > variables for the Adobe stuff. So it depends a bit on how > important > > we > > > think building from sources without the Adobe stuff is for this > > release. > > > If you did get the build to work without the Adobe stuff, > check your > > > environment and post the console output. I was fooled by > having a > > > PLAYERGLOBAL_HOME still set. When I took it away, more things > broke. > > > > > > I'm testing building with Flash/AIR now to try to make sure my > > js-only > > > changes didn't affect js-swf. > > > > > > -Alex > > > > > > On 9/19/19, 1:19 PM, "Piotr Zarzycki" < > piotrzarzyck...@gmail.com> > > wrote: > > > > > > Hi Alex, > > > > > > We need to have it in 0.9.6? > > > > > > Thanks, > > > Piotr > > > > > > On Thu, Sep 19, 2019, 9:49 PM wrote: > > > > > > > This is an automated email from the ASF dual-hosted git > > repository. > > > > > > > > aharui pushed a commit to branch release/0.9.6 > > > > in repository > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7Cdde0aae4a55a4671118c08d73e89027d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637046630527648007sdata=kKoCF6bn5IspCE%2FsgK9naLzfFp%2BQx26CHM7kRyG4rug%3Dreserved=0 > > > > > > > > > > > > The following commit(s) were added to > refs/heads/release/0.9.6 > > by > > > this > > > > push: > > > > new 55f3786 fix ASDoc js-only > > > > 55f3786 is described below > > > > > > > > commit
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
The only place to include it without altering the release artifacts is in the RELEASE_NOTES addendum in our wiki. We could do that, but folks probably won't look there until after they have a problem. -Alex On 9/21/19, 4:44 AM, "Andrew Wetmore" wrote: Would it be acceptable to include some sort of explanation that compiling from source will require setting a number of environment variables, not just ANT_HOME, and that, if you really want to compile 0.9.6 from source, you should contact [LIST EMAIL] for instructions on what to do? It sort of dodges the issue, but permits moving forward with the release with the presumption that, as Alex says, most people will want and use the compiled binaries. I guess I would rather acknowledge the problem than look like we don't realize there is a problem. Andrew On Fri, Sep 20, 2019 at 2:10 AM Alex Harui wrote: > I think we all want to get a release out. > > My user experience was the equivalent of taking the source package and > trying to build it without setting any environment variables other than > ANT_HOME as specified in the README. It did not work for me. > > The question is: how many of our users are going to try to build the > source package? And when it fails and the ask about it, will it bother > them to be told to go get the Adobe stuff and set environment variables? I > think it is a small number of people, almost everyone else is going to grab > binaries. However, it is bothering me because we are an open source > project and our minimum configuration should work but doesn't. > > -Alex > > On 9/19/19, 9:20 PM, "Piotr Zarzycki" wrote: > > I'm in favor of moving forward. I would like to finally release stuff. > > I can live with setting up env. Variables. I'm concern by the user > experience than mine. > > Thanks, > Piotr > > On Thu, Sep 19, 2019, 10:36 PM Alex Harui > wrote: > > > Don't know. Judgement call. > > > > We've done a bunch of work since 0.9.4 to allow folks to be able to > > compile without the Adobe Flash and AIR SDKs. I've run into a > couple of > > problems. ASDoc's JSON generator was failing if you didn't have > Flash > > SDK. I mentioned it in the RC1 discuss thread. I think because it > is only > > this one example it is probably ok. > > > > What is less ok is another commit I have pending which is that the > main > > SWC build fails if you don't have Flash and AIR SDKs. In theory, > none of > > you should have been able to get the build to work without > environment > > variables for the Adobe stuff. So it depends a bit on how important > we > > think building from sources without the Adobe stuff is for this > release. > > If you did get the build to work without the Adobe stuff, check your > > environment and post the console output. I was fooled by having a > > PLAYERGLOBAL_HOME still set. When I took it away, more things broke. > > > > I'm testing building with Flash/AIR now to try to make sure my > js-only > > changes didn't affect js-swf. > > > > -Alex > > > > On 9/19/19, 1:19 PM, "Piotr Zarzycki" > wrote: > > > > Hi Alex, > > > > We need to have it in 0.9.6? > > > > Thanks, > > Piotr > > > > On Thu, Sep 19, 2019, 9:49 PM wrote: > > > > > This is an automated email from the ASF dual-hosted git > repository. > > > > > > aharui pushed a commit to branch release/0.9.6 > > > in repository > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7Cdde0aae4a55a4671118c08d73e89027d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637046630527648007sdata=kKoCF6bn5IspCE%2FsgK9naLzfFp%2BQx26CHM7kRyG4rug%3Dreserved=0 > > > > > > > > > The following commit(s) were added to refs/heads/release/0.9.6 > by > > this > > > push: > > > new 55f3786 fix ASDoc js-only > > > 55f3786 is described below > > > > > > commit 55f37864c2a1b58b00eb41bad9ae2a9c121a6c6e > > > Author: Alex Harui > > > AuthorDate: Thu Sep 19 11:19:28 2019 -0700 > > > > > > fix ASDoc js-only > > > --- > > > .../ASDoc/src/main/config/asdoc-js-config.xml | 41 > > > +- > > > 1 file changed, 40 insertions(+), 1 deletion(-) > > > > >
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
Would it be acceptable to include some sort of explanation that compiling
from source will require setting a number of environment variables, not
just ANT_HOME, and that, if you really want to compile 0.9.6 from source,
you should contact [LIST EMAIL] for instructions on what to do? It sort of
dodges the issue, but permits moving forward with the release with the
presumption that, as Alex says, most people will want and use the compiled
binaries.
I guess I would rather acknowledge the problem than look like we don't
realize there is a problem.
Andrew
On Fri, Sep 20, 2019 at 2:10 AM Alex Harui wrote:
> I think we all want to get a release out.
>
> My user experience was the equivalent of taking the source package and
> trying to build it without setting any environment variables other than
> ANT_HOME as specified in the README. It did not work for me.
>
> The question is: how many of our users are going to try to build the
> source package? And when it fails and the ask about it, will it bother
> them to be told to go get the Adobe stuff and set environment variables? I
> think it is a small number of people, almost everyone else is going to grab
> binaries. However, it is bothering me because we are an open source
> project and our minimum configuration should work but doesn't.
>
> -Alex
>
> On 9/19/19, 9:20 PM, "Piotr Zarzycki" wrote:
>
> I'm in favor of moving forward. I would like to finally release stuff.
>
> I can live with setting up env. Variables. I'm concern by the user
> experience than mine.
>
> Thanks,
> Piotr
>
> On Thu, Sep 19, 2019, 10:36 PM Alex Harui
> wrote:
>
> > Don't know. Judgement call.
> >
> > We've done a bunch of work since 0.9.4 to allow folks to be able to
> > compile without the Adobe Flash and AIR SDKs. I've run into a
> couple of
> > problems. ASDoc's JSON generator was failing if you didn't have
> Flash
> > SDK. I mentioned it in the RC1 discuss thread. I think because it
> is only
> > this one example it is probably ok.
> >
> > What is less ok is another commit I have pending which is that the
> main
> > SWC build fails if you don't have Flash and AIR SDKs. In theory,
> none of
> > you should have been able to get the build to work without
> environment
> > variables for the Adobe stuff. So it depends a bit on how important
> we
> > think building from sources without the Adobe stuff is for this
> release.
> > If you did get the build to work without the Adobe stuff, check your
> > environment and post the console output. I was fooled by having a
> > PLAYERGLOBAL_HOME still set. When I took it away, more things broke.
> >
> > I'm testing building with Flash/AIR now to try to make sure my
> js-only
> > changes didn't affect js-swf.
> >
> > -Alex
> >
> > On 9/19/19, 1:19 PM, "Piotr Zarzycki"
> wrote:
> >
> > Hi Alex,
> >
> > We need to have it in 0.9.6?
> >
> > Thanks,
> > Piotr
> >
> > On Thu, Sep 19, 2019, 9:49 PM wrote:
> >
> > > This is an automated email from the ASF dual-hosted git
> repository.
> > >
> > > aharui pushed a commit to branch release/0.9.6
> > > in repository
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7C0c98322e88ba48a1b80e08d73d81d93f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045500251094592sdata=mnsURL1gMlxcfmcHp2cC4j%2FEcp18AbP0lMakTFj0nKw%3Dreserved=0
> > >
> > >
> > > The following commit(s) were added to refs/heads/release/0.9.6
> by
> > this
> > > push:
> > > new 55f3786 fix ASDoc js-only
> > > 55f3786 is described below
> > >
> > > commit 55f37864c2a1b58b00eb41bad9ae2a9c121a6c6e
> > > Author: Alex Harui
> > > AuthorDate: Thu Sep 19 11:19:28 2019 -0700
> > >
> > > fix ASDoc js-only
> > > ---
> > > .../ASDoc/src/main/config/asdoc-js-config.xml | 41
> > > +-
> > > 1 file changed, 40 insertions(+), 1 deletion(-)
> > >
> > > diff --git
> > a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > > b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > > index a720ac6..8fd00e5 100644
> > > --- a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > > +++ b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > > @@ -141,7 +141,7 @@
> > >
> > >
> > >
> > > -
> > >
> >
> {playerglobalHome}/{targetPlayerMajorVersion}.{targetPlayerMinorVersion}
> > > +
> > ${frameworks_dir}/js/libs/XMLJS.swc
> > >
> > >
> > >
> > > @@ -537,6 +537,8 @@
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
I think we all want to get a release out.
My user experience was the equivalent of taking the source package and trying
to build it without setting any environment variables other than ANT_HOME as
specified in the README. It did not work for me.
The question is: how many of our users are going to try to build the source
package? And when it fails and the ask about it, will it bother them to be
told to go get the Adobe stuff and set environment variables? I think it is a
small number of people, almost everyone else is going to grab binaries.
However, it is bothering me because we are an open source project and our
minimum configuration should work but doesn't.
-Alex
On 9/19/19, 9:20 PM, "Piotr Zarzycki" wrote:
I'm in favor of moving forward. I would like to finally release stuff.
I can live with setting up env. Variables. I'm concern by the user
experience than mine.
Thanks,
Piotr
On Thu, Sep 19, 2019, 10:36 PM Alex Harui wrote:
> Don't know. Judgement call.
>
> We've done a bunch of work since 0.9.4 to allow folks to be able to
> compile without the Adobe Flash and AIR SDKs. I've run into a couple of
> problems. ASDoc's JSON generator was failing if you didn't have Flash
> SDK. I mentioned it in the RC1 discuss thread. I think because it is
only
> this one example it is probably ok.
>
> What is less ok is another commit I have pending which is that the main
> SWC build fails if you don't have Flash and AIR SDKs. In theory, none of
> you should have been able to get the build to work without environment
> variables for the Adobe stuff. So it depends a bit on how important we
> think building from sources without the Adobe stuff is for this release.
> If you did get the build to work without the Adobe stuff, check your
> environment and post the console output. I was fooled by having a
> PLAYERGLOBAL_HOME still set. When I took it away, more things broke.
>
> I'm testing building with Flash/AIR now to try to make sure my js-only
> changes didn't affect js-swf.
>
> -Alex
>
> On 9/19/19, 1:19 PM, "Piotr Zarzycki" wrote:
>
> Hi Alex,
>
> We need to have it in 0.9.6?
>
> Thanks,
> Piotr
>
> On Thu, Sep 19, 2019, 9:49 PM wrote:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > aharui pushed a commit to branch release/0.9.6
> > in repository
>
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7C0c98322e88ba48a1b80e08d73d81d93f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045500251094592sdata=mnsURL1gMlxcfmcHp2cC4j%2FEcp18AbP0lMakTFj0nKw%3Dreserved=0
> >
> >
> > The following commit(s) were added to refs/heads/release/0.9.6 by
> this
> > push:
> > new 55f3786 fix ASDoc js-only
> > 55f3786 is described below
> >
> > commit 55f37864c2a1b58b00eb41bad9ae2a9c121a6c6e
> > Author: Alex Harui
> > AuthorDate: Thu Sep 19 11:19:28 2019 -0700
> >
> > fix ASDoc js-only
> > ---
> > .../ASDoc/src/main/config/asdoc-js-config.xml | 41
> > +-
> > 1 file changed, 40 insertions(+), 1 deletion(-)
> >
> > diff --git
> a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > index a720ac6..8fd00e5 100644
> > --- a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > +++ b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > @@ -141,7 +141,7 @@
> >
> >
> >
> > -
> >
>
{playerglobalHome}/{targetPlayerMajorVersion}.{targetPlayerMinorVersion}
> > +
> ${frameworks_dir}/js/libs/XMLJS.swc
> >
> >
> >
> > @@ -537,6 +537,8 @@
> >
> >
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ITextFieldView.as
> >
> >
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ImageAndTextButtonView.as
> >
> >
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CheckBoxView.as
> > +
> >
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CloseButtonView.as
> > +
> >
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ControlBarMeasurementBead.as
> >
> >
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSButtonView.as
> >
> >
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
I'm in favor of moving forward. I would like to finally release stuff.
I can live with setting up env. Variables. I'm concern by the user
experience than mine.
Thanks,
Piotr
On Thu, Sep 19, 2019, 10:36 PM Alex Harui wrote:
> Don't know. Judgement call.
>
> We've done a bunch of work since 0.9.4 to allow folks to be able to
> compile without the Adobe Flash and AIR SDKs. I've run into a couple of
> problems. ASDoc's JSON generator was failing if you didn't have Flash
> SDK. I mentioned it in the RC1 discuss thread. I think because it is only
> this one example it is probably ok.
>
> What is less ok is another commit I have pending which is that the main
> SWC build fails if you don't have Flash and AIR SDKs. In theory, none of
> you should have been able to get the build to work without environment
> variables for the Adobe stuff. So it depends a bit on how important we
> think building from sources without the Adobe stuff is for this release.
> If you did get the build to work without the Adobe stuff, check your
> environment and post the console output. I was fooled by having a
> PLAYERGLOBAL_HOME still set. When I took it away, more things broke.
>
> I'm testing building with Flash/AIR now to try to make sure my js-only
> changes didn't affect js-swf.
>
> -Alex
>
> On 9/19/19, 1:19 PM, "Piotr Zarzycki" wrote:
>
> Hi Alex,
>
> We need to have it in 0.9.6?
>
> Thanks,
> Piotr
>
> On Thu, Sep 19, 2019, 9:49 PM wrote:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > aharui pushed a commit to branch release/0.9.6
> > in repository
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7Ce89e6b8c27de4c9708df08d73d3ea535%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045211631183873sdata=6RUG3ci0p%2F%2BQT3vYHOMFRqqW0QtukJPg8sydnisbSEc%3Dreserved=0
> >
> >
> > The following commit(s) were added to refs/heads/release/0.9.6 by
> this
> > push:
> > new 55f3786 fix ASDoc js-only
> > 55f3786 is described below
> >
> > commit 55f37864c2a1b58b00eb41bad9ae2a9c121a6c6e
> > Author: Alex Harui
> > AuthorDate: Thu Sep 19 11:19:28 2019 -0700
> >
> > fix ASDoc js-only
> > ---
> > .../ASDoc/src/main/config/asdoc-js-config.xml | 41
> > +-
> > 1 file changed, 40 insertions(+), 1 deletion(-)
> >
> > diff --git
> a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > index a720ac6..8fd00e5 100644
> > --- a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > +++ b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > @@ -141,7 +141,7 @@
> >
> >
> >
> > -
> >
> {playerglobalHome}/{targetPlayerMajorVersion}.{targetPlayerMinorVersion}
> > +
> ${frameworks_dir}/js/libs/XMLJS.swc
> >
> >
> >
> > @@ -537,6 +537,8 @@
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ITextFieldView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ImageAndTextButtonView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CheckBoxView.as
> > +
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CloseButtonView.as
> > +
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ControlBarMeasurementBead.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSButtonView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSTextButtonView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSToggleButtonView.as
> > @@ -558,6 +560,8 @@
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HScrollBarTrackView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/VRuleView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HRuleView.as
> > +
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/SolidBackgroundBead.as
> > +
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/SolidBackgroundWithChangeListenerBead.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextInputView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextInputWithBorderView.as
> >
> >
>
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
Don't know. Judgement call.
We've done a bunch of work since 0.9.4 to allow folks to be able to compile
without the Adobe Flash and AIR SDKs. I've run into a couple of problems.
ASDoc's JSON generator was failing if you didn't have Flash SDK. I mentioned
it in the RC1 discuss thread. I think because it is only this one example it
is probably ok.
What is less ok is another commit I have pending which is that the main SWC
build fails if you don't have Flash and AIR SDKs. In theory, none of you
should have been able to get the build to work without environment variables
for the Adobe stuff. So it depends a bit on how important we think building
from sources without the Adobe stuff is for this release. If you did get the
build to work without the Adobe stuff, check your environment and post the
console output. I was fooled by having a PLAYERGLOBAL_HOME still set. When I
took it away, more things broke.
I'm testing building with Flash/AIR now to try to make sure my js-only changes
didn't affect js-swf.
-Alex
On 9/19/19, 1:19 PM, "Piotr Zarzycki" wrote:
Hi Alex,
We need to have it in 0.9.6?
Thanks,
Piotr
On Thu, Sep 19, 2019, 9:49 PM wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> aharui pushed a commit to branch release/0.9.6
> in repository
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7Ce89e6b8c27de4c9708df08d73d3ea535%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045211631183873sdata=6RUG3ci0p%2F%2BQT3vYHOMFRqqW0QtukJPg8sydnisbSEc%3Dreserved=0
>
>
> The following commit(s) were added to refs/heads/release/0.9.6 by this
> push:
> new 55f3786 fix ASDoc js-only
> 55f3786 is described below
>
> commit 55f37864c2a1b58b00eb41bad9ae2a9c121a6c6e
> Author: Alex Harui
> AuthorDate: Thu Sep 19 11:19:28 2019 -0700
>
> fix ASDoc js-only
> ---
> .../ASDoc/src/main/config/asdoc-js-config.xml | 41
> +-
> 1 file changed, 40 insertions(+), 1 deletion(-)
>
> diff --git a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> index a720ac6..8fd00e5 100644
> --- a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> +++ b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> @@ -141,7 +141,7 @@
>
>
>
> -
>
{playerglobalHome}/{targetPlayerMajorVersion}.{targetPlayerMinorVersion}
> +
${frameworks_dir}/js/libs/XMLJS.swc
>
>
>
> @@ -537,6 +537,8 @@
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ITextFieldView.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ImageAndTextButtonView.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CheckBoxView.as
> +
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CloseButtonView.as
> +
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ControlBarMeasurementBead.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSButtonView.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSTextButtonView.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSToggleButtonView.as
> @@ -558,6 +560,8 @@
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HScrollBarTrackView.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/VRuleView.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HRuleView.as
> +
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/SolidBackgroundBead.as
> +
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/SolidBackgroundWithChangeListenerBead.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextInputView.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextInputWithBorderView.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextAreaView.as
> @@ -572,6 +576,41 @@
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/VScrollBar.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/HScrollBar.as
>
>
${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/ScrollBar.as
> +
Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only
Hi Alex,
We need to have it in 0.9.6?
Thanks,
Piotr
On Thu, Sep 19, 2019, 9:49 PM wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> aharui pushed a commit to branch release/0.9.6
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>
>
> The following commit(s) were added to refs/heads/release/0.9.6 by this
> push:
> new 55f3786 fix ASDoc js-only
> 55f3786 is described below
>
> commit 55f37864c2a1b58b00eb41bad9ae2a9c121a6c6e
> Author: Alex Harui
> AuthorDate: Thu Sep 19 11:19:28 2019 -0700
>
> fix ASDoc js-only
> ---
> .../ASDoc/src/main/config/asdoc-js-config.xml | 41
> +-
> 1 file changed, 40 insertions(+), 1 deletion(-)
>
> diff --git a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> index a720ac6..8fd00e5 100644
> --- a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> +++ b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> @@ -141,7 +141,7 @@
>
>
>
> -
>
> {playerglobalHome}/{targetPlayerMajorVersion}.{targetPlayerMinorVersion}
> + ${frameworks_dir}/js/libs/XMLJS.swc
>
>
>
> @@ -537,6 +537,8 @@
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ITextFieldView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ImageAndTextButtonView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CheckBoxView.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CloseButtonView.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ControlBarMeasurementBead.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSButtonView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSTextButtonView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSToggleButtonView.as
> @@ -558,6 +560,8 @@
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HScrollBarTrackView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/VRuleView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HRuleView.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/SolidBackgroundBead.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/SolidBackgroundWithChangeListenerBead.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextInputView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextInputWithBorderView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextAreaView.as
> @@ -572,6 +576,41 @@
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/VScrollBar.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/HScrollBar.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/ScrollBar.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/controllers/ButtonAutoRepeatController.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/controllers/DropDownListController.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/TextFieldItemRenderer.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/VScrollBar.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/HScrollBar.as
> +
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/ScrollBar.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/CSSShape.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/CSSSprite.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/IBorderModel.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/StageProxy.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/StyleableCSSTextField.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/WrappedMovieClip.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/WrappedShape.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/WrappedSprite.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/WrappedTextField.as
> +
>
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/UIButtonBase.as
> +
>
>
