Build failed in Jenkins: royale-asjs_MXTests #723

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

Build failed in Jenkins: royale-asjs_MXTests #722

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

Release Step 003 Succeeded

[Apache Royale CI Server]

1. If you are releasing the utils jars (compiler-jburg-types and 
compiler-build-tools), Run:
  ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
 ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Release Step 002a Succeeded

[Apache Royale CI Server]

Continue on to Release Step 003

Release Step 002 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands:
git push
git push origin org.apache.royale.compiler-0.9.6-rc1

You will need your Apache/Github username and 2FA token.

Release Step 001a Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following 
commands:
git push

You will need your Apache/Github username and 2FA token.

Release Step 001 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands:
git push
git checkout release/0.9.6
git push -u origin release/0.9.6

You will need your Apache/Github username and 2FA token.

Re: Let's bump Royale version to 1.0

[Carlos Rovira]

That's great Angelo! :)

El vie., 26 abr. 2019 a las 13:06, Angelo Lazzari ()
escribió:

> yes, I always send video to my client, it is a really good way to explain
> new process and teach things...
>
> I will write a new email about the video course...
>
> Angelo
>
> On Fri, Apr 26, 2019 at 11:39 AM Carlos Rovira 
> wrote:
>
> > Hi Angelo, that's great! :)
> >
> > any help here is very appreciated.
> >
> > Share in a new mail a concrete contribution before starting to work on
> it,
> > so we can know about it and help you on the task so your work fit
> perfectly
> > in the overall picture.
> >
> > I'd like to create videos too, and people asked about it in facebook and
> > twitter. Do you have skills in creating videos?
> >
> >
> >
> > El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari (<
> > lazzari.ang...@gmail.com>)
> > escribió:
> >
> > > Yes, i can give some slots to help with documentation or example
> project
> > or
> > > so... I think tutorial videos could be help to understand rapidly the
> > > platform and could help new user to get ready in a few hours to start
> > build
> > > their project.
> > >
> > > Angelo
> > >
> > > On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira <
> carlosrov...@apache.org>
> > > wrote:
> > >
> > > > Agree with latest comments.
> > > >
> > > > I think we should work in docs and ease the start of new users to
> > target
> > > > 1.0
> > > > And in the process fix some few things (i.e: don't want to reach 1.0
> > with
> > > > Jewel Table in its current state and API)
> > > >
> > > > What do you think?
> > > >
> > > > If you all agree could you think on how to contribute to that effort?
> > Can
> > > > we have as a near goal to bring 1.0 planing ourselves to donate some
> > > hours
> > > > to Apache Royale to make this happen? If some of us help in the
> current
> > > > state I think we can get to it sooner.
> > > >
> > > > Thanks
> > > >
> > > >
> > > > El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> > > > lazzari.ang...@gmail.com>)
> > > > escribió:
> > > >
> > > > > I am completely agree with Olaf: start using a new platform where
> the
> > > > > documentation is not complete, clean and updated it is a really bad
> > > > > thing...and it would be a potential reason to increase the
> difficulty
> > > to
> > > > > adopt the platform...
> > > > >
> > > > > Angelo
> > > > >
> > > > > El vie., 26 abr. 2019 8:54, Olaf Krueger 
> > > > escribió:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Basically, I think it's important to provide a great developer
> > > > > experience.
> > > > > > IMO, that's more important than trying to implement missing
> > features.
> > > > > >
> > > > > > One thing to achieve this is documentation of course.
> > > > > > Thanks to all of you there already exist a lot of docs, but it
> > feels
> > > a
> > > > > bit
> > > > > > messy because they are hosted at different places, e.g.:
> > > > > >
> > > > > > - royale-docs repo
> > > > > > - royale-asjs wiki
> > > > > > - royale-asjs Readme
> > > > > > - https://royale.apache.org
> > > > > > - ...?
> > > > > >
> > > > > > As a user, it's hard to get an overview of what is available...
> and
> > > > > where.
> > > > > > Maybe it's a good idea to consolidate the docs before releasing
> > 1.0.
> > > > > >
> > > > > > Just my 2 cents,
> > > > > > Olaf
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > > Angelo Lazzari
> > > mobile: +34 683 137 087
> > > mail: lazzari.ang...@gmail.com
> > >
> > >
> > >
> > >
> >
> 
> > > Verify the correspondence of the addressee; otherwise, notify that to
> the
> > > sender and, conscious of the responsibility for the undue use, destroy
> > the
> > > message and its copies.
> > >
> > >
> >
> 
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
> Angelo Lazzari
> mobile: +34 683 137 087
> mail: lazzari.ang...@gmail.com
>
>
>
> 
> Verify the correspondence of the addressee; otherwise, notify that to the
> sender and, conscious of the responsibility for the undue use, destroy the
> message and its copies.
>
> 
>


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

Re: Version property (was: Let's bump Royale version to 1.0)

[Alex Harui]

On 4/26/19, 4:29 AM, "Kessler CTR Mark J"  
wrote:

> So far, we have not had the release scripts properly generate the right 
version number for the NPM artifacts.


This spurred a question for me.  Is there a way to find out what version 
number the SDK binaries are in code for Royale?  Sort of like the Flex SDK 
mx.core.FlexVersion or at least a build date?

Not at this time.  IMO, runtime versioning wasn't worth the cost of all of 
those strings and code in the production app.  Also, Royale was designed from 
the beginning to try to be "version-agnostic".  By using loose-coupling via 
Beads/PAYG/ValuesManager and lots of interfaces instead of direct class 
references, there shouldn't be a need to deal with version incompatibilities at 
runtime like Flex did with the Marshall Plan and FlexVersion and more.

Flex had to care about version incompatibilities because the fundamental base 
classes were not loosely-coupled.  Flex HelloWorld was 128K not just because 
UIComponent was huge, but because UIComponent pulled in other classes as 
init-time strongly-coupled dependencies.  A good thing to think about as you 
write Royale framework code is, "can every dependency be easily replaced"?

After we hit 1.0 (and hopefully find some volunteers to write regression 
tests), then new APIs to existing classes will need to be considered carefully 
and implemented in extensions.  So there will be some extension of IUIBase that 
has some new API instead of adding new APIs to IUIBase.  I have a personal 
preference to use long names instead of numbers, so the extension will 
hopefully be called IUIBaseWithWhatever instead of IUIBase2.

If you are asking about build-time versioning, we haven't done anything there 
either.  As long as there is no impact on production apps I think it is fine 
for folks to contribute something if there is a need.

My 2 cents,
-Alex


-Mark K

-Original Message-
From: Alex Harui [mailto:aha...@adobe.com.INVALID]
Sent: Friday, April 26, 2019 2:44 AM
To: dev@royale.apache.org
Subject: [Non-DoD Source] Re: Let's bump Royale version to 1.0

I do not have an opinion on what technical/marketing criteria we use to 
decide which release to call 1.0.  I'm not working directly with 
users/customers.

I do not currently have time/energy/budget to work on any of the things 
folks think need to be done to get to 1.0 and barely have enough time to work 
on getting the next release out.  So someone else will have to supply the 
time/energy/budget to get these tasks done.

I do have an opinion based on a practical aspect.  So far, we have not had 
the release scripts properly generate the right version number for the NPM 
artifacts.  That's why we've jumped from 0.9.4 to 0.9.6 and skipped 0.9.5.  So 
I would say we should not call this next release 1.0 and wait until the release 
automation can correctly version all artifacts with the right version number 
before we pick one to call 1.0.  With any luck I'll get the automation running 
next week and will ask for someone to volunteer to test drive it.

-Alex

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

I’m all for buikding a knowledge base in Stack Overflow! The mailing list 
should only be used for developing Royale. Questions about using Royale should 
go to SO

The competitors of Royale are React, Vue, Angular, ...
Lots of developers are now used to those workflows. 
In case of React, create-react-app sets you up with a brand new, ready to go 
project in less than 30 seconds. That should be a benchmark for Royale imo. 

Dany


Verstuurd vanaf mijn iPhone

> Op 26 apr. 2019 om 12:42 heeft Frost, Andrew  het 
> volgende geschreven:
> 
> One other thought ... currently the way people ask for support is via these 
> mailing lists. Which are okay but I'm always conscious that I'm potentially 
> spamming people, plus the volume of mails is such that I have a rule to push 
> all these into a folder that I then review every day or two..
> 
> But if I want to find something out, I tend not to go search the mailing 
> list, I tend to search online. Looking through mailing list threads isn't the 
> easiest (and search engines don't necessarily pick things up from them very 
> well) but a major source of support is Stack Overflow... I use this a lot 
> with my other work and there's a lot of information there.
> 
> Apache Royale doesn't appear to have a tag; when I search for "royale" all I 
> got was stuff about "Clash Royale"; there are however 8 questions with 
> "flexjs" tags.
> 
> But wouldn't it be good for people to add questions and to contribute answers 
> there, both from the user perspective and perhaps also the dev perspective? 
> Would be interested in people's thoughts... (and perhaps I'll have to dig out 
> my SO credentials to start contributing there)
> 
> thanks
> 
>  Andrew
> 
> 
> -Original Message-
> From: Carlos Rovira [mailto:carlosrov...@apache.org] 
> Sent: 26 April 2019 10:39
> To: dev@royale.apache.org
> Subject: [EXTERNAL] Re: Let's bump Royale version to 1.0
> 
> Hi Angelo, that's great! :)
> 
> any help here is very appreciated.
> 
> Share in a new mail a concrete contribution before starting to work on it, so 
> we can know about it and help you on the task so your work fit perfectly in 
> the overall picture.
> 
> I'd like to create videos too, and people asked about it in facebook and 
> twitter. Do you have skills in creating videos?
> 
> 
> 
> El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari ()
> escribió:
> 
>> Yes, i can give some slots to help with documentation or example 
>> project or so... I think tutorial videos could be help to understand 
>> rapidly the platform and could help new user to get ready in a few 
>> hours to start build their project.
>> 
>> Angelo
>> 
>> On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira 
>> 
>> wrote:
>> 
>>> Agree with latest comments.
>>> 
>>> I think we should work in docs and ease the start of new users to 
>>> target
>>> 1.0
>>> And in the process fix some few things (i.e: don't want to reach 1.0 
>>> with Jewel Table in its current state and API)
>>> 
>>> What do you think?
>>> 
>>> If you all agree could you think on how to contribute to that 
>>> effort? Can we have as a near goal to bring 1.0 planing ourselves to 
>>> donate some
>> hours
>>> to Apache Royale to make this happen? If some of us help in the 
>>> current state I think we can get to it sooner.
>>> 
>>> Thanks
>>> 
>>> 
>>> El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
>>> lazzari.ang...@gmail.com>)
>>> escribió:
>>> 
 I am completely agree with Olaf: start using a new platform where 
 the documentation is not complete, clean and updated it is a 
 really bad thing...and it would be a potential reason to increase 
 the difficulty
>> to
 adopt the platform...
 
 Angelo
 
 El vie., 26 abr. 2019 8:54, Olaf Krueger 
>>> escribió:
 
> Hi,
> 
> Basically, I think it's important to provide a great developer
 experience.
> IMO, that's more important than trying to implement missing features.
> 
> One thing to achieve this is documentation of course.
> Thanks to all of you there already exist a lot of docs, but it 
> feels
>> a
 bit
> messy because they are hosted at different places, e.g.:
> 
> - royale-docs repo
> - royale-asjs wiki
> - royale-asjs Readme
> - 
> https://clicktime.symantec.com/3SEvxFs2HbjNAgsLBEtNLr17Vc?u=http
> s%3A%2F%2Froyale.apache.org
> - ...?
> 
> As a user, it's hard to get an overview of what is available... 
> and
 where.
> Maybe it's a good idea to consolidate the docs before releasing 1.0.
> 
> Just my 2 cents,
> Olaf
> 
> 
> 
> 
> 
> 
> 
> --
> Sent from: 
> https://clicktime.symantec.com/3LM5ngUtumonkv3VTyrZRJ77Vc?u=http
> %3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F
> 
 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%
>>> 2F%2Fabout.me%2Fcarlosrovira
>>> 
>> 
>> 

Build failed in Jenkins: royale-asjs_MXTests #721

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

[Kessler CTR Mark J]

Well imagine a new user blindly walking into the site.They go to the 
root of the site [1] and see that nice orange "getting started" button.  
Clicking on that takes you to the getting started page [2].   It has a link to 
the download page and it has IDE links which is good.  It would be nice if we 
added a few more links to things like examples and the ASDOC references.  Then 
I would feel like it has  a good start.   

 Now the first thing that happens is we are sending people away from the 
main Royale site and onto GitHub to look up the IDE information.  Are we using 
that as our main information sources now?  I feel like we should keep 
everything on one place for information.  Whether that is on apache or github 
doesn't matter as long as it's consistent.



[1] https://royale.apache.org/
[2] https://royale.apache.org/getting-started/


-Mark K

-Original Message-
From: Carlos Rovira [mailto:carlosrov...@apache.org] 
Sent: Friday, April 26, 2019 4:52 AM
To: dev@royale.apache.org
Subject: [Non-DoD Source] Re: Let's bump Royale version to 1.0

Hi Mark,

most of the points in your list should already done in the website, like
download SDK, minimum requerimiento, IDE's available, examples of using
components (this is blog examples and need more, but I'm the only one
pushing this examples, this could be easy to solve if others want to commit
blog post in the same way I did for new examples. The template is already
done, or I can help in publishing it if people donates content.

Other need more work: Starting a new App, ASDoc needs to be completed with
new APIs, since right now is just a sub set and in this form is not useful
for others.

Latest point is complicated to have this days, since it implies people
using Royale and sharing different techniques of integration.

Version property (was: Let's bump Royale version to 1.0)

[Kessler CTR Mark J]

> So far, we have not had the release scripts properly generate the right 
> version number for the NPM artifacts.


This spurred a question for me.  Is there a way to find out what version number 
the SDK binaries are in code for Royale?  Sort of like the Flex SDK 
mx.core.FlexVersion or at least a build date?


-Mark K

-Original Message-
From: Alex Harui [mailto:aha...@adobe.com.INVALID]
Sent: Friday, April 26, 2019 2:44 AM
To: dev@royale.apache.org
Subject: [Non-DoD Source] Re: Let's bump Royale version to 1.0

I do not have an opinion on what technical/marketing criteria we use to decide 
which release to call 1.0.  I'm not working directly with users/customers.

I do not currently have time/energy/budget to work on any of the things folks 
think need to be done to get to 1.0 and barely have enough time to work on 
getting the next release out.  So someone else will have to supply the 
time/energy/budget to get these tasks done.

I do have an opinion based on a practical aspect.  So far, we have not had the 
release scripts properly generate the right version number for the NPM 
artifacts.  That's why we've jumped from 0.9.4 to 0.9.6 and skipped 0.9.5.  So 
I would say we should not call this next release 1.0 and wait until the release 
automation can correctly version all artifacts with the right version number 
before we pick one to call 1.0.  With any luck I'll get the automation running 
next week and will ask for someone to volunteer to test drive it.

-Alex

Re: Let's bump Royale version to 1.0

[Angelo Lazzari]

yes, I always send video to my client, it is a really good way to explain
new process and teach things...

I will write a new email about the video course...

Angelo

On Fri, Apr 26, 2019 at 11:39 AM Carlos Rovira 
wrote:

> Hi Angelo, that's great! :)
>
> any help here is very appreciated.
>
> Share in a new mail a concrete contribution before starting to work on it,
> so we can know about it and help you on the task so your work fit perfectly
> in the overall picture.
>
> I'd like to create videos too, and people asked about it in facebook and
> twitter. Do you have skills in creating videos?
>
>
>
> El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari (<
> lazzari.ang...@gmail.com>)
> escribió:
>
> > Yes, i can give some slots to help with documentation or example project
> or
> > so... I think tutorial videos could be help to understand rapidly the
> > platform and could help new user to get ready in a few hours to start
> build
> > their project.
> >
> > Angelo
> >
> > On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira 
> > wrote:
> >
> > > Agree with latest comments.
> > >
> > > I think we should work in docs and ease the start of new users to
> target
> > > 1.0
> > > And in the process fix some few things (i.e: don't want to reach 1.0
> with
> > > Jewel Table in its current state and API)
> > >
> > > What do you think?
> > >
> > > If you all agree could you think on how to contribute to that effort?
> Can
> > > we have as a near goal to bring 1.0 planing ourselves to donate some
> > hours
> > > to Apache Royale to make this happen? If some of us help in the current
> > > state I think we can get to it sooner.
> > >
> > > Thanks
> > >
> > >
> > > El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> > > lazzari.ang...@gmail.com>)
> > > escribió:
> > >
> > > > I am completely agree with Olaf: start using a new platform where the
> > > > documentation is not complete, clean and updated it is a really bad
> > > > thing...and it would be a potential reason to increase the difficulty
> > to
> > > > adopt the platform...
> > > >
> > > > Angelo
> > > >
> > > > El vie., 26 abr. 2019 8:54, Olaf Krueger 
> > > escribió:
> > > >
> > > > > Hi,
> > > > >
> > > > > Basically, I think it's important to provide a great developer
> > > > experience.
> > > > > IMO, that's more important than trying to implement missing
> features.
> > > > >
> > > > > One thing to achieve this is documentation of course.
> > > > > Thanks to all of you there already exist a lot of docs, but it
> feels
> > a
> > > > bit
> > > > > messy because they are hosted at different places, e.g.:
> > > > >
> > > > > - royale-docs repo
> > > > > - royale-asjs wiki
> > > > > - royale-asjs Readme
> > > > > - https://royale.apache.org
> > > > > - ...?
> > > > >
> > > > > As a user, it's hard to get an overview of what is available... and
> > > > where.
> > > > > Maybe it's a good idea to consolidate the docs before releasing
> 1.0.
> > > > >
> > > > > Just my 2 cents,
> > > > > Olaf
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> > > > >
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> > Angelo Lazzari
> > mobile: +34 683 137 087
> > mail: lazzari.ang...@gmail.com
> >
> >
> >
> >
> 
> > Verify the correspondence of the addressee; otherwise, notify that to the
> > sender and, conscious of the responsibility for the undue use, destroy
> the
> > message and its copies.
> >
> >
> 
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Angelo Lazzari
mobile: +34 683 137 087
mail: lazzari.ang...@gmail.com



Verify the correspondence of the addressee; otherwise, notify that to the
sender and, conscious of the responsibility for the undue use, destroy the
message and its copies.

Re: Let's bump Royale version to 1.0

[Andrew Wetmore]

Way back when, I learned a lot from the "Flex in a Week" online
introduction [1]. Would it be useful to create something like this to go
along with Tour de Jewel?

a

[1] https://www.adobe.com/devnet/flex/videotraining.html

On Fri, Apr 26, 2019 at 7:42 AM Frost, Andrew 
wrote:

> One other thought ... currently the way people ask for support is via
> these mailing lists. Which are okay but I'm always conscious that I'm
> potentially spamming people, plus the volume of mails is such that I have a
> rule to push all these into a folder that I then review every day or two..
>
> But if I want to find something out, I tend not to go search the mailing
> list, I tend to search online. Looking through mailing list threads isn't
> the easiest (and search engines don't necessarily pick things up from them
> very well) but a major source of support is Stack Overflow... I use this a
> lot with my other work and there's a lot of information there.
>
> Apache Royale doesn't appear to have a tag; when I search for "royale" all
> I got was stuff about "Clash Royale"; there are however 8 questions with
> "flexjs" tags.
>
> But wouldn't it be good for people to add questions and to contribute
> answers there, both from the user perspective and perhaps also the dev
> perspective? Would be interested in people's thoughts... (and perhaps I'll
> have to dig out my SO credentials to start contributing there)
>
> thanks
>
>   Andrew
>
>
> -Original Message-
> From: Carlos Rovira [mailto:carlosrov...@apache.org]
> Sent: 26 April 2019 10:39
> To: dev@royale.apache.org
> Subject: [EXTERNAL] Re: Let's bump Royale version to 1.0
>
> Hi Angelo, that's great! :)
>
> any help here is very appreciated.
>
> Share in a new mail a concrete contribution before starting to work on it,
> so we can know about it and help you on the task so your work fit perfectly
> in the overall picture.
>
> I'd like to create videos too, and people asked about it in facebook and
> twitter. Do you have skills in creating videos?
>
>
>
> El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari (<
> lazzari.ang...@gmail.com>)
> escribió:
>
> > Yes, i can give some slots to help with documentation or example
> > project or so... I think tutorial videos could be help to understand
> > rapidly the platform and could help new user to get ready in a few
> > hours to start build their project.
> >
> > Angelo
> >
> > On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira
> > 
> > wrote:
> >
> > > Agree with latest comments.
> > >
> > > I think we should work in docs and ease the start of new users to
> > > target
> > > 1.0
> > > And in the process fix some few things (i.e: don't want to reach 1.0
> > > with Jewel Table in its current state and API)
> > >
> > > What do you think?
> > >
> > > If you all agree could you think on how to contribute to that
> > > effort? Can we have as a near goal to bring 1.0 planing ourselves to
> > > donate some
> > hours
> > > to Apache Royale to make this happen? If some of us help in the
> > > current state I think we can get to it sooner.
> > >
> > > Thanks
> > >
> > >
> > > El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> > > lazzari.ang...@gmail.com>)
> > > escribió:
> > >
> > > > I am completely agree with Olaf: start using a new platform where
> > > > the documentation is not complete, clean and updated it is a
> > > > really bad thing...and it would be a potential reason to increase
> > > > the difficulty
> > to
> > > > adopt the platform...
> > > >
> > > > Angelo
> > > >
> > > > El vie., 26 abr. 2019 8:54, Olaf Krueger 
> > > escribió:
> > > >
> > > > > Hi,
> > > > >
> > > > > Basically, I think it's important to provide a great developer
> > > > experience.
> > > > > IMO, that's more important than trying to implement missing
> features.
> > > > >
> > > > > One thing to achieve this is documentation of course.
> > > > > Thanks to all of you there already exist a lot of docs, but it
> > > > > feels
> > a
> > > > bit
> > > > > messy because they are hosted at different places, e.g.:
> > > > >
> > > > > - royale-docs repo
> > > > > - royale-asjs wiki
> > > > > - royale-asjs Readme
> > > > > -
> > > > > https://clicktime.symantec.com/3SEvxFs2HbjNAgsLBEtNLr17Vc?u=http
> > > > > s%3A%2F%2Froyale.apache.org
> > > > > - ...?
> > > > >
> > > > > As a user, it's hard to get an overview of what is available...
> > > > > and
> > > > where.
> > > > > Maybe it's a good idea to consolidate the docs before releasing
> 1.0.
> > > > >
> > > > > Just my 2 cents,
> > > > > Olaf
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from:
> > > > > https://clicktime.symantec.com/3LM5ngUtumonkv3VTyrZRJ77Vc?u=http
> > > > > %3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F
> > > > >
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%
> > > 2F%2Fabout.me%2Fcarlosrovira
> > >
> >
> >
> > --
> > Angelo Lazzari
> > mobile: +34 683

Re: Let's bump Royale version to 1.0

[Frost, Andrew]

One other thought ... currently the way people ask for support is via these 
mailing lists. Which are okay but I'm always conscious that I'm potentially 
spamming people, plus the volume of mails is such that I have a rule to push 
all these into a folder that I then review every day or two..

But if I want to find something out, I tend not to go search the mailing list, 
I tend to search online. Looking through mailing list threads isn't the easiest 
(and search engines don't necessarily pick things up from them very well) but a 
major source of support is Stack Overflow... I use this a lot with my other 
work and there's a lot of information there.

Apache Royale doesn't appear to have a tag; when I search for "royale" all I 
got was stuff about "Clash Royale"; there are however 8 questions with "flexjs" 
tags.

But wouldn't it be good for people to add questions and to contribute answers 
there, both from the user perspective and perhaps also the dev perspective? 
Would be interested in people's thoughts... (and perhaps I'll have to dig out 
my SO credentials to start contributing there)

thanks

  Andrew


-Original Message-
From: Carlos Rovira [mailto:carlosrov...@apache.org] 
Sent: 26 April 2019 10:39
To: dev@royale.apache.org
Subject: [EXTERNAL] Re: Let's bump Royale version to 1.0

Hi Angelo, that's great! :)

any help here is very appreciated.

Share in a new mail a concrete contribution before starting to work on it, so 
we can know about it and help you on the task so your work fit perfectly in the 
overall picture.

I'd like to create videos too, and people asked about it in facebook and 
twitter. Do you have skills in creating videos?



El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari ()
escribió:

> Yes, i can give some slots to help with documentation or example 
> project or so... I think tutorial videos could be help to understand 
> rapidly the platform and could help new user to get ready in a few 
> hours to start build their project.
>
> Angelo
>
> On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira 
> 
> wrote:
>
> > Agree with latest comments.
> >
> > I think we should work in docs and ease the start of new users to 
> > target
> > 1.0
> > And in the process fix some few things (i.e: don't want to reach 1.0 
> > with Jewel Table in its current state and API)
> >
> > What do you think?
> >
> > If you all agree could you think on how to contribute to that 
> > effort? Can we have as a near goal to bring 1.0 planing ourselves to 
> > donate some
> hours
> > to Apache Royale to make this happen? If some of us help in the 
> > current state I think we can get to it sooner.
> >
> > Thanks
> >
> >
> > El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> > lazzari.ang...@gmail.com>)
> > escribió:
> >
> > > I am completely agree with Olaf: start using a new platform where 
> > > the documentation is not complete, clean and updated it is a 
> > > really bad thing...and it would be a potential reason to increase 
> > > the difficulty
> to
> > > adopt the platform...
> > >
> > > Angelo
> > >
> > > El vie., 26 abr. 2019 8:54, Olaf Krueger 
> > escribió:
> > >
> > > > Hi,
> > > >
> > > > Basically, I think it's important to provide a great developer
> > > experience.
> > > > IMO, that's more important than trying to implement missing features.
> > > >
> > > > One thing to achieve this is documentation of course.
> > > > Thanks to all of you there already exist a lot of docs, but it 
> > > > feels
> a
> > > bit
> > > > messy because they are hosted at different places, e.g.:
> > > >
> > > > - royale-docs repo
> > > > - royale-asjs wiki
> > > > - royale-asjs Readme
> > > > - 
> > > > https://clicktime.symantec.com/3SEvxFs2HbjNAgsLBEtNLr17Vc?u=http
> > > > s%3A%2F%2Froyale.apache.org
> > > > - ...?
> > > >
> > > > As a user, it's hard to get an overview of what is available... 
> > > > and
> > > where.
> > > > Maybe it's a good idea to consolidate the docs before releasing 1.0.
> > > >
> > > > Just my 2 cents,
> > > > Olaf
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: 
> > > > https://clicktime.symantec.com/3LM5ngUtumonkv3VTyrZRJ77Vc?u=http
> > > > %3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F
> > > >
> > >
> >
> >
> > --
> > Carlos Rovira
> > https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%
> > 2F%2Fabout.me%2Fcarlosrovira
> >
>
>
> --
> Angelo Lazzari
> mobile: +34 683 137 087
> mail: lazzari.ang...@gmail.com
>
>
>
> --
> --
> Verify the correspondence of the addressee; otherwise, notify that to 
> the sender and, conscious of the responsibility for the undue use, 
> destroy the message and its copies.
>
> --
> --
>


--
Carlos Rovira
https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7V

Re: Let's bump Royale version to 1.0

[Carlos Rovira]

Hi Angelo, that's great! :)

any help here is very appreciated.

Share in a new mail a concrete contribution before starting to work on it,
so we can know about it and help you on the task so your work fit perfectly
in the overall picture.

I'd like to create videos too, and people asked about it in facebook and
twitter. Do you have skills in creating videos?



El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari ()
escribió:

> Yes, i can give some slots to help with documentation or example project or
> so... I think tutorial videos could be help to understand rapidly the
> platform and could help new user to get ready in a few hours to start build
> their project.
>
> Angelo
>
> On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira 
> wrote:
>
> > Agree with latest comments.
> >
> > I think we should work in docs and ease the start of new users to target
> > 1.0
> > And in the process fix some few things (i.e: don't want to reach 1.0 with
> > Jewel Table in its current state and API)
> >
> > What do you think?
> >
> > If you all agree could you think on how to contribute to that effort? Can
> > we have as a near goal to bring 1.0 planing ourselves to donate some
> hours
> > to Apache Royale to make this happen? If some of us help in the current
> > state I think we can get to it sooner.
> >
> > Thanks
> >
> >
> > El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> > lazzari.ang...@gmail.com>)
> > escribió:
> >
> > > I am completely agree with Olaf: start using a new platform where the
> > > documentation is not complete, clean and updated it is a really bad
> > > thing...and it would be a potential reason to increase the difficulty
> to
> > > adopt the platform...
> > >
> > > Angelo
> > >
> > > El vie., 26 abr. 2019 8:54, Olaf Krueger 
> > escribió:
> > >
> > > > Hi,
> > > >
> > > > Basically, I think it's important to provide a great developer
> > > experience.
> > > > IMO, that's more important than trying to implement missing features.
> > > >
> > > > One thing to achieve this is documentation of course.
> > > > Thanks to all of you there already exist a lot of docs, but it feels
> a
> > > bit
> > > > messy because they are hosted at different places, e.g.:
> > > >
> > > > - royale-docs repo
> > > > - royale-asjs wiki
> > > > - royale-asjs Readme
> > > > - https://royale.apache.org
> > > > - ...?
> > > >
> > > > As a user, it's hard to get an overview of what is available... and
> > > where.
> > > > Maybe it's a good idea to consolidate the docs before releasing 1.0.
> > > >
> > > > Just my 2 cents,
> > > > Olaf
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> > > >
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
> Angelo Lazzari
> mobile: +34 683 137 087
> mail: lazzari.ang...@gmail.com
>
>
>
> 
> Verify the correspondence of the addressee; otherwise, notify that to the
> sender and, conscious of the responsibility for the undue use, destroy the
> message and its copies.
>
> 
>


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

Twitter Poll about releasing Apache Royale 1.0!

[Carlos Rovira]

Hi all!


we are discussing about releasing a 1.0 version of #ApacheRoyale

!


Do you want to participate in our poll? click in the link below! :)

https://twitter.com/ApacheRoyale/status/1121703139890094081



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

Build failed in Jenkins: royale-asjs_MXTests #720

[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

Jenkins build is back to normal : TourDeFlexMigration #739

[Apache Royale CI Server]

See 

Re: Let's bump Royale version to 1.0

[Carlos Rovira]

Hi Alex,

I think that if you have the time to finish the automation is good enough.
This is one is maybe the most important point to get solved.
Once releasing is just push a button for any of us, things should be more
easy.
Hope others could go with rest of the task to do, that a side of fixing
some few things for a 1.0, should be focused on docs, and make accessible
Royale for newcomers.

I'm with you that is not real to get directly a 1.0 as next release, so
going to 0.9.6 and then in few weeks trying again for a 0.9.7 will be the
most easy way to reach 1.0
If in that process we find the release is still having some issues, we can
go to 0.9.8, and so on



El vie., 26 abr. 2019 a las 8:43, Alex Harui ()
escribió:

> I do not have an opinion on what technical/marketing criteria we use to
> decide which release to call 1.0.  I'm not working directly with
> users/customers.
>
> I do not currently have time/energy/budget to work on any of the things
> folks think need to be done to get to 1.0 and barely have enough time to
> work on getting the next release out.  So someone else will have to supply
> the time/energy/budget to get these tasks done.
>
> I do have an opinion based on a practical aspect.  So far, we have not had
> the release scripts properly generate the right version number for the NPM
> artifacts.  That's why we've jumped from 0.9.4 to 0.9.6 and skipped 0.9.5.
> So I would say we should not call this next release 1.0 and wait until the
> release automation can correctly version all artifacts with the right
> version number before we pick one to call 1.0.  With any luck I'll get the
> automation running next week and will ask for someone to volunteer to test
> drive it.
>
> -Alex
>
> On 4/25/19, 9:57 AM, "Kessler CTR Mark J" 
> wrote:
>
> To give a perspective on the references and examples part from our
> organization...
>
>  When we started trying to convert one of our small apps we choose
> the Jewel set of components.  This was because it had lots of visible
> content and examples [1] whereas the standard examples were more limited
> [2].  Carlos does a good job of advertising new features with pictures,
> short descriptions, and some examples.  It would be nice to consolidate
> that information back into  the Royale site.  The Tour de Jewel examples
> being hosted on the Royale site is a good idea.  This is why we used Jewel
> as our base to build our organizational library from.  There might be other
> component sets that are fully functional, but without good references and
> examples they are basically unknown or gray boxes.
>
> The hosted ASDOCs on the Royale site [3] are a bit harder to read
> and are missing different component sets like jewel.  We were not able to
> use it for finding most of the things we were looking for.  Instead we used
> the SDK source and searched for class names / content.  Then we could walk
> the class file source and their inheritance to find what we were looking
> for.  Like hunting for premade beads.
>
>
> So if I were to order what a person might need to start (I know we
> have parts of this already):
>
> -How to download SDK binaries and get minimum requirements done.
> -What IDE's are available and how to set them up.
> -Starting a new app and getting it to compile for the first time.
> -Good reference (ASDOCs) being more complete.
> -Examples of using the components and how to use them.
> -Whole example applications showing a purpose and integration of
> multiple techniques.
>
>
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Ftourdejewel%2F&data=02%7C01%7Caharui%40adobe.com%7Ce884bd0d1c2f49f6bebf08d6c99f2129%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636918082633163959&sdata=H0JPIF3M9MEYOhNSKp7rNFdrXa61pR2fZveGS3Ccs1c%3D&reserved=0
> [2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fcategory%2Froyale-examples%2F&data=02%7C01%7Caharui%40adobe.com%7Ce884bd0d1c2f49f6bebf08d6c99f2129%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636918082633163959&sdata=2AIJu8SJoERkzHjDW58kwzgeVNNqjLYAaCPx%2BBedcYU%3D&reserved=0
> [3]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fasdoc%2F&data=02%7C01%7Caharui%40adobe.com%7Ce884bd0d1c2f49f6bebf08d6c99f2129%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636918082633163959&sdata=L01ZNhEXKo001E25idVo9md2vqqhxKx%2FwCf%2BL%2BAzCuM%3D&reserved=0
>
> -Mark K
>
>
>
>

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

Re: Let's bump Royale version to 1.0

[Carlos Rovira]

Hi Mark,

most of the points in your list should already done in the website, like
download SDK, minimum requerimiento, IDE's available, examples of using
components (this is blog examples and need more, but I'm the only one
pushing this examples, this could be easy to solve if others want to commit
blog post in the same way I did for new examples. The template is already
done, or I can help in publishing it if people donates content.

Other need more work: Starting a new App, ASDoc needs to be completed with
new APIs, since right now is just a sub set and in this form is not useful
for others.

Latest point is complicated to have this days, since it implies people
using Royale and sharing different techniques of integration.


El jue., 25 abr. 2019 a las 18:57, Kessler CTR Mark J
() escribió:

> To give a perspective on the references and examples part from our
> organization...
>
>  When we started trying to convert one of our small apps we choose the
> Jewel set of components.  This was because it had lots of visible content
> and examples [1] whereas the standard examples were more limited [2].
> Carlos does a good job of advertising new features with pictures, short
> descriptions, and some examples.  It would be nice to consolidate that
> information back into  the Royale site.  The Tour de Jewel examples being
> hosted on the Royale site is a good idea.  This is why we used Jewel as our
> base to build our organizational library from.  There might be other
> component sets that are fully functional, but without good references and
> examples they are basically unknown or gray boxes.
>
> The hosted ASDOCs on the Royale site [3] are a bit harder to read and
> are missing different component sets like jewel.  We were not able to use
> it for finding most of the things we were looking for.  Instead we used the
> SDK source and searched for class names / content.  Then we could walk the
> class file source and their inheritance to find what we were looking for.
> Like hunting for premade beads.
>
>
> So if I were to order what a person might need to start (I know we have
> parts of this already):
>
> -How to download SDK binaries and get minimum requirements done.
> -What IDE's are available and how to set them up.
> -Starting a new app and getting it to compile for the first time.
> -Good reference (ASDOCs) being more complete.
> -Examples of using the components and how to use them.
> -Whole example applications showing a purpose and integration of multiple
> techniques.
>
>
>
> [1] https://royale.apache.org/tourdejewel/
> [2] https://royale.apache.org/category/royale-examples/
> [3] https://royale.apache.org/asdoc/
>
> -Mark K
>
>

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

Re: Let's bump Royale version to 1.0

[Angelo Lazzari]

Yes, i can give some slots to help with documentation or example project or
so... I think tutorial videos could be help to understand rapidly the
platform and could help new user to get ready in a few hours to start build
their project.

Angelo

On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira 
wrote:

> Agree with latest comments.
>
> I think we should work in docs and ease the start of new users to target
> 1.0
> And in the process fix some few things (i.e: don't want to reach 1.0 with
> Jewel Table in its current state and API)
>
> What do you think?
>
> If you all agree could you think on how to contribute to that effort? Can
> we have as a near goal to bring 1.0 planing ourselves to donate some hours
> to Apache Royale to make this happen? If some of us help in the current
> state I think we can get to it sooner.
>
> Thanks
>
>
> El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> lazzari.ang...@gmail.com>)
> escribió:
>
> > I am completely agree with Olaf: start using a new platform where the
> > documentation is not complete, clean and updated it is a really bad
> > thing...and it would be a potential reason to increase the difficulty to
> > adopt the platform...
> >
> > Angelo
> >
> > El vie., 26 abr. 2019 8:54, Olaf Krueger 
> escribió:
> >
> > > Hi,
> > >
> > > Basically, I think it's important to provide a great developer
> > experience.
> > > IMO, that's more important than trying to implement missing features.
> > >
> > > One thing to achieve this is documentation of course.
> > > Thanks to all of you there already exist a lot of docs, but it feels a
> > bit
> > > messy because they are hosted at different places, e.g.:
> > >
> > > - royale-docs repo
> > > - royale-asjs wiki
> > > - royale-asjs Readme
> > > - https://royale.apache.org
> > > - ...?
> > >
> > > As a user, it's hard to get an overview of what is available... and
> > where.
> > > Maybe it's a good idea to consolidate the docs before releasing 1.0.
> > >
> > > Just my 2 cents,
> > > Olaf
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Angelo Lazzari
mobile: +34 683 137 087
mail: lazzari.ang...@gmail.com



Verify the correspondence of the addressee; otherwise, notify that to the
sender and, conscious of the responsibility for the undue use, destroy the
message and its copies.

Re: Let's bump Royale version to 1.0

[Carlos Rovira]

Agree with latest comments.

I think we should work in docs and ease the start of new users to target 1.0
And in the process fix some few things (i.e: don't want to reach 1.0 with
Jewel Table in its current state and API)

What do you think?

If you all agree could you think on how to contribute to that effort? Can
we have as a near goal to bring 1.0 planing ourselves to donate some hours
to Apache Royale to make this happen? If some of us help in the current
state I think we can get to it sooner.

Thanks


El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari ()
escribió:

> I am completely agree with Olaf: start using a new platform where the
> documentation is not complete, clean and updated it is a really bad
> thing...and it would be a potential reason to increase the difficulty to
> adopt the platform...
>
> Angelo
>
> El vie., 26 abr. 2019 8:54, Olaf Krueger  escribió:
>
> > Hi,
> >
> > Basically, I think it's important to provide a great developer
> experience.
> > IMO, that's more important than trying to implement missing features.
> >
> > One thing to achieve this is documentation of course.
> > Thanks to all of you there already exist a lot of docs, but it feels a
> bit
> > messy because they are hosted at different places, e.g.:
> >
> > - royale-docs repo
> > - royale-asjs wiki
> > - royale-asjs Readme
> > - https://royale.apache.org
> > - ...?
> >
> > As a user, it's hard to get an overview of what is available... and
> where.
> > Maybe it's a good idea to consolidate the docs before releasing 1.0.
> >
> > Just my 2 cents,
> > Olaf
> >
> >
> >
> >
> >
> >
> >
> > --
> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >
>


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

Build failed in Jenkins: royale-asjs_MXTests #719

[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: Let's bump Royale version to 1.0

[Angelo Lazzari]

I am completely agree with Olaf: start using a new platform where the
documentation is not complete, clean and updated it is a really bad
thing...and it would be a potential reason to increase the difficulty to
adopt the platform...

Angelo

El vie., 26 abr. 2019 8:54, Olaf Krueger  escribió:

> Hi,
>
> Basically, I think it's important to provide a great developer experience.
> IMO, that's more important than trying to implement missing features.
>
> One thing to achieve this is documentation of course.
> Thanks to all of you there already exist a lot of docs, but it feels a bit
> messy because they are hosted at different places, e.g.:
>
> - royale-docs repo
> - royale-asjs wiki
> - royale-asjs Readme
> - https://royale.apache.org
> - ...?
>
> As a user, it's hard to get an overview of what is available... and where.
> Maybe it's a good idea to consolidate the docs before releasing 1.0.
>
> Just my 2 cents,
> Olaf
>
>
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>