Re: Building a Faq for Royale

2019-04-30 Thread Alex Harui
Hi Dany,

I don't have any formed opinion on the best way to collect FAQ.

FWIW, in theory, dev@ is for questions related to the development of the 
framework code that goes in the Apache Royale repos.  Users@ and StackOverflow 
(SO) are intended to support folks using Royale to build applications.  Some 
Apache projects don't even have a users@ list, they only use SO and vice-versa. 
 I'm assuming you want to build a FAQ for application developers and maybe SO 
is a good enough way to determine FAQ since folks can upvote questions.

Or maybe the FAQ should be about getting started and SO will cover harder 
questions.  I'm not sure it matters.  I'll be happy if folks are asking 
questions because it means they are using Royale.  So try something, let's see 
how it feels and adjust as we go.

My main point in my previous post was to encourage us to use the public repos 
and wikis to lower the effort for others to contribute.

My 2 cents,
-Alex

On 4/30/19, 10:14 PM, "Dany Dhondt"  wrote:

Hi Alex,

Would it be an idea to launch every new question on this list with a [FAQ] 
prefix, discuss it and when the answer is accepted, post it to the Faq section?

Dany

> Op 1 mei 2019, om 00:45 heeft Alex Harui  het 
volgende geschreven:
> 
> FWIW, I would much prefer that the FAQ be part of the royale-docs so we 
can get PRs from folks.
> 
> Thoughts?
> -Alex
> 
> On 4/30/19, 2:08 PM, "Carlos Rovira" mailto:carlosrov...@apache.org>> wrote:
> 
>Hi Dany,
> 
>just created you account. I write it to your @mac.com account now to 
send
>you user/pass
>if you don't get nothing let me know privately
>thanks
> 
>El mar., 30 abr. 2019 a las 17:19, Dany Dhondt 
()
>escribió:
> 
>> No. It IS the right address. Don’t know why it marked as INVALID
>> Dany
>> 
>> Verstuurd vanaf mijn iPhone
>> 
>>> Op 30 apr. 2019 om 17:04 heeft Carlos Rovira 
>> het volgende geschreven:
>>> 
>>> Dany,
>>> please sent me the email I must use privately, since yours in the list
>> puts
>>> "invalid" so I think is not the want you use.
>>> thanks!
>>> 
>>> El mar., 30 abr. 2019 a las 17:03, Carlos Rovira (<
>> carlosrov...@apache.org>)
>>> escribió:
>>> 
 Hi Dany,
 
 I already shared the actual FAQ link [1], maybe you missed it.
 You can change it whatever you want, just think that changes will need
 approve of the rest.
 
 I'll sent you know credentials in private
 
 thanks!
 
 [1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Ffaq%2F&data=02%7C01%7Caharui%40adobe.com%7Cc602a5c9a58e4c16625908d6cdf3dce5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922844632860222&sdata=KvwsnCwqChyJtEo3hRDIKCY0NV3gTwmdNsiit74t7uo%3D&reserved=0
 

 
 El mar., 30 abr. 2019 a las 16:54, Dany Dhondt
>> (mailto:archeme...@mac.com.invalid>>)
 escribió:
 
> Hi Carlos,
> 
> That’s ok.
> Maybe you could setup a Faq section and create the empty base page so 
I
> don’t mess anything up?
> 
> Thx
> Dany
> 
>> Op 30 apr. 2019, om 16:42 heeft Carlos Rovira <
>> carlosrov...@apache.org >
> het volgende geschreven:
>> 
>> Hi Dany,
>> 
>> I can give you access to our pre production web site, so you can
>> change
>> text content. Then as you finish others can review and see if all is
>> ok
> or
>> needs any adjustment, etc... then we willl publish it to the public
> site.
>> If you are ok I can make you and user in private. Just a warning:
>> since
> we
>> use Wordpress that use to be very sensitive to global changes, you
> should
>> try just to touch "content" (add a section, add rows, add text,...),
> but if
>> you see other changes are needed please first ask about it, since 
some
>> times this could lead to other derivate problems.
>> 
>> thanks!
>> 
>> 
>> 
>> El mar., 30 abr. 2019 a las 16:30, Dany Dhondt
> (mailto:archeme...@mac.com.invalid>>)
>> escribió:
>> 
>>> Hi,
>>> 
>>> Seems the idea of having a faq section on our website is supported.
>>> I’m willing to start such a faq.
>>> How do we tackle this? Do we need a database or keep it plain text?
> Anyo

Build failed in Jenkins: royale-asjs_MXTests #736

2019-04-30 Thread Apache Royale CI Server
See 


--
[...truncated 2.11 MB...]
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MetaDataDefinition.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ISpinnerView.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/SpinnerView.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IViewportModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/WrappedHTMLElement.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/DropLocation.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/layout/LayoutData.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/errors/CursorError.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/TextLineMetrics.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/CSSStyleDeclaration.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/utils/FocusEventConverter.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MethodDefinition.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/display/Graphics.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ScrollControlBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/ListBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataProviderVirtualItemRendererMapper.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/WatcherBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IImage.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/BrowserEvent.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/PanelModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/models/PanelModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IPopUp.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/ButtonTestScript.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/spark/scripts/ButtonTestScript.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/ComboBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DateField.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/RoyaleContext.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ContainerBaseStrandChildren.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/BinaryData.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/UIUtils.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/ListSingleSelectionMouseController.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/MenuBarMouseController.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/controllers/MenuBarMouseController.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/e

Re: Example of access external JS using Apache Royale

2019-04-30 Thread Dany Dhondt
Wouldn’t it be a nice proof of concept if we tried to implement a widely used 
js lib into Royale?
There are a lot of js packages that are used thousands of times a day, like 
moment.js, lodash, …

Dany

> Op 1 mei 2019, om 01:13 heeft Alex Harui  het 
> volgende geschreven:
> 
> Isn't the ACE editor already an example?  Or maybe there are different 
> scenarios for external JS usage.
> 
> -Alex
> 
> On 4/30/19, 2:42 PM, "Carlos Rovira"  > wrote:
> 
>Hi,
> 
>I'm planing to make a blog example about using external JS or CSS in Apache
>Royale since people ask for it, and I think is one of the key points for
>people that wants to use Royale.
>My plan is to create a simple example that imports a JS script and then use
>bracket access. The example in concrete will use the script for coloring
>code that we use in TDJ that is external to Royale to show how we do it.
> 
>But I think that's just one of the ways to use external JS (bracket
>notation access).
>I think there's more:
>- dot notation -> but this required typedefs (Let me know if I'm wrong).
>and in that case, I don't have clear where we can add code to typedefs to
>do this. In the other way, how users can do something like this in their
>codebases. For me this is unexplored terrain, so hope others that knows
>about it could give some techniques, or point to some docs if we already
>has something. Maybe it could be great they could write some doc in our
>GitHub pages
> 
>- More ways?? Let me know.
> 
>I can work on this in few days , hope you could let me know about those
>alternate methods I didn't control
> 
>thanks
> 
>-- 
>Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C91b86d3f05e94a7fad1a08d6cdb4b310%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922573317036871&sdata=48234zx%2FlriaHuhJcqvUq05R1cZNJgkP8y5Jh3K2IKM%3D&reserved=0
>  
> 


Re: Building a Faq for Royale

2019-04-30 Thread Dany Dhondt
Hi Alex,

Would it be an idea to launch every new question on this list with a [FAQ] 
prefix, discuss it and when the answer is accepted, post it to the Faq section?

Dany

> Op 1 mei 2019, om 00:45 heeft Alex Harui  het 
> volgende geschreven:
> 
> FWIW, I would much prefer that the FAQ be part of the royale-docs so we can 
> get PRs from folks.
> 
> Thoughts?
> -Alex
> 
> On 4/30/19, 2:08 PM, "Carlos Rovira"  > wrote:
> 
>Hi Dany,
> 
>just created you account. I write it to your @mac.com account now to send
>you user/pass
>if you don't get nothing let me know privately
>thanks
> 
>El mar., 30 abr. 2019 a las 17:19, Dany Dhondt 
> ()
>escribió:
> 
>> No. It IS the right address. Don’t know why it marked as INVALID
>> Dany
>> 
>> Verstuurd vanaf mijn iPhone
>> 
>>> Op 30 apr. 2019 om 17:04 heeft Carlos Rovira 
>> het volgende geschreven:
>>> 
>>> Dany,
>>> please sent me the email I must use privately, since yours in the list
>> puts
>>> "invalid" so I think is not the want you use.
>>> thanks!
>>> 
>>> El mar., 30 abr. 2019 a las 17:03, Carlos Rovira (<
>> carlosrov...@apache.org>)
>>> escribió:
>>> 
 Hi Dany,
 
 I already shared the actual FAQ link [1], maybe you missed it.
 You can change it whatever you want, just think that changes will need
 approve of the rest.
 
 I'll sent you know credentials in private
 
 thanks!
 
 [1] 
 https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Ffaq%2F&data=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295&sdata=2m2QWWXA9BP3OQv2LcDmL9qfyyuO7GxUjPlhGWdZ28k%3D&reserved=0
  
 
 
 El mar., 30 abr. 2019 a las 16:54, Dany Dhondt
>> (mailto:archeme...@mac.com.invalid>>)
 escribió:
 
> Hi Carlos,
> 
> That’s ok.
> Maybe you could setup a Faq section and create the empty base page so I
> don’t mess anything up?
> 
> Thx
> Dany
> 
>> Op 30 apr. 2019, om 16:42 heeft Carlos Rovira <
>> carlosrov...@apache.org >
> het volgende geschreven:
>> 
>> Hi Dany,
>> 
>> I can give you access to our pre production web site, so you can
>> change
>> text content. Then as you finish others can review and see if all is
>> ok
> or
>> needs any adjustment, etc... then we willl publish it to the public
> site.
>> If you are ok I can make you and user in private. Just a warning:
>> since
> we
>> use Wordpress that use to be very sensitive to global changes, you
> should
>> try just to touch "content" (add a section, add rows, add text,...),
> but if
>> you see other changes are needed please first ask about it, since some
>> times this could lead to other derivate problems.
>> 
>> thanks!
>> 
>> 
>> 
>> El mar., 30 abr. 2019 a las 16:30, Dany Dhondt
> (mailto:archeme...@mac.com.invalid>>)
>> escribió:
>> 
>>> Hi,
>>> 
>>> Seems the idea of having a faq section on our website is supported.
>>> I’m willing to start such a faq.
>>> How do we tackle this? Do we need a database or keep it plain text?
> Anyone
>>> know of an online tool to manage it?
>>> Who’s managing the website itself?
>>> 
>>> Thoughts?
>>> 
>>> thx
>>> Dany
>> 
>> 
>> 
>> --
>> Carlos Rovira
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295&sdata=lcXkrphiwnSPQ4xuTYBgJGq1djZGHdquRohv%2F%2BmWt8Q%3D&reserved=0
>>  
>> 
> 
> 
 
 --
 Carlos Rovira
 https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295&sdata=lcXkrphiwnSPQ4xuTYBgJGq1djZGHdquRohv%2F%2BmWt8Q%3D&reserved=0
  
 

Build failed in Jenkins: royale-asjs_MXTests #735

2019-04-30 Thread Apache Royale CI Server
See 


--
[...truncated 2.03 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Mark Kessler
> Regarding your other response, I'm not sure that grep worked with Ant on 
> Windows.  It would be best to either have Ant generate the entire file or use 
> its replaceregex task on a known pattern.

There already exists one of those.  That's why I kept the current file
name as it was.  The following I found in the build.xml file in the
root.  It looks like it would almost work out of the box.  Would just
change the path to be more specific location.










-Mark K

On Tue, Apr 30, 2019 at 7:31 PM Alex Harui  wrote:
>
> I'm fine with starting with your example.  Are other versions in Royale 
> including the build number?  Are you expecting the build systems to update 
> that file on each build?  That might be trickier.  The Maven builds check for 
> uncommitted files.
>
> Regarding your other response, I'm not sure that grep worked with Ant on 
> Windows.  It would be best to either have Ant generate the entire file or use 
> its replaceregex task on a known pattern.
>
> My 2 cents,
> -Alex
>


Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Alex Harui
I'm fine with starting with your example.  Are other versions in Royale 
including the build number?  Are you expecting the build systems to update that 
file on each build?  That might be trickier.  The Maven builds check for 
uncommitted files.

Regarding your other response, I'm not sure that grep worked with Ant on 
Windows.  It would be best to either have Ant generate the entire file or use 
its replaceregex task on a known pattern.

My 2 cents,
-Alex

On 4/30/19, 4:02 PM, "Mark Kessler"  wrote:

Don't need every SWC with a version.  Just one for the whole SDK would
be fine.  I proposed just a single one stored in the core.  We can
modify the build file to just point to the single file instead of
doing a path search.  See the start of my example [1].


[1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FKesslerConsulting%2Froyale-asjs%2Fcommit%2F84262f3a2e56cc6b58ccdf283d039c94fb10cafb&data=02%7C01%7Caharui%40adobe.com%7Cd74e4fe942624e46e11708d6cdbfdac8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922621260197257&sdata=9UFENmZCH%2BwoK3OJHx1e%2B85bu%2FhIeIr%2F94QS4NYO5xA%3D&reserved=0

-Mark K


On Tue, Apr 30, 2019 at 6:42 PM Alex Harui  wrote:
>
> To be more specific:
>
> Version.as in Flex was included into every class.  I do not recommend 
doing that in Royale.  It didn't have enough value for the cost.
>
> FlexVersion.as in Flex was used for runtime versioning.  Code could use 
it to take different paths.  I hope we don't need that in Royale.
>
> The Flex and Royale compilers will put the compiler version in SWFs but 
do not put any string in JS output.  Someday, the Royale compiler may be 
released separately from the SWCs.  Royale may stop releasing certain SWCs in 
the future if there is no interest in maintaining them.  Then we will have to 
decide whether to update the version of those SWCs after they are frozen.  
Royale SWCs do not carry version information on a per-SWC basis.  But in some 
future, you could be using some version of the Royale compiler to compile with 
SWCs from different versions of the Royale SDKs.
>
> This version information is defined in the pom for folks using Maven.  It 
is not defined at all for other build mechanisms (Ant, command-line, IDEs) 
because the non-Maven artifacts do not have versions in the file names.  That's 
on purpose.  We want to make it easy for non-Maven users to swap versions of 
SDKs.  Maven users prioritize explicit dependency information over swapping of 
SDK versions.
>
> In summary, Royale may not be released like Flex where all SWCs are 
updated for each release along with a compiler.  So I'm not exactly sure what 
problem is trying to be solved, but it won't hurt to have a version bead or 
version constant.  And if someone wants to propose a way to get the compiler to 
inject a version string in JS output, that's fine too, but keep in mind that 
all of these verions strings might get removed during minification so they will 
probably need to be an exported public variable/constant.
>
> It would be great to have the version automatically updated for each 
release, but I think the number of places we currently change are small so 
having one more place probably is ok.  All it takes is a volunteer to create 
the PRs or commit the code.
>
> My 2 cents,
> -Alex
>
>




Re: How to try locally Royale-docs repo

2019-04-30 Thread Alex Harui
IIRC, I installed Jekyll.  Then run:

  jekyll build --config local_config.yml

Then some output folder contains html.

There is an Ant script that runs Jekyll.

HTH,
-Alex

On 4/30/19, 2:43 PM, "Carlos Rovira"  wrote:

Hi,

I saw Josh was working on Royale-docs repo.
I'd be interested in fix and some things and be able to do some changes,
but to do so I need to know how I can try it in my local Mac.

Someone can point me how you are working on this? I have the repo cloned,
now I need to know what tool I should have on Mac to change and test
locally before commit anything to see is ok.

then I'll need what's the current plans with Royale-docs and if if Josh,
Andrew or others are working on it, let me know what you're doing to avoid
conflicts or touch the same thing at the same time.

thanks!


-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8f8b4eb97c684bf025bf08d6cdb4f237%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922574377914519&sdata=0hKSOBkLOyMH2uhHwNpC1dHCuF%2FpPB8paoyvajr2eao%3D&reserved=0




Re: Example of access external JS using Apache Royale

2019-04-30 Thread Alex Harui
Isn't the ACE editor already an example?  Or maybe there are different 
scenarios for external JS usage.

-Alex

On 4/30/19, 2:42 PM, "Carlos Rovira"  wrote:

Hi,

I'm planing to make a blog example about using external JS or CSS in Apache
Royale since people ask for it, and I think is one of the key points for
people that wants to use Royale.
My plan is to create a simple example that imports a JS script and then use
bracket access. The example in concrete will use the script for coloring
code that we use in TDJ that is external to Royale to show how we do it.

But I think that's just one of the ways to use external JS (bracket
notation access).
I think there's more:
- dot notation -> but this required typedefs (Let me know if I'm wrong).
and in that case, I don't have clear where we can add code to typedefs to
do this. In the other way, how users can do something like this in their
codebases. For me this is unexplored terrain, so hope others that knows
about it could give some techniques, or point to some docs if we already
has something. Maybe it could be great they could write some doc in our
GitHub pages

- More ways?? Let me know.

I can work on this in few days , hope you could let me know about those
alternate methods I didn't control

thanks

-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C91b86d3f05e94a7fad1a08d6cdb4b310%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922573317036871&sdata=48234zx%2FlriaHuhJcqvUq05R1cZNJgkP8y5Jh3K2IKM%3D&reserved=0




Re: Royale in a Week

2019-04-30 Thread Alex Harui
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%2F&data=02%7C01%7Caharui%40adobe.com%7C5e6f1266e7384aa2831c08d6cda3c6a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922500628304365&sdata=b%2BhDtiykkxmq9c83dOP%2FF9RrucysABFyICNXaulhjqw%3D&reserved=0




Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Mark Kessler
Don't need every SWC with a version.  Just one for the whole SDK would
be fine.  I proposed just a single one stored in the core.  We can
modify the build file to just point to the single file instead of
doing a path search.  See the start of my example [1].


[1] 
https://github.com/KesslerConsulting/royale-asjs/commit/84262f3a2e56cc6b58ccdf283d039c94fb10cafb

-Mark K


On Tue, Apr 30, 2019 at 6:42 PM Alex Harui  wrote:
>
> To be more specific:
>
> Version.as in Flex was included into every class.  I do not recommend doing 
> that in Royale.  It didn't have enough value for the cost.
>
> FlexVersion.as in Flex was used for runtime versioning.  Code could use it to 
> take different paths.  I hope we don't need that in Royale.
>
> The Flex and Royale compilers will put the compiler version in SWFs but do 
> not put any string in JS output.  Someday, the Royale compiler may be 
> released separately from the SWCs.  Royale may stop releasing certain SWCs in 
> the future if there is no interest in maintaining them.  Then we will have to 
> decide whether to update the version of those SWCs after they are frozen.  
> Royale SWCs do not carry version information on a per-SWC basis.  But in some 
> future, you could be using some version of the Royale compiler to compile 
> with SWCs from different versions of the Royale SDKs.
>
> This version information is defined in the pom for folks using Maven.  It is 
> not defined at all for other build mechanisms (Ant, command-line, IDEs) 
> because the non-Maven artifacts do not have versions in the file names.  
> That's on purpose.  We want to make it easy for non-Maven users to swap 
> versions of SDKs.  Maven users prioritize explicit dependency information 
> over swapping of SDK versions.
>
> In summary, Royale may not be released like Flex where all SWCs are updated 
> for each release along with a compiler.  So I'm not exactly sure what problem 
> is trying to be solved, but it won't hurt to have a version bead or version 
> constant.  And if someone wants to propose a way to get the compiler to 
> inject a version string in JS output, that's fine too, but keep in mind that 
> all of these verions strings might get removed during minification so they 
> will probably need to be an exported public variable/constant.
>
> It would be great to have the version automatically updated for each release, 
> but I think the number of places we currently change are small so having one 
> more place probably is ok.  All it takes is a volunteer to create the PRs or 
> commit the code.
>
> My 2 cents,
> -Alex
>
>


Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Mark Kessler
We can through an old mechanism that appears to be left from the
Apache Flex side that does just this.

Around line1192 of the root build.xml [1].  It specifically hunts down
files called "Version.as" and uses RegEx to update the version number
and build number.  So when the SDK is built for release, it will
automatically update the Version.as files using the "release.version"
property.  Meaning after we create the file(Version.as) having the
correct version format inside it it will be something that stays
up-to-date automatically.  Little tweaks needed it looks like, but it
should work.

build.xml lines look like this:















I won't have a chance to test the build.xml right now to finish it,
but here is what the rest of it would look like [2] (very short).

Usage for the end user:

import org.apache.royale.core.Version;

trace(Version.CURRENT_VERSION);


[1] https://github.com/apache/royale-asjs/blob/develop/build.xml
[2] 
https://github.com/KesslerConsulting/royale-asjs/commit/84262f3a2e56cc6b58ccdf283d039c94fb10cafb

-Mark K

On Tue, Apr 30, 2019 at 5:17 PM Carlos Rovira  wrote:
>
> Well,
> since others techs make that maybe it would be ok to have it baked. Right
> now I don't have a strong opinion about what to do maybe others could bring
> more light, but Version class seems ok to me, and hope we could have it get
> the version directly without manual modifications what will very cumbersome
> to manage for releases, niglhly builds, etc..
>


Re: Building a Faq for Royale

2019-04-30 Thread Alex Harui
FWIW, I would much prefer that the FAQ be part of the royale-docs so we can get 
PRs from folks.

Thoughts?
-Alex

On 4/30/19, 2:08 PM, "Carlos Rovira"  wrote:

Hi Dany,

just created you account. I write it to your @mac.com account now to send
you user/pass
if you don't get nothing let me know privately
thanks

El mar., 30 abr. 2019 a las 17:19, Dany Dhondt 
()
escribió:

> No. It IS the right address. Don’t know why it marked as INVALID
> Dany
>
> Verstuurd vanaf mijn iPhone
>
> > Op 30 apr. 2019 om 17:04 heeft Carlos Rovira 
> het volgende geschreven:
> >
> > Dany,
> > please sent me the email I must use privately, since yours in the list
> puts
> > "invalid" so I think is not the want you use.
> > thanks!
> >
> > El mar., 30 abr. 2019 a las 17:03, Carlos Rovira (<
> carlosrov...@apache.org>)
> > escribió:
> >
> >> Hi Dany,
> >>
> >> I already shared the actual FAQ link [1], maybe you missed it.
> >> You can change it whatever you want, just think that changes will need
> >> approve of the rest.
> >>
> >> I'll sent you know credentials in private
> >>
> >> thanks!
> >>
> >> [1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Ffaq%2F&data=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295&sdata=2m2QWWXA9BP3OQv2LcDmL9qfyyuO7GxUjPlhGWdZ28k%3D&reserved=0
> >>
> >> El mar., 30 abr. 2019 a las 16:54, Dany Dhondt
> ()
> >> escribió:
> >>
> >>> Hi Carlos,
> >>>
> >>> That’s ok.
> >>> Maybe you could setup a Faq section and create the empty base page so 
I
> >>> don’t mess anything up?
> >>>
> >>> Thx
> >>> Dany
> >>>
>  Op 30 apr. 2019, om 16:42 heeft Carlos Rovira <
> carlosrov...@apache.org>
> >>> het volgende geschreven:
> 
>  Hi Dany,
> 
>  I can give you access to our pre production web site, so you can
> change
>  text content. Then as you finish others can review and see if all is
> ok
> >>> or
>  needs any adjustment, etc... then we willl publish it to the public
> >>> site.
>  If you are ok I can make you and user in private. Just a warning:
> since
> >>> we
>  use Wordpress that use to be very sensitive to global changes, you
> >>> should
>  try just to touch "content" (add a section, add rows, add text,...),
> >>> but if
>  you see other changes are needed please first ask about it, since 
some
>  times this could lead to other derivate problems.
> 
>  thanks!
> 
> 
> 
>  El mar., 30 abr. 2019 a las 16:30, Dany Dhondt
> >>> ()
>  escribió:
> 
> > Hi,
> >
> > Seems the idea of having a faq section on our website is supported.
> > I’m willing to start such a faq.
> > How do we tackle this? Do we need a database or keep it plain text?
> >>> Anyone
> > know of an online tool to manage it?
> > Who’s managing the website itself?
> >
> > Thoughts?
> >
> > thx
> > Dany
> 
> 
> 
>  --
>  Carlos Rovira
>  
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295&sdata=lcXkrphiwnSPQ4xuTYBgJGq1djZGHdquRohv%2F%2BmWt8Q%3D&reserved=0
> >>>
> >>>
> >>
> >> --
> >> Carlos Rovira
> >> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295&sdata=lcXkrphiwnSPQ4xuTYBgJGq1djZGHdquRohv%2F%2BmWt8Q%3D&reserved=0
> >>
> >>
> >
> > --
> > Carlos Rovira
> > 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295&sdata=lcXkrphiwnSPQ4xuTYBgJGq1djZGHdquRohv%2F%2BmWt8Q%3D&reserved=0
>
>

-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295&sdata=lcXkrphiwnSPQ4xuTYBgJGq1djZGHdquRohv%2F%2BmWt8Q%3D&reserved=0




Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Alex Harui
To be more specific:

Version.as in Flex was included into every class.  I do not recommend doing 
that in Royale.  It didn't have enough value for the cost.

FlexVersion.as in Flex was used for runtime versioning.  Code could use it to 
take different paths.  I hope we don't need that in Royale.

The Flex and Royale compilers will put the compiler version in SWFs but do not 
put any string in JS output.  Someday, the Royale compiler may be released 
separately from the SWCs.  Royale may stop releasing certain SWCs in the future 
if there is no interest in maintaining them.  Then we will have to decide 
whether to update the version of those SWCs after they are frozen.  Royale SWCs 
do not carry version information on a per-SWC basis.  But in some future, you 
could be using some version of the Royale compiler to compile with SWCs from 
different versions of the Royale SDKs.

This version information is defined in the pom for folks using Maven.  It is 
not defined at all for other build mechanisms (Ant, command-line, IDEs) because 
the non-Maven artifacts do not have versions in the file names.  That's on 
purpose.  We want to make it easy for non-Maven users to swap versions of SDKs. 
 Maven users prioritize explicit dependency information over swapping of SDK 
versions.

In summary, Royale may not be released like Flex where all SWCs are updated for 
each release along with a compiler.  So I'm not exactly sure what problem is 
trying to be solved, but it won't hurt to have a version bead or version 
constant.  And if someone wants to propose a way to get the compiler to inject 
a version string in JS output, that's fine too, but keep in mind that all of 
these verions strings might get removed during minification so they will 
probably need to be an exported public variable/constant.

It would be great to have the version automatically updated for each release, 
but I think the number of places we currently change are small so having one 
more place probably is ok.  All it takes is a volunteer to create the PRs or 
commit the code.

My 2 cents,
-Alex



On 4/30/19, 2:17 PM, "Carlos Rovira"  wrote:

Well,
since others techs make that maybe it would be ok to have it baked. Right
now I don't have a strong opinion about what to do maybe others could bring
more light, but Version class seems ok to me, and hope we could have it get
the version directly without manual modifications what will very cumbersome
to manage for releases, niglhly builds, etc..

El mar., 30 abr. 2019 a las 22:14, Mark Kessler (<
kesslerconsult...@gmail.com>) escribió:

> Well that would work in addition too, but not replace what I'm talking
> about.  I'm talking about the SDK having a built in version.  A
> version bead would be more building an app using the SDK and the app
> having it's own version.
>
>
> -Mark K
>
> On Tue, Apr 30, 2019 at 2:39 PM Piotr Zarzycki
>  wrote:
> >
> > +1 to Josh's idea that we provide bead with logic which serves version.
> >
> > Thanks,
> > Piotr
>


-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C5cf03e97fd1e4d637be208d6cdb14239%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922558582228586&sdata=lF%2FwGT5b6MoKml%2BocTXLOxuaukVn7%2BkkdgRmUE59EuY%3D&reserved=0




SOF question about enterFrame in Royale need some response

2019-04-30 Thread Carlos Rovira
Hi,

Andrew posted in SOF a question about enterFrame event in JS [1]. I'm not
sure about how this is done in Royale since I didn't use it for many time
since Flash times.

Hope others could give it some response

thanks

https://stackoverflow.com/questions/tagged/apache-royale

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


How to try locally Royale-docs repo

2019-04-30 Thread Carlos Rovira
Hi,

I saw Josh was working on Royale-docs repo.
I'd be interested in fix and some things and be able to do some changes,
but to do so I need to know how I can try it in my local Mac.

Someone can point me how you are working on this? I have the repo cloned,
now I need to know what tool I should have on Mac to change and test
locally before commit anything to see is ok.

then I'll need what's the current plans with Royale-docs and if if Josh,
Andrew or others are working on it, let me know what you're doing to avoid
conflicts or touch the same thing at the same time.

thanks!


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


Example of access external JS using Apache Royale

2019-04-30 Thread Carlos Rovira
Hi,

I'm planing to make a blog example about using external JS or CSS in Apache
Royale since people ask for it, and I think is one of the key points for
people that wants to use Royale.
My plan is to create a simple example that imports a JS script and then use
bracket access. The example in concrete will use the script for coloring
code that we use in TDJ that is external to Royale to show how we do it.

But I think that's just one of the ways to use external JS (bracket
notation access).
I think there's more:
- dot notation -> but this required typedefs (Let me know if I'm wrong).
and in that case, I don't have clear where we can add code to typedefs to
do this. In the other way, how users can do something like this in their
codebases. For me this is unexplored terrain, so hope others that knows
about it could give some techniques, or point to some docs if we already
has something. Maybe it could be great they could write some doc in our
GitHub pages

- More ways?? Let me know.

I can work on this in few days , hope you could let me know about those
alternate methods I didn't control

thanks

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


Re: Royale in a Week

2019-04-30 Thread Carlos Rovira
Hi Andrew,

don't understand what you mean with "My first step would be to review the
old curriculum"
are you talking to create a curriculum app with royale?

I think the best way to go over Royale in a week is to use the same
structure as Flex in a week when possible. And nobody better than you to
start writing it
Then if you need help with specific parts we always can join and help as
you request.

thanks for working on this

Carlos


El mar., 30 abr. 2019 a las 21:41, Andrew Wetmore ()
escribió:

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


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


Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Carlos Rovira
Well,
since others techs make that maybe it would be ok to have it baked. Right
now I don't have a strong opinion about what to do maybe others could bring
more light, but Version class seems ok to me, and hope we could have it get
the version directly without manual modifications what will very cumbersome
to manage for releases, niglhly builds, etc..

El mar., 30 abr. 2019 a las 22:14, Mark Kessler (<
kesslerconsult...@gmail.com>) escribió:

> Well that would work in addition too, but not replace what I'm talking
> about.  I'm talking about the SDK having a built in version.  A
> version bead would be more building an app using the SDK and the app
> having it's own version.
>
>
> -Mark K
>
> On Tue, Apr 30, 2019 at 2:39 PM Piotr Zarzycki
>  wrote:
> >
> > +1 to Josh's idea that we provide bead with logic which serves version.
> >
> > Thanks,
> > Piotr
>


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


Re: Building a Faq for Royale

2019-04-30 Thread Carlos Rovira
Hi Dany,

just created you account. I write it to your @mac.com account now to send
you user/pass
if you don't get nothing let me know privately
thanks

El mar., 30 abr. 2019 a las 17:19, Dany Dhondt ()
escribió:

> No. It IS the right address. Don’t know why it marked as INVALID
> Dany
>
> Verstuurd vanaf mijn iPhone
>
> > Op 30 apr. 2019 om 17:04 heeft Carlos Rovira 
> het volgende geschreven:
> >
> > Dany,
> > please sent me the email I must use privately, since yours in the list
> puts
> > "invalid" so I think is not the want you use.
> > thanks!
> >
> > El mar., 30 abr. 2019 a las 17:03, Carlos Rovira (<
> carlosrov...@apache.org>)
> > escribió:
> >
> >> Hi Dany,
> >>
> >> I already shared the actual FAQ link [1], maybe you missed it.
> >> You can change it whatever you want, just think that changes will need
> >> approve of the rest.
> >>
> >> I'll sent you know credentials in private
> >>
> >> thanks!
> >>
> >> [1] https://royale.apache.org/faq/
> >>
> >> El mar., 30 abr. 2019 a las 16:54, Dany Dhondt
> ()
> >> escribió:
> >>
> >>> Hi Carlos,
> >>>
> >>> That’s ok.
> >>> Maybe you could setup a Faq section and create the empty base page so I
> >>> don’t mess anything up?
> >>>
> >>> Thx
> >>> Dany
> >>>
>  Op 30 apr. 2019, om 16:42 heeft Carlos Rovira <
> carlosrov...@apache.org>
> >>> het volgende geschreven:
> 
>  Hi Dany,
> 
>  I can give you access to our pre production web site, so you can
> change
>  text content. Then as you finish others can review and see if all is
> ok
> >>> or
>  needs any adjustment, etc... then we willl publish it to the public
> >>> site.
>  If you are ok I can make you and user in private. Just a warning:
> since
> >>> we
>  use Wordpress that use to be very sensitive to global changes, you
> >>> should
>  try just to touch "content" (add a section, add rows, add text,...),
> >>> but if
>  you see other changes are needed please first ask about it, since some
>  times this could lead to other derivate problems.
> 
>  thanks!
> 
> 
> 
>  El mar., 30 abr. 2019 a las 16:30, Dany Dhondt
> >>> ()
>  escribió:
> 
> > Hi,
> >
> > Seems the idea of having a faq section on our website is supported.
> > I’m willing to start such a faq.
> > How do we tackle this? Do we need a database or keep it plain text?
> >>> Anyone
> > know of an online tool to manage it?
> > Who’s managing the website itself?
> >
> > Thoughts?
> >
> > thx
> > Dany
> 
> 
> 
>  --
>  Carlos Rovira
>  http://about.me/carlosrovira
> >>>
> >>>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>

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


Re: extending IUIBase with interfaces (was: Re: Version property (was: Let's bump Royale version to 1.0))

2019-04-30 Thread Alex Harui
Hi Carlos,

I've said this before:  I feel bad sometimes that Flex taught folks some 
questionable programming practices.

The short answer:
-Don't reference concrete classes
-Choose composition patterns over inheritance

The long answer:

Yishay and Andrew are headed in the right direction.  A good goal for Royale is 
to try to avoid references to concrete classes (other than what your class 
subclasses).  Referencing concrete classes essentially breaks PAYG by creating 
an unreplaceable chain of dependencies.  Flex referenced too many concrete 
classes and we all paid for it.

But addition to using interfaces, we should try to remember that Royale is more 
about composition than inheritance.  Beads are composed into instances to 
implement functionality.  Hopefully, many beads can be re-used on other 
instances with different base class ancestry if the API surfaces are designed 
correctly.

And, not only are beads best referenced via their interfaces, you can also ask 
"has" instead of "is".  IOW, you can ask if an instance "has" a bead instead of 
just testing if the instance "is" (implements) an interface.

The first word in PAYG is Pay.  PAYG is not Free-AYG.  Somebody has to pay.  
The more features you use, the more you pay in download size and performance, 
especially at startup.  The point of PAYG and beads is to enable optimization.  
If you want to make cookies and you buy each ingredient separately it will take 
up more space and weight because of the packaging as opposed to buying one bag 
of ready-to-bake cookie mix.  But the point of having separate ingredients is 
so you can replace white flour with whole wheat or rye or gluten-free easily.

If it turns out there is significant overhead in some set of beads, you can 
choose to inline them, just like any other inlining optimization.  That is a 
manual process today.  Inlining is effectively copying code, so it sounds like 
that is what you are doing today.  But the copying of code should only be a 
last resort after proving that the composition patterns have too much overhead. 
 The inlining will have its own overhead, usually in download size, as you 
mentioned.

I explained the "exploded component" concept a while back.  It attempts to 
illustrate composition by showing how, in MXML, a component can really be 
declared as its beads.  For example:



Could be written more verbosely as:


   



  


Then a ToggleButton could be implemented by simply replacing the controller 
(and probably the view).


   



  


So it is only for convenience, so you don't have to type all of these tags, 
that we create a top-level component (TLC) called Button that pre-packages some 
set of beads and write glue code that proxies some of the bead APIs to the 
TLC's API such as:

public class Button extends UIBase
{
   public function set label(value:String):void
   {
  model.label = value;
   }
}

The point, relative to this topic, is there is a cost to this convenience, 
which is the line or two of glue code.

So, with beads, it is only for convenience that the TLC implements these PAYG 
interfaces.  If you package up the implementation of IClassSelectorListSupport 
into a bead, that bead should be able to be composed into different classes 
with different base classes.  We actually have a choice of whether to add the 
glue code that proxies that implementation to the API surface.  If you do that 
proxying, then other code can look like:

if (myInstance is IClassSelectorListSupport)
   (myInstance as IClassSelectorListSupport).someAPi = "foo";

But the other option is the "has" pattern, which looks like:

Var foo:IClassSelectorListSupport = 
myInstance.getBeadByType(IClassSelectorListSupport);
If (foo)
foo.someAPI = "foo";

I've not done any measuring of which is better, but the latter does not require 
glue code, which allows someone to just drop in any IClassSelectorListSupport 
bead on some other random instance they've created and not make any assumptions 
about base classes or proxy code to interfaces.  For example:


  

  


This instance, declared in MXML without the overhead of creating a TLC and 
proxying code to the API surface, would work with the "has" code, but not the 
"is" code.

Is it all worth it?  I don't know.  I'm waiting to see folks try it, especially 
in more complex apps.  But for sure, composition "has" patterns are more 
flexible than traditional "is" patterns.

This "has" pattern allows us to sort of have multiple inheritance or "mixin" 
type patterns, but it is done by accessing the beads directly not by proxying 
code to the TLC so "inheritance" isn't an accurate word.  TLCs are more for 
convenience, to avoid repeating a lot of tags in MXML or calling addBead a lot, 
but we should try to make our code even more flexible by not requiring folks to 
work with TLCs.

So, in theory, you should try to package the implementation of 
IClassSelectorListSupport into a bead and see if you run into pro

Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Mark Kessler
Well that would work in addition too, but not replace what I'm talking
about.  I'm talking about the SDK having a built in version.  A
version bead would be more building an app using the SDK and the app
having it's own version.


-Mark K

On Tue, Apr 30, 2019 at 2:39 PM Piotr Zarzycki
 wrote:
>
> +1 to Josh's idea that we provide bead with logic which serves version.
>
> Thanks,
> Piotr


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: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Piotr Zarzycki
+1 to Josh's idea that we provide bead with logic which serves version.

Thanks,
Piotr

On Tue, Apr 30, 2019, 8:18 PM Kessler CTR Mark J
 wrote:

> As an example, here is how to access the version number in other
> languages.  Some easier to use than others.  Looks like the easiest ones
> are just static const strings.
>
> Flex[1]:  mx.core.FlexVersion.CURRENT_VERSION
> Dotnet[2]: System.Environment.Version
> Java[3]:System.getProperty("java.version");
> React[4]: React.version
> Angular[5]: import { VERSION } from '@angular/core';  VERSION.full
> Groovy[6]: GroovySystem.getVersion();
> Ruby[7]: RUBY_VERSION
> Python[8]: sys.version
> Node.Js[9]: process.version
> PHP[10]: phpversion()
>
>
> So I would like the SDK to provide something similar.  It looks like we
> still have a mechanism setup in the build.xml we are just missing the files
> it's looking for (Version.as files).  Let's add the following file and see
> if it with a little tweak in pathing would turn it into a self-managing
> version file when building the SDK for release.  This looks like a smallest
> simplest mechanism to implement this.  Especially since it's regex pattern
> matching the old version format, it doesn't matter how we layout the file.
>
> File: Version.as
>
> package org.apache.royale.core
> {
> public class Version
> {
> public static const CURRENT_VERSION:String = "0.9.6.0";
> }
> }
>
>
> SDK Usage for developer:
> Import org.apache.core.Version;
> trace(Version.CURRENT_VERSION);
>
>
> [1] https://flex.apache.org/asdoc/mx/core/FlexVersion.html
> [2]
> https://docs.microsoft.com/en-us/dotnet/api/system.environment.version?view=netframework-4.8
> [3]
> https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html
> [4]
> https://stackoverflow.com/questions/36994564/how-can-one-tell-the-version-of-react-running-at-runtime-in-the-browser
> [5]
> https://stackoverflow.com/questions/36456843/how-to-check-angular2-version-with-typescript
> [6]
> http://docs.groovy-lang.org/latest/html/api/groovy/lang/GroovySystem.html
> [7]
> https://stackoverflow.com/questions/1589751/determine-ruby-version-from-within-rails
> [8] https://docs.python.org/3/library/sys.html
> [9] https://nodejs.org/api/process.html#process_process_version
> [10] https://www.php.net/manual/en/function.phpversion.php
>
>
> -Mark K
>
>
> -Original Message-
> From: Carlos Rovira [mailto:carlosrov...@apache.org]
> Sent: Tuesday, April 30, 2019 10:37 AM
> To: dev@royale.apache.org
> Subject: Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale
> version to 1.0)
>
> Hi Mark,
>
> sorry but all you state can be solved with the solution I exposed to you.
> There's no need to add an identifier to an SDK since you can add it
> yourself from the SDK you downloaded or get by the multiple ways available.
> In any of the cases the numbers are not baked into code, but are available
> in different parts and you can use defines to bake it into your code and
> use it in the same way you use to do in Flex. At least I don't see from
> your response that your points will not be covered in that way
>


RE: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Kessler CTR Mark J
As an example, here is how to access the version number in other languages.  
Some easier to use than others.  Looks like the easiest ones are just static 
const strings.

Flex[1]:  mx.core.FlexVersion.CURRENT_VERSION
Dotnet[2]: System.Environment.Version
Java[3]:System.getProperty("java.version");
React[4]: React.version
Angular[5]: import { VERSION } from '@angular/core';  VERSION.full
Groovy[6]: GroovySystem.getVersion();
Ruby[7]: RUBY_VERSION
Python[8]: sys.version
Node.Js[9]: process.version
PHP[10]: phpversion()


So I would like the SDK to provide something similar.  It looks like we still 
have a mechanism setup in the build.xml we are just missing the files it's 
looking for (Version.as files).  Let's add the following file and see if it 
with a little tweak in pathing would turn it into a self-managing version file 
when building the SDK for release.  This looks like a smallest simplest 
mechanism to implement this.  Especially since it's regex pattern matching the 
old version format, it doesn't matter how we layout the file.

File: Version.as

package org.apache.royale.core
{
public class Version
{
public static const CURRENT_VERSION:String = "0.9.6.0";
}
}


SDK Usage for developer: 
Import org.apache.core.Version;
trace(Version.CURRENT_VERSION);


[1] https://flex.apache.org/asdoc/mx/core/FlexVersion.html
[2] 
https://docs.microsoft.com/en-us/dotnet/api/system.environment.version?view=netframework-4.8
[3] https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html
[4] 
https://stackoverflow.com/questions/36994564/how-can-one-tell-the-version-of-react-running-at-runtime-in-the-browser
[5] 
https://stackoverflow.com/questions/36456843/how-to-check-angular2-version-with-typescript
[6] http://docs.groovy-lang.org/latest/html/api/groovy/lang/GroovySystem.html
[7] 
https://stackoverflow.com/questions/1589751/determine-ruby-version-from-within-rails
[8] https://docs.python.org/3/library/sys.html
[9] https://nodejs.org/api/process.html#process_process_version
[10] https://www.php.net/manual/en/function.phpversion.php


-Mark K


-Original Message-
From: Carlos Rovira [mailto:carlosrov...@apache.org] 
Sent: Tuesday, April 30, 2019 10:37 AM
To: dev@royale.apache.org
Subject: Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale 
version to 1.0)

Hi Mark,

sorry but all you state can be solved with the solution I exposed to you.
There's no need to add an identifier to an SDK since you can add it
yourself from the SDK you downloaded or get by the multiple ways available.
In any of the cases the numbers are not baked into code, but are available
in different parts and you can use defines to bake it into your code and
use it in the same way you use to do in Flex. At least I don't see from
your response that your points will not be covered in that way


Stars in Github

2019-04-30 Thread Carlos Rovira
Hi!,

one more important thing to pursue: Get stars in Apache Royale ASJS Github
repo:

https://github.com/apache/royale-asjs/stargazers

We currently have 222...we need much much more!! :)

projects are more valuable if this number grows.

So share your love and give us star! :)

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


Re: RE: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Carlos Rovira
I think is a good idea to create a bead. But maybe is not needed to add to
Express for example by default.
People that wants it could just add it in this main Application file in the
beads section.

I think this is a good opportunity to contribute it via PR, what do you
think Mark?

just my 2...

El El mar, 30 abr 2019 a las 18:00, Josh Tynjala 
escribió:

> What if Royale had some kind of VersionBead that you could add to the main
> application? It could be optional with Basic, but maybe baked in by default
> with Express and other component sets that are less focused on small output
> size.
>
> - Josh
>
> On 2019/04/30 10:46:27, Kessler CTR Mark J 
> wrote:
> > Lol, I can't seem to explain it properly.  Take maven/ant/config files
> out of the equation it doesn't matter for this example.  This has to do
> with getting some identifying information into the official SDK releases.
> We don't want to pass variables as an SDK user.  We want the official SDK
> to already come packaged with a version number or a build number or a build
> date...
> >
> >
> > Here's the scenario that I would love to see happen:
> >
> > 1.  SDK user downloads official Royale SDK release and never modifies it.
> >
> > 2.  SDK User compiles their app using official SDK and references an
> official SDK property that contains the SDK identifier already built in
> it.  Meaning I should be able to code complete off of the SDK and find
> something that already exists and could return me an official identifier.
> >
> >
> > -Mark K
> >
> > -Original Message-
> > From: Carlos Rovira [mailto:carlosrov...@apache.org]
> > Sent: Monday, April 29, 2019 1:14 PM
> > To: dev@royale.apache.org
> > Subject: [Non-DoD Source] Re: Version property (was: Let's bump Royale
> version to 1.0)
> >
> > ok,
> >
> > we do the following in maven for other needs so this will be valid for
> you
> > too:
> >
> > in your maven properties.
> >
> > 0.9.6-OR-WHATEVER
> >
> > 
> > org.apache.royale.compiler
> > royale-maven-plugin
> > true
> > 
> > ...
> > 
> > 
> > BUILD::royaleVersion
> > '"${royale.framework.version}"'
> > 
> > ...
> > 
> > ...
> >
> >
> > defines can be done in ANT, asconfigc, config.xml
> >
> > Then in AS3 or MXML
> >
> > /**
> > * ROYALE VERSION NUMBER
> > */
> > private static var _royaleVersion :String = BUILD::royaleVersion;
> >
> > So now you can use in any place you want
> >
> > HTH
> >
> > Carlos
> >
> >
>


Re: RE: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Josh Tynjala
What if Royale had some kind of VersionBead that you could add to the main 
application? It could be optional with Basic, but maybe baked in by default 
with Express and other component sets that are less focused on small output 
size.

- Josh

On 2019/04/30 10:46:27, Kessler CTR Mark J  
wrote: 
> Lol, I can't seem to explain it properly.  Take maven/ant/config files out of 
> the equation it doesn't matter for this example.  This has to do with getting 
> some identifying information into the official SDK releases.  We don't want 
> to pass variables as an SDK user.  We want the official SDK to already come 
> packaged with a version number or a build number or a build date...
> 
> 
> Here's the scenario that I would love to see happen:
> 
> 1.  SDK user downloads official Royale SDK release and never modifies it.
> 
> 2.  SDK User compiles their app using official SDK and references an official 
> SDK property that contains the SDK identifier already built in it.  Meaning I 
> should be able to code complete off of the SDK and find something that 
> already exists and could return me an official identifier.
> 
> 
> -Mark K
> 
> -Original Message-
> From: Carlos Rovira [mailto:carlosrov...@apache.org] 
> Sent: Monday, April 29, 2019 1:14 PM
> To: dev@royale.apache.org
> Subject: [Non-DoD Source] Re: Version property (was: Let's bump Royale 
> version to 1.0)
> 
> ok,
> 
> we do the following in maven for other needs so this will be valid for you
> too:
> 
> in your maven properties.
> 
> 0.9.6-OR-WHATEVER
> 
> 
> org.apache.royale.compiler
> royale-maven-plugin
> true
> 
> ...
> 
> 
> BUILD::royaleVersion
> '"${royale.framework.version}"'
> 
> ...
> 
> ...
> 
> 
> defines can be done in ANT, asconfigc, config.xml
> 
> Then in AS3 or MXML
> 
> /**
> * ROYALE VERSION NUMBER
> */
> private static var _royaleVersion :String = BUILD::royaleVersion;
> 
> So now you can use in any place you want
> 
> HTH
> 
> Carlos
> 
> 


Re: Building a Faq for Royale

2019-04-30 Thread Dany Dhondt
No. It IS the right address. Don’t know why it marked as INVALID
Dany

Verstuurd vanaf mijn iPhone

> Op 30 apr. 2019 om 17:04 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Dany,
> please sent me the email I must use privately, since yours in the list puts
> "invalid" so I think is not the want you use.
> thanks!
> 
> El mar., 30 abr. 2019 a las 17:03, Carlos Rovira ()
> escribió:
> 
>> Hi Dany,
>> 
>> I already shared the actual FAQ link [1], maybe you missed it.
>> You can change it whatever you want, just think that changes will need
>> approve of the rest.
>> 
>> I'll sent you know credentials in private
>> 
>> thanks!
>> 
>> [1] https://royale.apache.org/faq/
>> 
>> El mar., 30 abr. 2019 a las 16:54, Dany Dhondt ()
>> escribió:
>> 
>>> Hi Carlos,
>>> 
>>> That’s ok.
>>> Maybe you could setup a Faq section and create the empty base page so I
>>> don’t mess anything up?
>>> 
>>> Thx
>>> Dany
>>> 
 Op 30 apr. 2019, om 16:42 heeft Carlos Rovira 
>>> het volgende geschreven:
 
 Hi Dany,
 
 I can give you access to our pre production web site, so you can change
 text content. Then as you finish others can review and see if all is ok
>>> or
 needs any adjustment, etc... then we willl publish it to the public
>>> site.
 If you are ok I can make you and user in private. Just a warning: since
>>> we
 use Wordpress that use to be very sensitive to global changes, you
>>> should
 try just to touch "content" (add a section, add rows, add text,...),
>>> but if
 you see other changes are needed please first ask about it, since some
 times this could lead to other derivate problems.
 
 thanks!
 
 
 
 El mar., 30 abr. 2019 a las 16:30, Dany Dhondt
>>> ()
 escribió:
 
> Hi,
> 
> Seems the idea of having a faq section on our website is supported.
> I’m willing to start such a faq.
> How do we tackle this? Do we need a database or keep it plain text?
>>> Anyone
> know of an online tool to manage it?
> Who’s managing the website itself?
> 
> Thoughts?
> 
> thx
> Dany
 
 
 
 --
 Carlos Rovira
 http://about.me/carlosrovira
>>> 
>>> 
>> 
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>> 
>> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira



Re: Building a Faq for Royale

2019-04-30 Thread Carlos Rovira
Hi Dany,

I already shared the actual FAQ link [1], maybe you missed it.
You can change it whatever you want, just think that changes will need
approve of the rest.

I'll sent you know credentials in private

thanks!

[1] https://royale.apache.org/faq/

El mar., 30 abr. 2019 a las 16:54, Dany Dhondt ()
escribió:

> Hi Carlos,
>
> That’s ok.
> Maybe you could setup a Faq section and create the empty base page so I
> don’t mess anything up?
>
> Thx
> Dany
>
> > Op 30 apr. 2019, om 16:42 heeft Carlos Rovira 
> het volgende geschreven:
> >
> > Hi Dany,
> >
> > I can give you access to our pre production web site, so you can change
> > text content. Then as you finish others can review and see if all is ok
> or
> > needs any adjustment, etc... then we willl publish it to the public site.
> > If you are ok I can make you and user in private. Just a warning: since
> we
> > use Wordpress that use to be very sensitive to global changes, you should
> > try just to touch "content" (add a section, add rows, add text,...), but
> if
> > you see other changes are needed please first ask about it, since some
> > times this could lead to other derivate problems.
> >
> > thanks!
> >
> >
> >
> > El mar., 30 abr. 2019 a las 16:30, Dany Dhondt
> ()
> > escribió:
> >
> >> Hi,
> >>
> >> Seems the idea of having a faq section on our website is supported.
> >> I’m willing to start such a faq.
> >> How do we tackle this? Do we need a database or keep it plain text?
> Anyone
> >> know of an online tool to manage it?
> >> Who’s managing the website itself?
> >>
> >> Thoughts?
> >>
> >> thx
> >> Dany
> >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>

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


Re: Building a Faq for Royale

2019-04-30 Thread Carlos Rovira
Dany,
please sent me the email I must use privately, since yours in the list puts
"invalid" so I think is not the want you use.
thanks!

El mar., 30 abr. 2019 a las 17:03, Carlos Rovira ()
escribió:

> Hi Dany,
>
> I already shared the actual FAQ link [1], maybe you missed it.
> You can change it whatever you want, just think that changes will need
> approve of the rest.
>
> I'll sent you know credentials in private
>
> thanks!
>
> [1] https://royale.apache.org/faq/
>
> El mar., 30 abr. 2019 a las 16:54, Dany Dhondt ()
> escribió:
>
>> Hi Carlos,
>>
>> That’s ok.
>> Maybe you could setup a Faq section and create the empty base page so I
>> don’t mess anything up?
>>
>> Thx
>> Dany
>>
>> > Op 30 apr. 2019, om 16:42 heeft Carlos Rovira 
>> het volgende geschreven:
>> >
>> > Hi Dany,
>> >
>> > I can give you access to our pre production web site, so you can change
>> > text content. Then as you finish others can review and see if all is ok
>> or
>> > needs any adjustment, etc... then we willl publish it to the public
>> site.
>> > If you are ok I can make you and user in private. Just a warning: since
>> we
>> > use Wordpress that use to be very sensitive to global changes, you
>> should
>> > try just to touch "content" (add a section, add rows, add text,...),
>> but if
>> > you see other changes are needed please first ask about it, since some
>> > times this could lead to other derivate problems.
>> >
>> > thanks!
>> >
>> >
>> >
>> > El mar., 30 abr. 2019 a las 16:30, Dany Dhondt
>> ()
>> > escribió:
>> >
>> >> Hi,
>> >>
>> >> Seems the idea of having a faq section on our website is supported.
>> >> I’m willing to start such a faq.
>> >> How do we tackle this? Do we need a database or keep it plain text?
>> Anyone
>> >> know of an online tool to manage it?
>> >> Who’s managing the website itself?
>> >>
>> >> Thoughts?
>> >>
>> >> thx
>> >> Dany
>> >
>> >
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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


Re: Building a Faq for Royale

2019-04-30 Thread Dany Dhondt
Hi Carlos,

That’s ok.
Maybe you could setup a Faq section and create the empty base page so I don’t 
mess anything up?

Thx
Dany

> Op 30 apr. 2019, om 16:42 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Hi Dany,
> 
> I can give you access to our pre production web site, so you can change
> text content. Then as you finish others can review and see if all is ok or
> needs any adjustment, etc... then we willl publish it to the public site.
> If you are ok I can make you and user in private. Just a warning: since we
> use Wordpress that use to be very sensitive to global changes, you should
> try just to touch "content" (add a section, add rows, add text,...), but if
> you see other changes are needed please first ask about it, since some
> times this could lead to other derivate problems.
> 
> thanks!
> 
> 
> 
> El mar., 30 abr. 2019 a las 16:30, Dany Dhondt ()
> escribió:
> 
>> Hi,
>> 
>> Seems the idea of having a faq section on our website is supported.
>> I’m willing to start such a faq.
>> How do we tackle this? Do we need a database or keep it plain text? Anyone
>> know of an online tool to manage it?
>> Who’s managing the website itself?
>> 
>> Thoughts?
>> 
>> thx
>> Dany
> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira



Re: extending IUIBase with interfaces (was: Re: Version property (was: Let's bump Royale version to 1.0))

2019-04-30 Thread Carlos Rovira
Hi Yishay,

El mar., 30 abr. 2019 a las 13:27, Yishay Weiss ()
escribió:

> It seems to me this is more an AS3 issue than a Royale issue. It would be
> cool to enhance AS to include features such as Mixins, but as long as we
> have a simple single inheritance model the solution you implemented is
> probably optimal.
>
>
If you and others think is the best we can get, maybe we can left as is.
Maybe we can just optimize as Andrew said making that a class to be
implemented by the rest of classes, in that way all share that and changing
just one class will change the 3 implementors at once...


> Also, in my opinion you should always check to see if a said object
> implements an interface, rather than extends a class. If you stick to that
> your solution works fine.
>
>
the problem with this is what I stated before. I expect users to use
UIBase/StyledUIBase classes instead or interface in this class of context.
And the problem in this case is that we can't generalize a code since not
all components will be "StyledUIBase". For me this is the most serious
problem

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


Re: Building a Faq for Royale

2019-04-30 Thread Carlos Rovira
Hi Dany,

I can give you access to our pre production web site, so you can change
text content. Then as you finish others can review and see if all is ok or
needs any adjustment, etc... then we willl publish it to the public site.
If you are ok I can make you and user in private. Just a warning: since we
use Wordpress that use to be very sensitive to global changes, you should
try just to touch "content" (add a section, add rows, add text,...), but if
you see other changes are needed please first ask about it, since some
times this could lead to other derivate problems.

thanks!



El mar., 30 abr. 2019 a las 16:30, Dany Dhondt ()
escribió:

> Hi,
>
> Seems the idea of having a faq section on our website is supported.
> I’m willing to start such a faq.
> How do we tackle this? Do we need a database or keep it plain text? Anyone
> know of an online tool to manage it?
> Who’s managing the website itself?
>
> Thoughts?
>
> thx
> Dany



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


Re: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Carlos Rovira
Hi Mark,

sorry but all you state can be solved with the solution I exposed to you.
There's no need to add an identifier to an SDK since you can add it
yourself from the SDK you downloaded or get by the multiple ways available.
In any of the cases the numbers are not baked into code, but are available
in different parts and you can use defines to bake it into your code and
use it in the same way you use to do in Flex. At least I don't see from
your response that your points will not be covered in that way




El mar., 30 abr. 2019 a las 12:46, Kessler CTR Mark J
() escribió:

> Lol, I can't seem to explain it properly.  Take maven/ant/config files out
> of the equation it doesn't matter for this example.  This has to do with
> getting some identifying information into the official SDK releases.  We
> don't want to pass variables as an SDK user.  We want the official SDK to
> already come packaged with a version number or a build number or a build
> date...
>
>
> Here's the scenario that I would love to see happen:
>
> 1.  SDK user downloads official Royale SDK release and never modifies it.
>
> 2.  SDK User compiles their app using official SDK and references an
> official SDK property that contains the SDK identifier already built in
> it.  Meaning I should be able to code complete off of the SDK and find
> something that already exists and could return me an official identifier.
>
>
> -Mark K
>
> -Original Message-
> From: Carlos Rovira [mailto:carlosrov...@apache.org]
> Sent: Monday, April 29, 2019 1:14 PM
> To: dev@royale.apache.org
> Subject: [Non-DoD Source] Re: Version property (was: Let's bump Royale
> version to 1.0)
>
> ok,
>
> we do the following in maven for other needs so this will be valid for you
> too:
>
> in your maven properties.
>
> 0.9.6-OR-WHATEVER
>
> 
> org.apache.royale.compiler
> royale-maven-plugin
> true
> 
> ...
> 
> 
> BUILD::royaleVersion
> '"${royale.framework.version}"'
> 
> ...
> 
> ...
>
>
> defines can be done in ANT, asconfigc, config.xml
>
> Then in AS3 or MXML
>
> /**
> * ROYALE VERSION NUMBER
> */
> private static var _royaleVersion :String = BUILD::royaleVersion;
>
> So now you can use in any place you want
>
> HTH
>
> Carlos
>
>

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


Building a Faq for Royale

2019-04-30 Thread Dany Dhondt
Hi,

Seems the idea of having a faq section on our website is supported.
I’m willing to start such a faq. 
How do we tackle this? Do we need a database or keep it plain text? Anyone know 
of an online tool to manage it?
Who’s managing the website itself?

Thoughts?

thx
Dany

Build failed in Jenkins: royale-asjs_MXTests #734

2019-04-30 Thread Apache Royale CI Server
See 


--
[...truncated 2.04 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 


RE: extending IUIBase with interfaces (was: Re: Version property (was: Let's bump Royale version to 1.0))

2019-04-30 Thread Yishay Weiss
It seems to me this is more an AS3 issue than a Royale issue. It would be cool 
to enhance AS to include features such as Mixins, but as long as we have a 
simple single inheritance model the solution you implemented is probably 
optimal.



I personally wouldn’t worry too much about code duplication of one liners in 
framework code. The average user isn’t going to care.



Also, in my opinion you should always check to see if a said object implements 
an interface, rather than extends a class. If you stick to that your solution 
works fine.




From: Carlos Rovira 
Sent: Tuesday, April 30, 2019 12:29:10 PM
To: dev@royale.apache.org
Subject: Re: extending IUIBase with interfaces (was: Re: Version property (was: 
Let's bump Royale version to 1.0))

Hi Andrew,

thanks for your thoughts. One of the main problems here that I didn't put
on my email is that you loose the opportunity to ask if the components is a
"StyledUIBase", since we are "bifurcating" the code when implement in Group
and DataContainerBase and others the interface IClassSelectorLitsSupport.
You can ask for "IClassSelectorLitsSupport", but you probably would want
just ask for StyledUIBase.

El mar., 30 abr. 2019 a las 8:14, Frost, Andrew ()
escribió:

> Hi Carlos
>
> Isn't this similar to the challenge that Adobe had with EventDispatcher?
> which I think is why there are two possibilities:
> a) derive from EventDispatcher
> b) implement IEventDispatcher
>
> In the second case, you have to create an instance of EventDispatcher
> within your class, and then you have to implement the IEventDispatcher
> functions with calls to the EventDispatcher object. So it's not
> zero-effort, but it's not too bad (and probably the best option you can get
> without multiple inheritance..). Yes there's repeated code, but it's
> limited to one line per function so is relatively easy to copy/paste.
>

This solution could save code duplication if method bodies are long. In
this case method bodies are similar, so I'm afraid will not apply here to
make a significant difference


>
> Not 100% sure if the same approach can be applied in the scenario you're
> talking about, but that might help perhaps..? So the functionality you want
> to repeat would go into a class ("ClassSelectorListSupportImpl"?) and you
> create one of these in each of the classes that derive from
> UIBase/Group/etc and implement IClassSelectorLitsSupport.
>

Yes, this could be similar to before and more elegant, but the problem is
the same I put before.


>
> Some alternatives perhaps:
> - I'm also wondering whether you could create a helper function that
> actually adjusted the class prototype and programmatically added the
> necessary functions to your classes... ?
> - the repeated functionality could be put into other .as files and just
> 'included' in the classes? I know, this is a major hack, but I've seen it
> done :-(
>
>
hehe, prefer not to go that way ;-)

What I want to expose here is that beads are a good composition way and
love it. But we still has a problem in cases like this.

Thinking on this and seeing how the overall picture is now, I think the
actual solution is not helping PAYG at all. Maybe we should see if we can
add IClassSelectorLitsSupport to UIBase and remove
IClassSelectorLitsSupport implementations (StyledUIBase and the rest).
We'll be saving code, and Basic components will have access to that API
that is tiny and seems finaly make sense to be in UIBase.

At least I see other frameworks out there have it's own "addClass",
"removeClass", etc... as part of it's core, since nowadays the use of CSS
selectors is crucial and people will needed always (and that's the key for
PAYG).

Thoughts?



>
> Hope it helps..
>
> thanks
>
>Andrew
>
>
>
> -Original Message-
> From: Carlos Rovira [mailto:carlosrov...@apache.org]
> Sent: 29 April 2019 18:04
> To: dev@royale.apache.org
> Subject: [EXTERNAL] extending IUIBase with interfaces (was: Re: Version
> property (was: Let's bump Royale version to 1.0))
>
> Hi Alex,
>
> initial problem is: I want to add to all jewel components (that use to
> have UIBase as common class) a new interface and implement the methods. In
> concrete interface is: IClassSelectorListSupport
>
> So the expected result should be to make all Jewel components implement
> IClassSelectorListSupport, but to avoid repeat code in all classes we need
> a root for all the components.
>
> Perfect point would be UIBase, but we can't add at that point for PAYG
> reasons.
>
> Current solution in Jewel is to create StyledUIBase that is
>
> public class StyledUIBase extends UIBase implements
> IClassSelectorListSupport
>
> but this makes other classes like jewel Group that extend html Group have
> UIBase in the hierarchical chain instead StyledUIBase, so we need to make
> Group as this:
>
> public class Group extends org.apache.royale.html.Group implements
> IClassSelectorListSupport
>
> same for
>
> public class DataContainerBase ext

RE: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0)

2019-04-30 Thread Kessler CTR Mark J
Lol, I can't seem to explain it properly.  Take maven/ant/config files out of 
the equation it doesn't matter for this example.  This has to do with getting 
some identifying information into the official SDK releases.  We don't want to 
pass variables as an SDK user.  We want the official SDK to already come 
packaged with a version number or a build number or a build date...


Here's the scenario that I would love to see happen:

1.  SDK user downloads official Royale SDK release and never modifies it.

2.  SDK User compiles their app using official SDK and references an official 
SDK property that contains the SDK identifier already built in it.  Meaning I 
should be able to code complete off of the SDK and find something that already 
exists and could return me an official identifier.


-Mark K

-Original Message-
From: Carlos Rovira [mailto:carlosrov...@apache.org] 
Sent: Monday, April 29, 2019 1:14 PM
To: dev@royale.apache.org
Subject: [Non-DoD Source] Re: Version property (was: Let's bump Royale version 
to 1.0)

ok,

we do the following in maven for other needs so this will be valid for you
too:

in your maven properties.

0.9.6-OR-WHATEVER


org.apache.royale.compiler
royale-maven-plugin
true

...


BUILD::royaleVersion
'"${royale.framework.version}"'

...

...


defines can be done in ANT, asconfigc, config.xml

Then in AS3 or MXML

/**
* ROYALE VERSION NUMBER
*/
private static var _royaleVersion :String = BUILD::royaleVersion;

So now you can use in any place you want

HTH

Carlos



Re: Let's bump Royale version to 1.0 -- submit your bid for assistance to the group by Friday May 3

2019-04-30 Thread Carlos Rovira
Hi Dany,

El mar., 30 abr. 2019 a las 5:55, Dany Dhondt ()
escribió:

> Hi Justin,
>
> As much as I would like to write an article on Royale vs. competitors, I
> can’t do so at this moment because I don’t have enough Royale knowledge
> yet. But there are things I could point at so that the Royale team can
> formulate answers.
> Here are some questions and ideas I have which could be addressed:
>
> 1. Royale blog
> On our site, there is a section called ‘blog’. Shouldn’t we rename that?
> To me, a blog is something of the past. ‘Examples’ or ‘Code snippets’ or
> something similar would be better.
>

I'm ok with this, but we must get the right word. Currently we use "blog"
for:

* announcements and notify releases
* articles
* examples (ala Peter Dehaan's flex blog examples style)

So "Examples" is not right to me since we are posting announcements, while
articles could be a more elaborated writing about some concept that could
have examples.

I'm ok to change it if others want if we found a label more generic and
modern



>
> 2. Faq
> We definitely need a faq. Common answers to basic questions can go there.
> Also, when our StackOverflow database gets rolling, we can put links to our
> faq there.
>

Yeah! I thought on this too. This could be a good point to work on. There's
already a page (link on footer), with some points a put when created the
page.
Making a good FAQ page would be great. And there's many things and sections
we can add to it. This maybe could be a good point for you to start if you
want


>
> 3. (Re)rendering
> One of the core principles of React is that it uses a virtual dom. You
> never write to the dom directly. React does that for you. That’s why JQuery
> doesn’t match at all with React. The main advantage of this, is that only
> those DOM nodes get updated which actually change, making React really
> fast. How does Royale tackle this? Can someone explain this in an easy to
> understand way?
>

I think Harbs explained this, but maybe we should have a more compressive
data about this. Maybe if Harbs is very busy right now Alex could give us a
paragraph or something about this.
For what I understand Royale is more fast than React, but don't have the
proper words or concepts ready to explain this in a more technical way.


> 4. Managing (global) state
> Updating a component in React is done by calling setState() and passing an
> object to that method. That’s all very well and simple in small projects.
> Passing state from parents to children is straightforward. You just pass
> in state as props to underlying components. The other way around though is
> hard, very hard. Handling global state is done by implementing 3rd party
> technologies like Redux, MobX or recently by implementing React hooks.
> I believe that Royale binding mechanisms could be superior to this. So the
> question here: how does Royale handles global sta
>

I think you refer here how to deal with global models in apps in opposite
to models of single components.
In flex we had frameworks like Swiz, Parsley and more.
In Royale PureMVC is already working, although for example I'm not using it
in out real app yet. But I think this is what you have right now to use as
today.

We plan to make a new library based on metadata to mimic the most important
functionality that we had in Swiz, I refer to [Dispatcher],
[EventDispatcher] and [Inject]
This is a requisite for our next real app iteration, but still can say when
will start to wok on that, only can say that hopefully will be soon and
will be donated to Apache Royale


>
> 5. Justin, at some point in your message, you talk about ‘command line
> nonsense’. I believe you’re right and wrong at the same time.
> Right because indeed, learning React is far more than learning one
> technology. You have to dig through npm, node, JSX, typescript (if you want
> strong typing), webpack/rollup, babel, … and in the end, most of us use
> create-react-app just to hide all those configurations. BUT
> Wrong because there is a massive open source community where you can find
> almost anything you might need in your project. Building a modern web app
> is all about combining existing code to create your application.
> That brings me to this question: is it possible to embed existing pure
> javascript components into Royale?
>

yes! I think I need to make soon a blog example about this. For example in
Tour de Jewel, the code coloring is done by another JS script calling its
methods. Other way is wrapping in Royale classes like we did with Material
Design Lite (MDL UI set). I think there's more with typedefs, but I need to
learn more from this. I'll ask Alex/Harbs to explain more about this.


> An example: one of the most crucial components in any admin application is
> a calendar. In my Flex days, I had to spend hundreds of dollars to get a
> decent calendar component. In React, I use fullcalendar which is a great
> calendar/sheduling javascript component. Creating a calendar component from
> 

Re: extending IUIBase with interfaces (was: Re: Version property (was: Let's bump Royale version to 1.0))

2019-04-30 Thread Carlos Rovira
Hi Andrew,

thanks for your thoughts. One of the main problems here that I didn't put
on my email is that you loose the opportunity to ask if the components is a
"StyledUIBase", since we are "bifurcating" the code when implement in Group
and DataContainerBase and others the interface IClassSelectorLitsSupport.
You can ask for "IClassSelectorLitsSupport", but you probably would want
just ask for StyledUIBase.

El mar., 30 abr. 2019 a las 8:14, Frost, Andrew ()
escribió:

> Hi Carlos
>
> Isn't this similar to the challenge that Adobe had with EventDispatcher?
> which I think is why there are two possibilities:
> a) derive from EventDispatcher
> b) implement IEventDispatcher
>
> In the second case, you have to create an instance of EventDispatcher
> within your class, and then you have to implement the IEventDispatcher
> functions with calls to the EventDispatcher object. So it's not
> zero-effort, but it's not too bad (and probably the best option you can get
> without multiple inheritance..). Yes there's repeated code, but it's
> limited to one line per function so is relatively easy to copy/paste.
>

This solution could save code duplication if method bodies are long. In
this case method bodies are similar, so I'm afraid will not apply here to
make a significant difference


>
> Not 100% sure if the same approach can be applied in the scenario you're
> talking about, but that might help perhaps..? So the functionality you want
> to repeat would go into a class ("ClassSelectorListSupportImpl"?) and you
> create one of these in each of the classes that derive from
> UIBase/Group/etc and implement IClassSelectorLitsSupport.
>

Yes, this could be similar to before and more elegant, but the problem is
the same I put before.


>
> Some alternatives perhaps:
> - I'm also wondering whether you could create a helper function that
> actually adjusted the class prototype and programmatically added the
> necessary functions to your classes... ?
> - the repeated functionality could be put into other .as files and just
> 'included' in the classes? I know, this is a major hack, but I've seen it
> done :-(
>
>
hehe, prefer not to go that way ;-)

What I want to expose here is that beads are a good composition way and
love it. But we still has a problem in cases like this.

Thinking on this and seeing how the overall picture is now, I think the
actual solution is not helping PAYG at all. Maybe we should see if we can
add IClassSelectorLitsSupport to UIBase and remove
IClassSelectorLitsSupport implementations (StyledUIBase and the rest).
We'll be saving code, and Basic components will have access to that API
that is tiny and seems finaly make sense to be in UIBase.

At least I see other frameworks out there have it's own "addClass",
"removeClass", etc... as part of it's core, since nowadays the use of CSS
selectors is crucial and people will needed always (and that's the key for
PAYG).

Thoughts?



>
> Hope it helps..
>
> thanks
>
>Andrew
>
>
>
> -Original Message-
> From: Carlos Rovira [mailto:carlosrov...@apache.org]
> Sent: 29 April 2019 18:04
> To: dev@royale.apache.org
> Subject: [EXTERNAL] extending IUIBase with interfaces (was: Re: Version
> property (was: Let's bump Royale version to 1.0))
>
> Hi Alex,
>
> initial problem is: I want to add to all jewel components (that use to
> have UIBase as common class) a new interface and implement the methods. In
> concrete interface is: IClassSelectorListSupport
>
> So the expected result should be to make all Jewel components implement
> IClassSelectorListSupport, but to avoid repeat code in all classes we need
> a root for all the components.
>
> Perfect point would be UIBase, but we can't add at that point for PAYG
> reasons.
>
> Current solution in Jewel is to create StyledUIBase that is
>
> public class StyledUIBase extends UIBase implements
> IClassSelectorListSupport
>
> but this makes other classes like jewel Group that extend html Group have
> UIBase in the hierarchical chain instead StyledUIBase, so we need to make
> Group as this:
>
> public class Group extends org.apache.royale.html.Group implements
> IClassSelectorListSupport
>
> same for
>
> public class DataContainerBase extends
> org.apache.royale.core.DataContainerBase implements
> IClassSelectorListSupport
>
> This make we have 3 classes that are duplicating the same exact code
> implementing in the same maner addClass, removeClass, etc..
>
> what can we do for this cases?
>
> Hope is more clear now,
>
> thanks
>
>
>
> El lun., 29 abr. 2019 a las 17:41, Alex Harui ()
> escribió:
>
> >
> > @Carlos, I couldn't understand your scenario.  Feel free to start a
> > separate thread on it.  The key aspect, as a guess, is trying to avoid
> > code that assumes that an instance is a subclass of a particular base
> > class instead of an implementation of an interface.
> >
> > HTH,
> > -Alex
> >
> > On 4/29/19, 7:29 AM, "Carlos Rovira"  wrote:
> >
> > @Mark, if you use Maven, then artifacts in the poms a

Re: StackOverflow tips

2019-04-30 Thread Carlos Rovira
Hi Dany

as I posted in other thread we just go "apache-royale" tag, so can start
posting as you want
I'll try to do it as well :)

El lun., 29 abr. 2019 a las 21:23, Dany Dhondt ()
escribió:

> Yes, you’re right.
>
>
> Verstuurd vanaf mijn iPhone
>
> > Op 29 apr. 2019 om 20:20 heeft Carlos Rovira 
> het volgende geschreven:
> >
> > Hi Danny,
> >
> > I think "as3" and "mxml" should be on itself. if people wants to relate
> to
> > Royale they should add "apache-royale", if not I think we'll end with
> many
> > tags, and we should try to "concentrate" knowledge as much as possible.
> >
> >
> > El lun., 29 abr. 2019 a las 19:24, Dany Dhondt
> ()
> > escribió:
> >
> >> Great idea!
> >> If we have our tag(s), we’re on our way.
> >> And what about ‘royale-mxml’ and ‘royale-as3’?
> >>
> >> Dany
> >>
> >>> Op 29 apr. 2019, om 19:18 heeft Carlos Rovira  >
> >> het volgende geschreven:
> >>>
> >>> Should I ask on our twitter account for someone that could create stack
> >>> over flow "apache-royals" tag?
> >>> I can share that we want to start participating there...
> >>> thoughts?
> >>>
> >>> El lun., 29 abr. 2019 a las 19:06, Dany Dhondt
> >> ()
> >>> escribió:
> >>>
>  Hi, has anyone more than 1500 reputation points on SO?
> 
>  To create tags on SO you need 1500 reps [1]
>  How to gain reputation [2]
>  Answering your own question [3]
> 
> 
>  [1]
> 
> >>
> https://meta.stackexchange.com/questions/103676/how-to-add-a-new-tag-on-stack-overflow
>  [2] https://stackoverflow.com/help/whats-reputation
>  [3] https://stackoverflow.com/help/self-answer
> >>>
> >>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>

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


Let's bump Royale version to 1.0

2019-04-30 Thread Piotr Zarzycki
Hi Guys,

Thank you so far for a great discussion. I see that there is an obvious
needs to improve documentation the most.

I would like to express my personal feelings regarding releasing anything
what is not 1.0 after 0.9.6. Based on my experience with this project I
don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will take less than
6-8 months form now on. Even if we will have automatic release process I
cannot believe that is going to happen in a less time than I mention.

Why I'm thinking like that:
- Justin just provided to the contributors generous offer - it's been
couple of days and there is absolutely no response.
- I've seen as part of the responses some concrete issues towards code in
SDK. I don't believe that there will be anyone who fix them UNLESS someone
need that stuff in his application which has been under development in his
daily job. Which leads me to conclusion that we will wait months before
anything from that list will be fixed.

How Royale is going on right now?
In my original email I expressed that it is enough good to bump it to 1.0 -
which gets us more credibility and push us to a better light. I got clear
responses from community that the only thing which is in the way of to 1.0
is documentation.

W have one production app in Royale, another one has been created by
Carlos. I'm working on the third one. Justin mention fourth one which I'm
reviewing right now because it is written in Flex - it looks there won't be
problem with porting to Royale. To me it is enough proof that Royale is as
good as is to expose itself for more wider audience. Because this is
exactly what will happen when we bump to that magic 1.0.
People on this project are talking about community, my proposition to bump
Royale to 1.0 is towards community with hope that it helps grow thanks to
that step. With hope that finally I will see on the list more people, with
hope that I will see someone who doesn't have background in ActionScript,
but was curious about the project.

In this thread I don't see rejection to my idea, so I'm going to work to
improve some areas and start release with bumped version to 1.0, whether it
will be after 0.9.7, 0.9.8 it doesn't matter - What's really matter is that
we are not facing in current version any walls during development, so this
is enough to me giving that framework 1.0.

Thanks,
Piotr

pon., 29 kwi 2019 o 19:44 Carlos Rovira 
napisał(a):

> Hi Justin,
>
> great initiative, but some thoughts:
>
> 1.- As Olaf said, Alex or I are just two more devs, so we can say what
> should we do. That's the apache way! :), only work towards the goal and
> giving advice to make things happen. We decisions are community managed
>
> 2.- I think is very generous offer so people can contribute and earn some
> money and a great plan,
>
> Some things you should take into account for the rewarding plan:
>
> * We just get results of the poll about releasing published few minutes
> ago. Seems people wants to focus docs first and release second (from 61
> votes).
> * In the other hand, I see Alex is still fighting with the release process.
> He stated that probably this week he will have the process ready to be
> tested by someone.
> If he get to that point that will be awesome, and hope others could be the
> first one in try to "push the button". If that works ok, we'll have a 0.9.6
> release (I think the one by Alex), and then a 0.9.7 (by that new release
> manager). At that point, I figure we can plan 0.9.8, 0.9.9 and Finlay 1.0.
> For me release should happen at least from month to month. have sense?
>
> Just my my thoughts, but hope other want to share here what they can do and
> work to earn some money too! :)
>
>
>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
> >
> >
>


-- 

Piotr Zarzycki

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