Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

2019-10-16 Thread Andrew Wetmore
Can they have their own dedicated page, wreathed around with cautions and
disclaimers to scare away folks who should not be using them?

On Wed, Oct 16, 2019 at 9:42 AM Carlos Rovira 
wrote:

> Hi,
>
> we get request to remove Nightly builds from download page (see issue in
> GitHub below).
> I open this thread to discuss where is better place for it.
>
> thanks
>
>
> El mié., 16 oct. 2019 a las 14:26, GitBox () escribió:
>
> > carlosrovira commented on issue #498: Nightly builds must not be promoted
> > on download pages
> > URL:
> > https://github.com/apache/royale-asjs/issues/498#issuecomment-542675010
> >
> >
> >I searched to the place in our mailing list that seems to be the
> source
> > of the actual state for nightly on download page:
> >
> >
> >
> http://apache-royale-development.20373.n8.nabble.com/Need-help-with-CSS-class-selector-font-family-is-always-Arial-tp1418p1485.html
> >
> >I think If we want to change it we need to discuss in list how we want
> > it now
> >
> >
> >
> > 
> > This is an automated message from the Apache Git Service.
> > To respond to the message, please log on to GitHub and use the
> > URL above to go to the specific comment.
> >
> > For queries about this service, please contact Infrastructure at:
> > us...@infra.apache.org
> >
> >
> > With regards,
> > Apache Git Services
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

2019-10-09 Thread Andrew Wetmore
I recently had a hard drive crash, so I have a new hard drive without many
past artifacts, a virgin system. I was using 0.9.4 in Moonshine before the
crash without, as far as I know, any Ant or npm magic. Have things changed
significantly between that release and this one?

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Oct 9, 2019 at 6:40 PM Andrew Wetmore  wrote:

> Instructions that require Ant or npm are not, in my humble opinion,
> entry-level instructions. I should not have to be an SDK constructor in
> order to use Royale to build the apps I want to build.
>
> The instructions need to be a TON clearer, and more obvious from the
> typical entry points where a new user would encounter Royale. We should
> possibly also add qualifiers to any statements that an IDE like Moonshine
> supports Royale. It does not support Royale as we deliver it, but only
> after it has been tweaked by processes that are obvious to those developing
> Royale but not to the world at large.
>
> Sorry if I sound irked, but consider that my reaction may mirror that of
> many who want to try Royale out but trip over the starting line.
>
> Andrew
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> <#m_-6424551647352680386_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Wed, Oct 9, 2019 at 5:52 PM Josh Tynjala 
> wrote:
>
>> The main royale-asjs README mentions the Adobe stuff as optional
>> dependencies, but the instructions seem to be aimed at contributors:
>>
>>
>> https://github.com/apache/royale-asjs#additional-prerequisites-for-swf-output
>>
>> What a non-contributor user is expected to do appears to be mentioned on
>> this page (it requires running the InstallAdobeSDKs.xml Ant script):
>>
>> https://apache.github.io/royale-docs/get-started/download-royale
>>
>> I recall that if you install the npm version of Royale, it will ask to
>> download the Adobe dependencies for you. That's probably the easiest way
>> for a new user to get started.
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC <https://bowlerhat.dev>
>>
>>
>> On Wed, Oct 9, 2019 at 1:44 PM Andrew Wetmore 
>> wrote:
>>
>> > Thanks @Josh Tynjala  . Do we say that
>> > anywhere in the instructions where a new user would run into it?
>> >
>> >
>> > <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>> Virus-free.
>> > www.avast.com
>> > <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> > <#m_-3106823410389824051_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> >
>> > On Wed, Oct 9, 2019 at 5:27 PM Josh Tynjala 
>> > wrote:
>> >
>> >> If you downloaded the js-swf binary distribution, you need to add the
>> >> Adobe
>> >> dependencies manually. We cannot distribute them.
>> >>
>> >> The playerglobal.swc in the js-only version is not the real one from
>> >> Adobe.
>> >> It's just a placeholder to make certain IDEs happy. I think it's just a
>> >> copy of js.swc.
>> >>
>> >> --
>> >> Josh Tynjala
>> >> Bowler Hat LLC <https://bowlerhat.dev>
>> >>
>> >>
>> >> On Wed, Oct 9, 2019 at 1:16 PM Andrew Wetmore 
>> >> wrote:
>> >>
>> >> > I wiped out the previous project and tried again with the Royale
>> JS-SWF
>> >> > version. When I try to compile the project in Moonshine for either
>> JS or
>> >> > Flash, I see this error message: "This SDK does not contains
>> >> > playerglobal.swc in frameworks\libs\player\11.7\playerglobal.swc.
>> >> Download
>> >> > playerglobal here". When I look in the package for the JS-only
>> version,
>> >> > playerglobal is there. I do not see it in the JS_SWF version.
>> >> >
>> >> > <
>> >> >
>> >>
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >> > >
>> >> &g

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

2019-10-09 Thread Andrew Wetmore
That would be fine. I am stuck, evidently, at something in the 0.9.6
release of the JS-only version being broken.

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Oct 9, 2019 at 7:09 PM Josh Tynjala 
wrote:

> Node/npm is pretty normal prerequisite for most JS development these days,
> but I understand your point.
>
> Ideally, we should be encouraging developers to start with the JS-only
> version, which doesn't require any of those special dependencies (other
> than Java, which is necessary to run the compiler).
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Wed, Oct 9, 2019 at 2:41 PM Andrew Wetmore  wrote:
>
> > Instructions that require Ant or npm are not, in my humble opinion,
> > entry-level instructions. I should not have to be an SDK constructor in
> > order to use Royale to build the apps I want to build.
> >
> > The instructions need to be a TON clearer, and more obvious from the
> > typical entry points where a new user would encounter Royale. We should
> > possibly also add qualifiers to any statements that an IDE like Moonshine
> > supports Royale. It does not support Royale as we deliver it, but only
> > after it has been tweaked by processes that are obvious to those
> developing
> > Royale but not to the world at large.
> >
> > Sorry if I sound irked, but consider that my reaction may mirror that of
> > many who want to try Royale out but trip over the starting line.
> >
> > Andrew
> >
> > <
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > >
> > Virus-free.
> > www.avast.com
> > <
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > >
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > On Wed, Oct 9, 2019 at 5:52 PM Josh Tynjala 
> > wrote:
> >
> > > The main royale-asjs README mentions the Adobe stuff as optional
> > > dependencies, but the instructions seem to be aimed at contributors:
> > >
> > >
> > >
> >
> https://github.com/apache/royale-asjs#additional-prerequisites-for-swf-output
> > >
> > > What a non-contributor user is expected to do appears to be mentioned
> on
> > > this page (it requires running the InstallAdobeSDKs.xml Ant script):
> > >
> > > https://apache.github.io/royale-docs/get-started/download-royale
> > >
> > > I recall that if you install the npm version of Royale, it will ask to
> > > download the Adobe dependencies for you. That's probably the easiest
> way
> > > for a new user to get started.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Wed, Oct 9, 2019 at 1:44 PM Andrew Wetmore 
> > wrote:
> > >
> > > > Thanks @Josh Tynjala  . Do we say that
> > > > anywhere in the instructions where a new user would run into it?
> > > >
> > > >
> > > > <
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > >
> > > Virus-free.
> > > > www.avast.com
> > > > <
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > > >
> > > > <#m_-3106823410389824051_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > >
> > > > On Wed, Oct 9, 2019 at 5:27 PM Josh Tynjala <
> joshtynj...@bowlerhat.dev
> > >
> > > > wrote:
> > > >
> > > >> If you downloaded the js-swf binary distribution, you need to add
> the
> > > >> Adobe
> > > >> dependencies manually. We cannot distribute them.
> > > >>
> > > >> The playerglobal.swc in the js-only version is not the real one from
> > > >> Adobe.
> > > >> It's just a placeholder to make certain IDEs happy. I think it's
> just
> > a
> > > >> copy of js.swc.
> > > >>
> > > >> --
> > > >> Josh Tynjala
> > > >> Bowler Hat LLC <https://bowlerhat.dev>
> > > >>
> > > >>
> > > >> On Wed, Oct 9, 

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

2019-10-09 Thread Andrew Wetmore
Instructions that require Ant or npm are not, in my humble opinion,
entry-level instructions. I should not have to be an SDK constructor in
order to use Royale to build the apps I want to build.

The instructions need to be a TON clearer, and more obvious from the
typical entry points where a new user would encounter Royale. We should
possibly also add qualifiers to any statements that an IDE like Moonshine
supports Royale. It does not support Royale as we deliver it, but only
after it has been tweaked by processes that are obvious to those developing
Royale but not to the world at large.

Sorry if I sound irked, but consider that my reaction may mirror that of
many who want to try Royale out but trip over the starting line.

Andrew

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Oct 9, 2019 at 5:52 PM Josh Tynjala 
wrote:

> The main royale-asjs README mentions the Adobe stuff as optional
> dependencies, but the instructions seem to be aimed at contributors:
>
>
> https://github.com/apache/royale-asjs#additional-prerequisites-for-swf-output
>
> What a non-contributor user is expected to do appears to be mentioned on
> this page (it requires running the InstallAdobeSDKs.xml Ant script):
>
> https://apache.github.io/royale-docs/get-started/download-royale
>
> I recall that if you install the npm version of Royale, it will ask to
> download the Adobe dependencies for you. That's probably the easiest way
> for a new user to get started.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Wed, Oct 9, 2019 at 1:44 PM Andrew Wetmore  wrote:
>
> > Thanks @Josh Tynjala  . Do we say that
> > anywhere in the instructions where a new user would run into it?
> >
> >
> > <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> Virus-free.
> > www.avast.com
> > <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> > <#m_-3106823410389824051_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > On Wed, Oct 9, 2019 at 5:27 PM Josh Tynjala 
> > wrote:
> >
> >> If you downloaded the js-swf binary distribution, you need to add the
> >> Adobe
> >> dependencies manually. We cannot distribute them.
> >>
> >> The playerglobal.swc in the js-only version is not the real one from
> >> Adobe.
> >> It's just a placeholder to make certain IDEs happy. I think it's just a
> >> copy of js.swc.
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC <https://bowlerhat.dev>
> >>
> >>
> >> On Wed, Oct 9, 2019 at 1:16 PM Andrew Wetmore 
> >> wrote:
> >>
> >> > I wiped out the previous project and tried again with the Royale
> JS-SWF
> >> > version. When I try to compile the project in Moonshine for either JS
> or
> >> > Flash, I see this error message: "This SDK does not contains
> >> > playerglobal.swc in frameworks\libs\player\11.7\playerglobal.swc.
> >> Download
> >> > playerglobal here". When I look in the package for the JS-only
> version,
> >> > playerglobal is there. I do not see it in the JS_SWF version.
> >> >
> >> > <
> >> >
> >>
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >> > >
> >> > Virus-free.
> >> > www.avast.com
> >> > <
> >> >
> >>
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >> > >
> >> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >> >
> >> > On Wed, Oct 9, 2019 at 3:07 PM Alex Harui 
> >> > wrote:
> >> >
> >> > > When you build with AIR_HOME (which is required to create release
> >> > > artifacts, since we want to produce both jsonly and js-swf in one
> >> run), a
> >> > > different target called "jsonly-package" run and tries to muck with
> >> some
> >> > > files before packaging the js-only artifacts.  It could be that the
> >> > > jsonly-package needs updating now that SWF SWCs are listed in
> >> > > royale-config.xml.  That means we've had this bug for months and
> >> nobody
> >> >

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

2019-10-09 Thread Andrew Wetmore
Thanks @Josh Tynjala  . Do we say that anywhere
in the instructions where a new user would run into it?

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Oct 9, 2019 at 5:27 PM Josh Tynjala 
wrote:

> If you downloaded the js-swf binary distribution, you need to add the Adobe
> dependencies manually. We cannot distribute them.
>
> The playerglobal.swc in the js-only version is not the real one from Adobe.
> It's just a placeholder to make certain IDEs happy. I think it's just a
> copy of js.swc.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Wed, Oct 9, 2019 at 1:16 PM Andrew Wetmore  wrote:
>
> > I wiped out the previous project and tried again with the Royale JS-SWF
> > version. When I try to compile the project in Moonshine for either JS or
> > Flash, I see this error message: "This SDK does not contains
> > playerglobal.swc in frameworks\libs\player\11.7\playerglobal.swc.
> Download
> > playerglobal here". When I look in the package for the JS-only version,
> > playerglobal is there. I do not see it in the JS_SWF version.
> >
> > <
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > >
> > Virus-free.
> > www.avast.com
> > <
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > >
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > On Wed, Oct 9, 2019 at 3:07 PM Alex Harui 
> > wrote:
> >
> > > When you build with AIR_HOME (which is required to create release
> > > artifacts, since we want to produce both jsonly and js-swf in one
> run), a
> > > different target called "jsonly-package" run and tries to muck with
> some
> > > files before packaging the js-only artifacts.  It could be that the
> > > jsonly-package needs updating now that SWF SWCs are listed in
> > > royale-config.xml.  That means we've had this bug for months and nobody
> > > noticed until now.
> > >
> > > -Alex
> > >
> > > On 10/9/19, 9:38 AM, "Josh Tynjala" 
> wrote:
> > >
> > > It looks like the Ant target that updates the library-path for the
> > > JS-only
> > > build is called tweak-for-jsonly. Copied here for convenience:
> > >
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fasn0idata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=7h3ZHxgGsfZqP8kE22amKQYDr7%2BNyQa7EpoG86147uU%3Dreserved=0
> > >
> > > I see that it has unless="env.AIR_HOME", which means that this
> target
> > > is
> > > skipped if the AIR_HOME environment variable is set. With that in
> > > mind, I'm
> > > guessing that AIR_HOME needs to be set for the js-swf build, but
> > > cleared
> > > for the js-only build.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=Ih2P7zf2c%2BLPn5ktks02EE7k6s24RKcabVem7VqjWeg%3Dreserved=0
> > > >
> > >
> > >
> > > On Wed, Oct 9, 2019 at 6:52 AM Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> > > wrote:
> > >
> > > > Hi Guys,
> > > >
> > > > It looks like we have broken royale-config in released SDK.
> Andrew
> > > raised
> > > > in Moonshine GitHub issue that he couldn't build Hello World
> > > project. I
> > > > tried Moonshine and downloaded JS-only version of SDK. I get
> > > following
> > > > error [1].
> > > > I downloaded JS-SWF version and tried compile project again -
> this
> > > time it
> > > > went fine.
> > > >
> > > > JS-only version of released 0.9.6 contains in section
> > >  -
> > > > list of swc. - Those swc doesn't exists in JS-only.
> > > >
> > > > Fragment of conf

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

2019-10-09 Thread Andrew Wetmore
I wiped out the previous project and tried again with the Royale JS-SWF
version. When I try to compile the project in Moonshine for either JS or
Flash, I see this error message: "This SDK does not contains
playerglobal.swc in frameworks\libs\player\11.7\playerglobal.swc. Download
playerglobal here". When I look in the package for the JS-only version,
playerglobal is there. I do not see it in the JS_SWF version.

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Oct 9, 2019 at 3:07 PM Alex Harui  wrote:

> When you build with AIR_HOME (which is required to create release
> artifacts, since we want to produce both jsonly and js-swf in one run), a
> different target called "jsonly-package" run and tries to muck with some
> files before packaging the js-only artifacts.  It could be that the
> jsonly-package needs updating now that SWF SWCs are listed in
> royale-config.xml.  That means we've had this bug for months and nobody
> noticed until now.
>
> -Alex
>
> On 10/9/19, 9:38 AM, "Josh Tynjala"  wrote:
>
> It looks like the Ant target that updates the library-path for the
> JS-only
> build is called tweak-for-jsonly. Copied here for convenience:
>
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fasn0idata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=7h3ZHxgGsfZqP8kE22amKQYDr7%2BNyQa7EpoG86147uU%3Dreserved=0
>
> I see that it has unless="env.AIR_HOME", which means that this target
> is
> skipped if the AIR_HOME environment variable is set. With that in
> mind, I'm
> guessing that AIR_HOME needs to be set for the js-swf build, but
> cleared
> for the js-only build.
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=Ih2P7zf2c%2BLPn5ktks02EE7k6s24RKcabVem7VqjWeg%3Dreserved=0
> >
>
>
> On Wed, Oct 9, 2019 at 6:52 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> wrote:
>
> > Hi Guys,
> >
> > It looks like we have broken royale-config in released SDK. Andrew
> raised
> > in Moonshine GitHub issue that he couldn't build Hello World
> project. I
> > tried Moonshine and downloaded JS-only version of SDK. I get
> following
> > error [1].
> > I downloaded JS-SWF version and tried compile project again - this
> time it
> > went fine.
> >
> > JS-only version of released 0.9.6 contains in section
>  -
> > list of swc. - Those swc doesn't exists in JS-only.
> >
> > Fragment of config
> >
> > > 
> > >  libs/Basic.swc
> > >  libs/Binding.swc
> > >  libs/Charts.swc
> > >  libs/Collections.swc
> > >  libs/Core.swc
> > > 
> >
> >
> > JS-only nightly build of 0.9.7 - doesn't contains in that section
> anything
> >
> > >   
> > >   
> >
> >
> > [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F2lgvkdata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=IebVohnQGkmg%2BAO2RJCS2LRTdP3LQE0NoQ%2BUt7xlOJI%3Dreserved=0
> >
> > Thanks,
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=BmbfQaY1AjgUQk61TOlDZqRi1jWSJWDFaxgzaFiw1c4%3Dreserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=BmbfQaY1AjgUQk61TOlDZqRi1jWSJWDFaxgzaFiw1c4%3Dreserved=0
> >*
> >
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/





<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


Re: Acceptance of Royale by Flex Developers

2019-10-08 Thread Andrew Wetmore
omes to give another subset of
> meaning
> > >
> > > just my opinion about this.
> > >
> > > Carlos
> > >
> > >
> > >
> > > El mar., 8 oct. 2019 a las 9:23, Chris Velevitch (<
> > chris.velevi...@gmail.com>)
> > > escribió:
> > >
> > > > The use of the terms "strands" and "beads" still doesn't make
> sense to
> > > > me because they are concepts I have never heard before and it is
> > > > creating a barrier to acceptance and deepens the learning curve.
> As
> > > > far as I can tell, it's something to do with visual/UI
> components.
> > > >
> > > > The section "Strands and Beads" should ideally be titled "Visual
> > > > Components" because that section is about visual components and
> is
> > > > alluding to the fact visual components are standalone microcosms
> of
> > > > the MVC pattern and the ability to treat the model, view and
> > > > controller as plugins to the component. The statement that
> components
> > > > are "strands" is, in my mind, misleading because it doesn't make
> sense
> > > > to interchange terms components and strands if a strand is a
> > > > component. In fact, diving into the code, the "addBead" function
> gives
> > > > the "bead" a reference to the component the "bead" is being
> added to.
> > > >
> > > > It is clear from the documentation that "beads" are "plugins"
> and the
> > > > documentation should be talking about extending components with
> > > > plugins. All references to "bead" should be replaced with
> "plugin" and
> > > > all references to "strand" be replaced with either
> "hostComponent", or
> > > > "parent" or appropriately something else.
> > > >
> > > > We seem to be neglecting the rich heritage that we have gotten
> from
> > > > Adobe Flex and I don't see the point giving existing concepts new
> > > > names.
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C56331bd7a799497db41308d74c02c990%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637061447162721530sdata=zhUI1U2%2F0jU9Od5Pm2pE%2B6RKrJxm97BafPqJ%2FVxrB%2Bg%3Dreserved=0
> >
> >
> >
> > --
> >
> >
> > Chris
> > --
> > Chris Velevitch
> > m: 0415 469 095
> >
>
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C56331bd7a799497db41308d74c02c990%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637061447162721530sdata=zhUI1U2%2F0jU9Od5Pm2pE%2B6RKrJxm97BafPqJ%2FVxrB%2Bg%3Dreserved=0
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Andrew Wetmore
I have edited the release. The only thing I would improve, if I could, is
the graphic at the top. The release number appears as "v0.9.6". I am pretty
sure it would be better as "v. 0.9.6", but this is obviously not something
to delay the release for.

Andrew

On Tue, Oct 8, 2019 at 11:56 AM Andrew Wetmore  wrote:

> Got it! Thanks!
>
> On Tue, Oct 8, 2019 at 10:49 AM Carlos Rovira 
> wrote:
>
>> Yes! that's it :)
>>
>>
>> El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>> escribió:
>>
>> > I think that would be the link:
>> > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
>> >
>> > wt., 8 paź 2019 o 16:29 Andrew Wetmore 
>> napisał(a):
>> >
>> > > @Carlos Rovira  where is the draft post? I
>> had
>> > a
>> > > hard disk failure this past weekend and am slowly rebuilding my
>> system.
>> > > Have to find all my links again.
>> > >
>> > > a
>> > >
>> > > On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore 
>> > wrote:
>> > >
>> > > > I can do this in a couple of hours
>> > > >
>> > > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, <
>> carlosrov...@apache.org>
>> > > > wrote:
>> > > >
>> > > >> Hi Piotr,
>> > > >>
>> > > >> I'll wait Andrew's review and then will publish it. If Andrew make
>> his
>> > > >> changes this afternoon, I can follow up and publish it.
>> > > >> Then we can post on social networks next or wait to tomorrow
>> > > >>
>> > > >>
>> > > >>
>> > > >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
>> > > >> piotrzarzyck...@gmail.com>)
>> > > >> escribió:
>> > > >>
>> > > >> > Just to make sure that you understand why I asked you to post
>> > download
>> > > >> > links on website along with source code.
>> > > >> >
>> > > >> > I will announce on dev, users and announce list - someone who
>> read
>> > > >> email -
>> > > >> > will have two options:
>> > > >> > 1) Can click in that email on royale.apache.org
>> > > >> > 2) Can download directly binaries or source code from provided
>> links
>> > > in
>> > > >> the
>> > > >> > email
>> > > >> >
>> > > >> > If user do #1 he will see old links on website which will be
>> > > >> misleading. -
>> > > >> > Do you understand now why I asked you to publish stuff first ?
>> > > >> >
>> > > >> > However as I said if you prefer do this in a opposite way that's
>> > fine
>> > > >> with
>> > > >> > me. :)
>> > > >> >
>> > > >> >
>> > > >> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> > > >> > napisał(a):
>> > > >> >
>> > > >> > > This is the goal of syncing everything tomorrow. I asked you to
>> > > >> publish
>> > > >> > > first link and source code on website, cause my announce
>> probably
>> > go
>> > > >> > first
>> > > >> > > one and I didn't want to mislead with what will be on website.
>> > > >> However if
>> > > >> > > you wanted to do that differently I'm fine - Couple of hours of
>> > > >> > misleading
>> > > >> > > doesn't hurts anyone maybe. - We will see tomorrow.
>> > > >> > >
>> > > >> > > wt., 8 paź 2019 o 11:05 Carlos Rovira > >
>> > > >> > > napisał(a):
>> > > >> > >
>> > > >> > >> Hi,
>> > > >> > >> ok, is normal,
>> > > >> > >> as people following our dev, are as well using links to 0.9.6
>> > > >> releases.
>> > > >> > >> The update of links in website is more about to announce to
>> the
>> > > rest
>> > > >> of
>> > > >> > >> the
>> > > >>

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Andrew Wetmore
Got it! Thanks!

On Tue, Oct 8, 2019 at 10:49 AM Carlos Rovira 
wrote:

> Yes! that's it :)
>
>
> El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > I think that would be the link:
> > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> >
> > wt., 8 paź 2019 o 16:29 Andrew Wetmore  napisał(a):
> >
> > > @Carlos Rovira  where is the draft post? I
> had
> > a
> > > hard disk failure this past weekend and am slowly rebuilding my system.
> > > Have to find all my links again.
> > >
> > > a
> > >
> > > On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore 
> > wrote:
> > >
> > > > I can do this in a couple of hours
> > > >
> > > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira,  >
> > > > wrote:
> > > >
> > > >> Hi Piotr,
> > > >>
> > > >> I'll wait Andrew's review and then will publish it. If Andrew make
> his
> > > >> changes this afternoon, I can follow up and publish it.
> > > >> Then we can post on social networks next or wait to tomorrow
> > > >>
> > > >>
> > > >>
> > > >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
> > > >> piotrzarzyck...@gmail.com>)
> > > >> escribió:
> > > >>
> > > >> > Just to make sure that you understand why I asked you to post
> > download
> > > >> > links on website along with source code.
> > > >> >
> > > >> > I will announce on dev, users and announce list - someone who read
> > > >> email -
> > > >> > will have two options:
> > > >> > 1) Can click in that email on royale.apache.org
> > > >> > 2) Can download directly binaries or source code from provided
> links
> > > in
> > > >> the
> > > >> > email
> > > >> >
> > > >> > If user do #1 he will see old links on website which will be
> > > >> misleading. -
> > > >> > Do you understand now why I asked you to publish stuff first ?
> > > >> >
> > > >> > However as I said if you prefer do this in a opposite way that's
> > fine
> > > >> with
> > > >> > me. :)
> > > >> >
> > > >> >
> > > >> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki  >
> > > >> > napisał(a):
> > > >> >
> > > >> > > This is the goal of syncing everything tomorrow. I asked you to
> > > >> publish
> > > >> > > first link and source code on website, cause my announce
> probably
> > go
> > > >> > first
> > > >> > > one and I didn't want to mislead with what will be on website.
> > > >> However if
> > > >> > > you wanted to do that differently I'm fine - Couple of hours of
> > > >> > misleading
> > > >> > > doesn't hurts anyone maybe. - We will see tomorrow.
> > > >> > >
> > > >> > > wt., 8 paź 2019 o 11:05 Carlos Rovira 
> > > >> > > napisał(a):
> > > >> > >
> > > >> > >> Hi,
> > > >> > >> ok, is normal,
> > > >> > >> as people following our dev, are as well using links to 0.9.6
> > > >> releases.
> > > >> > >> The update of links in website is more about to announce to the
> > > rest
> > > >> of
> > > >> > >> the
> > > >> > >> world that is not as close to us as the rest of community.
> > > >> > >> So it's important to communicate in the most organized way we
> > can.
> > > >> > >>
> > > >> > >> thanks!
> > > >> > >>
> > > >> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> > > >> > >> piotrzarzyck...@gmail.com>)
> > > >> > >> escribió:
> > > >> > >>
> > > >> > >> > Just FYI: npm stuff and Maven artifacts are being published
> for
> > > >> couple
> > > >> > >> of
> > > >> > >> > days already, so people are using released 0.9.6 trough npm.
> -
> >

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Andrew Wetmore
@Carlos Rovira  where is the draft post? I had a
hard disk failure this past weekend and am slowly rebuilding my system.
Have to find all my links again.

a

On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore  wrote:

> I can do this in a couple of hours
>
> On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, 
> wrote:
>
>> Hi Piotr,
>>
>> I'll wait Andrew's review and then will publish it. If Andrew make his
>> changes this afternoon, I can follow up and publish it.
>> Then we can post on social networks next or wait to tomorrow
>>
>>
>>
>> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>> escribió:
>>
>> > Just to make sure that you understand why I asked you to post download
>> > links on website along with source code.
>> >
>> > I will announce on dev, users and announce list - someone who read
>> email -
>> > will have two options:
>> > 1) Can click in that email on royale.apache.org
>> > 2) Can download directly binaries or source code from provided links in
>> the
>> > email
>> >
>> > If user do #1 he will see old links on website which will be
>> misleading. -
>> > Do you understand now why I asked you to publish stuff first ?
>> >
>> > However as I said if you prefer do this in a opposite way that's fine
>> with
>> > me. :)
>> >
>> >
>> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki 
>> > napisał(a):
>> >
>> > > This is the goal of syncing everything tomorrow. I asked you to
>> publish
>> > > first link and source code on website, cause my announce probably go
>> > first
>> > > one and I didn't want to mislead with what will be on website.
>> However if
>> > > you wanted to do that differently I'm fine - Couple of hours of
>> > misleading
>> > > doesn't hurts anyone maybe. - We will see tomorrow.
>> > >
>> > > wt., 8 paź 2019 o 11:05 Carlos Rovira 
>> > > napisał(a):
>> > >
>> > >> Hi,
>> > >> ok, is normal,
>> > >> as people following our dev, are as well using links to 0.9.6
>> releases.
>> > >> The update of links in website is more about to announce to the rest
>> of
>> > >> the
>> > >> world that is not as close to us as the rest of community.
>> > >> So it's important to communicate in the most organized way we can.
>> > >>
>> > >> thanks!
>> > >>
>> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
>> > >> piotrzarzyck...@gmail.com>)
>> > >> escribió:
>> > >>
>> > >> > Just FYI: npm stuff and Maven artifacts are being published for
>> couple
>> > >> of
>> > >> > days already, so people are using released 0.9.6 trough npm. - It's
>> > >> happen
>> > >> > automatically in case of npm.
>> > >> >
>> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
>> > >> > napisał(a):
>> > >> >
>> > >> > > Fine with me. I make announce tomorrow morning and review what
>> was
>> > >> your
>> > >> > > change and update Draft.
>> > >> > >
>> > >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira 
>> > >> > > napisał(a):
>> > >> > >
>> > >> > >> Hi, Piotr,
>> > >> > >>
>> > >> > >> I think we should update all at the same time, since we want to
>> > post
>> > >> in
>> > >> > >> twitter, Facebook and linkedin.
>> > >> > >> Doesn't have sense to me upload just a few links since almost
>> > nobody
>> > >> > will
>> > >> > >> notice it (and are already in GitHub releases). If we need to
>> wait
>> > a
>> > >> day
>> > >> > >> to
>> > >> > >> send the official announcement it's ok for me. We can finish to
>> > >> improve
>> > >> > >> the
>> > >> > >> blog post in the meanwhile to do it better.
>> > >> > >>
>> > >> > >> For example, I changed a bit the wording, since we are not as
>> > >> "early" or
>> > >> > >> "alpha" 

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Andrew Wetmore
;> As well if someone notice something that needs to be updated can
> > >> notify
> > >> > >> us.
> > >> > >>
> > >> > >> Thanks
> > >> > >>
> > >> > >>
> > >> > >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
> > >> > >> piotrzarzyck...@gmail.com>)
> > >> > >> escribió:
> > >> > >>
> > >> > >> > Download and source code websites looks good to me. In blog
> post
> > >> you
> > >> > >> have
> > >> > >> > broken github links - review them and fix.
> > >> > >> >
> > >> > >> > Apart of that publish only Download and Source code. Blog post
> > >> should
> > >> > be
> > >> > >> > publish after I think official announce on dev, users and
> > announce
> > >> > >> mailing
> > >> > >> > list. I'm going to do that tomorrow, cause there is still time
> > for
> > >> > >> review
> > >> > >> > Draft of announcement.
> > >> > >> >
> > >> > >> > Thanks,
> > >> > >> > Piotr
> > >> > >> >
> > >> > >> > wt., 8 paź 2019 o 10:32 Carlos Rovira  >
> > >> > >> > napisał(a):
> > >> > >> >
> > >> > >> > > Hi,
> > >> > >> > >
> > >> > >> > > Thanks Piotr, for the link :)
> > >> > >> > >
> > >> > >> > > I just updated website on pre site please take a quick look
> and
> > >> I'll
> > >> > >> > > publish it:
> > >> > >> > >
> > >> > >> > >
> https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> > >> > >> > > https://royale.codeoscopic.com/download/
> > >> > >> > > https://royale.codeoscopic.com/source-code/
> > >> > >> > >
> > >> > >> > > thanks
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
> > >> > >> > carlosrov...@apache.org
> > >> > >> > > >)
> > >> > >> > > escribió:
> > >> > >> > >
> > >> > >> > > > Hi,
> > >> > >> > > >
> > >> > >> > > > I'm updating all website in pre. I changed download and
> > source
> > >> > code
> > >> > >> > > pages.
> > >> > >> > > > I'm going to do the blog post, for this I need the
> > Annoucment,
> > >> > but I
> > >> > >> > > can't
> > >> > >> > > > see it in my mail client.
> > >> > >> > > > @Piotr Zarzycki  can you send
> me
> > >> that
> > >> > >> email
> > >> > >> > > > off list? I'm going to start from the 0.9.4 one in the
> > >> meanwhile
> > >> > >> > > >
> > >> > >> > > > thanks
> > >> > >> > > >
> > >> > >> > > > Carlos
> > >> > >> > > >
> > >> > >> > > >
> > >> > >> > > >
> > >> > >> > > >
> > >> > >> > > > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
> > >> > >> > > > piotrzarzyck...@gmail.com>) escribió:
> > >> > >> > > >
> > >> > >> > > >> Carlos,
> > >> > >> > > >>
> > >> > >> > > >> Let me know if you have problems with updating links on
> > >> website.
> > >> > If
> > >> > >> > yes
> > >> > >> > > I
> > >> > >> > > >> will try to figure out how to do that.
> > >> > >> > > >>
> > >> > >> > > >> Thanks,
> > >> > >> > > >> Piotr

Re: Component Sets

2019-10-08 Thread Andrew Wetmore
There is not such a document yet, no. Help creating one would be welcome.

On Tue, Oct 8, 2019 at 4:22 AM Chris Velevitch 
wrote:

> There doesn't seem to be an all-encompassing document describing, MX,
> Spark and Jewel components and as well as the pros and cons of each
> nor is there a discussion on using third party web components,
> creating custom web components and how to the material design
> components.
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Release 0.9.6 Announce for web post?

2019-10-07 Thread Andrew Wetmore
I looked over the draft announcement, Piotr, and it seems fine as to the
English. I cannot speak to the technical details as well as other
committers can.

Andrew

On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki 
wrote:

> Currently I'm waiting for review of Draft of announcement. Till maximum
> Wednesday. Than I will send announce to dev, users and announce mailing
> list.
>
> I think you should create draft and post it once announce will be sent.
>
> Apart of that I should add our release somewhere in the whimsy but I don't
> remember where - I need to find that.
>
> Piotr
>
> On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore  wrote:
>
> > That would be good
> >
> > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, 
> > wrote:
> >
> > > Hi,
> > > I'll be updating website in next few hours, but I was thinking we don't
> > > have the habitual blog post for 0.9.6 release.
> > > Should I create one from scratch based on 0.9.4?
> > >
> > > thanks
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Release 0.9.6 Announce for web post?

2019-10-07 Thread Andrew Wetmore
That would be good

On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira,  wrote:

> Hi,
> I'll be updating website in next few hours, but I was thinking we don't
> have the habitual blog post for 0.9.6 release.
> Should I create one from scratch based on 0.9.4?
>
> thanks
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: Welcome Andrew Wetmore to Apache Royale's PMC

2019-10-04 Thread Andrew Wetmore
Thank you, friends! I will do my best to be a useful contributor.

On Fri, Oct 4, 2019 at 8:02 AM Piotr Zarzycki 
wrote:

>   Hi Andrew! Good luck! :)
>
> pt., 4 paź 2019 o 11:16 Harbs  napisał(a):
>
>> Welcome! I'm thrilled with all you’ve done for Royale! :-)
>>
>> Harbs
>>
>> > On Oct 3, 2019, at 8:55 PM, OmPrakash Muppirala 
>> wrote:
>> >
>> > It is with great pleasure that I announce that the Apache Royale PMC
>> members have voted in Andrew Wetmore to the PMC.  Please join us in
>> welcoming him.  This is a recognition of Andrew's great work in helping out
>> with Apache Royale's documentation among other things.
>> >
>> > Regards,
>> > Om
>> > (On behalf of Apache Royale PMC)
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Testimonials Page (Was: Re: About Royale Docs Improvements over latest months)

2019-10-03 Thread Andrew Wetmore
"Apache Royale captures the best of Apache Flex and the best of new trends
in web development, so it's the best of both worlds. We migrated a Flex
application to JavaScript in significantly less time than it would have
taken using the most popular JavaScript frameworks. The productivity,
programming model and combination of OOP and declarative languages make
Apache Royale a very solid development environment and a lot of fun to work
with! :)"

On Thu, Oct 3, 2019 at 3:30 PM Carlos Rovira 
wrote:

> Hi,
>
> Here's main that could serve as well as example (@Andrew if you can fix any
> grammar disaster I could make, please go ahead! :D) :
>
> -
>
> "Apache Royale captures the best of Apache Flex and the best of new trends
> in web development, so it's best of both worlds. We migrated a Flex
> application to javascript in significant less time than using the current
> top notch javascript frameworks out there. The productivity, the programing
> model and the combination of OOP and declarative languages makes it a very
> solid tech and very fun to work with! :)"
>
> Carlos Rovira
> Executive Chairman at Codeoscopic
>
> profile img to use: EB6igxEXYAE-PvU
> <https://pbs.twimg.com/media/EB6igxEXYAE-PvU?format=jpg=large>
>
> --
>
> I think is a small contribution that could be of help in our site. Harbs,
> Yishay, Piotr, and the rest...please take this request into consideration
> so we can fill the page with at least 4+ of this.
>
> thanks
>
> El mar., 1 oct. 2019 a las 20:54, Carlos Rovira ( >)
> escribió:
>
> > Hi all,
> >
> > we are talking about add a new "Testimonials" page were people could
> share
> > "How ApacheRoyale has helped" (you, your project, your company...) with a
> > new app, or a migration from Flex.
> >
> > Please submit to this thread a phrase or a paragraph that will capture
> > that topic for you and help us to fill that page with useful information
> > for others that come to Apache Royale.
> > (Note: Take into account that anyone that do this contribution is under
> > the assumption that allows us to use his phrase, name and info submitted
> in
> > out website as a Testimonial in that page and submitting implies give us
> > permission to do that :))
> >
> > Please provide an image as well for the profile. It can be your portrait,
> > or if you don't want your photo in our website, you can send us other
> > image(photo, logo or graphic) that represents you, to enhance the
> > testimonial. We reserve the option to use it or not depending on the
> image
> > provided if we think is not appropriate or could infringe some copyright
> or
> > rule. For this reason, please try to use original content and nothing
> that
> > could be offensive or problematic with any of the Apache rules or the
> > common sense :)
> >
> > This will help others to decide to join us or use Royale since others had
> > success in using it.
> >
> > Thanks all for your contribution to this page!! That will be of great
> > help! :)
> >
> > Carlos
> >
> >
> >
> > El mar., 1 oct. 2019 a las 20:39, Carlos Rovira (<
> carlosrov...@apache.org>)
> > escribió:
> >
> >> Hi,
> >> we can add testimonials page (as an additional page a part from showcase
> >> page). The actual theme has that integrated that will be easy to do.
> >> Will start a thread so others can write its own testimonial to be added.
> >>
> >> Thanks for the suggestion :)
> >>
> >>
> >>
> >> El mar., 1 oct. 2019 a las 19:37, Alex Harui ( >)
> >> escribió:
> >>
> >>> The showcase would be great, but if it is easier/faster to simply have
> a
> >>> page of links to blogs of our committers like you and Harbs that just
> >>> contain a paragraph or two about how Royale has helped, that might be a
> >>> good place to start.
> >>>
> >>> -Alex
> >>>
> >>> On 10/1/19, 10:02 AM, "Carlos Rovira" 
> wrote:
> >>>
> >>> Hi Alex,
> >>>
> >>> El mar., 1 oct. 2019 a las 17:50, Alex Harui
> >>> ()
> >>> escribió:
> >>>
> >>> > Thanks for working on the docs.
> >>> >
> >>> > Beyond the docs, what I would most like to see is "success
> >>> stories".  I
> >>> > keep thinking it would help if it was easier for folks to read
> >>> about how
> >>> > R

Re: About Royale Docs Improvements over latest months

2019-10-01 Thread Andrew Wetmore
I have not forgotten "Royale in a Week", the reworking of "Flex in a Week"
which I undertook to do. Will be working on that.

On Tue, Oct 1, 2019 at 2:37 PM Alex Harui  wrote:

> The showcase would be great, but if it is easier/faster to simply have a
> page of links to blogs of our committers like you and Harbs that just
> contain a paragraph or two about how Royale has helped, that might be a
> good place to start.
>
> -Alex
>
> On 10/1/19, 10:02 AM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> El mar., 1 oct. 2019 a las 17:50, Alex Harui ( >)
> escribió:
>
> > Thanks for working on the docs.
> >
> > Beyond the docs, what I would most like to see is "success
> stories".  I
> > keep thinking it would help if it was easier for folks to read about
> how
> > Royale has helped.
> >
>
> You refer to "showcase" page?
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2Fdata=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3Dreserved=0
> I still has that on my plate. I have to plan the info to showcase and
> post
> so people can submit about it
> But yes is one of the important pieces to work on. I'll try to get
> over it
> soon.
>
> thanks
>
>
> > My 2 cents,
> > -Alex
> >
> > On 10/1/19, 3:54 AM, "Andrew Wetmore"  wrote:
> >
> > This is great progress!
> >
> > I think one other area where we are still very thin is on using
> > RoyaleUnit
> > for testing.
> >
> > On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > about latest changes in docs done is latest months. This is a
> > summary of
> > > the work done (still in progress at some points):
> > >
> > > About layout, search and usability:
> > >
> > > * Now we have a more polished layout that should work right on
> > desktop,
> > > tablet and mobile, making more easy for new users coming to
> Royale
> > learn
> > > about it
> > > * The sidebar menu will show on the right as normal in tablet
> and
> > desktop.
> > > In mobile shows a button on the right side that make the menu
> slide
> > from
> > > the right
> > > * Now we have search functionality implemented thanks to
> Algolia
> > search.
> > > The index is crawled every 24h. Take into account if you make
> some
> > change
> > > and don't see it when searching as you upload the change.
> > > * Main menu now turns to dropdown if there's no enough room to
> show
> > it
> > > horizontally
> > >
> > > About content:
> > >
> > > * Added global styles for better readability and support of
> most of
> > the
> > > markdown options and highlighting of code (specially for AS3
> and
> > MXML)
> > > * Now all pages has "description" and "permalink" in the head
> > section to
> > > improve sharing and searching on internet. Remember to add this
> > lines so we
> > > make all navigation consistent with the rest of pages. If
> someone
> > notice a
> > > page without this, please add it or report it.
> > > * Added metadata for sharing in social networks more easily
> > capturing the
> > > previous point plus screenshot and name.
> > > * I tried to bring pages to the index that was still missing
> so we
> > have
> > > most of the overall structure in place. I'm pretty sure
> there's still
> > > missing concepts and things to bring to the docs, so keep your
> eyes
> > open to
> > > see what could still be missing and report it or add yourself.
> > > * Notice that some of that content is still a page mostly
> empty and
> > waiting
> > > to be filled. You're all invited to do so, just let others know
> > about it to
> > > avoid duplicate

Re: About Royale Docs Improvements over latest months

2019-10-01 Thread Andrew Wetmore
This is great progress!

I think one other area where we are still very thin is on using RoyaleUnit
for testing.

On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira 
wrote:

> Hi,
>
> about latest changes in docs done is latest months. This is a summary of
> the work done (still in progress at some points):
>
> About layout, search and usability:
>
> * Now we have a more polished layout that should work right on desktop,
> tablet and mobile, making more easy for new users coming to Royale learn
> about it
> * The sidebar menu will show on the right as normal in tablet and desktop.
> In mobile shows a button on the right side that make the menu slide from
> the right
> * Now we have search functionality implemented thanks to Algolia search.
> The index is crawled every 24h. Take into account if you make some change
> and don't see it when searching as you upload the change.
> * Main menu now turns to dropdown if there's no enough room to show it
> horizontally
>
> About content:
>
> * Added global styles for better readability and support of most of the
> markdown options and highlighting of code (specially for AS3 and MXML)
> * Now all pages has "description" and "permalink" in the head section to
> improve sharing and searching on internet. Remember to add this lines so we
> make all navigation consistent with the rest of pages. If someone notice a
> page without this, please add it or report it.
> * Added metadata for sharing in social networks more easily capturing the
> previous point plus screenshot and name.
> * I tried to bring pages to the index that was still missing so we have
> most of the overall structure in place. I'm pretty sure there's still
> missing concepts and things to bring to the docs, so keep your eyes open to
> see what could still be missing and report it or add yourself.
> * Notice that some of that content is still a page mostly empty and waiting
> to be filled. You're all invited to do so, just let others know about it to
> avoid duplicate efforts.
> * For Component Sets, I started to create a page per component where we add
> the most needed info to start with the component. It then refers to ASDocs
> for a full spec and access to all classes. I'm working on Jewel. Others are
> invited to use Jewel finished pages and use it as template for Basic,
> MXRoyale and other sets, and/or create new ones for components that are not
> similar and there's no counterpart on Jewel.
> * I added live content on Jewel components, since visual running examples
> are very powerful.
> * I added live example on the GitHub tutorial app.
> * I added many cross link references between Royale-docs, blog examples and
> ASDocs pages. Content must be in only one place but that content should be
> linked with the rest of royale contents in our network.
> * I tried to format all the pages I could to get most of the new visuals
> created, but I'm sure threr's still content to format, we can do this
> between all here, and anyone coming to Royale and browse content is invited
> to help in this point as well to submit more content to be reviewed and
> added.
> * I refactored all license pages to make all consistent with one style.
>
> To Help:
>
> I think there's many content already done and formatted in the right way to
> make others be able to add content that aligns to the rest of the doc
> pages. Andrew and I are here to help to give the finished results that
> conform to actual specs.
>
> There's still many things to do to get a full docs site. This is the list
> of things I see:
>
> * Fill Features and concepts pages still empty (View States, Data Binding,
> RPC methods pages, ). I think this can be the most important ones since
> are core concepts in Royale.
> * Complete Jewel and other sets reference pages. Very important for people
> coming. Here I plan to add for Jewel "style specs" too as someone mentioned
> some days ago, and I think this will be a very good idea.
> * Add Crux documentation, that should come in part from swiz framework docs
>
> What more things you still think are missing?
>
> Thanks
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

2019-09-23 Thread Andrew Wetmore
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

2019-09-23 Thread Andrew Wetmore
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 specif

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

2019-09-23 Thread Andrew Wetmore
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
> > > >
> > >

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

2019-09-22 Thread Andrew Wetmore
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.
> > > >
> > > >

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

2019-09-21 Thread Andrew Wetmore
 > > +
> > >
> >
> ${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
> > > +
> > >
> >
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/utils/CSSBorderUtils.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/utils/PNGEncoder.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/utils/SolidBorderUtil.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/utils/dbg/DOMPathUtil.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/AdvancedLayoutFeatures.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/CompoundTransform.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/IAssetLayoutFeatures.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/MatrixUtil.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/PathHelper.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/TransformOffsets.as
>     > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/shaderClasses/ColorShader.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/shaderClasses/ColorBurnShader.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/shaderClasses/ColorDodgeShader.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/shaderClasses/ExclusionShader.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/shaderClasses/HueShader.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/shaderClasses/LuminosityShader.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/shaderClasses/LuminosityMaskShader.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/shaderClasses/SaturationShader.as
> > > +
> > >
> >
> ${frameworks_dir}/projects/Graphics/src/main/royale/org/apache/royale/graphics/utils/shaderClasses/SoftLightShader.as
> > >
> > >
> >
> ${frameworks_dir}/projects/Jewel/src/main/royale/org/apache/royale/jewel/supportClasses/scrollbar/VScrollBar.as
> > >
> > >
> >
> ${frameworks_dir}/projects/Jewel/src/main/royale/org/apache/royale/jewel/supportClasses/scrollbar/HScrollBar.as
> > >
> > >
> >
> ${frameworks_dir}/projects/Jewel/src/main/royale/org/apache/royale/jewel/supportClasses/scrollbar/ScrollBar.as
> > >
> > >
> >
> >
> >
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: [royale-asjs] branch release/0.9.6 updated: Update RELEASE_NOTES.md

2019-09-16 Thread Andrew Wetmore
The hurricane and is aftermath slowed me down. Anyhow all my edits were
minor.

On Mon, Sep 16, 2019, 7:01 AM Piotr Zarzycki, 
wrote:

> Hi Andrew,
>
> I'm sorry but I already started preparing artifacts, so this probably won't
> go to 0.9.6.
>
> Thanks,
> Piotr
>
> pon., 16 wrz 2019 o 11:55  napisał(a):
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > andreww 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 4136e54  Update RELEASE_NOTES.md
> > 4136e54 is described below
> >
> > commit 4136e543b3dba11bfadb08d9ce357cbb36d7b9a4
> > Author: Andrew Wetmore 
> > AuthorDate: Mon Sep 16 06:55:05 2019 -0300
> >
> > Update RELEASE_NOTES.md
> >
> > Many small text edits.
> > ---
> >  RELEASE_NOTES.md | 62
> > 
> >  1 file changed, 31 insertions(+), 31 deletions(-)
> >
> > diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
> > index a4a4bb0..9e8ec3c 100644
> > --- a/RELEASE_NOTES.md
> > +++ b/RELEASE_NOTES.md
> > @@ -1,38 +1,38 @@
> >  Apache Royale 0.9.6
> >  ===
> >
> > -- Compiles faster
> > -- For applications targeting JavaScript, you can now incorporate the
> vast
> > resources available in existing, free, JavaScript libraries.
> > -- Many additional components available:
> > -  - for Jewel: Wizard, PopUp, TabBar, Module, ModuleLoader, FooterBar,
> > Badge, ScrollableSectionContent, HorizontalListScroll
> > -- Emulations of many other components available
> > -- Many improvements and fixes in Jewel UI Set:
> > -  - DateField/DateChooser full implememtation.
> > -  - Fixes to make components work right on IE11 and Android/iOS mobile
> > devices.
> > -  - Many improvements to all themes included (styles for new components,
> > added more styles like disabled missing in some components,...)
> > -  - Many beads included for Jewel set:
> > -- Added search filter bead on Jewel ComboBox
> > -- Added SearchFilterForList bead to use with Jewel List and
> TextInput.
> > +- Compiles faster.
> > +- For applications targeting JavaScript, you can now incorporate the
> vast
> > resources available in existing, free JavaScript libraries.
> > +- Many additional components are available:
> > +  - for the Jewel component set, Wizard, PopUp, TabBar, Module,
> > ModuleLoader, FooterBar, Badge, ScrollableSectionContent, and
> > HorizontalListScroll are now available.
> > +- Emulations of many other components are available.
> > +- Many improvements and fixes in the Jewel component set:
> > +  - Full implementation of DateField/DateChooser.
> > +  - Components now work correctly on IE11 and on Android/iOS mobile
> > devices.
> > +  - Many improvements to all themes, such as styles for new components
> > and a disabled style that was missing in some components.
> > +  - Many beads have been added for Jewel components:
> > +- Search filter bead on Jewel ComboBox
> > +- SearchFilterForList bead to use with Jewel List and TextInput
> >  - RequiredSelection for DropDownList
> > -  - Improvements on focus handling
> > -  - Button now extends from new BasicButton
> > -- Many improvements on Tour De Jewel demo app to show all new components
> > and beads developed in this version.
> > -- Added BrowserOrientation bead
> > -- Added loadCSS, to load external CSS dinamically.
> > -- Added generation of source-maps to all Royale libs for better
> debugging
> > framework code.
> > +  - Improvements to focus handling.
> > +  - Button now extends from new BasicButton.
> > +- Many improvements on Tour De Jewel demo app to show components and
> > beads introduced in this version.
> > +- Added BrowserOrientation bead.
> > +- Added loadCSS, to load external CSS dynamically.
> > +- Added generation of source-maps to all Royale libs for better
> debugging
> > of framework code.
> >  - Added new [RoyaleUnit](
> > https://apache.github.io/royale-docs/testing/royaleunit.html) library
> for
> > unit testing.
> > -- Improvements to AMF / RemoteObject Support
> > +- Improvements to AMF / RemoteObject Support.
> >  - AMFBinaryData api now matches flash.utils.ByteArray, (the missing
> > feature is non-UTF String encoding support). It therefore now works for
> > deep cloning via readObject/writeO

Release notes files

2019-09-15 Thread Andrew Wetmore
Should not the release notes files have the same headers that the code and
documentation files have?

a

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Discuss of release steps preparation

2019-09-14 Thread Andrew Wetmore
 > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml
> > > > > > (line: 129)
> > > > > >
> > > > > >
> > > > > >   
> > > > > >
> > > > > >
> > > > > >
> > > > > > 0.68472554 seconds
> > > > > >
> > > > > > macbookpro:~ carlosrovira$
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hope results are the expected ones :)
> > > > > >
> > > > > >
> > > > > > Best
> > > > > >
> > > > > >
> > > > > > Carlos
> > > > > >
> > > > > > El jue., 12 sept. 2019 a las 18:46, Alex Harui
> > > > > > ()
> > > > > > escribió:
> > > > > >
> > > > > > > Thanks for catching the places where FlexJS was still
> > being
> > > > > used.
> > > > > > >
> > > > > > > Your output indicates that there is a ROYALE_HOME
> > > environment
> > > > > > variable so
> > > > > > > it appears to be using your dev versions since I don't
> > > think
> > > > > NPM
> > > > > > would
> > > > > > > store its stuff in /Users/carlosrovira/Dev.  Anyway,
> good
> > > to
> > > > > > know that the
> > > > > > > environment variable can re-direct what the npm scripts
> > do.
> > > > If
> > > > > > you want to
> > > > > > > try without an environment variable that would be a
> > better
> > > > test
> > > > > > of what new
> > > > > > > users would experience and the output should reference
> > the
> > > > npm
> > > > > > node_modules
> > > > > > > folder.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > -Alex
> > > > > > >
> > > > > > > On 9/12/19, 1:53 AM, "Carlos Rovira" <
> > > > carlosrov...@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > think al went fine :)
> > > > > > >
> > > > > > > this is my output:
> > > > > > >
> > > > > > >
> > > > > > > + @apache-royale/royale-js-swf@0.9.6-beta9
> > > > > > >
> > > > > > > added 146 packages from 108 contributors in
> 426.831s
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > then I tried "mxmlc" just from command line:
> > > > > > >
> > > > > > >
> > > > > > > macbookpro:~ carlosrovira$ mxmlc
> > > > > > >
> > > > > > > Using Royale Compiler codebase:
> > > > > > >
>  /Users/carlosrovira/Dev/Royale/Source/royale-compiler
> > > > > > >
> > > > > > > Using Royale SDK:
> > > > > > /Users/carlosrovira/Dev/Royale/Source/royale-asjs
> > > > > > >
> > > > > > > MXMLJSC
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> +royalelib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> -sdk-js-lib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/js/Royale/generated-sources
> > > > > > >
> > > > > > > Loading configuration:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/royale-config.xml
> > > > > > >
> > > > > > >
> > > > > > > Error: a target file must be specified.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Error: a target file must be specified.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 0.888219402 seconds
> > > > > > >
> > > > > > > macbookpro:~ carlosrovira$
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Carlos Rovira
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C1c4ad6d04e534ee4bbc908d737aa8c2c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637039078002016836sdata=aa8EapVqmDC2iu7nmWBh20akTley4HB5QhCUK5U%2B1IE%3Dreserved=0
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C1c4ad6d04e534ee4bbc908d737aa8c2c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637039078002026826sdata=LpDM5%2BmgtTtSoRgRYPSk7kgh8KrcBQTrn6ZZte7YQYU%3Dreserved=0
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Editing files delayed

2019-09-10 Thread Andrew Wetmore
Thanks for your good wishes, Alex. We are at a friend's house, charging up
our devices. We will not have power or internet at our home until maybe
Saturday, although I may go out in search of internet access I can use from
time to time.

On Mon, Sep 9, 2019 at 11:46 PM Alex Harui  wrote:

> Andrew,
>
> I hope you and others are safe and the area recovers soon.
>
> I pushed your list of changes except the one about Modules since modules
> were in 0.9.4.
>
> You might be able to see the changes on commits@ or at these links:
>
> https://github.com/apache/royale-asjs/blob/release/0.9.6/RELEASE_NOTES.md
>
> https://github.com/apache/royale-asjs/blob/release/0.9.6/releasemgr/RELEASE_NOTES
>
> Thanks,
> -Alex
>
> On 9/9/19, 2:49 PM, "Andrew Wetmore"  wrote:
>
> Power will not be restored here until Friday, so I am offline until
> then
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Editing files delayed

2019-09-09 Thread Andrew Wetmore
Power will not be restored here until Friday, so I am offline until then


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-08 Thread Andrew Wetmore
We have no power until maybe Tuesday due to hurricane Dorian passing by.
Can review the files then.

On Sun, Sep 8, 2019, 4:47 AM Alex Harui,  wrote:

> I ran the ApproveRoyale script.  It is a good idea for the RM to run it
> before sending out the vote emails.  The script found:
>
> Generated output is in the binary package in these folders and shouldn't
> be, IMO.  Some clean step is missing somewhere.
> BasicJS/src/test
> CoreJS/src/test
> NetworkJS/src/test
> ReflectionJS/src/test
> RoyaleUnitJS/src/test
> XMLJS/src/test
>
> This file was found by rat.  I don't think it should be in the packages or
> our repo.
> .factorypath
>
> I pushed to the release branch some changes to the README URLs for
> playerglobal
> The README still says to use sudo on Mac for NPM.  I didn't have time to
> confirm.  Om, if you really think it shouldn't be in there go remove it.
>
> I also pushed changes to the NOTICE file copyright years
>
> The build failed because at least this one folder is missing from the
> package.  The packaging scripts may need to be changed to pick up new
> folders.
> royale-compiler/royaleunit-ant-tasks
>
> And then there is the RELEASE_NOTES files.  Andrew can you edit both the
> top-level RELEASE_NOTES.md and releasemgr/RELEASE_NOTES in royale-asjs?
>
> There might be more if I get past the royaleunit-ant-tasks failure, but
> I'm out of time for another 15 hours or so.
>
> HTH,
> -Alex
>
> On 9/6/19, 9:54 AM, "Andrew Wetmore"  wrote:
>
> I have only looked at the top-level release notes and readme files.
> Should
> I wait a day or so before digging down to look at the similar files in
> folders?
>
> On Fri, Sep 6, 2019 at 1:45 PM Josh Tynjala  >
> wrote:
>
> > I just updated the royale-compiler and royale-asjs release notes
> with the
> > things that I worked on. They're in the develop branch for now.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Ccd5c799cbcb94f13f2d508d732eae327%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637033856755836697sdata=vm%2BN2O4dit0i7WNu0Wf29K%2BjqMPRoP4pcNkfdph6GWc%3Dreserved=0
> >
> >
> >
> > On Fri, Sep 6, 2019 at 9:37 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > I was thinking about that in a very brave way at the beginning ! I
> was
> > > going to go trough commits from our last 0.9.4 release and prepare
> nice
> > > list for CHANGELOG, but since everything took double time then I
> assume.
> > -
> > > It's not going to happen from my sight.
> > >
> > > On Fri, Sep 6, 2019, 5:13 PM Andrew Wetmore 
> wrote:
> > >
> > > > The release notes file doesn't seem to have a section about
> what's in
> > > > 0.9.6, the current release.
> > > >
> > > > a
> > > >
> > > > On Fri, Sep 6, 2019 at 11:29 AM Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Carlos,
> > > > >
> > > > > IT depends on what commit MX is failing. I did branch for this
> RC
> > > couple
> > > > of
> > > > > days ago. In that time I was seeing some commits to develop
> related
> > to
> > > > MX.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > On Fri, Sep 6, 2019, 4:02 PM Carlos Rovira <
> carlosrov...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > thanks. One question I have is: I think MX Test was failing,
> does
> > it
> > > > > > affects the release or are not crucial to get the bits out?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (<
> > > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > > >
> > > > > > > Hi Guys,
> > > > > > >
> > > > > > > I have upload manually ant artifacts. Please start
> reviewing
> > stuff.
> > > > > Wha

Re: Discuss of release steps preparation

2019-09-07 Thread Andrew Wetmore
I think the release notes should definitely cover 0.9.6, at least at a high
level. Maybe points like this, if they are true:

   - Compiles faster
   - Many additional components available
   - Emulations of many other components available
   - For applications targeting JavaScript, you can now incorporate the
   vast resources available in existing, free, JavaScript libraries
   - Addition of familiar Flex features like modules
   - Dozens of bugs reported, investigated, and squashed. For details of
   closed bug reports see [link to GitHub bug list]

That would explain to most people why we are so happy to release 0.9.6 and,
in general, what they should be looking for.


On Sat, Sep 7, 2019 at 4:28 AM Piotr Zarzycki 
wrote:

> Hi Alex,
>
> That is only partially true what you are saying. Cause I'm definitely not
> the person, developer who when reaching some wall do not try to resolve it
> on it's own - Not that is not me.
>
> However in case of Royale release it's partially true, but let me explain
> why I asked first rather fix and ask:
>
> Building Royale framework on Windows is extremely long - and this is not
> limitation of my PC - I'm not the only one who experiencing such issue. You
> can definitely imagine that adding one line of echo and rebuild framework
> using releasesteps.xml can be challenge. - waiting 50 minutes. - Yeah I can
> do other stuff during that time, but it is not always possible.
>
> When I switched to Mac - all those problems simply gone. No hang on some
> files, building is two times faster, uploading working. - No problem at
> all.
>
> I simply wanted to count on people who are here, without hesitation ask for
> help even if I'm in a user mode - I'm doing that very rare.
>
> To all of you who are seeing now VOTE thread - please take some time and
> start voting, cause we finally have what we are trying to achieve for so
> many months.
>
> Thanks,
> Piotr
>
> sob., 7 wrz 2019 o 01:14 Alex Harui  napisał(a):
>
> > Those of you in favor of debugging the automation later must volunteer to
> > be the next RMs and do the debugging.
> >
> > Piotr, I'm sorry this effort took longer than expected, but IMO, that's
> > because I apparently could not convince you to take a developer instead
> of
> > user mindset.  By guessing at solutions and not providing console output
> > for others to help with or adding diagnostic output to the scripts,
> several
> > of your attempts failed which took a lot of your time.  I'm pretty sure I
> > said earlier that the release process is not a product developed and
> > maintained by me.  We need other people to be able to maintain and debug
> > Maven and Ant scripts.
> >
> > Similarly, I have not, nor has anyone else, tried a bunch of different
> > runtime configurations.  I don't know what would happen if you use a
> > different console window for each step.  I don't think the previous step
> > leaves environment variables for the next step, but I can't be sure of
> > that.  But the steps do set up files and folders to be used by the next
> > steps.  So if a working copy is not found at the folder specified, the
> > earlier step that tried to establish that working copy needs to be
> examined.
> >
> > Should this release get the votes to go out, the releasecandidate.xml
> > scripts have steps that merge branches and bump version numbers for Ant
> > (Maven should already be bumped).  Personally, I think we need to have
> some
> > sort of updated RELEASE_NOTES file.
> >
> > When I get done with migrating WebService, and fixing any issues with
> > virtual scrolling in ADG I will attempt to run the steps on Windows that
> > failed for Piotr.  But all of you who want to see more releases more
> often
> > need to try to find time to pitch in to improve the process.
> >
> > My 2 cents,
> > -Alex
> >
> > On 9/6/19, 3:59 AM, "Carlos Rovira"  wrote:
> >
> > Hi,
> >
> > maybe is not so bad to end this 0.9.6 manually, since there was many
> > progress in that front. Does not need necessarily be "all or
> nothing".
> > Or
> > 100% success.
> > Releasing now 0.9.6 can make lower the stress a bit and make a the
> > 0.9.7 in
> > few more weeks catch the final problems. As soon as we have this
> > working
> > and documentation more polished we can go to 1.0. We can even go from
> > 0.9.7
> > to 1.0 without necessarily do releases for 0.9.8 and 0.9.9
> >
> > just my 2ctns
> >
> >
> >
> > El vie., 6 sept. 2019 a las 11:00, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Alex,
> > >
> > > I would love to encourage more people to be RM, but unfortunately
> my
> > time
> > > which I should spend on that release was exceeded at least double.
> I
> > prefer
> > > make now manually commit than deal with it - I'm sorry about that.
> > >
> > > As for console output - you are saying that previous steps matters
> > to that
> > > one ? I sounds like I should do previous step in 

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Andrew Wetmore
I have only looked at the top-level release notes and readme files. Should
I wait a day or so before digging down to look at the similar files in
folders?

On Fri, Sep 6, 2019 at 1:45 PM Josh Tynjala 
wrote:

> I just updated the royale-compiler and royale-asjs release notes with the
> things that I worked on. They're in the develop branch for now.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Fri, Sep 6, 2019 at 9:37 AM Piotr Zarzycki 
> wrote:
>
> > I was thinking about that in a very brave way at the beginning ! I was
> > going to go trough commits from our last 0.9.4 release and prepare nice
> > list for CHANGELOG, but since everything took double time then I assume.
> -
> > It's not going to happen from my sight.
> >
> > On Fri, Sep 6, 2019, 5:13 PM Andrew Wetmore  wrote:
> >
> > > The release notes file doesn't seem to have a section about what's in
> > > 0.9.6, the current release.
> > >
> > > a
> > >
> > > On Fri, Sep 6, 2019 at 11:29 AM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > wrote:
> > >
> > > > Hi Carlos,
> > > >
> > > > IT depends on what commit MX is failing. I did branch for this RC
> > couple
> > > of
> > > > days ago. In that time I was seeing some commits to develop related
> to
> > > MX.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Fri, Sep 6, 2019, 4:02 PM Carlos Rovira 
> > > > wrote:
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > thanks. One question I have is: I think MX Test was failing, does
> it
> > > > > affects the release or are not crucial to get the bits out?
> > > > >
> > > > > Thanks
> > > > >
> > > > > El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > >
> > > > > > Hi Guys,
> > > > > >
> > > > > > I have upload manually ant artifacts. Please start reviewing
> stuff.
> > > > What
> > > > > if
> > > > > > vote passes - Should we merge 0.9.6 tag to develop ?
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > pt., 6 wrz 2019 o 13:09 Apache Royale CI Server <
> > > > > apacheroyal...@gmail.com>
> > > > > > napisał(a):
> > > > > >
> > > > > > > This is the discussion thread.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Piotr Zarzycki
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Piotr Zarzycki
> > > > > >
> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > http://cottage14.blogspot.com/
> > >
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Andrew Wetmore
The release notes file doesn't seem to have a section about what's in
0.9.6, the current release.

a

On Fri, Sep 6, 2019 at 11:29 AM Piotr Zarzycki 
wrote:

> Hi Carlos,
>
> IT depends on what commit MX is failing. I did branch for this RC couple of
> days ago. In that time I was seeing some commits to develop related to MX.
>
> Thanks,
> Piotr
>
> On Fri, Sep 6, 2019, 4:02 PM Carlos Rovira 
> wrote:
>
> > Hi Piotr,
> >
> > thanks. One question I have is: I think MX Test was failing, does it
> > affects the release or are not crucial to get the bits out?
> >
> > Thanks
> >
> > El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Guys,
> > >
> > > I have upload manually ant artifacts. Please start reviewing stuff.
> What
> > if
> > > vote passes - Should we merge 0.9.6 tag to develop ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pt., 6 wrz 2019 o 13:09 Apache Royale CI Server <
> > apacheroyal...@gmail.com>
> > > napisał(a):
> > >
> > > > This is the discussion thread.
> > > >
> > > > Thanks,
> > > > Piotr Zarzycki
> > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: New royal-doc pages to review: Jewel CheckBox and RadioButton

2019-08-30 Thread Andrew Wetmore
I have updated these pages.

On Thu, Aug 29, 2019 at 1:09 PM Andrew Wetmore  wrote:

> I will look at these pages in a couple of hours.
>
> On Thu, Aug 29, 2019 at 12:58 PM Carlos Rovira 
> wrote:
>
>> Hi Andrew,
>>
>> just committed new docs:
>>
>>
>> https://apache.github.io/royale-docs/component-sets/jewel/jewel-checkbox.html
>>
>> https://apache.github.io/royale-docs/component-sets/jewel/jewel-radiobutton.html
>>
>> hope you can review it and edit as you think is better when you can.
>>
>> For all:
>> I removed cache for GitHub pages since I need to remove cache manually in
>> my browser each time I upload new content.
>> I used: 
>>
>> seems it's working. If you know any other way to do this or a better one
>> please let me know
>>
>> thanks!
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: New royal-doc pages to review: Jewel CheckBox and RadioButton

2019-08-29 Thread Andrew Wetmore
I will look at these pages in a couple of hours.

On Thu, Aug 29, 2019 at 12:58 PM Carlos Rovira 
wrote:

> Hi Andrew,
>
> just committed new docs:
>
>
> https://apache.github.io/royale-docs/component-sets/jewel/jewel-checkbox.html
>
> https://apache.github.io/royale-docs/component-sets/jewel/jewel-radiobutton.html
>
> hope you can review it and edit as you think is better when you can.
>
> For all:
> I removed cache for GitHub pages since I need to remove cache manually in
> my browser each time I upload new content.
> I used: 
>
> seems it's working. If you know any other way to do this or a better one
> please let me know
>
> thanks!
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Sub-Menu in royale-docs: "Fundamental Concepts", "Core Concepts" or "Technology features"

2019-08-24 Thread Andrew Wetmore
re more to bring here...
> >> >
> >> > For me this is the main missing piece we need to address, and of
> course
> >> > completing not only that menu but many other pages still to fill.
> >> >
> >> > Just one thing to end: In each page after main title the template
> expect
> >> > the next line to be a short subtitle. For example, in the new
> "Externs"
> >> > page y added a new line after title "Use external javascript libraries
> >> in
> >> > ActiopnScript" So that line is shown in blue and with a bit more size
> to
> >> > match the web style. That line should help a user to quickly
> understand
> >> > what's that page about, since just "Externs" probably will not be of
> >> much
> >> > help for a beginner.
> >> >
> >> > many pages are still without subtitle, but as we go over all docs, we
> >> > should add this lines to help users reaching that pages.
> >> >
> >> > Thanks
> >> >
> >> > --
> >> > Carlos Rovira
> >> > http://about.me/carlosrovira
> >> >
> >>
> >>
> >> --
> >>
> >>
> >> Chris
> >> --
> >> Chris Velevitch
> >> m: 0415 469 095
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Add Royale to Wiki: Comparison of JavaScript frameworks

2019-08-07 Thread Andrew Wetmore
Thank you @Carlos Rovira 

On Wed, Aug 7, 2019 at 2:09 PM Carlos Rovira 
wrote:

> Hi Andrew,
>
> this is from [1]
>
> Browser Support for ES5 (2009)
> BrowserVersionFrom Date
> Chrome 23 Sep 2012
> Firefox 21 Apr 2013
> IE 9* Mar 2011
> IE / Edge 10 Sep 2012
> Safari 6 Jul 2012
> Opera 15 Jul 2013
>
>
> [1] https://www.w3schools.com/js/js_versions.asp
>
> El lun., 5 ago. 2019 a las 11:31, Andrew Wetmore ()
> escribió:
>
> > Yes, I feel a little bit like a guest at some other group's dinner party.
> >
> > Any thoughts on the minimum versions of the various browsers that we
> > support?
> >
> > On Mon, Aug 5, 2019 at 6:27 AM Carlos Rovira 
> > wrote:
> >
> > > Hi Andrew,
> > >
> > > El lun., 5 ago. 2019 a las 11:14, Andrew Wetmore ( >)
> > > escribió:
> > >
> > > >
> > > > Do we really have a GUI page layout? Is that not more like what Flex
> > > > Builder had?
> > > >
> > >
> > > Yeah, you're right. I was thinking about "layouts" feature, but is
> really
> > > what you say.
> > > The problem with this grids is that sometimes is hard to imagine what
> the
> > > author wants to refer.
> > >
> > > Thanks!
> > >
> > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Commercial Support Page (was: Fwd: AIR and Royale)

2019-08-07 Thread Andrew Wetmore
That looks very good, with the list of providers above the qualifications
for getting added to the list.

On Wed, Aug 7, 2019 at 2:18 PM Yishay Weiss  wrote:

> Good to hear Carlos, thanks.
>
>
>
> 
> From: Carlos Rovira 
> Sent: Wednesday, August 7, 2019 7:57:58 PM
> To: dev@royale.apache.org 
> Subject: Re: Royale Commercial Support Page (was: Fwd: AIR and Royale)
>
> Hi Piotr, Yshay,
>
> entry is now added and published :)
>
> https://royale.apache.org/royale-commercial-support/
>
>
>
> El mié., 7 ago. 2019 a las 8:07, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Hi Carlos,
> >
> > Yishay send you logo off the list. Is it ok ?
> >
> > Thanks,
> > Piotr
> >
> > pon., 5 sie 2019 o 11:32 Piotr Zarzycki 
> > napisał(a):
> >
> > > Yes! I'm ok!
> > >
> > > Thanks for asking.
> > >
> > > pon., 5 sie 2019 o 11:13 Yishay Weiss 
> > napisał(a):
> > >
> > >> Actually, please add a + before the phone number so it links to Skype.
> > >>
> > >>
> > >>
> > >> Piotr, are u ok with being added?
> > >>
> > >>
> > >>
> > >> 
> > >> From: Yishay Weiss 
> > >> Sent: Monday, August 5, 2019 12:09:40 PM
> > >> To: dev@royale.apache.org 
> > >> Subject: RE: Royale Commercial Support Page (was: Fwd: AIR and Royale)
> > >>
> > >> Looks good to me. Thanks.
> > >>
> > >>
> > >>
> > >> 
> > >> From: Carlos Rovira 
> > >> Sent: Monday, August 5, 2019 12:00:08 PM
> > >> To: dev@royale.apache.org 
> > >> Subject: Re: Royale Commercial Support Page (was: Fwd: AIR and Royale)
> > >>
> > >> Yeah! sorry :)
> > >>
> > >> https://royale.codeoscopic.com/royale-commercial-support/
> > >>
> > >> El lun., 5 ago. 2019 a las 10:49, Yishay Weiss (<
> yishayj...@hotmail.com
> > >)
> > >> escribió:
> > >>
> > >> >
> > >> > >ok, you can check here the addition before publish.
> > >> >
> > >> > Was there supposed to be a link?
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > El lun., 5 ago. 2019 a las 10:10, Yishay Weiss (<
> > yishayj...@hotmail.com
> > >> >)
> > >> > escribió:
> > >> >
> > >> > > I’ll try to find one. Thanks!
> > >> > >
> > >> > >
> > >> > >
> > >> > > 
> > >> > > From: Carlos Rovira 
> > >> > > Sent: Monday, August 5, 2019 10:59:51 AM
> > >> > > To: dev@royale.apache.org 
> > >> > > Subject: Re: Royale Commercial Support Page (was: Fwd: AIR and
> > Royale)
> > >> > >
> > >> > > Hi Yishay,
> > >> > >
> > >> > > I'm adding it. Could you provide a better logo?
> > >> > > (LOGO (if applies) (PNG, background transparent, good resolution
> (at
> > >> > least
> > >> > > above 800px))
> > >> > > thanks
> > >> > >
> > >> > > El lun., 5 ago. 2019 a las 9:23, Yishay Weiss (<
> > >> yishayj...@hotmail.com>)
> > >> > > escribió:
> > >> > >
> > >> > > > Apache Royale contributor(s): Piotr Zarzycki (committer and PMC
> > >> > member),
> > >> > > > Yishay Weiss (committer and PMC member).
> > >> > > >
> > >> > > > 
> > >> > > > From: Yishay Weiss
> > >> > > > Sent: Monday, August 5, 2019 10:17:52 AM
> > >> > > > To: dev@royale.apache.org 
> > >> > > > Subject: RE: Royale Commercial Support Page (was: Fwd: AIR and
> > >> Royale)
> > >> > > >
> > >> > > >
> > >> > > > Carlos, please add Prominic as well. Thanks.
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > Name: Prominic.NET
> > >> > > >
> > >> > > >
> > >> > > >
> >

Re: Add Royale to Wiki: Comparison of JavaScript frameworks

2019-08-05 Thread Andrew Wetmore
Yes, I feel a little bit like a guest at some other group's dinner party.

Any thoughts on the minimum versions of the various browsers that we
support?

On Mon, Aug 5, 2019 at 6:27 AM Carlos Rovira 
wrote:

> Hi Andrew,
>
> El lun., 5 ago. 2019 a las 11:14, Andrew Wetmore ()
> escribió:
>
> >
> > Do we really have a GUI page layout? Is that not more like what Flex
> > Builder had?
> >
>
> Yeah, you're right. I was thinking about "layouts" feature, but is really
> what you say.
> The problem with this grids is that sometimes is hard to imagine what the
> author wants to refer.
>
> Thanks!
>
>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
> >
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Add Royale to Wiki: Comparison of JavaScript frameworks

2019-08-05 Thread Andrew Wetmore
It is a start, at least.

Do we really have a GUI page layout? Is that not more like what Flex
Builder had?

On Mon, Aug 5, 2019 at 6:00 AM Carlos Rovira 
wrote:

> Many Thanks Andrew, I think is a good start.
> Looking at the tables, sometimes is difficult to see if we fit in a cell or
> another, but we can get over it as we released next version. For now I
> think is ok, and the initial objetive is to be listed :)
>
> Thanks!
>
> El sáb., 3 ago. 2019 a las 22:47, Andrew Wetmore ()
> escribió:
>
> > I have added columns and rows for Apache Royale  to this page [1], and
> have
> > made a stab at providing data in the cells. I am sure I have missed a
> bunch
> > of features we can say YES about, and do not have anything for the
> earliest
> > versions of each browser Royale works with, so any improvements anyone
> can
> > suggest are most welcome.
> >
> > a
> >
> > [1] https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
> >
> > On Fri, Aug 2, 2019 at 9:46 AM Andrew Wetmore 
> wrote:
> >
> > > This page [1] lists a bunch of features and functionality, and whether
> a
> > > given framework has/supports it. Can someone check my answers for
> Apache
> > > Royale?:
> > >
> > > Feature detection:
> > > DOM wrapped:
> > > Xml HTMLRequest data retrieval: YES
> > > Web socket
> > > Server push data retrieval
> > > Other data retrieval (xml, html, csv, atom)
> > > Drag and drop: YES
> > > Simple visual effects: YES
> > > Animation / advanced visual effects
> > > Back button support / history management
> > > Input form, widgets, validation: YES
> > > Grid: YES
> > > Hierarchical tree: YES
> > > Rich Text Editor: YES
> > > Autocompletion tools:
> > > HTML generation tools:
> > > Widgets / themeable, skinnable: YES
> > > GUI resizable panels and modal dialogs: YES???
> > > GUI page layout:
> > > Canvas support: YES
> > > Mobile/tablet support (touch support): YES
> > > Accessibility / Graceful degradation:
> > > ARIA compliant:
> > > Developer tools, visual design: [the current IDE support does not match
> > > this, does it?]
> > > Offline storage: YES
> > > Cross browser 2d vector graphics:
> > > Charting and dashboard: YES
> > > RTL support in UI components: YES
> > >
> > > [1] https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
> > >
> > > On Fri, Aug 2, 2019 at 9:15 AM Andrew Wetmore 
> > wrote:
> > >
> > >> This page lists framework compatibility with various browsers. What is
> > >> the earliest version of each of the following that the JS that Royale
> > >> (0.9.4) compiles can work with?
> > >>
> > >> IE
> > >> Firefox
> > >> Safari
> > >> Opera
> > >> Chrome
> > >>
> > >> On Fri, Aug 2, 2019 at 4:19 AM Carlos Rovira  >
> > >> wrote:
> > >>
> > >>> Yeah! Very important this kind of things for our future. Thanks for
> > >>> bringing this and to Andrew for filling it! :)
> > >>>
> > >>> El jue., 1 ago. 2019 a las 11:13, Andrew Wetmore (<
> cottag...@gmail.com
> > >)
> > >>> escribió:
> > >>>
> > >>> > That be me.
> > >>> >
> > >>> > I will take a look at it!
> > >>> >
> > >>> > On Thu, Aug 1, 2019 at 2:33 AM Piotr Zarzycki <
> > >>> piotrzarzyck...@gmail.com>
> > >>> > wrote:
> > >>> >
> > >>> > > Hi Guys,
> > >>> > >
> > >>> > > What do you think about adding Royale to this comparision [1] ? I
> > >>> > remember
> > >>> > > that someone from our Team was and Wiki editor, maybe could add
> > there
> > >>> > > Royale ?
> > >>> > >
> > >>> > > [1]
> > >>> https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
> > >>> > >
> > >>> > > Thanks,
> > >>> > > --
> > >>> > >
> > >>> > > Piotr Zarzycki
> > >>> > >
> > >>> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > >>> > > <https://www.patreon.com/piotrzarzycki>*
> > >>> > >
> > >>> >
> > >>> >
> > >>> > --
> > >>> > Andrew Wetmore
> > >>> >
> > >>> > http://cottage14.blogspot.com/
> > >>> >
> > >>>
> > >>>
> > >>> --
> > >>> Carlos Rovira
> > >>> http://about.me/carlosrovira
> > >>>
> > >>
> > >>
> > >> --
> > >> Andrew Wetmore
> > >>
> > >> http://cottage14.blogspot.com/
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > http://cottage14.blogspot.com/
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Add Royale to Wiki: Comparison of JavaScript frameworks

2019-08-03 Thread Andrew Wetmore
I have added columns and rows for Apache Royale  to this page [1], and have
made a stab at providing data in the cells. I am sure I have missed a bunch
of features we can say YES about, and do not have anything for the earliest
versions of each browser Royale works with, so any improvements anyone can
suggest are most welcome.

a

[1] https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks

On Fri, Aug 2, 2019 at 9:46 AM Andrew Wetmore  wrote:

> This page [1] lists a bunch of features and functionality, and whether a
> given framework has/supports it. Can someone check my answers for Apache
> Royale?:
>
> Feature detection:
> DOM wrapped:
> Xml HTMLRequest data retrieval: YES
> Web socket
> Server push data retrieval
> Other data retrieval (xml, html, csv, atom)
> Drag and drop: YES
> Simple visual effects: YES
> Animation / advanced visual effects
> Back button support / history management
> Input form, widgets, validation: YES
> Grid: YES
> Hierarchical tree: YES
> Rich Text Editor: YES
> Autocompletion tools:
> HTML generation tools:
> Widgets / themeable, skinnable: YES
> GUI resizable panels and modal dialogs: YES???
> GUI page layout:
> Canvas support: YES
> Mobile/tablet support (touch support): YES
> Accessibility / Graceful degradation:
> ARIA compliant:
> Developer tools, visual design: [the current IDE support does not match
> this, does it?]
> Offline storage: YES
> Cross browser 2d vector graphics:
> Charting and dashboard: YES
> RTL support in UI components: YES
>
> [1] https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
>
> On Fri, Aug 2, 2019 at 9:15 AM Andrew Wetmore  wrote:
>
>> This page lists framework compatibility with various browsers. What is
>> the earliest version of each of the following that the JS that Royale
>> (0.9.4) compiles can work with?
>>
>> IE
>> Firefox
>> Safari
>> Opera
>> Chrome
>>
>> On Fri, Aug 2, 2019 at 4:19 AM Carlos Rovira 
>> wrote:
>>
>>> Yeah! Very important this kind of things for our future. Thanks for
>>> bringing this and to Andrew for filling it! :)
>>>
>>> El jue., 1 ago. 2019 a las 11:13, Andrew Wetmore ()
>>> escribió:
>>>
>>> > That be me.
>>> >
>>> > I will take a look at it!
>>> >
>>> > On Thu, Aug 1, 2019 at 2:33 AM Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
>>> > wrote:
>>> >
>>> > > Hi Guys,
>>> > >
>>> > > What do you think about adding Royale to this comparision [1] ? I
>>> > remember
>>> > > that someone from our Team was and Wiki editor, maybe could add there
>>> > > Royale ?
>>> > >
>>> > > [1]
>>> https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
>>> > >
>>> > > Thanks,
>>> > > --
>>> > >
>>> > > Piotr Zarzycki
>>> > >
>>> > > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > > <https://www.patreon.com/piotrzarzycki>*
>>> > >
>>> >
>>> >
>>> > --
>>> > Andrew Wetmore
>>> >
>>> > http://cottage14.blogspot.com/
>>> >
>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>
>>
>> --
>> Andrew Wetmore
>>
>> http://cottage14.blogspot.com/
>>
>>
>>
>>
>>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Add Royale to Wiki: Comparison of JavaScript frameworks

2019-08-02 Thread Andrew Wetmore
This page [1] lists a bunch of features and functionality, and whether a
given framework has/supports it. Can someone check my answers for Apache
Royale?:

Feature detection:
DOM wrapped:
Xml HTMLRequest data retrieval: YES
Web socket
Server push data retrieval
Other data retrieval (xml, html, csv, atom)
Drag and drop: YES
Simple visual effects: YES
Animation / advanced visual effects
Back button support / history management
Input form, widgets, validation: YES
Grid: YES
Hierarchical tree: YES
Rich Text Editor: YES
Autocompletion tools:
HTML generation tools:
Widgets / themeable, skinnable: YES
GUI resizable panels and modal dialogs: YES???
GUI page layout:
Canvas support: YES
Mobile/tablet support (touch support): YES
Accessibility / Graceful degradation:
ARIA compliant:
Developer tools, visual design: [the current IDE support does not match
this, does it?]
Offline storage: YES
Cross browser 2d vector graphics:
Charting and dashboard: YES
RTL support in UI components: YES

[1] https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks

On Fri, Aug 2, 2019 at 9:15 AM Andrew Wetmore  wrote:

> This page lists framework compatibility with various browsers. What is the
> earliest version of each of the following that the JS that Royale (0.9.4)
> compiles can work with?
>
> IE
> Firefox
> Safari
> Opera
> Chrome
>
> On Fri, Aug 2, 2019 at 4:19 AM Carlos Rovira 
> wrote:
>
>> Yeah! Very important this kind of things for our future. Thanks for
>> bringing this and to Andrew for filling it! :)
>>
>> El jue., 1 ago. 2019 a las 11:13, Andrew Wetmore ()
>> escribió:
>>
>> > That be me.
>> >
>> > I will take a look at it!
>> >
>> > On Thu, Aug 1, 2019 at 2:33 AM Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> > wrote:
>> >
>> > > Hi Guys,
>> > >
>> > > What do you think about adding Royale to this comparision [1] ? I
>> > remember
>> > > that someone from our Team was and Wiki editor, maybe could add there
>> > > Royale ?
>> > >
>> > > [1]
>> https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
>> > >
>> > > Thanks,
>> > > --
>> > >
>> > > Piotr Zarzycki
>> > >
>> > > Patreon: *https://www.patreon.com/piotrzarzycki
>> > > <https://www.patreon.com/piotrzarzycki>*
>> > >
>> >
>> >
>> > --
>> > Andrew Wetmore
>> >
>> > http://cottage14.blogspot.com/
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Add Royale to Wiki: Comparison of JavaScript frameworks

2019-08-02 Thread Andrew Wetmore
This page lists framework compatibility with various browsers. What is the
earliest version of each of the following that the JS that Royale (0.9.4)
compiles can work with?

IE
Firefox
Safari
Opera
Chrome

On Fri, Aug 2, 2019 at 4:19 AM Carlos Rovira 
wrote:

> Yeah! Very important this kind of things for our future. Thanks for
> bringing this and to Andrew for filling it! :)
>
> El jue., 1 ago. 2019 a las 11:13, Andrew Wetmore ()
> escribió:
>
> > That be me.
> >
> > I will take a look at it!
> >
> > On Thu, Aug 1, 2019 at 2:33 AM Piotr Zarzycki  >
> > wrote:
> >
> > > Hi Guys,
> > >
> > > What do you think about adding Royale to this comparision [1] ? I
> > remember
> > > that someone from our Team was and Wiki editor, maybe could add there
> > > Royale ?
> > >
> > > [1]  https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
> > >
> > > Thanks,
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Add Royale to Wiki: Comparison of JavaScript frameworks

2019-08-01 Thread Andrew Wetmore
That be me.

I will take a look at it!

On Thu, Aug 1, 2019 at 2:33 AM Piotr Zarzycki 
wrote:

> Hi Guys,
>
> What do you think about adding Royale to this comparision [1] ? I remember
> that someone from our Team was and Wiki editor, maybe could add there
> Royale ?
>
> [1]  https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Apache Royale Website statistics

2019-07-26 Thread Andrew Wetmore
It will be interesting to monitor the number of page views when the
showcase of active Apache Royale applications becomes available. I think if
there is a big jump, it would be nice to showcase it and at the same time
draw attention to the new showcase.

On Thu, Jul 25, 2019 at 3:08 PM Carlos Rovira 
wrote:

> Hi,
>
> here's a screenshot of the website statistics
>
> https://imgur.com/spFb5af
>
> This is from WP admin area, don't know if we have some other Apache ones to
> compare
>
> What do you think about sharing some data in social networks?
> And what data do you think is most interesting and could impact more out
> there?
>
> thanks
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Commercial Support Page (was: Fwd: AIR and Royale)

2019-07-26 Thread Andrew Wetmore
I have made a bunch of small text changes. This is a useful tutorial!

On Thu, Jul 25, 2019 at 9:59 PM Andrew Wetmore  wrote:

> I will do a text review early tomorrow.
>
> On Thu, Jul 25, 2019 at 7:54 PM Carlos Rovira 
> wrote:
>
>> Hi!
>>
>> New commercial support page is ready and published. Andrew, I get some of
>> the texts from other apache webs, but anyway some review for your part
>> would be great! :)
>>
>> https://royale.apache.org/royale-commercial-support/
>>
>> Anyone that wants to be listed, please follow instructions!! :)
>>
>>
>>
>>
>> El vie., 7 jun. 2019 a las 15:51, Andrew Wetmore ()
>> escribió:
>>
>>> This is s great idea
>>>
>>> On Fri, Jun 7, 2019, 6:24 AM Carlos Rovira, 
>>> wrote:
>>>
>>> > Hi,
>>> >
>>> > I'll be creating a page on the website in the following days with a
>>> list of
>>> > third party providers that offers commercial support for Apache
>>> Royale, in
>>> > the lines we saw in the links shared by Dave Fisher as examples in
>>> other
>>> > Apache products.
>>> >
>>> > It could be companies or individuals.
>>> >
>>> > Anyone that wants to be listed, please share here the following data:
>>> >
>>> > * NAME
>>> > * SHORT DESCRIPTION (if applies)
>>> > * LOGO (if applies) (PNG, background transparent, good resolution (at
>>> least
>>> > above 800px)
>>> > * WEBSITE URL
>>> > * CONTACT PERSON (in case of individual can be same as NAME)
>>> > * EMAIL OF CONTACT
>>> > * PHONE OF CONTACT
>>> > * APACHE ROYALE CONTRIBUTOR (if the company or individual has people
>>> > contributing to this project, or if is an individual contributes to
>>> this
>>> > project)
>>> >
>>> > thanks
>>> >
>>> >
>>> > -- Forwarded message -----
>>> > De: Carlos Rovira 
>>> >
>>> > If you consider this ok, I can create a thread so companies that want
>>> to be
>>> > listed, can express they want to, and I can create a page in our site
>>> with
>>> > the logos and urls and maybe more (contact person?, ...)
>>> >
>>> > thanks
>>> >
>>> >
>>> >
>>> > --
>>> > Carlos Rovira
>>> > http://about.me/carlosrovira
>>> >
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Commercial Support Page (was: Fwd: AIR and Royale)

2019-07-25 Thread Andrew Wetmore
I will do a text review early tomorrow.

On Thu, Jul 25, 2019 at 7:54 PM Carlos Rovira 
wrote:

> Hi!
>
> New commercial support page is ready and published. Andrew, I get some of
> the texts from other apache webs, but anyway some review for your part
> would be great! :)
>
> https://royale.apache.org/royale-commercial-support/
>
> Anyone that wants to be listed, please follow instructions!! :)
>
>
>
>
> El vie., 7 jun. 2019 a las 15:51, Andrew Wetmore ()
> escribió:
>
>> This is s great idea
>>
>> On Fri, Jun 7, 2019, 6:24 AM Carlos Rovira, 
>> wrote:
>>
>> > Hi,
>> >
>> > I'll be creating a page on the website in the following days with a
>> list of
>> > third party providers that offers commercial support for Apache Royale,
>> in
>> > the lines we saw in the links shared by Dave Fisher as examples in other
>> > Apache products.
>> >
>> > It could be companies or individuals.
>> >
>> > Anyone that wants to be listed, please share here the following data:
>> >
>> > * NAME
>> > * SHORT DESCRIPTION (if applies)
>> > * LOGO (if applies) (PNG, background transparent, good resolution (at
>> least
>> > above 800px)
>> > * WEBSITE URL
>> > * CONTACT PERSON (in case of individual can be same as NAME)
>> > * EMAIL OF CONTACT
>> > * PHONE OF CONTACT
>> > * APACHE ROYALE CONTRIBUTOR (if the company or individual has people
>> > contributing to this project, or if is an individual contributes to this
>> > project)
>> >
>> > thanks
>> >
>> >
>> > -- Forwarded message -
>> > De: Carlos Rovira 
>> >
>> > If you consider this ok, I can create a thread so companies that want
>> to be
>> > listed, can express they want to, and I can create a page in our site
>> with
>> > the logos and urls and maybe more (contact person?, ...)
>> >
>> > thanks
>> >
>> >
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Crux Branch

2019-07-04 Thread Andrew Wetmore
This is great.

However, even with the original Swiz I found the documentation quite thin
and that it made a lot of assumptions about what a general developer might
know and need to know. This site [1] made an attempt about ten years ago to
improve on an intro to Swiz. What plans are in the works to not only
provide Crux, but make it welcoming and accessible? Tour de Crux??

a

[1] https://deshartman.wordpress.com/2010/02/07/first-swiz/

On Thu, Jul 4, 2019 at 1:17 PM Josh Tynjala 
wrote:

> Cool stuff, Greg and Carlos!
>
> One concern: In Flash, the "addedToStage" event does not bubble. It's
> actually the "added" event that bubbles and is used by frameworks like
> Swiz, Cairngorm, Robotlegs, etc.
>
> To avoid potential confusion for people migrating an existing app from
> Flex/Flash that might already listen for that event (and wouldn't expect it
> to bubble), I'd recommend using a different name than "addedToStage". It
> could be "added", like Flash. Or it could even have a new name that's
> similar to "addedToStage", but is more relevant to Royale. Royale doesn't
> have a "stage", so that name feels a bit out of place to me anyway. Maybe
> "addedToApplication" or something like that.
>
> - Josh
>
>
> On Wed, Jul 3, 2019, 11:11 PM Greg Dove  wrote:
>
> > Hi all,
> >
> > Just a quick advance notice that we are getting something very similar to
> > Swiz before too long.
> > There is a new branch called feature/Crux
> >
> > We can still explore other possible ways to incorporate Swiz code in
> Royale
> > (we have looked at having the code donated in the past), but for now at
> > least it is as a derivative work, differentiated by name as 'Crux' and
> > hence the name of the branch. 'Crux' means a main or pivotal point -
> > something important - and a common English expression that can express
> that
> > is when someone says ""the crux of the matter" - it means an important
> > thing to focus on.
> >
> > The name is what it is now - it is short and has a powerful meaning. But
> > certainly we can review that too.
> >
> > The branch has the beginnings of the original Swiz functionality which
> > supports metadata driven Injection (including runtime Binding Injection),
> > EventHandlers, main Dispatcher etc.
> > Those things are already shown in 3 examples [1] in examples/crux in the
> > branch, (but I did not check the ant builds for those yet- I will get to
> > that). Beyond those features, I have not ventured far yet, and perhaps
> some
> > of the others may not be relevant for Royale.
> >
> > In case it's useful elsewhere, there is also a new JSStageEvents  'stage
> > events' simulator bead which works from the main application level, and
> > provides bubbling 'addedToStage' events which Crux listens to at the top
> > level. These can be filtered (so not everything generates the events, for
> > example). Not sure if that might be useful for other things, just
> > mentioning it for now... It does dispatch 'removedFromStage' as well, but
> > too late for bubbling, so I will investigate if I can do something a bit
> > sneaky to see if I can make that work. Otherwise it is always possible to
> > add  removedFromStage  listeners directly to the target of interest
> inside
> > an 'addedToStage' listener.
> >
> > I expect there will be bugs, and I of course there will be many things I
> > can continue to improve, so this is just an early announcement for your
> > awareness. Carlos sponsored a large chunk of my time on this, so you have
> > him to thank for that, but I have also contributed a lot of my own time,
> > and will continue to do so. Thanks also to Alex for recent guidance on
> > licencing issues, this was uncharted territory for me.
> >
> > Anyhow, Carlos will, I am sure, provide more info, he is very familiar
> with
> > Swiz from the past.
> >
> > -Greg
> >
> >
> > 1. https://github.com/apache/royale-asjs/tree/feature/Crux/examples/crux
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Commercial Support Page (was: Fwd: AIR and Royale)

2019-06-07 Thread Andrew Wetmore
This is s great idea

On Fri, Jun 7, 2019, 6:24 AM Carlos Rovira,  wrote:

> Hi,
>
> I'll be creating a page on the website in the following days with a list of
> third party providers that offers commercial support for Apache Royale, in
> the lines we saw in the links shared by Dave Fisher as examples in other
> Apache products.
>
> It could be companies or individuals.
>
> Anyone that wants to be listed, please share here the following data:
>
> * NAME
> * SHORT DESCRIPTION (if applies)
> * LOGO (if applies) (PNG, background transparent, good resolution (at least
> above 800px)
> * WEBSITE URL
> * CONTACT PERSON (in case of individual can be same as NAME)
> * EMAIL OF CONTACT
> * PHONE OF CONTACT
> * APACHE ROYALE CONTRIBUTOR (if the company or individual has people
> contributing to this project, or if is an individual contributes to this
> project)
>
> thanks
>
>
> -- Forwarded message -
> De: Carlos Rovira 
>
> If you consider this ok, I can create a thread so companies that want to be
> listed, can express they want to, and I can create a page in our site with
> the logos and urls and maybe more (contact person?, ...)
>
> thanks
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: Embedded Assets (was Re: AIR and Royale)

2019-06-06 Thread Andrew Wetmore
@carlos.rov...@gmail.com  I think the
"flex-equivalents" page should go just below the "components" page in the
ToC. If you told me how to add things to the ToC, I don't remember it!

And, really, I think both Component Sets and Flex Equivalents should be
under a User Interface heading, as the source files are.

On Thu, Jun 6, 2019 at 6:20 PM Carlos Rovira 
wrote:

> Hi Andrew,
>
> Can see so much about that page, I didn't know about it. looking at history
> I just renamed it when I was refactoring names, but I think you created
> that, isn't it? Maybe you had some plan to put in a certain place in the
> TOC to be accesible?
> Or maybe you're asking me to add it to the TOC? if so let me know in what
> point you want it and I can add it
>
> thanks
>
>
> El jue., 6 jun. 2019 a las 15:07, Andrew Wetmore ()
> escribió:
>
> > I just added a brief statement about using a URL instead of embedding
> > assets in Royale in the "Flex Equivalents" page [1].
> >
> > @Carlos Rovira  , where does that page appear
> > when
> > a user is looking through the documentation? I can't find my way to it
> > through the compiled Help Docs, or in the ToC.
> >
> >
> >
> > [1]  royale-docs <https://github.com/apache/royale-docs>/user-interface
> > <https://github.com/apache/royale-docs/tree/master/user-interface>/
> > flex-equivalents.md
> >
> > On Thu, Jun 6, 2019 at 9:26 AM Frost, Andrew 
> > wrote:
> >
> > > Thanks, Alex & Carlos
> > >
> > > Yes I agree basically, embedding something in terms of how Flex does it
> > > isn't something that's relevant for Royale or HTTP-based solutions in
> the
> > > same way, and we certainly don't want to end up encoding something into
> > > text base64 formats..
> > >
> > > It might be nice to have the compiler do some magic to recognise this
> > > scenario and to grab the swf file, extract the image and then change
> the
> > > mxml so that it just becomes a url reference.. but that's probably a
> lot
> > of
> > > work compared to just doing this as a manual operation which is just a
> > > one-off update needed in the code.
> > >
> > > So that:
> > > 
> > > is turned into something like
> > > 
> > >
> > > Anyway, if we get asked to do this then I'll take a look to see whether
> > it
> > > could be merged into the toolchain somehow.. having a quick look into
> the
> > > SWF it could be fun as these icons are actually not just pure images
> but
> > > include some shape output from the Flash/Animate authoring tools too..
> > but
> > > I guess we can just have some quick AS3 tool to extract these with the
> > > appropriate shape and save them to png..
> > >
> > > For now I'll wait to see whether the project does actually go ahead!!
> > >
> > > thanks
> > >
> > >Andrew
> > >
> > >
> > > -Original Message-
> > > From: Carlos Rovira [mailto:carlosrov...@apache.org]
> > > Sent: 06 June 2019 11:33
> > > To: dev@royale.apache.org
> > > Subject: [EXTERNAL] Re: Embedded Assets (was Re: AIR and Royale)
> > >
> > > Hi,
> > >
> > > I think in the case of HTML, does not have sense to me the concept of
> > > Embed like in Flex. Maybe of SWF target or others (don't know if WebAsm
> > > could benefit from something like this) Maybe for HTML use something
> like
> > > Embed metadata, could just copy the assets to the resources folder to
> be
> > > available, since like Alex said, a request per asset is needed and
> making
> > > other kind of big file seems strange in this case (maybe not). Although
> > we
> > > have solved the copying of assets in different ways through compiler
> for
> > > libraries and ANT/MAVEN automation in Application.
> > >
> > > for me this could be something to investigate in the future, but with
> low
> > > priority, since I think we still have bigger fish to fry
> > >
> > > just my 2...
> > >
> > >
> > > El mié., 5 jun. 2019 a las 18:07, Alex Harui ( > >)
> > > escribió:
> > >
> > > > Regarding embedded assets in Royale:
> > > >
> > > > There is no embedded asset support at this time because it is not
> > > > obvious to me it will be worth it.  We need a volunteer to devise a
> > > > strategy that works and implement it.
> > >

Re: Embedded Assets (was Re: AIR and Royale)

2019-06-06 Thread Andrew Wetmore
ntec.com/3LTnHE8ZRpM1rsYjqUUg5xV7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F3L9wbF4uCYccj7EQCUBeXbp7Vc%253Fu%253Dhttps%25253A%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3D7Cp77z%252FW16Gf%252B9Q8P0%252Fs7qOBZdGYOh71F0bX%252BYLwXp8%253D%26reserved%3D0
> > >>> %2F%2Ftheblog.adobe.com%2Fthe-future-of-adobe-air%2F>
> > >>> [2]
> >
> https://clicktime.symantec.com/32YzRLFVBkACau1g6fYnSyR7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F36DC33RH3RXctPTGAK4XztY7Vc%253Fu%253Dhttps%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3DWmyyWadQQ1saSrBkTeuYmPiM0vDW49J3Lob%252BC7eejfg%253D%26reserved%3D0
> > >>> %3A%2F%2Fservices.harman.com%2Fpartners%2Fadobe <
> > >>>
> >
> https://clicktime.symantec.com/3FbC1ESabdLRDQj4WKt3mvF7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F36DC33RH3RXctPTGAK4XztY7Vc%253Fu%253Dhttps%25253A%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3DJGO%252Fg99Iey8nKvQN5Hzd2EmXkle35QSllbc5UyDaj%252FE%253D%26reserved%3D0
> > >>> %2F%2Fservices.harman.com%2Fpartners%2Fadobe>
> > >>
> > >>
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon:
> > >> *
> >
> https://clicktime.symantec.com/3Jpifi5EEL2icEQYT7KGyLz7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F32dvoAS1WTaQP1E2yQmx5pn7Vc%253Fu%253Dhttps%25253A%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3D%252FDiwRHFQCxdxO7pjeV85svwoRoI8nZmWpWBKDNgzr3w%253D%26reserved%3D0
> > >> %2F%2Fwww.patreon.com%2Fpiotrzarzycki
> > >> <
> >
> https://clicktime.symantec.com/3Jpifi5EEL2icEQYT7KGyLz7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F32dvoAS1WTaQP1E2yQmx5pn7Vc%253Fu%253Dhttps%25253A%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3D%252FDiwRHFQCxdxO7pjeV85svwoRoI8nZmWpWBKDNgzr3w%253D%26reserved%3D0
> > >> %2F%2Fwww.patreon.com%2Fpiotrzarzycki>*
> > >>
> > >
> > >
> > > --
> > > Carlos Rovira
> > >
> >
> https://clicktime.symantec.com/32xi5m2jt6cypwahMZPza5b7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F3Peb7VMJWFagYLtTD2HSBGD7Vc%253Fu%253Dhttp%25253A%25252F%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3DPE5%252FahFsZHO5iuUE9pbP3jnax2KYXkxJBvBS%252Bfxb22Y%253D%26reserved%3D0
> > > %2Fabout.me%2Fcarlosrovira
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://clicktime.symantec.com/338hPRiMe7pQWFRqHyrJDfV7Vc?u=http%3A%2F%2Fabout.me%2Fcarlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


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

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

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

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


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Docs layout almost ready

2019-05-19 Thread Andrew Wetmore
@Carlos I notice that we have a Docs page called "UI sets" [1]. Elsewhere
we call them "Component sets". We should standardize on one term; I prefer
"Component sets" as "UI" includes a lot of things besides components.

[1] https://apache.github.io/royale-docs/UI_Sets.html

On Sun, May 19, 2019 at 8:36 AM Carlos Rovira 
wrote:

> Great Andrew,
>
> As I posted in other thread, this days I plan to add many Jewel docs
> content, so please feel free to correct at your discretion
>
> thanks!
>
> El dom., 19 may. 2019 a las 12:50, Andrew Wetmore ()
> escribió:
>
> > Made a couple of small tweaks to those instructions, mainly to correct a
> > typo.
> >
> > On Sun, May 19, 2019 at 4:52 AM Carlos Rovira 
> > wrote:
> >
> > > Hi,
> > >
> > > I could finally contribute to this repo thanks to the multiple changes
> of
> > > Adrian. One of them is how to develop in local here:
> > >
> > > https://github.com/apache/royale-docs
> > >
> > > At the end of the page in the readme is this:
> > >
> > > Build Locally
> > >
> > >1.
> > >
> > >Install Ruby+Devkit <https://rubyinstaller.org/downloads/>. Ruby is
> > >required to run Jekyll.
> > >2.
> > >
> > >Install Jekyll <https://jekyllrb.com/>
> > >3.
> > >
> > >If you want to provide a local configuration copy _config.yml to
> > >local_config.yml
> > >4.
> > >
> > >To build the docs run the following command:
> > >
> > >The website will be rendered inside the _site folder.
> > >5.
> > >
> > >To browse the docs using built-in Jekyll server run the following
> > >command:
> > >
> > >The website will be availeble at http://127.0.0.1:4000/royale-docs/
> > >
> > >
> > >
> > > El dom., 19 may. 2019 a las 4:11, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>)
> > > escribió:
> > >
> > > > Hi Andrew,
> > > >
> > > > Whenever you go to some page and see https://apache.github.io it
> means
> > > > that
> > > > content is part of royale-docs. It you see something else it's part
> of
> > > > WordPress.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > >
> > > >
> > > > On Sat, May 18, 2019, 9:25 PM Andrew Wetmore 
> > > wrote:
> > > >
> > > > > It looks quite good.
> > > > >
> > > > > Where do the source pages live now? I see a couple of small text
> > > errors I
> > > > > would like to fix.
> > > > >
> > > > > On Sat, May 18, 2019 at 3:57 PM Carlos Rovira <
> > carlosrov...@apache.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > Hi all!,
> > > > > >
> > > > > > I think latest combined efforts we have the Royale-docs layout
> > ready.
> > > > > > Please take a look and let us know what you think.
> > > > > >
> > > > > > https://apache.github.io/royale-docs/Get%20Started.html
> > > > > >
> > > > > > (remember clean your browser cache, since you could not see the
> > pages
> > > > > > correctly updated)
> > > > > >
> > > > > > I think we should concentrate now of fill, fix and correct
> > iterating
> > > > all
> > > > > > what we can. Making stories and what we think will help people
> > > coming.
> > > > > > A good site where you all should look to get inspiration is for
> > > example
> > > > > > React docs: https://reactjs.org/docs/getting-started.html
> > > > > >
> > > > > > I plan to start a Jewel part on frameworks and try to add real
> > > examples
> > > > > > like in blog examples.
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > > http://about.me/carlosrovira
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Andrew Wetmore
> > > > >
> > > > > http://cottage14.blogspot.com/
> > > > >
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Docs layout almost ready

2019-05-19 Thread Andrew Wetmore
Made a couple of small tweaks to those instructions, mainly to correct a
typo.

On Sun, May 19, 2019 at 4:52 AM Carlos Rovira 
wrote:

> Hi,
>
> I could finally contribute to this repo thanks to the multiple changes of
> Adrian. One of them is how to develop in local here:
>
> https://github.com/apache/royale-docs
>
> At the end of the page in the readme is this:
>
> Build Locally
>
>1.
>
>Install Ruby+Devkit <https://rubyinstaller.org/downloads/>. Ruby is
>required to run Jekyll.
>2.
>
>Install Jekyll <https://jekyllrb.com/>
>3.
>
>If you want to provide a local configuration copy _config.yml to
>local_config.yml
>4.
>
>To build the docs run the following command:
>
>The website will be rendered inside the _site folder.
>5.
>
>To browse the docs using built-in Jekyll server run the following
>command:
>
>The website will be availeble at http://127.0.0.1:4000/royale-docs/
>
>
>
> El dom., 19 may. 2019 a las 4:11, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Hi Andrew,
> >
> > Whenever you go to some page and see https://apache.github.io it means
> > that
> > content is part of royale-docs. It you see something else it's part of
> > WordPress.
> >
> > Thanks,
> > Piotr
> >
> >
> >
> > On Sat, May 18, 2019, 9:25 PM Andrew Wetmore 
> wrote:
> >
> > > It looks quite good.
> > >
> > > Where do the source pages live now? I see a couple of small text
> errors I
> > > would like to fix.
> > >
> > > On Sat, May 18, 2019 at 3:57 PM Carlos Rovira  >
> > > wrote:
> > >
> > > > Hi all!,
> > > >
> > > > I think latest combined efforts we have the Royale-docs layout ready.
> > > > Please take a look and let us know what you think.
> > > >
> > > > https://apache.github.io/royale-docs/Get%20Started.html
> > > >
> > > > (remember clean your browser cache, since you could not see the pages
> > > > correctly updated)
> > > >
> > > > I think we should concentrate now of fill, fix and correct iterating
> > all
> > > > what we can. Making stories and what we think will help people
> coming.
> > > > A good site where you all should look to get inspiration is for
> example
> > > > React docs: https://reactjs.org/docs/getting-started.html
> > > >
> > > > I plan to start a Jewel part on frameworks and try to add real
> examples
> > > > like in blog examples.
> > > >
> > > > Thanks
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > http://cottage14.blogspot.com/
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Docs layout almost ready

2019-05-18 Thread Andrew Wetmore
It looks quite good.

Where do the source pages live now? I see a couple of small text errors I
would like to fix.

On Sat, May 18, 2019 at 3:57 PM Carlos Rovira 
wrote:

> Hi all!,
>
> I think latest combined efforts we have the Royale-docs layout ready.
> Please take a look and let us know what you think.
>
> https://apache.github.io/royale-docs/Get%20Started.html
>
> (remember clean your browser cache, since you could not see the pages
> correctly updated)
>
> I think we should concentrate now of fill, fix and correct iterating all
> what we can. Making stories and what we think will help people coming.
> A good site where you all should look to get inspiration is for example
> React docs: https://reactjs.org/docs/getting-started.html
>
> I plan to start a Jewel part on frameworks and try to add real examples
> like in blog examples.
>
> Thanks
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: About having an Apache Royale page on Wikipedia

2019-05-18 Thread Andrew Wetmore
@Carlos I would go ahead and announce the Wikipedia page. I will add other
material to it gradually, but cannot make a significant further change this
weekend.

On Sat, May 18, 2019 at 5:14 AM Carlos Rovira 
wrote:

> Great!
>
> I added AS3 Extension in the VSCode part to try to edit :)
>
> I can tweet it or I can wait if you plan to do more completion in next
> days. Also I'll add to website since the theme supports Wikipedia :)
>
> thanks!
>
>
>
>
>
> El vie., 17 may. 2019 a las 19:03, Andrew Wetmore ()
> escribió:
>
> > It is now here: [1]. I will update the Apache Flex site, which mentions
> > Royale, to point to it.
> >
> > [1] https://en.wikipedia.org/wiki/Apache_Royale
> >
> > On Fri, May 17, 2019 at 1:56 PM Andrew Wetmore 
> > wrote:
> >
> > > Following the GEMO "good enough, move on" principle, I am going to try
> to
> > > move the page to "live" status. We can continue refining it and adding
> > > information indefinitely.
> > >
> > > On Fri, May 17, 2019 at 1:21 PM Andrew Wetmore 
> > > wrote:
> > >
> > >> @Carlos if the client does not want to give access to a pre-production
> > >> site, would they agree to our posting a webtour, a video of the site
> in
> > >> action?
> > >>
> > >> Thank you for the thoughts about what to say about Royale. I will
> > include
> > >> multi-target thoughts!.
> > >>
> > >> On Fri, May 17, 2019 at 12:45 PM Carlos Rovira <
> carlosrov...@apache.org
> > >
> > >> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> we asking our client about what we can share about our first
> production
> > >>> royale app.
> > >>> Let's see if we can post the link to a pre-production site, if we can
> > >>> post user/pass to enter it, and if we can't do that at least post
> some
> > >>> screen shots
> > >>>
> > >>> @Andrew Wetmore  thanks for working on the
> > >>> wikipedia page, that looks like a good starting point! :)
> > >>> just few ideas: talk about Royale not just as technology that can
> > target
> > >>> HTML, but like a multi target one capable of be extended in the
> future
> > to
> > >>> target next ones like WebAssembly, or other native ones.
> > >>>
> > >>> Thanks!
> > >>>
> > >>> Carlos
> > >>>
> > >>>
> > >>>
> > >>> El vie., 17 may. 2019 a las 14:29, Andrew Wetmore (<
> > cottag...@gmail.com>)
> > >>> escribió:
> > >>>
> > >>>> Here is the current state of our Wikipedia page in my editor area
> > [1]. I
> > >>>> have a few things to add, like figuring out how to make the logo
> > appear
> > >>>> in
> > >>>> the info box and adding more interesting stuff to the "salient
> > features"
> > >>>> section. I also want to add a section about the community and how to
> > >>>> become
> > >>>> a participant.
> > >>>>
> > >>>> [1] https://en.wikipedia.org/wiki/User:Inukjuak/Apache_Royale
> > >>>>
> > >>>> On Fri, May 17, 2019 at 8:48 AM Harbs 
> wrote:
> > >>>>
> > >>>> > That sucks… :-(
> > >>>> >
> > >>>> > One thing I like about git based wikis is that you can edit
> locally
> > >>>> on a
> > >>>> > text editor and these things don’t happen (as long as your text
> > >>>> editor does
> > >>>> > automatic saves).
> > >>>> >
> > >>>> > > On May 17, 2019, at 1:24 PM, Andrew Wetmore <
> cottag...@gmail.com>
> > >>>> wrote:
> > >>>> > >
> > >>>> > > @Harbs: thank you!
> > >>>> > >
> > >>>> > > Slight setback on the Wikipedia page: I was about 80% done
> > creating
> > >>>> it in
> > >>>> > > the Wikipedia sandbox, stepped away to do other things for a
> > couple
> > >>>> of
> > >>>> > > hours, Windows did an update and all my work was lost (the
> sandbox
> > >>>> does
> > >>>> > not
> > >>>> &

Re: Adding Jewel classes to Apache Royale AS3 reference

2019-05-18 Thread Andrew Wetmore
I wonder if there should be coverage of all the component sets in both
ASDoc and the help docs. @aharui had a good, succinct decription of the
style and purpose of each set in an email to this group, but I can't find
it.

On Sat, May 18, 2019, 5:33 AM Carlos Rovira, 
wrote:

> Hi,
>
> one thing people complains about docs and reference was about AS3 Reference
> not complete.
> For example, I notice Jewel UI set is not listed.
> There's some place where I can read how that works to try to add it or
> someone can explain what we should do?
> or if others have some cycles go and add it?
>
> thanks
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: About having an Apache Royale page on Wikipedia

2019-05-17 Thread Andrew Wetmore
It is now here: [1]. I will update the Apache Flex site, which mentions
Royale, to point to it.

[1] https://en.wikipedia.org/wiki/Apache_Royale

On Fri, May 17, 2019 at 1:56 PM Andrew Wetmore  wrote:

> Following the GEMO "good enough, move on" principle, I am going to try to
> move the page to "live" status. We can continue refining it and adding
> information indefinitely.
>
> On Fri, May 17, 2019 at 1:21 PM Andrew Wetmore 
> wrote:
>
>> @Carlos if the client does not want to give access to a pre-production
>> site, would they agree to our posting a webtour, a video of the site in
>> action?
>>
>> Thank you for the thoughts about what to say about Royale. I will include
>> multi-target thoughts!.
>>
>> On Fri, May 17, 2019 at 12:45 PM Carlos Rovira 
>> wrote:
>>
>>> Hi,
>>>
>>> we asking our client about what we can share about our first production
>>> royale app.
>>> Let's see if we can post the link to a pre-production site, if we can
>>> post user/pass to enter it, and if we can't do that at least post some
>>> screen shots
>>>
>>> @Andrew Wetmore  thanks for working on the
>>> wikipedia page, that looks like a good starting point! :)
>>> just few ideas: talk about Royale not just as technology that can target
>>> HTML, but like a multi target one capable of be extended in the future to
>>> target next ones like WebAssembly, or other native ones.
>>>
>>> Thanks!
>>>
>>> Carlos
>>>
>>>
>>>
>>> El vie., 17 may. 2019 a las 14:29, Andrew Wetmore ()
>>> escribió:
>>>
>>>> Here is the current state of our Wikipedia page in my editor area [1]. I
>>>> have a few things to add, like figuring out how to make the logo appear
>>>> in
>>>> the info box and adding more interesting stuff to the "salient features"
>>>> section. I also want to add a section about the community and how to
>>>> become
>>>> a participant.
>>>>
>>>> [1] https://en.wikipedia.org/wiki/User:Inukjuak/Apache_Royale
>>>>
>>>> On Fri, May 17, 2019 at 8:48 AM Harbs  wrote:
>>>>
>>>> > That sucks… :-(
>>>> >
>>>> > One thing I like about git based wikis is that you can edit locally
>>>> on a
>>>> > text editor and these things don’t happen (as long as your text
>>>> editor does
>>>> > automatic saves).
>>>> >
>>>> > > On May 17, 2019, at 1:24 PM, Andrew Wetmore 
>>>> wrote:
>>>> > >
>>>> > > @Harbs: thank you!
>>>> > >
>>>> > > Slight setback on the Wikipedia page: I was about 80% done creating
>>>> it in
>>>> > > the Wikipedia sandbox, stepped away to do other things for a couple
>>>> of
>>>> > > hours, Windows did an update and all my work was lost (the sandbox
>>>> does
>>>> > not
>>>> > > seem to have a "save" function). When I am done swearing and kicking
>>>> > > things, I will rebuild it, more quickly the second time, so it
>>>> should be
>>>> > > ready to go live sometime this weekend.
>>>> > >
>>>> > > On Fri, May 17, 2019 at 4:11 AM Harbs >>> >>> > harbs.li...@gmail.com>> wrote:
>>>> > >
>>>> > >> Here’s one:
>>>> > >> https://marketinginflection.com/printui-demo.php <
>>>> > https://marketinginflection.com/printui-demo.php> <
>>>> > >> https://marketinginflection.com/printui-demo.php <
>>>> > https://marketinginflection.com/printui-demo.php>>
>>>> > >>
>>>> > >>> On May 17, 2019, at 1:27 AM, Andrew Wetmore 
>>>> > wrote:
>>>> > >>>
>>>> > >>> I believe there are a couple of live applications using Royale.
>>>> Do we
>>>> > >> have
>>>> > >>> links to them I could reference on the Wikipedia page, or are they
>>>> > >> internal
>>>> > >>> company apps?
>>>> > >>>
>>>> > >>> On Thu, May 16, 2019 at 3:28 PM Carlos Rovira <
>>>> carlosrov...@apache.org
>>>> > >
>>>> > >>> wrote:
>>>

Re: About having an Apache Royale page on Wikipedia

2019-05-17 Thread Andrew Wetmore
Following the GEMO "good enough, move on" principle, I am going to try to
move the page to "live" status. We can continue refining it and adding
information indefinitely.

On Fri, May 17, 2019 at 1:21 PM Andrew Wetmore  wrote:

> @Carlos if the client does not want to give access to a pre-production
> site, would they agree to our posting a webtour, a video of the site in
> action?
>
> Thank you for the thoughts about what to say about Royale. I will include
> multi-target thoughts!.
>
> On Fri, May 17, 2019 at 12:45 PM Carlos Rovira 
> wrote:
>
>> Hi,
>>
>> we asking our client about what we can share about our first production
>> royale app.
>> Let's see if we can post the link to a pre-production site, if we can
>> post user/pass to enter it, and if we can't do that at least post some
>> screen shots
>>
>> @Andrew Wetmore  thanks for working on the
>> wikipedia page, that looks like a good starting point! :)
>> just few ideas: talk about Royale not just as technology that can target
>> HTML, but like a multi target one capable of be extended in the future to
>> target next ones like WebAssembly, or other native ones.
>>
>> Thanks!
>>
>> Carlos
>>
>>
>>
>> El vie., 17 may. 2019 a las 14:29, Andrew Wetmore ()
>> escribió:
>>
>>> Here is the current state of our Wikipedia page in my editor area [1]. I
>>> have a few things to add, like figuring out how to make the logo appear
>>> in
>>> the info box and adding more interesting stuff to the "salient features"
>>> section. I also want to add a section about the community and how to
>>> become
>>> a participant.
>>>
>>> [1] https://en.wikipedia.org/wiki/User:Inukjuak/Apache_Royale
>>>
>>> On Fri, May 17, 2019 at 8:48 AM Harbs  wrote:
>>>
>>> > That sucks… :-(
>>> >
>>> > One thing I like about git based wikis is that you can edit locally on
>>> a
>>> > text editor and these things don’t happen (as long as your text editor
>>> does
>>> > automatic saves).
>>> >
>>> > > On May 17, 2019, at 1:24 PM, Andrew Wetmore 
>>> wrote:
>>> > >
>>> > > @Harbs: thank you!
>>> > >
>>> > > Slight setback on the Wikipedia page: I was about 80% done creating
>>> it in
>>> > > the Wikipedia sandbox, stepped away to do other things for a couple
>>> of
>>> > > hours, Windows did an update and all my work was lost (the sandbox
>>> does
>>> > not
>>> > > seem to have a "save" function). When I am done swearing and kicking
>>> > > things, I will rebuild it, more quickly the second time, so it
>>> should be
>>> > > ready to go live sometime this weekend.
>>> > >
>>> > > On Fri, May 17, 2019 at 4:11 AM Harbs >> >> > harbs.li...@gmail.com>> wrote:
>>> > >
>>> > >> Here’s one:
>>> > >> https://marketinginflection.com/printui-demo.php <
>>> > https://marketinginflection.com/printui-demo.php> <
>>> > >> https://marketinginflection.com/printui-demo.php <
>>> > https://marketinginflection.com/printui-demo.php>>
>>> > >>
>>> > >>> On May 17, 2019, at 1:27 AM, Andrew Wetmore 
>>> > wrote:
>>> > >>>
>>> > >>> I believe there are a couple of live applications using Royale. Do
>>> we
>>> > >> have
>>> > >>> links to them I could reference on the Wikipedia page, or are they
>>> > >> internal
>>> > >>> company apps?
>>> > >>>
>>> > >>> On Thu, May 16, 2019 at 3:28 PM Carlos Rovira <
>>> carlosrov...@apache.org
>>> > >
>>> > >>> wrote:
>>> > >>>
>>> > >>>> Great Andrew! Thanks! :)
>>> > >>>>
>>> > >>>> El jue., 16 may. 2019 a las 20:23, Andrew Wetmore (<
>>> > cottag...@gmail.com
>>> > >>> )
>>> > >>>> escribió:
>>> > >>>>
>>> > >>>>> I can do that! I am a Wikipedia editor, although not active
>>> enough to
>>> > >>>> avoid
>>> > >>>>> close scrutiny of what I write.
>>> > >>>&

Re: About having an Apache Royale page on Wikipedia

2019-05-17 Thread Andrew Wetmore
@Carlos if the client does not want to give access to a pre-production
site, would they agree to our posting a webtour, a video of the site in
action?

Thank you for the thoughts about what to say about Royale. I will include
multi-target thoughts!.

On Fri, May 17, 2019 at 12:45 PM Carlos Rovira 
wrote:

> Hi,
>
> we asking our client about what we can share about our first production
> royale app.
> Let's see if we can post the link to a pre-production site, if we can post
> user/pass to enter it, and if we can't do that at least post some screen
> shots
>
> @Andrew Wetmore  thanks for working on the wikipedia
> page, that looks like a good starting point! :)
> just few ideas: talk about Royale not just as technology that can target
> HTML, but like a multi target one capable of be extended in the future to
> target next ones like WebAssembly, or other native ones.
>
> Thanks!
>
> Carlos
>
>
>
> El vie., 17 may. 2019 a las 14:29, Andrew Wetmore ()
> escribió:
>
>> Here is the current state of our Wikipedia page in my editor area [1]. I
>> have a few things to add, like figuring out how to make the logo appear in
>> the info box and adding more interesting stuff to the "salient features"
>> section. I also want to add a section about the community and how to
>> become
>> a participant.
>>
>> [1] https://en.wikipedia.org/wiki/User:Inukjuak/Apache_Royale
>>
>> On Fri, May 17, 2019 at 8:48 AM Harbs  wrote:
>>
>> > That sucks… :-(
>> >
>> > One thing I like about git based wikis is that you can edit locally on a
>> > text editor and these things don’t happen (as long as your text editor
>> does
>> > automatic saves).
>> >
>> > > On May 17, 2019, at 1:24 PM, Andrew Wetmore 
>> wrote:
>> > >
>> > > @Harbs: thank you!
>> > >
>> > > Slight setback on the Wikipedia page: I was about 80% done creating
>> it in
>> > > the Wikipedia sandbox, stepped away to do other things for a couple of
>> > > hours, Windows did an update and all my work was lost (the sandbox
>> does
>> > not
>> > > seem to have a "save" function). When I am done swearing and kicking
>> > > things, I will rebuild it, more quickly the second time, so it should
>> be
>> > > ready to go live sometime this weekend.
>> > >
>> > > On Fri, May 17, 2019 at 4:11 AM Harbs > > harbs.li...@gmail.com>> wrote:
>> > >
>> > >> Here’s one:
>> > >> https://marketinginflection.com/printui-demo.php <
>> > https://marketinginflection.com/printui-demo.php> <
>> > >> https://marketinginflection.com/printui-demo.php <
>> > https://marketinginflection.com/printui-demo.php>>
>> > >>
>> > >>> On May 17, 2019, at 1:27 AM, Andrew Wetmore 
>> > wrote:
>> > >>>
>> > >>> I believe there are a couple of live applications using Royale. Do
>> we
>> > >> have
>> > >>> links to them I could reference on the Wikipedia page, or are they
>> > >> internal
>> > >>> company apps?
>> > >>>
>> > >>> On Thu, May 16, 2019 at 3:28 PM Carlos Rovira <
>> carlosrov...@apache.org
>> > >
>> > >>> wrote:
>> > >>>
>> > >>>> Great Andrew! Thanks! :)
>> > >>>>
>> > >>>> El jue., 16 may. 2019 a las 20:23, Andrew Wetmore (<
>> > cottag...@gmail.com
>> > >>> )
>> > >>>> escribió:
>> > >>>>
>> > >>>>> I can do that! I am a Wikipedia editor, although not active
>> enough to
>> > >>>> avoid
>> > >>>>> close scrutiny of what I write.
>> > >>>>>
>> > >>>>> The article will outline the origins, purpose, development, and
>> > >>>> particular
>> > >>>>> characteristics of Royale. Once I have the first version up and
>> > >>>> published,
>> > >>>>> we can work on improving it.
>> > >>>>>
>> > >>>>> On Thu, May 16, 2019 at 12:11 PM Carlos Rovira <
>> > >> carlosrov...@apache.org>
>> > >>>>> wrote:
>> > >>>>>
>> > >>>>>> Hi Andrew,
>> > >>>>>>
>> > >>>>>> what do you think about to create a page in Wikipedia for Apache
>> > >>>> Royale?
>> > >>>>>> Then we can link from the website.
>> > >>>>>>
>> > >>>>>> I think that's a task where you can help a lot and where your
>> > writing
>> > >>>> and
>> > >>>>>> editing skills will be most needed that any other skills.
>> > >>>>>>
>> > >>>>>> Let us know what you think! :)
>> > >>>>>>
>> > >>>>>> Thank you
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> --
>> > >>>>>> Carlos Rovira
>> > >>>>>> http://about.me/carlosrovira
>> > >>>>>>
>> > >>>>>>
>> > >>>>>
>> > >>>>> --
>> > >>>>> Andrew Wetmore
>> > >>>>>
>> > >>>>> http://cottage14.blogspot.com/
>> > >>>>>
>> > >>>>
>> > >>>>
>> > >>>> --
>> > >>>> Carlos Rovira
>> > >>>> http://about.me/carlosrovira
>> > >>>>
>> > >>>
>> > >>>
>> > >>> --
>> > >>> Andrew Wetmore
>> > >>>
>> > >>> http://cottage14.blogspot.com/
>> > >>
>> > >>
>> > >
>> > > --
>> > > Andrew Wetmore
>> > >
>> > > http://cottage14.blogspot.com/ <http://cottage14.blogspot.com/>
>> >
>>
>>
>> --
>> Andrew Wetmore
>>
>> http://cottage14.blogspot.com/
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Docs Changes Proposal

2019-05-17 Thread Andrew Wetmore
@Piotr: yes, that is correct. If I use the menu, it is like I am using the
table of contents of a physical book. If I follow a link within the text,
it is as if I am picking up a different physical book.

On Fri, May 17, 2019 at 7:18 AM Piotr Zarzycki 
wrote:

> Andrew,
>
> By saying that:
>
> "If I am starting from the help
> docs I do not want the window to suddenly be focusing on something else; I
> would prefer a new window to appear with whatever I clicked on so I can go
> back to the first window easily and continue my studies."
>
> Do you mean when you are being in doc [1] - above apply on anything what
> you click inside text - Am I right ? Above new window rule do not apply
> when you navigating trough menu on the right sight in doc [1]?
>
> [1] https://apache.github.io/royale-docs/
>
> Thanks,
> Piotr
>
> pt., 17 maj 2019 o 12:12 Andrew Wetmore  napisał(a):
>
> > I agree with @Piotr that context is key. If I am starting from the help
> > docs I do not want the window to suddenly be focusing on something else;
> I
> > would prefer a new window to appear with whatever I clicked on so I can
> go
> > back to the first window easily and continue my studies. Similarly, if my
> > context is the website, then I am thinking about the get-started stuff as
> > part of the website, and I am happy for the material I click on to take
> > over the current screen.
> >
> > On Fri, May 17, 2019 at 5:23 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > Let's see whether Andrew have different thoughts. He is an expert in
> case
> > > of documentation ;) Adrian is working on 1 or 2 small pull requests
> more.
> > > ;)
> > >
> > > pt., 17 maj 2019 o 10:11 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Ok Piotr,
> > > >
> > > > so I think we have all set as you said, and we just need to worry
> about
> > > the
> > > > content created to follow that guidelines
> > > >
> > > > :)
> > > >
> > > > El vie., 17 may. 2019 a las 10:07, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > In my opinion it depends where you are clicking on Get Started. If
> > you
> > > > are
> > > > > clicking on Get Started on main page (main menu or footer) you
> should
> > > > stay
> > > > > in the same window. I think it should be true for whatever option
> in
> > > main
> > > > > menu you are clicking.
> > > > >
> > > > > However if you are in Docs already and click on "Apache Royale
> > > > > Documentation
> > > > > <https://apache.github.io/royale-docs/>" - it would can go to
> > separate
> > > > > window where you can easy navigate.
> > > > >
> > > > > My 2 cents ;)
> > > > >
> > > > >
> > > > > pt., 17 maj 2019 o 09:59 Carlos Rovira 
> > > > > napisał(a):
> > > > >
> > > > > > Hi Andrew,
> > > > > >
> > > > > > ok, so website navigation happens on the same window and docs in
> > its
> > > > own
> > > > > > window. That's ok for me too.
> > > > > >
> > > > > > What to do with the case of pages like "Get Started"? The link is
> > in
> > > > > > website, but goes to royale docs
> > > > > >
> > > > > > thanks
> > > > > >
> > > > > >
> > > > > >
> > > > > > El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<
> > > > cottag...@gmail.com
> > > > > >)
> > > > > > escribió:
> > > > > >
> > > > > > > I think "target=_blank" should be for links to location outside
> > of
> > > > > Royale
> > > > > > > docs. To me, that includes the Royale website. I would want it
> to
> > > > open
> > > > > > in a
> > > > > > > new window rather than taking over the window I am using to
> read
> > > the
> > > > > > docs.
> > > > > > >
> > > > > > > On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <
> > > > carlosrov...@apache.org
> > > > > >
> > > > > > > wrote:
> > &

Re: About having an Apache Royale page on Wikipedia

2019-05-17 Thread Andrew Wetmore
Here is the current state of our Wikipedia page in my editor area [1]. I
have a few things to add, like figuring out how to make the logo appear in
the info box and adding more interesting stuff to the "salient features"
section. I also want to add a section about the community and how to become
a participant.

[1] https://en.wikipedia.org/wiki/User:Inukjuak/Apache_Royale

On Fri, May 17, 2019 at 8:48 AM Harbs  wrote:

> That sucks… :-(
>
> One thing I like about git based wikis is that you can edit locally on a
> text editor and these things don’t happen (as long as your text editor does
> automatic saves).
>
> > On May 17, 2019, at 1:24 PM, Andrew Wetmore  wrote:
> >
> > @Harbs: thank you!
> >
> > Slight setback on the Wikipedia page: I was about 80% done creating it in
> > the Wikipedia sandbox, stepped away to do other things for a couple of
> > hours, Windows did an update and all my work was lost (the sandbox does
> not
> > seem to have a "save" function). When I am done swearing and kicking
> > things, I will rebuild it, more quickly the second time, so it should be
> > ready to go live sometime this weekend.
> >
> > On Fri, May 17, 2019 at 4:11 AM Harbs  harbs.li...@gmail.com>> wrote:
> >
> >> Here’s one:
> >> https://marketinginflection.com/printui-demo.php <
> https://marketinginflection.com/printui-demo.php> <
> >> https://marketinginflection.com/printui-demo.php <
> https://marketinginflection.com/printui-demo.php>>
> >>
> >>> On May 17, 2019, at 1:27 AM, Andrew Wetmore 
> wrote:
> >>>
> >>> I believe there are a couple of live applications using Royale. Do we
> >> have
> >>> links to them I could reference on the Wikipedia page, or are they
> >> internal
> >>> company apps?
> >>>
> >>> On Thu, May 16, 2019 at 3:28 PM Carlos Rovira  >
> >>> wrote:
> >>>
> >>>> Great Andrew! Thanks! :)
> >>>>
> >>>> El jue., 16 may. 2019 a las 20:23, Andrew Wetmore (<
> cottag...@gmail.com
> >>> )
> >>>> escribió:
> >>>>
> >>>>> I can do that! I am a Wikipedia editor, although not active enough to
> >>>> avoid
> >>>>> close scrutiny of what I write.
> >>>>>
> >>>>> The article will outline the origins, purpose, development, and
> >>>> particular
> >>>>> characteristics of Royale. Once I have the first version up and
> >>>> published,
> >>>>> we can work on improving it.
> >>>>>
> >>>>> On Thu, May 16, 2019 at 12:11 PM Carlos Rovira <
> >> carlosrov...@apache.org>
> >>>>> wrote:
> >>>>>
> >>>>>> Hi Andrew,
> >>>>>>
> >>>>>> what do you think about to create a page in Wikipedia for Apache
> >>>> Royale?
> >>>>>> Then we can link from the website.
> >>>>>>
> >>>>>> I think that's a task where you can help a lot and where your
> writing
> >>>> and
> >>>>>> editing skills will be most needed that any other skills.
> >>>>>>
> >>>>>> Let us know what you think! :)
> >>>>>>
> >>>>>> Thank you
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Carlos Rovira
> >>>>>> http://about.me/carlosrovira
> >>>>>>
> >>>>>>
> >>>>>
> >>>>> --
> >>>>> Andrew Wetmore
> >>>>>
> >>>>> http://cottage14.blogspot.com/
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Carlos Rovira
> >>>> http://about.me/carlosrovira
> >>>>
> >>>
> >>>
> >>> --
> >>> Andrew Wetmore
> >>>
> >>> http://cottage14.blogspot.com/
> >>
> >>
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/ <http://cottage14.blogspot.com/>
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: About having an Apache Royale page on Wikipedia

2019-05-17 Thread Andrew Wetmore
@Harbs: thank you!

Slight setback on the Wikipedia page: I was about 80% done creating it in
the Wikipedia sandbox, stepped away to do other things for a couple of
hours, Windows did an update and all my work was lost (the sandbox does not
seem to have a "save" function). When I am done swearing and kicking
things, I will rebuild it, more quickly the second time, so it should be
ready to go live sometime this weekend.

On Fri, May 17, 2019 at 4:11 AM Harbs  wrote:

> Here’s one:
> https://marketinginflection.com/printui-demo.php <
> https://marketinginflection.com/printui-demo.php>
>
> > On May 17, 2019, at 1:27 AM, Andrew Wetmore  wrote:
> >
> > I believe there are a couple of live applications using Royale. Do we
> have
> > links to them I could reference on the Wikipedia page, or are they
> internal
> > company apps?
> >
> > On Thu, May 16, 2019 at 3:28 PM Carlos Rovira 
> > wrote:
> >
> >> Great Andrew! Thanks! :)
> >>
> >> El jue., 16 may. 2019 a las 20:23, Andrew Wetmore ( >)
> >> escribió:
> >>
> >>> I can do that! I am a Wikipedia editor, although not active enough to
> >> avoid
> >>> close scrutiny of what I write.
> >>>
> >>> The article will outline the origins, purpose, development, and
> >> particular
> >>> characteristics of Royale. Once I have the first version up and
> >> published,
> >>> we can work on improving it.
> >>>
> >>> On Thu, May 16, 2019 at 12:11 PM Carlos Rovira <
> carlosrov...@apache.org>
> >>> wrote:
> >>>
> >>>> Hi Andrew,
> >>>>
> >>>> what do you think about to create a page in Wikipedia for Apache
> >> Royale?
> >>>> Then we can link from the website.
> >>>>
> >>>> I think that's a task where you can help a lot and where your writing
> >> and
> >>>> editing skills will be most needed that any other skills.
> >>>>
> >>>> Let us know what you think! :)
> >>>>
> >>>> Thank you
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Carlos Rovira
> >>>> http://about.me/carlosrovira
> >>>>
> >>>>
> >>>
> >>> --
> >>> Andrew Wetmore
> >>>
> >>> http://cottage14.blogspot.com/
> >>>
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Docs Changes Proposal

2019-05-17 Thread Andrew Wetmore
I agree with @Piotr that context is key. If I am starting from the help
docs I do not want the window to suddenly be focusing on something else; I
would prefer a new window to appear with whatever I clicked on so I can go
back to the first window easily and continue my studies. Similarly, if my
context is the website, then I am thinking about the get-started stuff as
part of the website, and I am happy for the material I click on to take
over the current screen.

On Fri, May 17, 2019 at 5:23 AM Piotr Zarzycki 
wrote:

> Let's see whether Andrew have different thoughts. He is an expert in case
> of documentation ;) Adrian is working on 1 or 2 small pull requests more.
> ;)
>
> pt., 17 maj 2019 o 10:11 Carlos Rovira 
> napisał(a):
>
> > Ok Piotr,
> >
> > so I think we have all set as you said, and we just need to worry about
> the
> > content created to follow that guidelines
> >
> > :)
> >
> > El vie., 17 may. 2019 a las 10:07, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > In my opinion it depends where you are clicking on Get Started. If you
> > are
> > > clicking on Get Started on main page (main menu or footer) you should
> > stay
> > > in the same window. I think it should be true for whatever option in
> main
> > > menu you are clicking.
> > >
> > > However if you are in Docs already and click on "Apache Royale
> > > Documentation
> > > <https://apache.github.io/royale-docs/>" - it would can go to separate
> > > window where you can easy navigate.
> > >
> > > My 2 cents ;)
> > >
> > >
> > > pt., 17 maj 2019 o 09:59 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Hi Andrew,
> > > >
> > > > ok, so website navigation happens on the same window and docs in its
> > own
> > > > window. That's ok for me too.
> > > >
> > > > What to do with the case of pages like "Get Started"? The link is in
> > > > website, but goes to royale docs
> > > >
> > > > thanks
> > > >
> > > >
> > > >
> > > > El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<
> > cottag...@gmail.com
> > > >)
> > > > escribió:
> > > >
> > > > > I think "target=_blank" should be for links to location outside of
> > > Royale
> > > > > docs. To me, that includes the Royale website. I would want it to
> > open
> > > > in a
> > > > > new window rather than taking over the window I am using to read
> the
> > > > docs.
> > > > >
> > > > > On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <
> > carlosrov...@apache.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Adrian,
> > > > > >
> > > > > > I read the Get Started page. Good work! :)
> > > > > >
> > > > > > just added a link that I think was missed, change it if you think
> > it
> > > > > should
> > > > > > point to other page.
> > > > > >
> > > > > > I want to ask about the links strategy. I see some of them that
> > > refers
> > > > to
> > > > > > the same Royale-docs part has target blank while other not.
> > > > > > We talked about this when launched the website: In the website we
> > put
> > > > all
> > > > > > links to be loaded on the same page, while external links to the
> > site
> > > > > load
> > > > > > in a blank page. I think we should do the same for Royale-docs.
> We
> > > just
> > > > > > need to consider if website and Royale-docs must load in the same
> > > page.
> > > > > For
> > > > > > example in website, a link to NPM will load in another page while
> > > > mailing
> > > > > > list info will load in the current one.
> > > > > >
> > > > > > thanks!
> > > > > >
> > > > > >
> > > > > >
> > > > > > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> > > > > carlosrov...@apache.org
> > > > > > >)
> > > > > > escribió:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > I trie

Re: About having an Apache Royale page on Wikipedia

2019-05-16 Thread Andrew Wetmore
I believe there are a couple of live applications using Royale. Do we have
links to them I could reference on the Wikipedia page, or are they internal
company apps?

On Thu, May 16, 2019 at 3:28 PM Carlos Rovira 
wrote:

> Great Andrew! Thanks! :)
>
> El jue., 16 may. 2019 a las 20:23, Andrew Wetmore ()
> escribió:
>
> > I can do that! I am a Wikipedia editor, although not active enough to
> avoid
> > close scrutiny of what I write.
> >
> > The article will outline the origins, purpose, development, and
> particular
> > characteristics of Royale. Once I have the first version up and
> published,
> > we can work on improving it.
> >
> > On Thu, May 16, 2019 at 12:11 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Andrew,
> > >
> > > what do you think about to create a page in Wikipedia for Apache
> Royale?
> > > Then we can link from the website.
> > >
> > > I think that's a task where you can help a lot and where your writing
> and
> > > editing skills will be most needed that any other skills.
> > >
> > > Let us know what you think! :)
> > >
> > > Thank you
> > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale Docs Changes Proposal

2019-05-16 Thread Andrew Wetmore
I think "target=_blank" should be for links to location outside of Royale
docs. To me, that includes the Royale website. I would want it to open in a
new window rather than taking over the window I am using to read the docs.

On Thu, May 16, 2019 at 7:11 AM Carlos Rovira 
wrote:

> Hi Adrian,
>
> I read the Get Started page. Good work! :)
>
> just added a link that I think was missed, change it if you think it should
> point to other page.
>
> I want to ask about the links strategy. I see some of them that refers to
> the same Royale-docs part has target blank while other not.
> We talked about this when launched the website: In the website we put all
> links to be loaded on the same page, while external links to the site load
> in a blank page. I think we should do the same for Royale-docs. We just
> need to consider if website and Royale-docs must load in the same page. For
> example in website, a link to NPM will load in another page while mailing
> list info will load in the current one.
>
> thanks!
>
>
>
> El jue., 16 may. 2019 a las 11:07, Carlos Rovira ( >)
> escribió:
>
> > Hi
> >
> > I tried various plugin solutions for WP and no one seems to fit what we
> > need. So I changed the url to the docs page as suggested. Going to
> publish
> > the site.
> >
> > I see the styles in headers and other things are not matching the site
> > styles. I'll try to fix that soon.
> >
> > Thanks
> >
> >
> > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> carlosrov...@apache.org>)
> > escribió:
> >
> >> Hi, I'm looking into this now: How to make website render the content of
> >> a GitHub page.
> >> About Menu I'll change to "Get Started" as Piotr suggested
> >>
> >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> >> adrianszuszkiew...@gmail.com>) escribió:
> >>
> >>> My pull request
> >>>
> >>> #17: Move Getting Started to Docs
> >>> URL: https://github.com/apache/royale-docs/pull/17
> >>>
> >>> has just been merged. Now I would like to ask someone with WordPress
> >>> access
> >>> to change the link on header's "GET STARTED" button and footer's
> "Getting
> >>> Started"
> >>>
> >>> from: https://royale.apache.org/getting-started/
> >>> to: https://apache.github.io/royale-docs/Get%20Started.html
> >>>
> >>> Thanks,
> >>> Adrian
> >>>
> >>>
> >>>
> >>> --
> >>> Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >>>
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: About having an Apache Royale page on Wikipedia

2019-05-16 Thread Andrew Wetmore
I can do that! I am a Wikipedia editor, although not active enough to avoid
close scrutiny of what I write.

The article will outline the origins, purpose, development, and particular
characteristics of Royale. Once I have the first version up and published,
we can work on improving it.

On Thu, May 16, 2019 at 12:11 PM Carlos Rovira 
wrote:

> Hi Andrew,
>
> what do you think about to create a page in Wikipedia for Apache Royale?
> Then we can link from the website.
>
> I think that's a task where you can help a lot and where your writing and
> editing skills will be most needed that any other skills.
>
> Let us know what you think! :)
>
> Thank you
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale in a Week

2019-05-10 Thread Andrew Wetmore
That will be great enhancements for Tour de jewel, which is already pretty
special.

On Fri, May 10, 2019 at 2:44 PM Carlos Rovira 
wrote:

> Hi Andrew
>
> about TDJ, my plan is to add more text and explanation to each page in TDJ.
> As well add modules. For example, button play ground, will be a module, and
> there we'll have what we have now but with better separation and
> explanation and maybe a bit of code too... So this could complement the
> documentation too.
>
>
>
> El vie., 10 may. 2019 a las 19:23, Andrew Wetmore ()
> escribió:
>
> > I have several thoughts about the "what" that the tutorials would show
> how
> > to build. I also don't think it has to be a single thing. I get a lot out
> > of the code examples of Tour de Jewel without requiring them to be
> > interrelated in some mega-app.
> >
> > On Fri, May 10, 2019 at 12:27 PM Dany Dhondt  >
> > wrote:
> >
> > > Great you started this Andrew. I’ll try to follow along.
> > >
> > > I’ve just had time to do a quick glance on the wiki page.
> > >
> > > Did you decide ‘what’ will be build? I’d prefer NOT to build a todo
> list
> > > (everyone is doing that :)).
> > > Because from the moment you decide what to build, there you have your
> > > story.
> > >
> > > Great work
> > > Dany
> > >
> > >
> > > > Op 10 mei 2019, om 13:34 heeft Andrew Wetmore 
> > het
> > > volgende geschreven:
> > > >
> > > > Hi, all:
> > > >
> > > > There is a wiki page [1] that has the structure of the old "Flex in a
> > > Week"
> > > > video course [2], some notes about what I think we need to add for a
> > > > similar course for Royale, and my proposed structure for "Royale in a
> > > Week".
> > > >
> > > > Before I go further, it would be helpful if people could cast a quick
> > eye
> > > > over the notes and proposed structure and identify key elements that
> > the
> > > > material must cover and that I may have overlooked. You could share
> > your
> > > > thoughts in this thread, or just add them to the "Stuff to include in
> > > > Royale in a Week" section of the wiki page.
> > > >
> > > > Next chance I get, I will build out each day's curriculum for Royale
> > in a
> > > > Week a little further. Then I think I will identify the stuff I
> think I
> > > can
> > > > create and the sections for which I will need help.
> > > >
> > > > The eventual deliverable will be a series of videos with transcripts
> > and
> > > > downloadable code. Do all the assets get hosted on Github? I would
> > expect
> > > > that we would publish the videos to a YouTube channel, as well as
> > giving
> > > > access to them on our website.
> > > >
> > > > Thanks!
> > > >
> > > > a
> > > >
> > > > [1]
> > https://github.com/apache/royale-asjs/wiki/Royale-in-a-Week-project
> > > > [2]  https://www.adobe.com/devnet/flex/videotraining.html
> > > >
> > > >
> > > > On Thu, May 9, 2019 at 12:51 PM Andrew Wetmore 
> > > wrote:
> > > >
> > > >> I am going to lay out my proposed table of contents for Royale in a
> > Week
> > > >> on a wiki page and get some feedback about its order and what I am
> > > >> forgetting to include.
> > > >>
> > > >> On Tue, Apr 30, 2019 at 8:12 PM Alex Harui  >
> > > >> wrote:
> > > >>
> > > >>> Hi Andrew,
> > > >>>
> > > >>> Thanks for taking this on.
> > > >>>
> > > >>> We have repos for code and for docs (royale-docs) and dev@ for
> > > >>> communication.  And we have a wiki.  We should try to use these
> tools
> > > as
> > > >>> much as possible unless there is a significant productivity gain to
> > be
> > > >>> using some other way.  That's because by using these tools, even if
> > > they
> > > >>> make you 10% slower, they automatically generate notices in the
> right
> > > >>> places, and hopefully others will join in and make the whole thing
> > > faster.
> > > >>> When we use other tools it might make a few folks faste

Re: Royale in a Week

2019-05-10 Thread Andrew Wetmore
I have several thoughts about the "what" that the tutorials would show how
to build. I also don't think it has to be a single thing. I get a lot out
of the code examples of Tour de Jewel without requiring them to be
interrelated in some mega-app.

On Fri, May 10, 2019 at 12:27 PM Dany Dhondt 
wrote:

> Great you started this Andrew. I’ll try to follow along.
>
> I’ve just had time to do a quick glance on the wiki page.
>
> Did you decide ‘what’ will be build? I’d prefer NOT to build a todo list
> (everyone is doing that :)).
> Because from the moment you decide what to build, there you have your
> story.
>
> Great work
> Dany
>
>
> > Op 10 mei 2019, om 13:34 heeft Andrew Wetmore  het
> volgende geschreven:
> >
> > Hi, all:
> >
> > There is a wiki page [1] that has the structure of the old "Flex in a
> Week"
> > video course [2], some notes about what I think we need to add for a
> > similar course for Royale, and my proposed structure for "Royale in a
> Week".
> >
> > Before I go further, it would be helpful if people could cast a quick eye
> > over the notes and proposed structure and identify key elements that the
> > material must cover and that I may have overlooked. You could share your
> > thoughts in this thread, or just add them to the "Stuff to include in
> > Royale in a Week" section of the wiki page.
> >
> > Next chance I get, I will build out each day's curriculum for Royale in a
> > Week a little further. Then I think I will identify the stuff I think I
> can
> > create and the sections for which I will need help.
> >
> > The eventual deliverable will be a series of videos with transcripts and
> > downloadable code. Do all the assets get hosted on Github? I would expect
> > that we would publish the videos to a YouTube channel, as well as giving
> > access to them on our website.
> >
> > Thanks!
> >
> > a
> >
> > [1]  https://github.com/apache/royale-asjs/wiki/Royale-in-a-Week-project
> > [2]  https://www.adobe.com/devnet/flex/videotraining.html
> >
> >
> > On Thu, May 9, 2019 at 12:51 PM Andrew Wetmore 
> wrote:
> >
> >> I am going to lay out my proposed table of contents for Royale in a Week
> >> on a wiki page and get some feedback about its order and what I am
> >> forgetting to include.
> >>
> >> On Tue, Apr 30, 2019 at 8:12 PM Alex Harui 
> >> wrote:
> >>
> >>> Hi Andrew,
> >>>
> >>> Thanks for taking this on.
> >>>
> >>> We have repos for code and for docs (royale-docs) and dev@ for
> >>> communication.  And we have a wiki.  We should try to use these tools
> as
> >>> much as possible unless there is a significant productivity gain to be
> >>> using some other way.  That's because by using these tools, even if
> they
> >>> make you 10% slower, they automatically generate notices in the right
> >>> places, and hopefully others will join in and make the whole thing
> faster.
> >>> When we use other tools it might make a few folks faster, but it is
> harder
> >>> for others to follow along on dev@ and commits@.
> >>>
> >>> My 2 cents,
> >>> -Alex
> >>>
> >>> On 4/30/19, 12:41 PM, "Andrew Wetmore"  wrote:
> >>>
> >>>I would be happy to work on creating a Royale equivalent to "Flex
> in a
> >>>Week".
> >>>
> >>>My first step would be to review the old curriculum and see where it
> >>> needs
> >>>updating to eliminate Flex-specific stuff that Royale does not have
> >>> or need
> >>>to worry about. I would then want to assemble a new curriculum (what
> >>> we
> >>>teach each of the seven days) and get confirmation from the group
> >>> that the
> >>>list looks adequate.
> >>>
> >>>My question is, where should I post such a document for feedback and
> >>>comments? My immediate impulse  is to create a mind map or document
> in
> >>>Google Docs and share it, but I think I have seen people suggest
> that
> >>> is
> >>>not the correct method.
> >>>
> >>>a
> >>>
> >>>--
> >>>Andrew Wetmore
> >>>
> >>>
> >>>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C5e6f1266e7384aa2831c08d6cda3c6a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922500628304365sdata=b%2BhDtiykkxmq9c83dOP%2FF9RrucysABFyICNXaulhjqw%3Dreserved=0
> >>>
> >>>
> >>>
> >>
> >> --
> >> Andrew Wetmore
> >>
> >> http://cottage14.blogspot.com/
> >>
> >>
> >>
> >>
> >>
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Four flavors of documentation

2019-05-10 Thread Andrew Wetmore
I ran into this very clear article [1] about the different types of
documentation a project needs, and the point of each type, on the doc list
for Libre Office. Key takeaway:

"There is a secret that needs to be understood in order to write good
software documentation: there isn’t one thing called documentation, there
are four. They are: tutorials, how-to guides, explanation and technical
reference. They represent four different purposes or functions, and require
four different approaches to their creation."

There has been some conversation about crafting our help docs in terms of
stories. To me, that can work for tutorials and how-to guides; but it works
less well for explanations and not at all for tech reference material. And
we need all four flavors.

a



[1]  https://www.divio.com/blog/documentation/

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale in a Week

2019-05-10 Thread Andrew Wetmore
Hi, all:

There is a wiki page [1] that has the structure of the old "Flex in a Week"
video course [2], some notes about what I think we need to add for a
similar course for Royale, and my proposed structure for "Royale in a Week".

Before I go further, it would be helpful if people could cast a quick eye
over the notes and proposed structure and identify key elements that the
material must cover and that I may have overlooked. You could share your
thoughts in this thread, or just add them to the "Stuff to include in
Royale in a Week" section of the wiki page.

Next chance I get, I will build out each day's curriculum for Royale in a
Week a little further. Then I think I will identify the stuff I think I can
create and the sections for which I will need help.

The eventual deliverable will be a series of videos with transcripts and
downloadable code. Do all the assets get hosted on Github? I would expect
that we would publish the videos to a YouTube channel, as well as giving
access to them on our website.

Thanks!

a

[1]  https://github.com/apache/royale-asjs/wiki/Royale-in-a-Week-project
[2]  https://www.adobe.com/devnet/flex/videotraining.html


On Thu, May 9, 2019 at 12:51 PM Andrew Wetmore  wrote:

> I am going to lay out my proposed table of contents for Royale in a Week
> on a wiki page and get some feedback about its order and what I am
> forgetting to include.
>
> On Tue, Apr 30, 2019 at 8:12 PM Alex Harui 
> wrote:
>
>> Hi Andrew,
>>
>> Thanks for taking this on.
>>
>> We have repos for code and for docs (royale-docs) and dev@ for
>> communication.  And we have a wiki.  We should try to use these tools as
>> much as possible unless there is a significant productivity gain to be
>> using some other way.  That's because by using these tools, even if they
>> make you 10% slower, they automatically generate notices in the right
>> places, and hopefully others will join in and make the whole thing faster.
>> When we use other tools it might make a few folks faster, but it is harder
>> for others to follow along on dev@ and commits@.
>>
>> My 2 cents,
>> -Alex
>>
>> On 4/30/19, 12:41 PM, "Andrew Wetmore"  wrote:
>>
>> I would be happy to work on creating a Royale equivalent to "Flex in a
>> Week".
>>
>> My first step would be to review the old curriculum and see where it
>> needs
>> updating to eliminate Flex-specific stuff that Royale does not have
>> or need
>> to worry about. I would then want to assemble a new curriculum (what
>> we
>> teach each of the seven days) and get confirmation from the group
>> that the
>> list looks adequate.
>>
>> My question is, where should I post such a document for feedback and
>> comments? My immediate impulse  is to create a mind map or document in
>> Google Docs and share it, but I think I have seen people suggest that
>> is
>> not the correct method.
>>
>> a
>>
>> --
>> Andrew Wetmore
>>
>>
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C5e6f1266e7384aa2831c08d6cda3c6a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922500628304365sdata=b%2BhDtiykkxmq9c83dOP%2FF9RrucysABFyICNXaulhjqw%3Dreserved=0
>>
>>
>>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale in a Week

2019-05-09 Thread Andrew Wetmore
I am going to lay out my proposed table of contents for Royale in a Week on
a wiki page and get some feedback about its order and what I am forgetting
to include.

On Tue, Apr 30, 2019 at 8:12 PM Alex Harui  wrote:

> Hi Andrew,
>
> Thanks for taking this on.
>
> We have repos for code and for docs (royale-docs) and dev@ for
> communication.  And we have a wiki.  We should try to use these tools as
> much as possible unless there is a significant productivity gain to be
> using some other way.  That's because by using these tools, even if they
> make you 10% slower, they automatically generate notices in the right
> places, and hopefully others will join in and make the whole thing faster.
> When we use other tools it might make a few folks faster, but it is harder
> for others to follow along on dev@ and commits@.
>
> My 2 cents,
> -Alex
>
> On 4/30/19, 12:41 PM, "Andrew Wetmore"  wrote:
>
> I would be happy to work on creating a Royale equivalent to "Flex in a
> Week".
>
> My first step would be to review the old curriculum and see where it
> needs
> updating to eliminate Flex-specific stuff that Royale does not have or
> need
> to worry about. I would then want to assemble a new curriculum (what we
> teach each of the seven days) and get confirmation from the group that
> the
> list looks adequate.
>
> My question is, where should I post such a document for feedback and
> comments? My immediate impulse  is to create a mind map or document in
> Google Docs and share it, but I think I have seen people suggest that
> is
> not the correct method.
>
> a
>
> --
> Andrew Wetmore
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C5e6f1266e7384aa2831c08d6cda3c6a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922500628304365sdata=b%2BhDtiykkxmq9c83dOP%2FF9RrucysABFyICNXaulhjqw%3Dreserved=0
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Royale video tutorials

2019-05-05 Thread Andrew Wetmore
Happy to help with editing. I am stronger with commas than with code.

On Sun, May 5, 2019 at 7:12 AM Piotr Zarzycki 
wrote:

> Hi Team,
>
> FYI: About a week ago, thanks to Prominic’s support, me and my friend
> Adrian started working on a video tutorial about Royale Framework and
> Moonshine IDE. We have heard all the voices on the mailing list and social
> media and decided to help newcomers start their journey with
> Moonshine/Royale in the easiest way possible.
>
> We are hoping to present the framework in the best light possible and
> enrich our tutorial with detailed examples of Royale usage.
>
> To be able to achieve this goal we are going to improve existing
> documentation in the areas we find most important. Changes will be provided
> by Adrian through a pull requests and some emails on this list.
>
> We hope to get your support and lots of help on the mailing list. :)
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Royale in a Week

2019-04-30 Thread Andrew Wetmore
I would be happy to work on creating a Royale equivalent to "Flex in a
Week".

My first step would be to review the old curriculum and see where it needs
updating to eliminate Flex-specific stuff that Royale does not have or need
to worry about. I would then want to assemble a new curriculum (what we
teach each of the seven days) and get confirmation from the group that the
list looks adequate.

My question is, where should I post such a document for feedback and
comments? My immediate impulse  is to create a mind map or document in
Google Docs and share it, but I think I have seen people suggest that is
not the correct method.

a

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Let's bump Royale version to 1.0

2019-04-26 Thread Andrew Wetmore
gt; -
> > > > > https://clicktime.symantec.com/3SEvxFs2HbjNAgsLBEtNLr17Vc?u=http
> > > > > s%3A%2F%2Froyale.apache.org
> > > > > - ...?
> > > > >
> > > > > As a user, it's hard to get an overview of what is available...
> > > > > and
> > > > where.
> > > > > Maybe it's a good idea to consolidate the docs before releasing
> 1.0.
> > > > >
> > > > > Just my 2 cents,
> > > > > Olaf
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from:
> > > > > https://clicktime.symantec.com/3LM5ngUtumonkv3VTyrZRJ77Vc?u=http
> > > > > %3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F
> > > > >
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%
> > > 2F%2Fabout.me%2Fcarlosrovira
> > >
> >
> >
> > --
> > Angelo Lazzari
> > mobile: +34 683 137 087
> > mail: lazzari.ang...@gmail.com
> >
> >
> >
> > --
> > --
> > Verify the correspondence of the addressee; otherwise, notify that to
> > the sender and, conscious of the responsibility for the undue use,
> > destroy the message and its copies.
> >
> > --
> > --
> >
>
>
> --
> Carlos Rovira
>
> https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%2F%2Fabout.me%2Fcarlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: RoyaleUnit

2019-03-16 Thread Andrew Wetmore
Yes! This will need some attention in the help docs, too...

On Sat, Mar 16, 2019 at 6:33 AM Carlos Rovira 
wrote:

> Hi Josh,
>
> Awesome news! Thanks for doing this. Maybe could I suggest to put all this
> info in the GitHub wiki so we have all available in a more convenient site?
> I'll tweet about this since it deserves to be shared! :)
>
> Thanks!
>
> El vie., 15 mar. 2019 a las 20:02, Josh Tynjala ()
> escribió:
>
> > By the way, I should mention that it's possible to use RoyaleUnit in pure
> > ActionScript projects compiled with Royale too. Here's an example where
> the
> > tests that RoyaleUnit runs on itself are executed in Node.js:
> >
> >
> >
> https://github.com/apache/royale-asjs/blob/develop/frameworks/projects/RoyaleUnit/src/test/royale/NodeTests.as
> >
> > In pure ActionScript projects, you may need to add a few SWC files from
> > Royale to your compiler options. Here's the asconfig.json file for Visual
> > Studio Code that I used to configure my Node.js project to use
> RoyaleUnit.
> > It should be pretty similar for browser projects.
> >
> >
> >
> https://github.com/apache/royale-asjs/blob/develop/frameworks/projects/RoyaleUnit/src/test/royale/asconfig.json
> >
> > - Josh
> >
> > On 2019/03/15 17:43:29, Josh Tynjala  wrote:
> > > Hey everyone,
> > >
> > > You may have noticed that I committed a new RoyaleUnit library to
> > royale-asjs yesterday. It is a unit testing library, similar to (and
> > greatly inspired by) FlexUnit. It is an upgrade to the barebones
> "Testing"
> > library that was based on my work from a while back. I brought a number
> of
> > things more in line with FlexUnit's API.
> > >
> > > * RoyaleUnit runs in web browsers, Node.js, and in the Flash runtimes.
> > > * For basic tests, in addition to the existing [Test], [Before], and
> > [After] metadata that we already had, I also added [Ignore],
> [BeforeClass],
> > and [AfterClass].
> > > * I also added [Suite] and [RunWith] metadata to run suites of tests.
> > > * I added a CIListener, similar to FlexUnit's, that supports connecting
> > to the socket server that FlexUnit's Ant task creates. Currently,
> > CIListener only works in the Flash runtimes. In other environments, you
> can
> > use TraceListener() and the results will be printed to the console with
> > trace(). There's also a FailureListener that may be useful. For instance,
> > in Node.js or AIR, you might use it to quit with different exit codes.
> > >
> > > As part of this process, I also updated the existing tests that we run
> > when building the Core and Basic libraries. It basically involved
> updating
> > the [RunWith] metadata with a new class, and switching the app startup to
> > use RoyaleUnitCore instead of FlexUnitCore. As I mentioned above, we can
> > still use FlexUnit's Ant task for SWFs, and I confirmed that this is
> > working correctly in the Ant build scripts.
> > >
> > > I can probably get the CIListener working in Node.js too, since it
> > natively supports sockets. However, web browsers don't support raw TCP
> > sockets in JS. Browsers have WebSockets, which are similar, but not
> exactly
> > the same. WebSockets require a special handshake to initialize the
> > connection that requires the server to support it. With that in mind,
> > FlexUnit's Ant task does not support WebSockets. However, it may be
> > possible to fork/update it to add that handshake.
> > >
> > > I'm sorry if I broke anything for anyone that was using the existing
> > Testing library. However, it's pretty easy to upgrade to RoyaleUnit. If
> you
> > need some example code, take a look at the tests for the Core library:
> > >
> > >
> >
> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/Core/src/test/royale
> > >
> > > If you need any help upgrading to RoyaleUnit, please let me know, and
> > I'll be happy to help!
> > >
> > > - Josh
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Board report March 2019 - Review

2019-03-12 Thread Andrew Wetmore
Edits complete.

On Tue, Mar 12, 2019 at 2:50 PM Andrew Wetmore  wrote:

> I will edit it right now.
>
> On Tue, Mar 12, 2019 at 11:07 AM Piotr Zarzycki 
> wrote:
>
>> Ohh!! I will submit it tomorrow then! :)
>>
>> Thanks!
>>
>> On Tue, Mar 12, 2019, 2:58 PM Olaf Krueger  wrote:
>>
>> > Hi Piotr,
>> >
>> > >I'm going to send report 13 or 14 March.
>> >
>> > Please notice that AFAIK the deadline is Wed Mar 13th!
>> >
>> > Thanks,
>> > Olaf
>> >
>> >
>> >
>> > --
>> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
>> >
>>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Board report March 2019 - Review

2019-03-12 Thread Andrew Wetmore
I will edit it right now.

On Tue, Mar 12, 2019 at 11:07 AM Piotr Zarzycki 
wrote:

> Ohh!! I will submit it tomorrow then! :)
>
> Thanks!
>
> On Tue, Mar 12, 2019, 2:58 PM Olaf Krueger  wrote:
>
> > Hi Piotr,
> >
> > >I'm going to send report 13 or 14 March.
> >
> > Please notice that AFAIK the deadline is Wed Mar 13th!
> >
> > Thanks,
> > Olaf
> >
> >
> >
> > --
> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Apache Royale on Stackoverflow

2019-03-04 Thread Andrew Wetmore
"apacheroyale" is fine with me.

SO's tutorial suggests that open-ended discussion-type questions fare worse
on the site than specific, solution-focused questions. I wonder if it would
be considered spam to "recreate" some of the conversations on tricky
Flex-to-Royale issues that we have already talked through in this channel.
Feels a bit like reality-show tv to me... An alternative would be to post
some of the current, not-yet-resolved questions. We might even attract
interesting response from outside the existing Royale community.

On Mon, Mar 4, 2019 at 8:57 AM Piotr Zarzycki 
wrote:

> I'm opt for "apacheroyale" - I'm using it for almost all posts on
> Moonshine's IDE twitter and fb, so it could be somehow consistent. ;)
>
> pon., 4 mar 2019 o 13:23 Andrew Wetmore  napisał(a):
>
> > Carlos and I were pondering possible tags for such an adventure. Options
> > seem to include "apacheroyale", "apache-royale", or just plain "royale".
> It
> > is telling that none of these tags currently exist.
> >
> > I am happy to lob softball questions to get conversations started, maybe:
> >
> > - What's the best migration path away from Flash for an enterprise-level
> > Flex app?
> > - What are the options for IDEs for developing in JS? [I note that
> > "moonshine" is not a recognized tag on SO at the moment]
> > - How can I reuse my AS3 and MXML code if Flash is not an option?
> > Other leading questions?
> >
> > I am happy to be the naive question-asker, but of course getting juice
> into
> > these conversations (and maybe drawing conversation-browsers toward
> Royale)
> > depends on those who have already found Royale providing answers.
> >
> > a
> >
> >
> >
> > On Mon, Mar 4, 2019 at 6:13 AM Carlos Rovira 
> > wrote:
> >
> > > Hi,
> > >
> > > I as you used Stackoverflow just for consulting. Just create my account
> > > now, so I'm learning too.
> > >
> > > What does mean for Apache Royale? Nowadays, a way to measure tech
> impact
> > > and how others could choose to go with Royale is see how easy is to
> find
> > > answers to questions. So you know, we want to know how something is
> done
> > > and people instead to go to normal docs, he google it, and normally for
> > > development problems stack overflow use to have responses.
> > >
> > > So, how we could "start"? I think we'll need to enter some common
> > > questions and maybe respond ourselves ? I really don't know, but there
> > > should be some way to start and have a "apacheroyale" tag for all the
> > > question related to us.
> > >
> > > For example, I think Andrew could be a good active to starting this if
> he
> > > thing is interesting, both investigating the way to do it and starting
> > some
> > > questions so we can answer and easing the rest of us entering SO
> world..
> > >
> > >
> > >
> > >
> > >
> > > El lun., 4 mar. 2019 a las 10:42, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Same here with time for answering. By presence - what do you mean ?
> I'm
> > >> rather read-only user for Stackoverflow - How does presence of Royale
> > can
> > >> be printed there ?
> > >>
> > >> pon., 4 mar 2019 o 10:38 Harbs  napisał(a):
> > >>
> > >> > Good idea, but I don’t know that I personally will have time to
> answer
> > >> SO
> > >> > questions.
> > >> >
> > >> > Harbs
> > >> >
> > >> > > On Mar 4, 2019, at 11:26 AM, Carlos Rovira <
> carlosrov...@apache.org
> > >
> > >> > wrote:
> > >> > >
> > >> > > Hi,
> > >> > >
> > >> > > I think one of our pending subjects is to be present on
> > Stackoverflow.
> > >> > > Starting to have questions and answers there and increasing
> presence
> > >> over
> > >> > > time should be a key goal for us.
> > >> > > What do you think?
> > >> > >
> > >> > > Thanks
> > >> > >
> > >> > > --
> > >> > > Carlos Rovira
> > >> > > http://about.me/carlosrovira
> > >> >
> > >> >
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> <https://www.patreon.com/piotrzarzycki>*
> > >>
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Apache Royale on Stackoverflow

2019-03-04 Thread Andrew Wetmore
Carlos and I were pondering possible tags for such an adventure. Options
seem to include "apacheroyale", "apache-royale", or just plain "royale". It
is telling that none of these tags currently exist.

I am happy to lob softball questions to get conversations started, maybe:

- What's the best migration path away from Flash for an enterprise-level
Flex app?
- What are the options for IDEs for developing in JS? [I note that
"moonshine" is not a recognized tag on SO at the moment]
- How can I reuse my AS3 and MXML code if Flash is not an option?
Other leading questions?

I am happy to be the naive question-asker, but of course getting juice into
these conversations (and maybe drawing conversation-browsers toward Royale)
depends on those who have already found Royale providing answers.

a



On Mon, Mar 4, 2019 at 6:13 AM Carlos Rovira 
wrote:

> Hi,
>
> I as you used Stackoverflow just for consulting. Just create my account
> now, so I'm learning too.
>
> What does mean for Apache Royale? Nowadays, a way to measure tech impact
> and how others could choose to go with Royale is see how easy is to find
> answers to questions. So you know, we want to know how something is done
> and people instead to go to normal docs, he google it, and normally for
> development problems stack overflow use to have responses.
>
> So, how we could "start"? I think we'll need to enter some common
> questions and maybe respond ourselves ? I really don't know, but there
> should be some way to start and have a "apacheroyale" tag for all the
> question related to us.
>
> For example, I think Andrew could be a good active to starting this if he
> thing is interesting, both investigating the way to do it and starting some
> questions so we can answer and easing the rest of us entering SO world..
>
>
>
>
>
> El lun., 4 mar. 2019 a las 10:42, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Same here with time for answering. By presence - what do you mean ? I'm
>> rather read-only user for Stackoverflow - How does presence of Royale can
>> be printed there ?
>>
>> pon., 4 mar 2019 o 10:38 Harbs  napisał(a):
>>
>> > Good idea, but I don’t know that I personally will have time to answer
>> SO
>> > questions.
>> >
>> > Harbs
>> >
>> > > On Mar 4, 2019, at 11:26 AM, Carlos Rovira 
>> > wrote:
>> > >
>> > > Hi,
>> > >
>> > > I think one of our pending subjects is to be present on Stackoverflow.
>> > > Starting to have questions and answers there and increasing presence
>> over
>> > > time should be a key goal for us.
>> > > What do you think?
>> > >
>> > > Thanks
>> > >
>> > > --
>> > > Carlos Rovira
>> > > http://about.me/carlosrovira
>> >
>> >
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Formatter Classes

2019-01-17 Thread Andrew Wetmore
This simplification sounds good. Will you be annotating how to use the new
bead structures, maybe with some examples, for those of us who are lost
among the strands?

On Thu, Jan 17, 2019 at 12:26 PM Harbs  wrote:

> I have the occasion this week to deal with the formatter classes, and I’d
> like to make some changes. I’d like input from others on the subject.
>
> Taking SimpleDateFormatter as an example:
> 1. The Formatter assumes that its being attached to a Strand with an
> IDateChooserModel.
> 2. It requires a “propertyName to be set and concatenates that with
> “Changed” and adds an event listener to the model.
> 3. When the property is changed, it formats the result which must be a
> “selectedDate” and then dispatches an event.
> 4. The view bead must attach an event listener to the Formatter to get
> notification when the format changes.
> 5. It also invariably attaches an event listener to the model when the
> model changes.
> 6. When the model changes we have first an event picked up by the
> formatter and then the formatter dispatches a separate event which is
> picked up by the view. The view then explicitly gets the formatted date
> from the formatter.
>
> That’s a lot of indirection for no apparent reason. It also limits how a
> formatter can be used. A DateFormatter can only be used in conjunction with
> a IDateChooserModel and it can only format a “selectedDate”. I ran into
> issues when trying to figure out how to use the formatters with date ranges.
>
> I want to change it to the following:
>
> 1. Make the formatter classes very simple Beads.
> 2. It will make no assumptions on there being any other beads and will not
> attach any event listeners.
> 3. Likewise, it will not dispatch any events.
> 4. Date Formatter classes would have a format(date:Date):String method
> which would take any valid date and return the formatted string.
> 5. When a view needs to update a formatted date, it would simply get the
> format bead and call format(). This would allow the bead to be instantiated
> by any class and would greatly simplify the code.
>
> I’d make similar changes to the other formatter classes.
>
> Any objections to these changes?
>
> Harbs



-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: [royale-docs] branch master updated: Create routing.md

2019-01-16 Thread Andrew Wetmore
copying Alex's comment into the bug report, as this is all new stuff to me.

On Wed, Jan 16, 2019 at 3:06 PM Alex Harui  wrote:

> We don't have enough information to create a routing implementation that
> would work everywhere for everybody.  I'm not even sure such a thing could
> exist.  There would probably be different choices for "routes-as-paths" and
> "routes-as-queries" and probably others.  I think the ASDoc app utilizes
> the only reusable pieces which are how to get the route from the URL and
> how to set the route on the URL.  I would imagine the tutorial would
> explain that.
>
> -Alex
>
> On 1/16/19, 10:56 AM, "Carlos Rovira"  wrote:
>
> Very interesting, didn't know we have infrastructure already to do
> this.
> I thought we only have ASDoc app that does this, but no reusable API
> in a
> SWC to perform routing.
> Can someone point me to the code?
>
> Thanks
>
> El mié., 16 ene. 2019 a las 19:31,  escribió:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > andreww pushed a commit to branch master
> > in repository
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-docs.gitdata=02%7C01%7Caharui%40adobe.com%7Ce2c7b0fc91e14766870b08d67be459d0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636832618014927222sdata=l5ZQDfPLg4vV3eTBdWcbgvKLZLc4El0cBrl15%2FcQ6UE%3Dreserved=0
> >
> >
> > The following commit(s) were added to refs/heads/master by this push:
> >  new 9e66e81  Create routing.md
> > 9e66e81 is described below
> >
> > commit 9e66e8132b8229556feba2ada9c98f4bcb2c1e1c
> > Author: Andrew Wetmore 
> > AuthorDate: Wed Jan 16 14:31:39 2019 -0400
> >
> > Create routing.md
> >
> > Created a stub of this page so visitors do not encounter a
> > page-not-found error.
> > ---
> >  .../application-tutorial/routing.md| 27
> > ++
> >  1 file changed, 27 insertions(+)
> >
> > diff --git a/create-an-application/application-tutorial/routing.md
> > b/create-an-application/application-tutorial/routing.md
> > new file mode 100644
> > index 000..b4967a2
> > --- /dev/null
> > +++ b/create-an-application/application-tutorial/routing.md
> > @@ -0,0 +1,27 @@
> > +---
> > +# 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
> > +#
> > +#
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Flicenses%2FLICENSE-2.0data=02%7C01%7Caharui%40adobe.com%7Ce2c7b0fc91e14766870b08d67be459d0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636832618014927222sdata=cxl8LNuZuvKg78TmJ2WN3iE55r0iUc4K%2B6o3jWBCfg8%3Dreserved=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.
> > +
> > +layout: docpage
> > +title: Routing
> > +---
> > +
> > +# Routing
> > +
> > +Instructions and sample code will appear here soon to show how you
> can
> > map URL parameters to different initial values in the application,
> and vice
> > versa.
> > +
>     > +
> > +{:align="center"}
> > +[Previous
> > Page](create-an-application/application-tutorial/local-storage.html)
> >
> >
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Ce2c7b0fc91e14766870b08d67be459d0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636832618014927222sdata=%2FsDS5EAIh4pwtKZqxTMLbFOzDdR4l0c6KWmDY0XOI%2FI%3Dreserved=0
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Issues with the first-app tutorial

2019-01-16 Thread Andrew Wetmore
Thank you.

On Wed, Jan 16, 2019 at 1:12 PM Alex Harui  wrote:

> I put links to the source in the GH issue.
>
> The missing pages do not exist yet.  I'm hoping someone else will take a
> stab at writing them.
>
> Thanks,
> -Alex
>
> On 1/16/19, 2:37 AM, "Andrew Wetmore"  wrote:
>
> If someone will point me to where the pages are, I could make such
> small
> changes. In the second bug report I ask if the missing page exist yet,
> as I
> don't know want to duplicate efforts
>
> On Wed, Jan 16, 2019, 12:44 AM Alex Harui  wrote:
>
> > Hi Andrew,
> >
> > I see you filed some issues.  Is there some action you are looking
> for
> > others to take on?  Seems like you could just change the name of the
> > attribute in that one example.
> >
> > Sorry if I'm missing something.
> >
> > -Alex
> >
> > On 1/14/19, 4:14 PM, "Alex Harui"  wrote:
> >
> > Hi Andrew,
> >
> > Either here or as a GH issue.  GH might be better if you need to
> > attach files or images/screenshots.
> >
> > -Alex
> >
> > On 1/14/19, 3:33 PM, "Andrew Wetmore" 
> wrote:
> >
> > Hi, all:
> >
> > I have run into some issues and questions related the code
> and the
> > instructions for the tutorial to show users how to build
> their
> > first app
> > [1]. How do I get them resolved? Just report them here in
> this
> > conversation?
> >
> > Thanks.
> >
> > a
> >
> > [1]
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.github.io%2Froyale-docs%2Fcreate-an-application%2Fapplication-tutorial.htmldata=02%7C01%7Caharui%40adobe.com%7Cd2800a6c04a5469189e208d67b9ea680%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636832318653836406sdata=LSACNoYB19TqcJUSSfQyluE3oPuLUrdb6qLUlYeQ%2Bjw%3Dreserved=0
> >
> > --
> > Andrew Wetmore
> >
> >
>     >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Cd2800a6c04a5469189e208d67b9ea680%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636832318653836406sdata=ctxSR4ROH8ddqUZb%2BVMxph5okKNlxuzalCfOtnVHDps%3Dreserved=0
> >
> >
> >
> >
> >
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Issues with the first-app tutorial

2019-01-16 Thread Andrew Wetmore
If someone will point me to where the pages are, I could make such small
changes. In the second bug report I ask if the missing page exist yet, as I
don't know want to duplicate efforts

On Wed, Jan 16, 2019, 12:44 AM Alex Harui  Hi Andrew,
>
> I see you filed some issues.  Is there some action you are looking for
> others to take on?  Seems like you could just change the name of the
> attribute in that one example.
>
> Sorry if I'm missing something.
>
> -Alex
>
> On 1/14/19, 4:14 PM, "Alex Harui"  wrote:
>
> Hi Andrew,
>
> Either here or as a GH issue.  GH might be better if you need to
> attach files or images/screenshots.
>
> -Alex
>
> On 1/14/19, 3:33 PM, "Andrew Wetmore"  wrote:
>
> Hi, all:
>
> I have run into some issues and questions related the code and the
> instructions for the tutorial to show users how to build their
> first app
> [1]. How do I get them resolved? Just report them here in this
> conversation?
>
> Thanks.
>
> a
>
> [1]
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.github.io%2Froyale-docs%2Fcreate-an-application%2Fapplication-tutorial.htmldata=02%7C01%7Caharui%40adobe.com%7C9ec37cca74d94db7c3a908d67a7e70f7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636831080882817811sdata=zVEInPPjH9nKt34uk1hYViU6jp%2FS%2FaaJfons5fqZEOY%3Dreserved=0
>
> --
> Andrew Wetmore
>
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C9ec37cca74d94db7c3a908d67a7e70f7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636831080882817811sdata=NfpD2eYQ1PBA2m3Iwc6iuY61wrdCVCL6KZXqxdU%2FG80%3Dreserved=0
>
>
>
>
>


Issues with the first-app tutorial

2019-01-14 Thread Andrew Wetmore
Hi, all:

I have run into some issues and questions related the code and the
instructions for the tutorial to show users how to build their first app
[1]. How do I get them resolved? Just report them here in this conversation?

Thanks.

a

[1]
https://apache.github.io/royale-docs/create-an-application/application-tutorial.html

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: User docs entry for strands and beads

2019-01-03 Thread Andrew Wetmore
Well, cool! I will check it later today. Thank you for taking a look.

On Thu, Jan 3, 2019 at 5:41 AM Alex Harui  wrote:

> Actually, I found some time to look and it was quite broken, probably from
> when we merged platform files.  I think it is working now (after the CI
> server builds it).
>
> -Alex
>
> On 1/1/19, 8:16 PM, "Alex Harui"  wrote:
>
> Bummer.  I haven’t tested that filter in a long time.  It is supposed
> to filter the list of classes to only those with an @toplevel or @viewbead
> ASDoc tag.  Longer term, the checkboxes would be replaced by a better
> filtering dialog otherwise after we add too many checkboxes, the UI would
> become unwieldy.
>
> Volunteers are welcome to fix it.  Might be a good way to learn more
> about Royale.
>
> -Alex
>
> From: Andrew Wetmore 
> Date: Tuesday, January 1, 2019 at 7:22 AM
> To: "dev@royale.apache.org" , Alex Harui <
> aha...@adobe.com>
> Subject: Re: User docs entry for strands and beads
>
> Hi, gang, and Happy New Year.
>
> @Alex Harui<mailto:aha...@adobe.com> thank you for your thoughts and
> pointers. I have an immediate question related to the ASDoc material: you
> say "I added a few ASDoc tags like @toplevel and @viewbead to some of the
> ASDoc and there is a cheap checkbox filter for it." No matter where I am in
> the ASDoc project, if I check that checkbox I get a blank display with an
> unending "Loading..." message. What is supposed to happen?
>
> On Sat, Dec 29, 2018 at 12:34 PM Alex Harui 
> wrote:
> Hi,
>
> Specifically, the "delete removeBead" change would consist of:
>
> 1) making the strand's array public
> 2) removing removeBead from IStrand and UIBase and HTMLElementWrapper
> (and other places)
> 3) adding an org.apache.royale.utils.removeBead function.
>
> Because, you are correct that someone is going to want to remove a
> bead at some point, but we shouldn't weigh down every app with
> "just-in-case" code and the API surface should discourage "un-recommended"
> practices.  It should be an extremely rare occurrence to remove a bead.
>
> On a related note, I checked the other day and HelloWorld is now over
> 80K.  It was once 29K.  That's how much "just-in-case" code we might have
> added.  At some point we need to go back and look at what was in the 51K of
> code we added and make sure it really has to be there.  Refactoring many of
> our utils classes into single-purpose functions may help.  Your latest
> change to UIUtils won't affect HelloWorld but will affect anyone else who
> uses UIUtils.  We need to break up UIUtils into separate functions so that
> convenience functions don't add weight to apps that don't use those
> functions.  Volunteers to make those changes are welcome.  In Flex,
> HelloWorld was 133K, we are dangerously approaching that number and we
> should hopefully not have to be even close to it if we are handling PAYG
> correctly.
>
> My 2 cents,
> -Alex
>
> On 12/29/18, 1:33 AM, "Carlos Rovira"  carlosrov...@apache.org>> wrote:
>
> Hi Alex,
>
> very valuable info as always.
>
> +1 to make "getBeadByType" return latest bead added and to keep
> removeBead
> API as we have today.
>
> I found that problem and although I understand your point and
> reasons on
> what you explain, we must understand the reality that many few
> users will
> be such advanced to know exactly that we want them to use Royale
> in that
> concrete way, so some people will try to add beads of the same
> type, and I
> think that we as a framework should be as flexible as possible to
> allow
> this kind of things
>
>
>
> El sáb., 29 dic. 2018 a las 8:55, Alex Harui
> ()
> escribió:
>
> > Answers/Opinions inline
> >
> > On 12/28/18, 5:07 AM, "Andrew Wetmore"  <mailto:cottag...@gmail.com>> wrote:
> >
> > Hi, all:
> >
> > I am working on the user doc page for strands and beads [1].
> This is
> > intended for application developers using Royale; there is
> unfinished
> > material available for developers working on Royale itself
> in the wiki
> > [2],
> > [3].
> >
> > From the app developer point of view, I want to answer these
> questions:
> >
> > 1. There are three ways of adding beads to a component:
> bake

Re: User docs entry for strands and beads

2019-01-01 Thread Andrew Wetmore
Hi, gang, and Happy New Year.

@Alex Harui  thank you for your thoughts and pointers. I
have an immediate question related to the ASDoc material: you say "I added
a few ASDoc tags like @toplevel and @viewbead to some of the ASDoc and
there is a cheap checkbox filter for it." No matter where I am in the ASDoc
project, if I check that checkbox I get a blank display with an unending
"Loading..." message. What is supposed to happen?

On Sat, Dec 29, 2018 at 12:34 PM Alex Harui 
wrote:

> Hi,
>
> Specifically, the "delete removeBead" change would consist of:
>
> 1) making the strand's array public
> 2) removing removeBead from IStrand and UIBase and HTMLElementWrapper (and
> other places)
> 3) adding an org.apache.royale.utils.removeBead function.
>
> Because, you are correct that someone is going to want to remove a bead at
> some point, but we shouldn't weigh down every app with "just-in-case" code
> and the API surface should discourage "un-recommended" practices.  It
> should be an extremely rare occurrence to remove a bead.
>
> On a related note, I checked the other day and HelloWorld is now over
> 80K.  It was once 29K.  That's how much "just-in-case" code we might have
> added.  At some point we need to go back and look at what was in the 51K of
> code we added and make sure it really has to be there.  Refactoring many of
> our utils classes into single-purpose functions may help.  Your latest
> change to UIUtils won't affect HelloWorld but will affect anyone else who
> uses UIUtils.  We need to break up UIUtils into separate functions so that
> convenience functions don't add weight to apps that don't use those
> functions.  Volunteers to make those changes are welcome.  In Flex,
> HelloWorld was 133K, we are dangerously approaching that number and we
> should hopefully not have to be even close to it if we are handling PAYG
> correctly.
>
> My 2 cents,
> -Alex
>
> On 12/29/18, 1:33 AM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> very valuable info as always.
>
> +1 to make "getBeadByType" return latest bead added and to keep
> removeBead
> API as we have today.
>
> I found that problem and although I understand your point and reasons
> on
> what you explain, we must understand the reality that many few users
> will
> be such advanced to know exactly that we want them to use Royale in
> that
> concrete way, so some people will try to add beads of the same type,
> and I
> think that we as a framework should be as flexible as possible to allow
> this kind of things
>
>
>
> El sáb., 29 dic. 2018 a las 8:55, Alex Harui ( >)
> escribió:
>
> > Answers/Opinions inline
> >
> > On 12/28/18, 5:07 AM, "Andrew Wetmore"  wrote:
> >
> > Hi, all:
> >
> > I am working on the user doc page for strands and beads [1].
> This is
> > intended for application developers using Royale; there is
> unfinished
> > material available for developers working on Royale itself in
> the wiki
> > [2],
> > [3].
> >
> > From the app developer point of view, I want to answer these
> questions:
> >
> > 1. There are three ways of adding beads to a component: baked in
> using
> > , through CSS, and dynamically using addBead(). Which
> method
> > is
> > best to use for what purposes?
> >
> > CSS sets up loosely-coupled defaults.  Almost all (probably all)
> Royale
> > components that are strands pick up default beads from CSS.  CSS
> allows
> > setting default beads for one or more instances of a component in a
> single
> > CSS Selector, just like CSS lets you set values on one or more
> > HTMLElements.  But if our SWCs specify a certain bead as a default,
> and the
> > app dev's CSS specifies a different one, it should be possible for
> certain
> > CSS tools to optimize away the original default bead so it isn't
> linked
> > into the output.
> >
> >  is the MXML way of calling addBead().  It allows the
> developer
> > to override the defaults bead from CSS for a single instance.  But
> now that
> > bead is not loosely coupled, so if someone later subclasses the
> class that
> > used js:beads or addBead, and specify a different bead, both the
> original
> > and the new bead will be in the output.  It isn't that much
> different from
> > specifying the "style" property on an HTMLElement in HTML.  Js:Beads
> 

User docs entry for strands and beads

2018-12-28 Thread Andrew Wetmore
Hi, all:

I am working on the user doc page for strands and beads [1]. This is
intended for application developers using Royale; there is unfinished
material available for developers working on Royale itself in the wiki [2],
[3].

>From the app developer point of view, I want to answer these questions:

1. There are three ways of adding beads to a component: baked in using
, through CSS, and dynamically using addBead(). Which method is
best to use for what purposes?

1a. I can see from the wiki clear examples for two methods of adding beads.
Can someone point to an example using CSS to add a bead to a component?

2. Is the order of beads on a strand significant?

3. How much should I worry about bead cleanup when a bead is no longer
actively used? I presume this would relate to dynamically-added beads, not
the  or CSS ones.

4. Where do I find the existing beads? Is there a curated list for each
release of Royale? How do I know which ones would be useful for a text
entry field, a list, a button?

Thanks!

a


[1]
https://apache.github.io/royale-docs/Welcome/Features/Strands%20and%20Beads.html
[2]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=71013028
[3] https://cwiki.apache.org/confluence/display/FLEX/Creating+Components

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-11 Thread Andrew Wetmore
fa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139sdata=2WfBpM%2Bo%2F26GErQ5NkHmzuy0ujybJbQF6ZP%2FyprpSuI%3Dreserved=0
> >> > > >> >
> >> > > >> >
> >> > > >> >
> >> > > >> > --
> >> > > >> >
> >> > > >> > Piotr Zarzycki
> >> > > >> >
> >> > > >> > Patreon: *
> >> > > >> >
> >> > > >>
> >> >
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139sdata=dOlqV6810%2FclGuVLkG7iANb1pP81G0w5CasABoLyFhQ%3Dreserved=0
> >> > > >> > <
> >> > > >> >
> >> > > >>
> >> >
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139sdata=dOlqV6810%2FclGuVLkG7iANb1pP81G0w5CasABoLyFhQ%3Dreserved=0
> >> > > >> > >*
> >> > > >> >
> >> > > >> >
> >> > > >> >
> >> > > >>
> >> > > >> --
> >> > > >>
> >> > > >> Piotr Zarzycki
> >> > > >>
> >> > > >> Patreon: *
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139sdata=dOlqV6810%2FclGuVLkG7iANb1pP81G0w5CasABoLyFhQ%3Dreserved=0
> >> > > >> <
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316026149sdata=z%2FvNW16MxrL9MYrmArIJ5EwGGkZM%2FgHaepflH2RoM0Y%3Dreserved=0
> >> >*
> >> > > >>
> >> > > >
> >> > > >
> >> > > > --
> >> > > > Carlos Rovira
> >> > > >
> >>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316026149sdata=Pwodec9x0zHukZlQQs%2BpY1hnqCvO51Suw9V3IQHPEaE%3Dreserved=0
> >> > > >
> >> > > >
> >> > >
> >> > > --
> >> > > Carlos Rovira
> >> > >
> >>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316026149sdata=Pwodec9x0zHukZlQQs%2BpY1hnqCvO51Suw9V3IQHPEaE%3Dreserved=0
> >> > >
> >> >
> >>
> >>
> >> --
> >> Carlos Rovira
> >>
> >>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316026149sdata=Pwodec9x0zHukZlQQs%2BpY1hnqCvO51Suw9V3IQHPEaE%3Dreserved=0
> >>
> >>
> >>
> >
> > --
> >
> > <http://www.codeoscopic.com>
> >
> > Carlos Rovira
> >
> > Presidente Ejecutivo
> >
> > M: +34 607 22 60 05
> >
> > http://www.codeoscopic.com
> >
> >
> > Conócenos en 1 minuto! <https://avant2.es/#video>
> >
> >
> > AVISO LEGAL: La información contenida en este correo electrónico, y en su
> > caso en los documentos adjuntos, es información privilegiada para uso
> > exclusivo de la persona y/o personas a las que va dirigido. No está
> > permitido el acceso a este mensaje a cualquier otra persona distinta a
> los
> > indicados. Si Usted no es uno de los destinatarios, cualquier
> duplicación,
> > reproducción, distribución, así como cualquier uso de la información
> > contenida en él o cualquiera otra acción u omisión tomada en relación con
> > el mismo, está prohibida y puede ser ilegal. En dicho caso, por favor,
> > notifíquelo al remitente y proceda a la eliminación de este correo
> > electrónico, así como de sus adjuntos si los hubiere. En cumplimiento de
> la
> > legislación española vigente en materia de protección de datos de
> carácter
> > personal y del RGPD 679/2016 le informamos que sus datos están siendo
> > objeto de tratamiento por parte de CODEOSCOPIC S.A. con CIFA85677342, con
> > la finalidad del mantenimiento y gestión de relaciones comerciales y
> > administrativas. La base jurídica del tratamiento es el interés legítimo
> de
> > la empresa. No se prevén cesiones de sus datos, salvo que exista una
> > obligación legal. Para ejercitar sus derechos puede dirigirse a
> CODEOSCOPIC
> > S.A., domiciliada enPaseo de la Habana, 9-11, 28036 de Madrid (MADRID), o
> > bien por email a...@codeoscopic.com, con el fin de ejercer sus derechos
> > de acceso, rectificación, supresión (derecho al olvido), limitación de
> > tratamiento, portabilidad de los datos, oposición, y a no ser objeto de
> > decisiones automatizadas, indicando como Asunto: “Derechos Ley Protección
> > de Datos”, y adjuntando fotocopia de su DNI. Delegado de protección de
> > datos:d...@codeoscopic.com
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-10 Thread Andrew Wetmore
Hi!

I have made some small edits to the announcement, and I think it is good to
go!

On Mon, Dec 10, 2018 at 11:10 AM Carlos Rovira 
wrote:

> Hi,
>
> since there's many changes in the website. I put here the links to review
> before publish in r.a.o:
>
> * Release Post
>
> @Andrew Wetmore  please review I added 2 paragraphs
> in addition to standard release post to explain better what people can find
> in 0.9.4
>
> https://royale.codeoscopic.com/apache-royale-v0-9-4-released/
>
> * Links that are the same. Just changed links from 0.9.2 to 0.9.4
>
> https://royale.codeoscopic.com/download/
> https://royale.codeoscopic.com/source-code/
>
> * Team Page (added Pushmina and Greg, no photos or more info for now)
>
> https://royale.codeoscopic.com/team/
>
> Let me know if you see all ok or we need to add something more
>
> Thanks
>
>
> El lun., 10 dic. 2018 a las 15:44, Carlos Rovira ()
> escribió:
>
>> Hi,
>>
>> I'm updating the site, and I'm finding this tow links are not working:
>>
>> royale-asjs artifacts
>> <https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/>
>> royale-asjs-jsonly artifacts
>> <https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/>
>>
>> (those are located at the end of download page, in pre-site the link is:
>> https://royale.codeoscopic.com/download/ )
>>
>> I'll continue updating things, if someone can let me know about this
>> before publish that will be great
>>
>> thanks!
>>
>>
>>
>> El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira ()
>> escribió:
>>
>>> Thanks Piotr,
>>>
>>> I'll do this on Monday evening
>>>
>>> thanks
>>>
>>> Carlos
>>>
>>>
>>> El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
>>> piotrzarzyck...@gmail.com>) escribió:
>>>
>>>> Hi Guys,
>>>>
>>>> I just published release [1]. Can someone update information on website
>>>> ?
>>>>
>>>> [1]
>>>> https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.4
>>>>
>>>> Thanks,
>>>> Piotr
>>>>
>>>> śr., 5 gru 2018 o 07:53 Alex Harui 
>>>> napisał(a):
>>>>
>>>> > Hey, how about that!?  The release script failed to do the svn commit
>>>> but
>>>> > Ant didn't fail.  I guess it was because my svn repos were funky. I
>>>> never
>>>> > thought to check dist or look for commit messages.I re-ran that
>>>> part
>>>> > and it looks like it worked this time.
>>>> >
>>>> > -Alex
>>>> >
>>>> > On 12/4/18, 3:03 AM, "Piotr Zarzycki" 
>>>> wrote:
>>>> >
>>>> > Hi Justin,
>>>> >
>>>> > Thanks for the link!
>>>> >
>>>> > Piotr
>>>> >
>>>> > wt., 4 gru 2018 o 11:45 Justin Mclean 
>>>> > napisał(a):
>>>> >
>>>> > > Hi,
>>>> > >
>>>> > > No it’s not been published yet or distributed to the mirrors.
>>>> [1]
>>>> > >
>>>> > > Thanks,
>>>> > > Justin
>>>> > >
>>>> > > 1.
>>>> >
>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2Fdata=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3Dreserved=0
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> > Piotr Zarzycki
>>>> >
>>>> > Patreon: *
>>>> >
>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3Dreserved=0
>>>> > <
>>>> >
>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3Dreserved=0
>>>> > >*
>>>> >
>>>> >
>>>> >
>>>>
>>>> --
>>>>
>>>> Piotr Zarzycki
>>>>
>>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>>> <https://www.patreon.com/piotrzarzycki>*
>>>>
>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: New Documentation PR

2018-11-09 Thread Andrew Wetmore
I will take a look.

On Fri, Nov 9, 2018 at 2:12 PM Alex Harui  wrote:

> @Andrew Wetmore (or any other committer),
> 
> We've received a Pull Request for the documentation.
> https://github.com/apache/royale-docs/pull/12
>
> Can you review?
>
> Thanks,
> -Alex
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: NextGenAS tutorials on Royale website

2018-10-02 Thread Andrew Wetmore
I wish there were a paragraph that explains WHY one would want to use
Node.js at all. It is not self-evident.

On Tue, Oct 2, 2018 at 7:41 PM Carlos Rovira 
wrote:

> Hi ,
>
> just introduced and edited NodeJS tutorial in pre site:
>
>
> https://royale.codeoscopic.com/hello-node-how-to-transpile-actionscript-for-node-js/
>
> If someone could check if all is ok and even try the example, it would be
> great I run out of time and could try my self.
>
> If all is ok, I can publish in r.a.o tomorrow morning
>
> thanks
>
> Carlos
>
>
>
> El mar., 2 oct. 2018 a las 19:17, Andrew Wetmore ()
> escribió:
>
> > This will be a great addition. Thanks, Josh!
> >
> > On Tue, Oct 2, 2018 at 2:06 PM Carlos Rovira 
> > wrote:
> >
> > > Hi,
> > >
> > > I contacted today Josh Tynjala, looking for the NodeJS tutorial he did
> > that
> > > I could not find.
> > > It seems he refactored his site and change domain and the tutorials
> > aren't
> > > not available
> > > I asked Josh to republish those tutorials on royale website with the
> > > revision to update from FlexJS to Royale.
> > >
> > > He did the permission, and as well for anything he's part of this
> project
> > > and PMC, so don't know if needs to expressly
> > > notifiy here about the donation of this material
> > >
> > > In the other hand I want to expose here if we are all ok to republish
> > this
> > > tutorials in our website.
> > >
> > > I'll take the opportunity to say thanks to Josh for his generous
> > donation!
> > > Thanks Josh! :)
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: NextGenAS tutorials on Royale website

2018-10-02 Thread Andrew Wetmore
This will be a great addition. Thanks, Josh!

On Tue, Oct 2, 2018 at 2:06 PM Carlos Rovira 
wrote:

> Hi,
>
> I contacted today Josh Tynjala, looking for the NodeJS tutorial he did that
> I could not find.
> It seems he refactored his site and change domain and the tutorials aren't
> not available
> I asked Josh to republish those tutorials on royale website with the
> revision to update from FlexJS to Royale.
>
> He did the permission, and as well for anything he's part of this project
> and PMC, so don't know if needs to expressly
> notifiy here about the donation of this material
>
> In the other hand I want to expose here if we are all ok to republish this
> tutorials in our website.
>
> I'll take the opportunity to say thanks to Josh for his generous donation!
> Thanks Josh! :)
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: New Blog Post to review - Loading Github external data through HTTPService

2018-09-23 Thread Andrew Wetmore
Hi: I will look at it in about an hour, when I get to a stopping place in
my current task.

I need this functionality in most of my apps, so I am really looking
forward to this example.

On Sun, Sep 23, 2018 at 3:22 PM Carlos Rovira 
wrote:

> Hi Andrew,
> just let you know that I finished the example completely and solved the
> IE11 problem. so it's ready for complete review ;)
>
> thanks
>
> El dom., 23 sept. 2018 a las 18:15, Carlos Rovira (<
> carlosrov...@apache.org>) escribió:
>
>> Hi Andrew,
>>
>> I have a new blog post for you to review. I still need to check a problem
>> in IE11, but I think the post is ready for review and modification.
>> Hope you could take the time and check it
>>
>> Thanks!
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: States problem [was: Re: Royale Transitions, Effects, States infrastructure]

2018-09-14 Thread Andrew Wetmore
Could one deal with this issue for now by creating a global "currentState"
property and referencing it on state change?

On Fri, Sep 14, 2018 at 7:29 PM Carlos Rovira 
wrote:

> Hi Alex,
>
> the issue comes from beads modifying strand className. This can be seen
> mixing states with jewel layouts. Jewel Layouts add or removes class names
> in the strand at runtime.
> Since, as you describe in the example, those changes are not part of some
> state (i.e: className.normal or className.someState, for example), the
> current class name is not stored anywhere, so when you change the state and
> comes back, Royale is not capable of recreate the right strand className
>
> You can see the issue in action if you compile the blog example about
> states [1]
>
>
> https://github.com/apache/royale-asjs/tree/develop/examples/blog/BE0008_Using_View_States_to_show_or_hide_content
>
> Compile the example and run (online version works ok due to it was
> published when the work was in unfinished stated)
>
> Then push the button to change state from login form to result screen and
> push the button back to go to the other state. You'll see the layout is not
> equal. If check the html in the broswer, you'll find class names are lost
> between state changes.
>
> What do you think would be a good solution to this problem?
>
> thanks
>
> Carlos
>
>
>
>
>
> El vie., 14 sept. 2018 a las 18:23, Alex Harui ( >)
> escribió:
>
> > Regarding class selectors and states, I guess I don't understand the
> > issue.  The code behind Royale (and Flex) states should be capturing
> values
> > of properties changed by the state before they get changed, then
> restoring
> > those properties.  IOW, if you were to have
> >
> > 
> >   
> >   
> > 
> >  > emphasis.important="emphasized" />
> >
> > Then the  myButton.emphasis="primary" at startup and when the state
> > changes to "important" the States impl should read myButton.emphasis and
> > store that value away before setting myButton.emphasis="emphasized".
> Then,
> > when the state changes back to "normal", the States impl should set
> > myButton.emphasis="primary" again.
> >
> > In the implementation for the emphasis property, if it involves changing
> > classLists, the implementation must do so in a way that handles having
> the
> > emphasis property changes at runtime.  The States impl isn't really doing
> > anything application developer code might do, so the implementation must
> > support properties being set and re-set.
> >
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: New blog example post to review

2018-08-01 Thread Andrew Wetmore
I have finished my edits and republished the blog entry.

Nice example!

a

On Wed, Aug 1, 2018 at 12:06 PM, Carlos Rovira 
wrote:

> Ok, no problem, then I'll copy the code to the real project
>
> thanks
>
> 2018-08-01 17:02 GMT+02:00 Andrew Wetmore :
>
> > @Carlos, I am editing the blog entry now. Some of my edits affect the
> text
> > within the code sample. I will let you know when I am done so you can
> > review my changes and port the relevant ones to the sample code.
> >
> > a
> >
> > On Wed, Aug 1, 2018 at 10:40 AM, Carlos Rovira 
> > wrote:
> >
> > > Finaly I added a link to the post to see the example in a separate
> > window.
> > > We'll be adding this link in all blog examples so folks can see the
> > > examples running alone :)
> > >
> > > https://royale.codeoscopic.com/blog-examples/BE0010_
> > > Customization_through_the_Royale_API/index.html
> > >
> > > 2018-08-01 15:34 GMT+02:00 Carlos Rovira :
> > >
> > > > Ok, just uploaded a new version with screen sizes depending on
> > browser's
> > > > with.
> > > > But since example is embed in html page, the size in that page will
> be
> > > > always as phone size, only running the inline html in a separate
> > > browser's
> > > > window will see the size change
> > > >
> > > > 2018-08-01 15:07 GMT+02:00 Carlos Rovira :
> > > >
> > > >> Hi Paul,
> > > >>
> > > >> that's right. Is what I see in most browsers I tested.
> > > >> But some minutes ago I updated to get a bit less width to fit on
> > Mobile.
> > > >> I think I'll put a media query to fit mobile and get a wider size on
> > > >> tablet and desktop...
> > > >>
> > > >> thanks!
> > > >>
> > > >>
> > > >>
> > > >> 2018-08-01 14:38 GMT+02:00 Paul Hastings :
> > > >>
> > > >>> On 8/1/2018 6:19 PM, Carlos Rovira wrote:
> > > >>>
> > > >>>> Hi Paul,
> > > >>>> to send images you can upload to some image service and post a
> link
> > > >>>>
> > > >>>
> > > >>> been so long i'd forgotten. in any case, this is what i'm seeing in
> > > IE11
> > > >>> on windows 7.
> > > >>>
> > > >>> https://www.dropbox.com/s/9gef2qznp3pce2a/ieRoyaleExample.jpg?dl=0
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Carlos Rovira
> > > >> http://about.me/carlosrovira
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: New blog example post to review

2018-08-01 Thread Andrew Wetmore
@Carlos, I am editing the blog entry now. Some of my edits affect the text
within the code sample. I will let you know when I am done so you can
review my changes and port the relevant ones to the sample code.

a

On Wed, Aug 1, 2018 at 10:40 AM, Carlos Rovira 
wrote:

> Finaly I added a link to the post to see the example in a separate window.
> We'll be adding this link in all blog examples so folks can see the
> examples running alone :)
>
> https://royale.codeoscopic.com/blog-examples/BE0010_
> Customization_through_the_Royale_API/index.html
>
> 2018-08-01 15:34 GMT+02:00 Carlos Rovira :
>
> > Ok, just uploaded a new version with screen sizes depending on browser's
> > with.
> > But since example is embed in html page, the size in that page will be
> > always as phone size, only running the inline html in a separate
> browser's
> > window will see the size change
> >
> > 2018-08-01 15:07 GMT+02:00 Carlos Rovira :
> >
> >> Hi Paul,
> >>
> >> that's right. Is what I see in most browsers I tested.
> >> But some minutes ago I updated to get a bit less width to fit on Mobile.
> >> I think I'll put a media query to fit mobile and get a wider size on
> >> tablet and desktop...
> >>
> >> thanks!
> >>
> >>
> >>
> >> 2018-08-01 14:38 GMT+02:00 Paul Hastings :
> >>
> >>> On 8/1/2018 6:19 PM, Carlos Rovira wrote:
> >>>
> >>>> Hi Paul,
> >>>> to send images you can upload to some image service and post a link
> >>>>
> >>>
> >>> been so long i'd forgotten. in any case, this is what i'm seeing in
> IE11
> >>> on windows 7.
> >>>
> >>> https://www.dropbox.com/s/9gef2qznp3pce2a/ieRoyaleExample.jpg?dl=0
> >>>
> >>
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: New blog example post to review

2018-08-01 Thread Andrew Wetmore
I am busy for a couple of hours, but will check it as soon as I can.

On Wed, Aug 1, 2018 at 6:55 AM, Carlos Rovira 
wrote:

> Hi Angelo, can you share some screenshot or something to see what are you
> seeing?
> thanks!
>
> 2018-08-01 11:29 GMT+02:00 Angelo Lazzari :
>
> > No, great post!
> >
> > I checked it out on my so.. but the example is not fitting correctly the
> > browser page...
> >
> > El mié., 1 ago. 2018 10:49, Carlos Rovira 
> > escribió:
> >
> > > Hi Andrew,
> > >
> > > hope you can check the following example post and review it:
> > >
> > > https://royale.codeoscopic.com/customization-through-the-royale-api/
> > >
> > > I'm introducing here animated gifs instead of static screen capture.
> This
> > > can be seen in the home, and will be used to post on social networks to
> > > better engage :)
> > >
> > > Let me know when we can publish it! :)
> > >
> > > Thanks
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Bead Docs etc.

2018-07-19 Thread Andrew Wetmore
Starting a page in the docs project and putting together material would be
great. Then we can link it into the published docs when it is ready. I am
not sure who grants permissions/access for that.

a

On Thu, Jul 19, 2018 at 8:14 AM, Harbs  wrote:

> I just started some folks (my daughter and some friends) on some Royale
> work. They’re still getting into things. Hopefully as they get more into
> things, they will be able to contribute.
>
> One of the big things they are struggling with is discovering what
> components there are and what bead can work with which components. If I was
> not here to help them, it would be almost impossible to get going. One of
> them expressed interest in helping writing documentation for this as they
> are learning.
>
> What’s the best way for her to do that? It doesn’t really fit into the
> wiki. I’m not sure how to give her access to the docs.
>
> I think ideally, this should be something that the code self-documents.
>
> Thoughts?
>
> Harbs




-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: New blog post to review "Using an Item Renderer with a List"

2018-07-13 Thread Andrew Wetmore
I have made some edits and updated this very useful blog entry.

On Fri, Jul 13, 2018 at 9:27 AM, Carlos Rovira 
wrote:

> Hi Andrew,
>
> here's another blog post just finished, hope you can take a look :)
>
> https://royale.codeoscopic.com/using-an-item-renderer-with-a-list/
>
> Thanks!
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: No Touch support?

2018-07-04 Thread Andrew Wetmore
@harbs could that become a blog entry?

On Wed, Jul 4, 2018, 2:19 PM Harbs,  wrote:

> Possibly.
>
> The way Hammer.js works is that you attach it to an element and create an
> instance of it or a controller. The specific touch events need to be
> specified.
>
> > On Jul 4, 2018, at 7:34 PM, Alex Harui  wrote:
> >
> > Harbs,
> >
> > Can we wrap Hammer.js into more easily reusable TouchControllers in
> Royale?
> >
> > IMO, it doesn't matter if it is a can of worms.  Royale hopefully makes
> it easy to replace TouchControllers.  So you can write one that mostly
> works and if someone offers a better one at some point, you can switch to
> that.  We won't bake one into the components and make the user wait for a
> next release to get improvements.
> >
> > My 2 cents,
> > -Alex
> >
> > On 7/4/18, 9:26 AM, "Harbs"  wrote:
> >
> >Hi Carlos,
> >
> >Touch support is a can of worms.
> >
> >Basic touch support comes for free from Mouse Events. Anything more
> than that, gets very complex very quickly.
> >
> >I use Hammer.js in my own app to handle touch, and it works very well.
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhammerjs.github.io%2F=02%7C01%7Caharui%40adobe.com%7C69560100ba4747a4e52808d5e1cae3c3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636663183877387695=8By2PeXtYHtWAy9%2BwBFwvW3CdtAEx%2Fly80MJCO8oqtM%3D=0
> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhammerjs.github.io%2F=02%7C01%7Caharui%40adobe.com%7C69560100ba4747a4e52808d5e1cae3c3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636663183877387695=8By2PeXtYHtWAy9%2BwBFwvW3CdtAEx%2Fly80MJCO8oqtM%3D=0
> >
> >
> >Harbs
> >
> >> On Jul 4, 2018, at 4:47 PM, Carlos Rovira 
> wrote:
> >>
> >> Hi,
> >>
> >> I'm looking how to provide touch support for Drawer so users can slide
> out.
> >> Is a default behavior in this kind of components.
> >>
> >> I'm seeing there's no TouchEvent or something similar. I think this is
> an
> >> important flaw, since not having this is like to say we are not prepared
> >> for mobile and in the end we lost users.
> >>
> >>
> >>
> >> --
> >> Carlos Rovira
> >>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C69560100ba4747a4e52808d5e1cae3c3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636663183877387695=7j8FPbQ59eU0hMPOLfelshVI6DDqVCJtLrxGWpK4MVQ%3D=0
> >
> >
> >
>
>


  1   2   3   >