Build failed in Jenkins: royale-asjs_MXTests #733

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

Jenkins build is back to normal : royale-asjs_jsonly #2890

[Apache Royale CI Server]

See 

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

[Dany Dhondt]

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.

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.

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?

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

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?
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 
scratch takes years as anyone who has tried will confirm.

6. Components, components, components, …
As I stated before, embracing a new application technology involves the 
immediate availability of standard components. PAYG architecture, beads and 
strands is all very powerful, but as a developer new to Royale, I’d want 
ready-to-use, powerful, beautiful components which interoperate seamlessly.

Just some random thoughts…


Dany


> Op 27 apr. 2019, om 06:52 heeft Justin M. Hill  het 
> volgende geschreven:
> 
> Hi Dany,
> 
> Are you willing to write an article about why users should choose or at least 
> consider heavily Apache Royale over the competitors - React, Vue, and Angular?
> 
> I think it is important to clearly explain "Why you should care about Royale" 
> on the homepage compared to the competitors you mentioned.
> 
> Ideally, this article would be written not just for those with an 
> ActionScript or Flex code base that are seeking a modernization target.  
> 
> 
> 
> The Moonshine IDE team is willing to donate $2,500 USD in total over the next 
> 30 days to anyone who can accomplish what Alex and Carlos want to see happen 
> to call it release 1.0.  
> 
> IF you who are willing to step up to the plate immediately (with a 
> deliverable no later than May 26, 2019) to help with:
> 
> * documentation (ASDoc style)
> 
> * examples (code snippets that do things like Tour de Royale)
> 
> * tutorials (well written, friendly, understandable, educational material)
> 
> * a mini reproduction of the aforementioned Flex In a Week Series (great 
> idea!) 
> https://www.adobe.com/devnet/flex/videotraining.html 
> 
> 
> * build automation
> 
> * automated test cases
> 
> * creation of a summary comparison table showing Royale relative to React, 
> Vue, Angular
> 
> * a longer write up of competitive articles detailed why Royale is important. 
>  BTW, one reason it can be important is because it is NOT controlled by giant 
> companies.
> 
> * a directory of consultants for hire:
> 
> * OR anything else Alex and Carlos specifically need to be convinced to push 
> to 1.0 release
> 
> THEN
> 
> Please submit to this public group your commitment and cost.
> 
> We will then do this 

Re: Get paid to help bring Apache Royale to version to 1.0 -- submit your bid for assistance to the group by Friday May 3

[Alex Harui]

Hi Royale folks,

First, we should thank Justin Hill for his generous offer.  Justin posted this 
offer on dev@flex as well.  This is a copy of my reply on dev@flex so apologies 
if you get this twice and no need to read it again.

This offer turns out to be a good opportunity to educate and/or remind folks 
how Apache projects are different from corporate-driven projects.  Here's my 
take on some of important principles at Apache.  Other Apache folks may have 
different opinions.

1) The Apache Software Foundation (the ASF) itself does not pay people to 
contribute to its projects.  So the subject of this email is a bit concerning 
since it could imply that.  But in this case, a company (Prominic) or a person 
(Justin Hill) is proposing to pay for contributions just like anyone hiring a 
contractor or employee.  Which is totally fine and in fact, encouraged.  It 
would be great if all of you who are planning to use Royale would pay for 
contributions as long as you make it clear that the ASF is not the entity 
paying.  This includes, of course, contributing patches or features to Royale 
that you write yourself (where you are paying yourself or your employer is 
paying you).  Royale is free software, but Royale will be better if every user 
finds a way to contribute.  There is no big corporation like Adobe putting in 
money up front to try to guarantee success.  This is more like a potluck than a 
restaurant.

IMO, it is fine for now for folks to post job offers on the mailing lists.  If 
we get too many job offers, we can ask for a separate mailing list or some 
other place to share job information, but for now, I am personally ok with 
having offers of work-for-pay posted on the list with a [JOB] prefix.  Others 
are welcome to object or propose other ideas.  But basically, we want to 
encourage the growth of the Royale job ecosystem without implying that Apache 
pays for contributions.  So in the future, please use [JOB] or whatever we 
converge on to distinguish that someone else is paying.

And that leads to point 2...

2) Work paid for by someone else is not guaranteed to be accepted into the 
codebase.  Whatever code or other IP is paid for and generated (documentation, 
graphics, videos, etc) might be rejected just like any other code contribution 
from a committer.  Rejections should be very rare in Royale as we have designed 
Royale to be loosely-coupled so the impact of some code on other code should be 
minimized.  But the fact remains that if a contribution does not have technical 
merit or has licensing issues it may not be accepted and certainly not because 
someone paid someone for it.

One reason something could be rejected is because of point 3...

3) Apache does not want to appear to be influenced by corporations and 
business.  What this really means is that no business entity should appear to 
be running the project, dictating schedules, roadmaps, etc.  Apache is all 
about individuals.  The person with a few hours on the weekend should be able 
to contribute.  Of course, businesses with more money can pay more folks to 
write more code and overwhelm the weekend person.  That's just life.  But that 
business cannot reject the weekend person's contribution just because it 
doesn’t fit into that business's goals/schedule.  And, no business can claim to 
be "the provider", "the sponsor", "the home of", or use similar phrases to 
imply that they are the sole entity in charge of the project.  So if a paid 
contribution implies something like that, that would be grounds for rejection.

Similarly, because Apache is about individuals, we get to point 4...

4) No individual has more influence than any other individual.  No matter who 
pays you or how many hours you have to contribute or whether you contribute 
documentation or code or help answer questions, you have an equal voice.  Sure, 
there will be technical experts on subsections of the code that have a vision 
of what that subsection should do, but that's why Royale is loosely coupled:  
so you can fork that subsection and create your own variant.  Royale itself 
probably won't designate one component set as "the one to use".  There are many 
to choose from with pros and cons for your needs.  And thus, it isn't up to 
Carlos or me or any other person to dictate what is or isn't going to happen.

Instead, projects get work done in a different way...

5) Apache projects use consensus.  Without a boss to make the call, Apache 
projects rely on consensus (actually, general consensus) to make decisions.  
That can take more time when everyone has an equal say, but there really aren't 
other options.  So if you have an idea to help Royale, post it and neither 
Carlos nor I will make a decision on it.  We may voice our opinions, but it 
will be up to everyone else reading this email list and maybe responding to 
twitter posts to make it clear which ideas are most popular.  And then, since 
Prominic or Justin Hill is paying, ultimately it is 

Release Step 007 Succeeded

[Apache Royale CI Server]

1. Run ant -f releasesteps.xml Release_Step_007 -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_007_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_007_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 006 Succeeded

[Apache Royale CI Server]

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

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

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

[Justin M. Hill]

To clarify -- anyone on the Moonshine IDE team will recuse ourselves from
voting on which bids to proceed with.

Again, the intent is for this to be a group decision to try to add some
extra work hours to bring home a 1.0 release ASAP so people can start using
this great technology in production, have tutorials, and documentation that
helps them understand Royale and why it should matter to them.

Thank you,

Justin Hill

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

[Justin M. Hill]

Hi Carlos and Olaf,

To clarify: the offer extends to everyone:  Alex, Carlos, everyone here.

Everyone can submit bids.   The group will vote on who to pay.  I have no
idea if this will work to inspire / motivate / organize, but it is worth a
shot.

Everyone's time is valuable, and balancing unpaid work on open source
projects with client driven (paid) work is naturally a challenge.   The
idea is to allow financially for more focus to be on getting Royale 1.0
completed within a month.

People can submit bids from $1.00 to $2,500.00.  As a group we can choose
multiple bids or a single bid.   We will do whatever the group votes on
with the budget I presented.


The Moonshine-IDE.com team would do more if we could.   From a code
contribution perspective, we are working diligently on releases every 2
weeks or so.

I understand the Apache way is similar to a potluck dinner, and everyone
brings what they can.  We are bringing an IDE focused on fast on-boarding
for new users for Royale.

The next release will hopefully include Carlos' suggestion to have a
non-sandbox Mac version, in addition to the one available in the Mac App
Store / iTunes.  This will help power users who want to make use of
existing software they have downloaded instead of using our "get your
environment setup in one click" helper app.  There will be other features
too, especially related to GitHub and making it easy to bring example
Royale projects into the IDE which are posted to GitHub.



I understand more documentation was the vote from the Twitter pole.  We
agree and have been working on the tutorial aspect.   Specifically:  two
weeks ago Piotr recruited a video tutorial specialist.  He is going to be
working on some of the goals with Piotr.  However, he does not know Royale,
so he will be learning it.  This is actually great, because it will help
Piotr to explain it to someone, who in turn can explain it in a video to
everyone.


Also, we have given to Piotr a portion of one of our production Flex
applications which includes a login sequence and a basic contact details
management (edit your e-mail and phone number type app) to be used in a
tutorial potentially.

We can never have enough tutorials, though!  I'd love to see a lot more
people working on tutorials.


ASDocs and finalizing the API of key things like the Jewel Data Grid, along
with the build process automation, are all critical items.   I fully agree.


My hope, now that the group has reached consensus on what 1.0 will take, is
that we can get very specific milestones defined in GitHub:
https://github.com/apache/royale-asjs/milestones


For example, exactly what do we need to have fixed with the build process
automation?

Which specific sections of the documentation need to be improved?

Having specific issues for these items will make it crystal clear what the
group must complete before 1.0 is considered done.


If the group decides we need a build specialist from outside the Royale
community group, then we can try to get help on UpWork.  We would rather
keep the funding in the direct community since so many of you have worked
so hard unpaid on this project for so long.   Still, whatever the group
decides is needed, lets figure out how to get it pipe lined into existence
in the next 30 days.

Thank you,

Justin Hill



- Message from Olaf Krueger  on Sun, 28 Apr 2019
23:20:03 -0700 (MST) -
   
  To: dev@royale.apache.org
   
 Subject: Re: Let's bump Royale version to 1.0 -- submit your bid for 
assistance to
  the group by Friday May 3
   

Hi Justin,
thanks for your amazing offer!

> ...what Alex and Carlos want to see happen...

Before others will do this I would just like to mention that no individuals
make decisions here at Apache. It's always the community! ;-)

However, I am curious about the feedback!

Thanks,
Olaf


- Message from Carlos Rovira  on Mon, 29 Apr
2019 19:44:32 +0200 -
   
  To: dev@royale.apache.org
   
 Subject: Re: Let's bump Royale version to 1.0 -- submit your bid for 
assistance to
  the group by Friday May 3
   

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 

Build failed in Jenkins: royale-asjs_MXTests #732

[Apache Royale CI Server]

See 


Changes:

[carlosrovira] jewel-table: DataContainerBase already implements

--
[...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 005a Succeeded

[Apache Royale CI Server]

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

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

Re: StackOverflow tips

[Dany Dhondt]

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

Release Step 005 Succeeded

[Apache Royale CI Server]

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

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

Re: StackOverflow tips

[Carlos Rovira]

Hi,

just posted here:

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

please share and retweet! :)

Carlos



El lun., 29 abr. 2019 a las 20:20, Carlos Rovira ()
escribió:

> 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

Release Step 004 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_004 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: StackOverflow tips

[Carlos Rovira]

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

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

[Carlos Rovira]

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

Re: Twitter Poll about releasing Apache Royale 1.0!

[Carlos Rovira]

Hi results of the poll! :)

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

43% Yes! Let's bump to v1.0!
10% Better continue polishing
47% Focus on docs first. <..winner

Total : 61 votes

seems people wants we have to create docs first and very near we release 1.0



El vie., 26 abr. 2019 a las 11:32, Carlos Rovira ()
escribió:

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

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

Re: StackOverflow tips

[Carlos Rovira]

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

Re: Let's bump Royale version to 1.0

[Carlos Rovira]

Great! I'll follow your indications :)

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

> Carlos,
>
> Everyone can add a comment to a question. Once you’ve earned enough
> reputation, you can actually ‘answer’ a question.
>
> Reputation points are earned mainly through being upvoted by someone else.
> So, If your read a question which is interesting, upvote the question.
> If you read a comment or an answer which is good, upvote that.
> If you want to comment on a question or on a comment, don’t hesitate
> because that’s when other people can upvote your comment!
>
> Dany
>
> > Op 29 apr. 2019, om 18:50 heeft Carlos Rovira 
> het volgende geschreven:
> >
> > Hi,
> > agree too, I think the most convenient is "apache-royale", so go ahead.
> >
> > If I want to respond a question you post, I can do it directly? or I must
> > earn some points first doing something?
> >
> > thanks!
> >
> >
> >
> > El lun., 29 abr. 2019 a las 18:41, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Dany,
> >>
> >> Thanks. I'm personally fine if it is common to use apache-royale tag.
> >> Anyone is not in favor of that ?
> >>
> >> Piotr
> >>
> >> pon., 29 kwi 2019 o 18:38 Dany Dhondt 
> >> napisał(a):
> >>
> >>> Piotr,
> >>>
> >>> If you do a search on apache, here are some of the tags:
> >>>
> >>> apache-camel
> >>> apache-flink
> >>> apache-spark
> >>> apache-storm
> >>> …
> >>>
> >>> A few other examples:
> >>>
> >>> react-native
> >>> create-react-app
> >>> …
> >>>
> >>> Is you browse the tags on SO, you’ll see it’s very common.
> >>>
> >>> Also, npm naming conventions are all dash separated, or hyphen
> separated.
> >>>
> >>> I think we should follow this naming convention.
> >>>
> >>> Dany
> >>>
> >>>
> >>>
>  Op 29 apr. 2019, om 18:14 heeft Piotr Zarzycki <
> >>> piotrzarzyck...@gmail.com> het volgende geschreven:
> 
>  Dany,
> 
>  Is it a common way on stack overflow ? It looks too me to complicated,
> >>> have
>  something additional between two word.
> 
>  Thanks,
>  Piotr
> 
>  pon., 29 kwi 2019 o 18:01 Dany Dhondt 
>  napisał(a):
> 
> > Shouldn’t it be better to name it apache-royale?
> > That’s the way most tags are build I think
> >
> > Dany
> >
> >
> >> Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki <
> > piotrzarzyck...@gmail.com> het volgende geschreven:
> >>
> >> Hi Dany,
> >>
> >> We have agreed on "apacheroyale" tag in different thread. I think
> you
> > could
> >> use that.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pon., 29 kwi 2019 o 17:56 Dany Dhondt 
> >> napisał(a):
> >>
> >>> Can somebody create some royale tags please? I don’t have enough
> >> rep.
> >>> points at this moment.
> >>> Also, shouldn’t we agree on some basic royale tags?
> >>> When the tags are made, I’ll start posting some questions.
> >>>
> >>> Dany
> >>>
>  Op 29 apr. 2019, om 17:27 heeft Alex Harui
> >>  
> >>> het volgende geschreven:
> 
>  I agree we want to develop a presence on Stack Overflow.  I still
> >>> can't
> >>> figure out how to earn enough points be able to answer any
> questions
> >>> so
> > I
> >>> won't be of much help until that happens.
> 
>  -Alex
> 
>  On 4/29/19, 7:32 AM, "Carlos Rovira" 
> >>> wrote:
> 
>  Hi,
> 
>  about StackOverFlow, we already discussed to start creating
> >>> questions
> >>> in
>  SOF, but finally nobody does. I think I should not create one and
> >>> respond
>  myself right? it will be very sad to do in that way. So if someone
> >>> start to
>  post questions in SOF, I promise to respond, at least if it's
> >>> something I
>  can know how to respond. It could be things you already know, but
> >> we
> >>> must
>  start in some way.
> 
>  SOF is crucial for us, I talked with customers that pointed me
> >> that
> >>> Apache
>  Royale is not on SOF, so his devs can easily search problems
> >> there.
> >>> And
>  this is the google for developers. If we are not there, Royale
> >> will
> >>> never
>  succeed, So if you want Royale to succeed we all should put some
> >>> work, what
>  we can, in SOF. @dany, if you want to start this effort we can
> >>> follow
> >>> you.
>  Just let's know in a mail here so we can go to that link and
> >>> respond.
> >>> If
>  you start that your work will be follow :)
> 
>  @Andrew, "Flex In a Week" is a very good idea too. I think we can
> >>> work on
>  that, but again, we need some kind of plan. A team to work on
> >> that.
> >>> Things
>  like that can't be create by only one man's work. Volunteers?
> 
>  @Om, I not use NPM but will try Royale CLI since we need 

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

[Carlos Rovira]

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


El lun., 29 abr. 2019 a las 18:42, Kessler CTR Mark J
() escribió:

> Let me clarify.
>
> @Carlos,
>  It's not a dependency issue, it's a matter of finding out what the
> SDK version or build number of the SDK or any form of uniquely identifying
> information about the SDK in code.  So the apps we build using Flex we can
> just get the Flex version by referencing mx.core.FlexVersion in code.  Then
> in our application logs when an app starts up we can see the message
> "Compiled with SDK v4.16.0.".  So it allows us to more easily troubleshoot
> issues later.
>
> @Alex,
> Yes that would be great to have any important versions in there.  How
> about we just keep it  like a compile time constant / compiler "define"
> statement that has the version built it?
>
>
>
> -Mark K
>


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

StackOverflow tips

[Dany Dhondt]

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

Release Step 004 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_004 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.

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

[Carlos Rovira]

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 are all what you
> need,
> so maven takes care of pulling all right dependencies you need.
>
> @Alex, about extending IUIBase, my own experience is that beads are a
> very
> good way to extend/compose more code you need, but extending core
> interfaces like the one you said is not the case. Let me put you an
> example: For Jewel I use "StyledUIBase" that extends "UIBase" to add
> IClassSelectorListSupport, the css CRUD API (addClass, removeClass,
> etc..):
>
> public class StyledUIBase extends UIBase implements
> IClassSelectorListSupport
>
> This makes that some components are easy to extend but others need to
> be
> recreate. There are lots of cases in Jewel where I need to
>
> If you search in Jewel for implements IClassSelectorListSupport
>  you'll find Jewel Group, Jewel DataContainerBase and Jewel Table, are
> implementing that class while, so they are not StyledUIBase in it's
> core
> are standard UIBase and at its level we implement the interface and add
> again all methods repeating the code. So we are duplicating that code
> all
> that times.
>
> I think this is one of the few things I don't like in Jewel, If you
> know
> some way to do this in a better way, I can change it
>
> thanks
>
> --
Carlos Rovira
http://about.me/carlosrovira

Royale_Release_Step_006 - Build # 13 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_006 - Build # 13 - Failure:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_006/13/
 to view the results.

Release Step 005a Succeeded

[Apache Royale CI Server]

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

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

Royale_Release_Step_005a_If_Utils - Build # 4 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_005a_If_Utils - Build # 4 - Failure:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005a_If_Utils/4/
 to view the results.

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Carlos,

Everyone can add a comment to a question. Once you’ve earned enough reputation, 
you can actually ‘answer’ a question.

Reputation points are earned mainly through being upvoted by someone else. So, 
If your read a question which is interesting, upvote the question.
If you read a comment or an answer which is good, upvote that.
If you want to comment on a question or on a comment, don’t hesitate because 
that’s when other people can upvote your comment!

Dany

> Op 29 apr. 2019, om 18:50 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Hi,
> agree too, I think the most convenient is "apache-royale", so go ahead.
> 
> If I want to respond a question you post, I can do it directly? or I must
> earn some points first doing something?
> 
> thanks!
> 
> 
> 
> El lun., 29 abr. 2019 a las 18:41, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
> 
>> Dany,
>> 
>> Thanks. I'm personally fine if it is common to use apache-royale tag.
>> Anyone is not in favor of that ?
>> 
>> Piotr
>> 
>> pon., 29 kwi 2019 o 18:38 Dany Dhondt 
>> napisał(a):
>> 
>>> Piotr,
>>> 
>>> If you do a search on apache, here are some of the tags:
>>> 
>>> apache-camel
>>> apache-flink
>>> apache-spark
>>> apache-storm
>>> …
>>> 
>>> A few other examples:
>>> 
>>> react-native
>>> create-react-app
>>> …
>>> 
>>> Is you browse the tags on SO, you’ll see it’s very common.
>>> 
>>> Also, npm naming conventions are all dash separated, or hyphen separated.
>>> 
>>> I think we should follow this naming convention.
>>> 
>>> Dany
>>> 
>>> 
>>> 
 Op 29 apr. 2019, om 18:14 heeft Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com> het volgende geschreven:
 
 Dany,
 
 Is it a common way on stack overflow ? It looks too me to complicated,
>>> have
 something additional between two word.
 
 Thanks,
 Piotr
 
 pon., 29 kwi 2019 o 18:01 Dany Dhondt 
 napisał(a):
 
> Shouldn’t it be better to name it apache-royale?
> That’s the way most tags are build I think
> 
> Dany
> 
> 
>> Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki <
> piotrzarzyck...@gmail.com> het volgende geschreven:
>> 
>> Hi Dany,
>> 
>> We have agreed on "apacheroyale" tag in different thread. I think you
> could
>> use that.
>> 
>> Thanks,
>> Piotr
>> 
>> pon., 29 kwi 2019 o 17:56 Dany Dhondt 
>> napisał(a):
>> 
>>> Can somebody create some royale tags please? I don’t have enough
>> rep.
>>> points at this moment.
>>> Also, shouldn’t we agree on some basic royale tags?
>>> When the tags are made, I’ll start posting some questions.
>>> 
>>> Dany
>>> 
 Op 29 apr. 2019, om 17:27 heeft Alex Harui
>> >>> 
>>> het volgende geschreven:
 
 I agree we want to develop a presence on Stack Overflow.  I still
>>> can't
>>> figure out how to earn enough points be able to answer any questions
>>> so
> I
>>> won't be of much help until that happens.
 
 -Alex
 
 On 4/29/19, 7:32 AM, "Carlos Rovira" 
>>> wrote:
 
 Hi,
 
 about StackOverFlow, we already discussed to start creating
>>> questions
>>> in
 SOF, but finally nobody does. I think I should not create one and
>>> respond
 myself right? it will be very sad to do in that way. So if someone
>>> start to
 post questions in SOF, I promise to respond, at least if it's
>>> something I
 can know how to respond. It could be things you already know, but
>> we
>>> must
 start in some way.
 
 SOF is crucial for us, I talked with customers that pointed me
>> that
>>> Apache
 Royale is not on SOF, so his devs can easily search problems
>> there.
>>> And
 this is the google for developers. If we are not there, Royale
>> will
>>> never
 succeed, So if you want Royale to succeed we all should put some
>>> work, what
 we can, in SOF. @dany, if you want to start this effort we can
>>> follow
>>> you.
 Just let's know in a mail here so we can go to that link and
>>> respond.
>>> If
 you start that your work will be follow :)
 
 @Andrew, "Flex In a Week" is a very good idea too. I think we can
>>> work on
 that, but again, we need some kind of plan. A team to work on
>> that.
>>> Things
 like that can't be create by only one man's work. Volunteers?
 
 @Om, I not use NPM but will try Royale CLI since we need something
>>> really
 fast to compete with React or others, or people will never jump to
> out
 wagon.
 
 thanks for all the thoughts! :)
 
 
 
 
 
 El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala (<
>>> bigosma...@gmail.com>)
 escribió:
 
> On Fri, Apr 26, 2019 at 7:37 

Re: Let's bump Royale version to 1.0

[Carlos Rovira]

Hi,
agree too, I think the most convenient is "apache-royale", so go ahead.

If I want to respond a question you post, I can do it directly? or I must
earn some points first doing something?

thanks!



El lun., 29 abr. 2019 a las 18:41, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Dany,
>
> Thanks. I'm personally fine if it is common to use apache-royale tag.
> Anyone is not in favor of that ?
>
> Piotr
>
> pon., 29 kwi 2019 o 18:38 Dany Dhondt 
> napisał(a):
>
> > Piotr,
> >
> > If you do a search on apache, here are some of the tags:
> >
> > apache-camel
> > apache-flink
> > apache-spark
> > apache-storm
> > …
> >
> > A few other examples:
> >
> > react-native
> > create-react-app
> > …
> >
> > Is you browse the tags on SO, you’ll see it’s very common.
> >
> > Also, npm naming conventions are all dash separated, or hyphen separated.
> >
> > I think we should follow this naming convention.
> >
> > Dany
> >
> >
> >
> > > Op 29 apr. 2019, om 18:14 heeft Piotr Zarzycki <
> > piotrzarzyck...@gmail.com> het volgende geschreven:
> > >
> > > Dany,
> > >
> > > Is it a common way on stack overflow ? It looks too me to complicated,
> > have
> > > something additional between two word.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pon., 29 kwi 2019 o 18:01 Dany Dhondt 
> > > napisał(a):
> > >
> > >> Shouldn’t it be better to name it apache-royale?
> > >> That’s the way most tags are build I think
> > >>
> > >> Dany
> > >>
> > >>
> > >>> Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki <
> > >> piotrzarzyck...@gmail.com> het volgende geschreven:
> > >>>
> > >>> Hi Dany,
> > >>>
> > >>> We have agreed on "apacheroyale" tag in different thread. I think you
> > >> could
> > >>> use that.
> > >>>
> > >>> Thanks,
> > >>> Piotr
> > >>>
> > >>> pon., 29 kwi 2019 o 17:56 Dany Dhondt 
> > >>> napisał(a):
> > >>>
> >  Can somebody create some royale tags please? I don’t have enough
> rep.
> >  points at this moment.
> >  Also, shouldn’t we agree on some basic royale tags?
> >  When the tags are made, I’ll start posting some questions.
> > 
> >  Dany
> > 
> > > Op 29 apr. 2019, om 17:27 heeft Alex Harui
>  > >
> >  het volgende geschreven:
> > >
> > > I agree we want to develop a presence on Stack Overflow.  I still
> > can't
> >  figure out how to earn enough points be able to answer any questions
> > so
> > >> I
> >  won't be of much help until that happens.
> > >
> > > -Alex
> > >
> > > On 4/29/19, 7:32 AM, "Carlos Rovira" 
> > wrote:
> > >
> > >  Hi,
> > >
> > >  about StackOverFlow, we already discussed to start creating
> > questions
> >  in
> > >  SOF, but finally nobody does. I think I should not create one and
> >  respond
> > >  myself right? it will be very sad to do in that way. So if someone
> >  start to
> > >  post questions in SOF, I promise to respond, at least if it's
> >  something I
> > >  can know how to respond. It could be things you already know, but
> we
> >  must
> > >  start in some way.
> > >
> > >  SOF is crucial for us, I talked with customers that pointed me
> that
> >  Apache
> > >  Royale is not on SOF, so his devs can easily search problems
> there.
> >  And
> > >  this is the google for developers. If we are not there, Royale
> will
> >  never
> > >  succeed, So if you want Royale to succeed we all should put some
> >  work, what
> > >  we can, in SOF. @dany, if you want to start this effort we can
> > follow
> >  you.
> > >  Just let's know in a mail here so we can go to that link and
> > respond.
> >  If
> > >  you start that your work will be follow :)
> > >
> > >  @Andrew, "Flex In a Week" is a very good idea too. I think we can
> >  work on
> > >  that, but again, we need some kind of plan. A team to work on
> that.
> >  Things
> > >  like that can't be create by only one man's work. Volunteers?
> > >
> > >  @Om, I not use NPM but will try Royale CLI since we need something
> >  really
> > >  fast to compete with React or others, or people will never jump to
> > >> out
> > >  wagon.
> > >
> > >  thanks for all the thoughts! :)
> > >
> > >
> > >
> > >
> > >
> > >  El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala (<
> >  bigosma...@gmail.com>)
> > >  escribió:
> > >
> > >> On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt
> > >>  > >
> > >> wrote:
> > >>
> > >>> 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
> > 

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

[Kessler CTR Mark J]

Let me clarify.

@Carlos,
 It's not a dependency issue, it's a matter of finding out what the SDK 
version or build number of the SDK or any form of uniquely identifying 
information about the SDK in code.  So the apps we build using Flex we can just 
get the Flex version by referencing mx.core.FlexVersion in code.  Then in our 
application logs when an app starts up we can see the message "Compiled with 
SDK v4.16.0.".  So it allows us to more easily troubleshoot issues later.

@Alex,
Yes that would be great to have any important versions in there.  How about 
we just keep it  like a compile time constant / compiler "define" statement 
that has the version built it?



-Mark K

Re: Let's bump Royale version to 1.0

[Piotr Zarzycki]

Dany,

Thanks. I'm personally fine if it is common to use apache-royale tag.
Anyone is not in favor of that ?

Piotr

pon., 29 kwi 2019 o 18:38 Dany Dhondt 
napisał(a):

> Piotr,
>
> If you do a search on apache, here are some of the tags:
>
> apache-camel
> apache-flink
> apache-spark
> apache-storm
> …
>
> A few other examples:
>
> react-native
> create-react-app
> …
>
> Is you browse the tags on SO, you’ll see it’s very common.
>
> Also, npm naming conventions are all dash separated, or hyphen separated.
>
> I think we should follow this naming convention.
>
> Dany
>
>
>
> > Op 29 apr. 2019, om 18:14 heeft Piotr Zarzycki <
> piotrzarzyck...@gmail.com> het volgende geschreven:
> >
> > Dany,
> >
> > Is it a common way on stack overflow ? It looks too me to complicated,
> have
> > something additional between two word.
> >
> > Thanks,
> > Piotr
> >
> > pon., 29 kwi 2019 o 18:01 Dany Dhondt 
> > napisał(a):
> >
> >> Shouldn’t it be better to name it apache-royale?
> >> That’s the way most tags are build I think
> >>
> >> Dany
> >>
> >>
> >>> Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com> het volgende geschreven:
> >>>
> >>> Hi Dany,
> >>>
> >>> We have agreed on "apacheroyale" tag in different thread. I think you
> >> could
> >>> use that.
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> pon., 29 kwi 2019 o 17:56 Dany Dhondt 
> >>> napisał(a):
> >>>
>  Can somebody create some royale tags please? I don’t have enough rep.
>  points at this moment.
>  Also, shouldn’t we agree on some basic royale tags?
>  When the tags are made, I’ll start posting some questions.
> 
>  Dany
> 
> > Op 29 apr. 2019, om 17:27 heeft Alex Harui  >
>  het volgende geschreven:
> >
> > I agree we want to develop a presence on Stack Overflow.  I still
> can't
>  figure out how to earn enough points be able to answer any questions
> so
> >> I
>  won't be of much help until that happens.
> >
> > -Alex
> >
> > On 4/29/19, 7:32 AM, "Carlos Rovira" 
> wrote:
> >
> >  Hi,
> >
> >  about StackOverFlow, we already discussed to start creating
> questions
>  in
> >  SOF, but finally nobody does. I think I should not create one and
>  respond
> >  myself right? it will be very sad to do in that way. So if someone
>  start to
> >  post questions in SOF, I promise to respond, at least if it's
>  something I
> >  can know how to respond. It could be things you already know, but we
>  must
> >  start in some way.
> >
> >  SOF is crucial for us, I talked with customers that pointed me that
>  Apache
> >  Royale is not on SOF, so his devs can easily search problems there.
>  And
> >  this is the google for developers. If we are not there, Royale will
>  never
> >  succeed, So if you want Royale to succeed we all should put some
>  work, what
> >  we can, in SOF. @dany, if you want to start this effort we can
> follow
>  you.
> >  Just let's know in a mail here so we can go to that link and
> respond.
>  If
> >  you start that your work will be follow :)
> >
> >  @Andrew, "Flex In a Week" is a very good idea too. I think we can
>  work on
> >  that, but again, we need some kind of plan. A team to work on that.
>  Things
> >  like that can't be create by only one man's work. Volunteers?
> >
> >  @Om, I not use NPM but will try Royale CLI since we need something
>  really
> >  fast to compete with React or others, or people will never jump to
> >> out
> >  wagon.
> >
> >  thanks for all the thoughts! :)
> >
> >
> >
> >
> >
> >  El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala (<
>  bigosma...@gmail.com>)
> >  escribió:
> >
> >> On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt
> >>  >
> >> wrote:
> >>
> >>> 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
> >>>
> >>>
> >> The Royale CLI is modeled closely after the create-react-app.  The
> >> docs
>  for
> >> the alpha version is available here:
> >>
> 
> >>
> 

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Piotr,

If you do a search on apache, here are some of the tags:

apache-camel
apache-flink
apache-spark
apache-storm
…

A few other examples:

react-native
create-react-app
…

Is you browse the tags on SO, you’ll see it’s very common.

Also, npm naming conventions are all dash separated, or hyphen separated.

I think we should follow this naming convention.

Dany



> Op 29 apr. 2019, om 18:14 heeft Piotr Zarzycki  
> het volgende geschreven:
> 
> Dany,
> 
> Is it a common way on stack overflow ? It looks too me to complicated, have
> something additional between two word.
> 
> Thanks,
> Piotr
> 
> pon., 29 kwi 2019 o 18:01 Dany Dhondt 
> napisał(a):
> 
>> Shouldn’t it be better to name it apache-royale?
>> That’s the way most tags are build I think
>> 
>> Dany
>> 
>> 
>>> Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki <
>> piotrzarzyck...@gmail.com> het volgende geschreven:
>>> 
>>> Hi Dany,
>>> 
>>> We have agreed on "apacheroyale" tag in different thread. I think you
>> could
>>> use that.
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> pon., 29 kwi 2019 o 17:56 Dany Dhondt 
>>> napisał(a):
>>> 
 Can somebody create some royale tags please? I don’t have enough rep.
 points at this moment.
 Also, shouldn’t we agree on some basic royale tags?
 When the tags are made, I’ll start posting some questions.
 
 Dany
 
> Op 29 apr. 2019, om 17:27 heeft Alex Harui 
 het volgende geschreven:
> 
> I agree we want to develop a presence on Stack Overflow.  I still can't
 figure out how to earn enough points be able to answer any questions so
>> I
 won't be of much help until that happens.
> 
> -Alex
> 
> On 4/29/19, 7:32 AM, "Carlos Rovira"  wrote:
> 
>  Hi,
> 
>  about StackOverFlow, we already discussed to start creating questions
 in
>  SOF, but finally nobody does. I think I should not create one and
 respond
>  myself right? it will be very sad to do in that way. So if someone
 start to
>  post questions in SOF, I promise to respond, at least if it's
 something I
>  can know how to respond. It could be things you already know, but we
 must
>  start in some way.
> 
>  SOF is crucial for us, I talked with customers that pointed me that
 Apache
>  Royale is not on SOF, so his devs can easily search problems there.
 And
>  this is the google for developers. If we are not there, Royale will
 never
>  succeed, So if you want Royale to succeed we all should put some
 work, what
>  we can, in SOF. @dany, if you want to start this effort we can follow
 you.
>  Just let's know in a mail here so we can go to that link and respond.
 If
>  you start that your work will be follow :)
> 
>  @Andrew, "Flex In a Week" is a very good idea too. I think we can
 work on
>  that, but again, we need some kind of plan. A team to work on that.
 Things
>  like that can't be create by only one man's work. Volunteers?
> 
>  @Om, I not use NPM but will try Royale CLI since we need something
 really
>  fast to compete with React or others, or people will never jump to
>> out
>  wagon.
> 
>  thanks for all the thoughts! :)
> 
> 
> 
> 
> 
>  El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala (<
 bigosma...@gmail.com>)
>  escribió:
> 
>> On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt
>>  
>> wrote:
>> 
>>> 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
>>> 
>>> 
>> The Royale CLI is modeled closely after the create-react-app.  The
>> docs
 for
>> the alpha version is available here:
>> 
 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fnpm%2Fclidata=02%7C01%7Caharui%40adobe.com%7C950f12a2b0f24cad192508d6ccaf8241%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636921451512477017sdata=4VN8JejglMeW08ZcNV6fCJ%2BdYJjOHcvfGDL099jives%3Dreserved=0
>> If I get more feedback, I am keep improving this tool.
>> 
>> Thanks,
>> Om
>> 
>> 
>> 
>>> Verstuurd vanaf mijn iPhone
>>> 
 Op 26 apr. 2019 om 12:42 heeft Frost, Andrew <
>> andrew.fr...@harman.com
> 
>>> 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
>>> 

Release Step 004 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_004 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

[Piotr Zarzycki]

Dany,

Is it a common way on stack overflow ? It looks too me to complicated, have
something additional between two word.

Thanks,
Piotr

pon., 29 kwi 2019 o 18:01 Dany Dhondt 
napisał(a):

> Shouldn’t it be better to name it apache-royale?
> That’s the way most tags are build I think
>
> Dany
>
>
> > Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki <
> piotrzarzyck...@gmail.com> het volgende geschreven:
> >
> > Hi Dany,
> >
> > We have agreed on "apacheroyale" tag in different thread. I think you
> could
> > use that.
> >
> > Thanks,
> > Piotr
> >
> > pon., 29 kwi 2019 o 17:56 Dany Dhondt 
> > napisał(a):
> >
> >> Can somebody create some royale tags please? I don’t have enough rep.
> >> points at this moment.
> >> Also, shouldn’t we agree on some basic royale tags?
> >> When the tags are made, I’ll start posting some questions.
> >>
> >> Dany
> >>
> >>> Op 29 apr. 2019, om 17:27 heeft Alex Harui 
> >> het volgende geschreven:
> >>>
> >>> I agree we want to develop a presence on Stack Overflow.  I still can't
> >> figure out how to earn enough points be able to answer any questions so
> I
> >> won't be of much help until that happens.
> >>>
> >>> -Alex
> >>>
> >>> On 4/29/19, 7:32 AM, "Carlos Rovira"  wrote:
> >>>
> >>>   Hi,
> >>>
> >>>   about StackOverFlow, we already discussed to start creating questions
> >> in
> >>>   SOF, but finally nobody does. I think I should not create one and
> >> respond
> >>>   myself right? it will be very sad to do in that way. So if someone
> >> start to
> >>>   post questions in SOF, I promise to respond, at least if it's
> >> something I
> >>>   can know how to respond. It could be things you already know, but we
> >> must
> >>>   start in some way.
> >>>
> >>>   SOF is crucial for us, I talked with customers that pointed me that
> >> Apache
> >>>   Royale is not on SOF, so his devs can easily search problems there.
> >> And
> >>>   this is the google for developers. If we are not there, Royale will
> >> never
> >>>   succeed, So if you want Royale to succeed we all should put some
> >> work, what
> >>>   we can, in SOF. @dany, if you want to start this effort we can follow
> >> you.
> >>>   Just let's know in a mail here so we can go to that link and respond.
> >> If
> >>>   you start that your work will be follow :)
> >>>
> >>>   @Andrew, "Flex In a Week" is a very good idea too. I think we can
> >> work on
> >>>   that, but again, we need some kind of plan. A team to work on that.
> >> Things
> >>>   like that can't be create by only one man's work. Volunteers?
> >>>
> >>>   @Om, I not use NPM but will try Royale CLI since we need something
> >> really
> >>>   fast to compete with React or others, or people will never jump to
> out
> >>>   wagon.
> >>>
> >>>   thanks for all the thoughts! :)
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>   El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala (<
> >> bigosma...@gmail.com>)
> >>>   escribió:
> >>>
>  On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt
>  >>>
>  wrote:
> 
> > 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
> >
> >
>  The Royale CLI is modeled closely after the create-react-app.  The
> docs
> >> for
>  the alpha version is available here:
> 
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fnpm%2Fclidata=02%7C01%7Caharui%40adobe.com%7C950f12a2b0f24cad192508d6ccaf8241%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636921451512477017sdata=4VN8JejglMeW08ZcNV6fCJ%2BdYJjOHcvfGDL099jives%3Dreserved=0
>  If I get more feedback, I am keep improving this tool.
> 
>  Thanks,
>  Om
> 
> 
> 
> > Verstuurd vanaf mijn iPhone
> >
> >> Op 26 apr. 2019 om 12:42 heeft Frost, Andrew <
> andrew.fr...@harman.com
> >>>
> > 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 

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Alex,

By commenting on questions, and when somebody upvotes your comment, you’ll earn 
points and at some point, you’ll get a badge permitting you to answer questions

Dany

> Op 29 apr. 2019, om 17:56 heeft Dany Dhondt  het 
> volgende geschreven:
> 
>> I agree we want to develop a presence on Stack Overflow.  I still can't 
>> figure out how to earn enough points be able to answer any questions so I 
>> won't be of much help until that happens.

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

[Mark Thomas]

I have no idea why this has been sent to me personally. I assume some
form of addressing error.

Mark


On 29/04/2019 16:41, Alex Harui wrote:
> @Mark, I'm assuming you want something in the output that identifies the 
> actual versions used.  In Royale, you may also need to identify the version 
> of the transpiler as well, and maybe the version of Google Closure.  If you 
> want to propose (or better yet, implement) a PAYG way to do that in Royale, 
> please do so.  If other folks think this will be useful, please speak up so 
> we get a sense of how important it is.  A simple hack may be to embed the 
> pom.xml file in your output as a string if you are using Maven.  If you use 
> Ant, you could grab the SDK version from build.properties or embed the 
> flex-sdk-description.xml file.
> 
> @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 are all what you need,
> so maven takes care of pulling all right dependencies you need.
> 
> @Alex, about extending IUIBase, my own experience is that beads are a very
> good way to extend/compose more code you need, but extending core
> interfaces like the one you said is not the case. Let me put you an
> example: For Jewel I use "StyledUIBase" that extends "UIBase" to add
> IClassSelectorListSupport, the css CRUD API (addClass, removeClass, 
> etc..):
> 
> public class StyledUIBase extends UIBase implements
> IClassSelectorListSupport
> 
> This makes that some components are easy to extend but others need to be
> recreate. There are lots of cases in Jewel where I need to
> 
> If you search in Jewel for implements IClassSelectorListSupport
>  you'll find Jewel Group, Jewel DataContainerBase and Jewel Table, are
> implementing that class while, so they are not StyledUIBase in it's core
> are standard UIBase and at its level we implement the interface and add
> again all methods repeating the code. So we are duplicating that code all
> that times.
> 
> I think this is one of the few things I don't like in Jewel, If you know
> some way to do this in a better way, I can change it
> 
> thanks
> 
> 
> 
> 
> 
> El lun., 29 abr. 2019 a las 12:36, Kessler CTR Mark J
> () escribió:
> 
> >  Yeah just concerned with an official build number, or date, or
> > something with numbers we can use to identify a production app back to 
> what
> > SDK was used to compile it.  Imagine having an app released on 
> production
> > and a user reports a problem. We would need to reproduce the problem in 
> a
> > test environment.  This would include using the same SDK to compile the
> > app.  Currently in Flex, we can just access its version directly which
> > makes things faster.
> >
> > If the SDK doesn't have anything like this at the moment and we did
> > add that functionality in there, I would say let's just use a date field
> > since it could be automated.  Something like MMDD type format.
> >
> >
> > -Mark K
> >
> >
> > -Original Message-
> > From: Alex Harui [mailto:aha...@adobe.com.INVALID]
> > Sent: Friday, April 26, 2019 12:02 PM
> > To: dev@royale.apache.org
> > Subject: [Non-DoD Source] Re: Version property (was: Let's bump Royale
> > version to 1.0)
> >
> >
> >
> > 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 

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Shouldn’t it be better to name it apache-royale?
That’s the way most tags are build I think

Dany


> Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki  
> het volgende geschreven:
> 
> Hi Dany,
> 
> We have agreed on "apacheroyale" tag in different thread. I think you could
> use that.
> 
> Thanks,
> Piotr
> 
> pon., 29 kwi 2019 o 17:56 Dany Dhondt 
> napisał(a):
> 
>> Can somebody create some royale tags please? I don’t have enough rep.
>> points at this moment.
>> Also, shouldn’t we agree on some basic royale tags?
>> When the tags are made, I’ll start posting some questions.
>> 
>> Dany
>> 
>>> Op 29 apr. 2019, om 17:27 heeft Alex Harui 
>> het volgende geschreven:
>>> 
>>> I agree we want to develop a presence on Stack Overflow.  I still can't
>> figure out how to earn enough points be able to answer any questions so I
>> won't be of much help until that happens.
>>> 
>>> -Alex
>>> 
>>> On 4/29/19, 7:32 AM, "Carlos Rovira"  wrote:
>>> 
>>>   Hi,
>>> 
>>>   about StackOverFlow, we already discussed to start creating questions
>> in
>>>   SOF, but finally nobody does. I think I should not create one and
>> respond
>>>   myself right? it will be very sad to do in that way. So if someone
>> start to
>>>   post questions in SOF, I promise to respond, at least if it's
>> something I
>>>   can know how to respond. It could be things you already know, but we
>> must
>>>   start in some way.
>>> 
>>>   SOF is crucial for us, I talked with customers that pointed me that
>> Apache
>>>   Royale is not on SOF, so his devs can easily search problems there.
>> And
>>>   this is the google for developers. If we are not there, Royale will
>> never
>>>   succeed, So if you want Royale to succeed we all should put some
>> work, what
>>>   we can, in SOF. @dany, if you want to start this effort we can follow
>> you.
>>>   Just let's know in a mail here so we can go to that link and respond.
>> If
>>>   you start that your work will be follow :)
>>> 
>>>   @Andrew, "Flex In a Week" is a very good idea too. I think we can
>> work on
>>>   that, but again, we need some kind of plan. A team to work on that.
>> Things
>>>   like that can't be create by only one man's work. Volunteers?
>>> 
>>>   @Om, I not use NPM but will try Royale CLI since we need something
>> really
>>>   fast to compete with React or others, or people will never jump to out
>>>   wagon.
>>> 
>>>   thanks for all the thoughts! :)
>>> 
>>> 
>>> 
>>> 
>>> 
>>>   El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala (<
>> bigosma...@gmail.com>)
>>>   escribió:
>>> 
 On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt >> 
 wrote:
 
> 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
> 
> 
 The Royale CLI is modeled closely after the create-react-app.  The docs
>> for
 the alpha version is available here:
 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fnpm%2Fclidata=02%7C01%7Caharui%40adobe.com%7C950f12a2b0f24cad192508d6ccaf8241%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636921451512477017sdata=4VN8JejglMeW08ZcNV6fCJ%2BdYJjOHcvfGDL099jives%3Dreserved=0
 If I get more feedback, I am keep improving this tool.
 
 Thanks,
 Om
 
 
 
> 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 

Re: Let's bump Royale version to 1.0

[Piotr Zarzycki]

Hi Dany,

We have agreed on "apacheroyale" tag in different thread. I think you could
use that.

Thanks,
Piotr

pon., 29 kwi 2019 o 17:56 Dany Dhondt 
napisał(a):

> Can somebody create some royale tags please? I don’t have enough rep.
> points at this moment.
> Also, shouldn’t we agree on some basic royale tags?
> When the tags are made, I’ll start posting some questions.
>
> Dany
>
> > Op 29 apr. 2019, om 17:27 heeft Alex Harui 
> het volgende geschreven:
> >
> > I agree we want to develop a presence on Stack Overflow.  I still can't
> figure out how to earn enough points be able to answer any questions so I
> won't be of much help until that happens.
> >
> > -Alex
> >
> > On 4/29/19, 7:32 AM, "Carlos Rovira"  wrote:
> >
> >Hi,
> >
> >about StackOverFlow, we already discussed to start creating questions
> in
> >SOF, but finally nobody does. I think I should not create one and
> respond
> >myself right? it will be very sad to do in that way. So if someone
> start to
> >post questions in SOF, I promise to respond, at least if it's
> something I
> >can know how to respond. It could be things you already know, but we
> must
> >start in some way.
> >
> >SOF is crucial for us, I talked with customers that pointed me that
> Apache
> >Royale is not on SOF, so his devs can easily search problems there.
> And
> >this is the google for developers. If we are not there, Royale will
> never
> >succeed, So if you want Royale to succeed we all should put some
> work, what
> >we can, in SOF. @dany, if you want to start this effort we can follow
> you.
> >Just let's know in a mail here so we can go to that link and respond.
> If
> >you start that your work will be follow :)
> >
> >@Andrew, "Flex In a Week" is a very good idea too. I think we can
> work on
> >that, but again, we need some kind of plan. A team to work on that.
> Things
> >like that can't be create by only one man's work. Volunteers?
> >
> >@Om, I not use NPM but will try Royale CLI since we need something
> really
> >fast to compete with React or others, or people will never jump to out
> >wagon.
> >
> >thanks for all the thoughts! :)
> >
> >
> >
> >
> >
> >El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala (<
> bigosma...@gmail.com>)
> >escribió:
> >
> >> On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt  >
> >> wrote:
> >>
> >>> 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
> >>>
> >>>
> >> The Royale CLI is modeled closely after the create-react-app.  The docs
> for
> >> the alpha version is available here:
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fnpm%2Fclidata=02%7C01%7Caharui%40adobe.com%7C950f12a2b0f24cad192508d6ccaf8241%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636921451512477017sdata=4VN8JejglMeW08ZcNV6fCJ%2BdYJjOHcvfGDL099jives%3Dreserved=0
> >> If I get more feedback, I am keep improving this tool.
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>
> >>> 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 

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Can somebody create some royale tags please? I don’t have enough rep. points at 
this moment.
Also, shouldn’t we agree on some basic royale tags?
When the tags are made, I’ll start posting some questions.

Dany

> Op 29 apr. 2019, om 17:27 heeft Alex Harui  het 
> volgende geschreven:
> 
> I agree we want to develop a presence on Stack Overflow.  I still can't 
> figure out how to earn enough points be able to answer any questions so I 
> won't be of much help until that happens.
> 
> -Alex
> 
> On 4/29/19, 7:32 AM, "Carlos Rovira"  wrote:
> 
>Hi,
> 
>about StackOverFlow, we already discussed to start creating questions in
>SOF, but finally nobody does. I think I should not create one and respond
>myself right? it will be very sad to do in that way. So if someone start to
>post questions in SOF, I promise to respond, at least if it's something I
>can know how to respond. It could be things you already know, but we must
>start in some way.
> 
>SOF is crucial for us, I talked with customers that pointed me that Apache
>Royale is not on SOF, so his devs can easily search problems there. And
>this is the google for developers. If we are not there, Royale will never
>succeed, So if you want Royale to succeed we all should put some work, what
>we can, in SOF. @dany, if you want to start this effort we can follow you.
>Just let's know in a mail here so we can go to that link and respond. If
>you start that your work will be follow :)
> 
>@Andrew, "Flex In a Week" is a very good idea too. I think we can work on
>that, but again, we need some kind of plan. A team to work on that. Things
>like that can't be create by only one man's work. Volunteers?
> 
>@Om, I not use NPM but will try Royale CLI since we need something really
>fast to compete with React or others, or people will never jump to out
>wagon.
> 
>thanks for all the thoughts! :)
> 
> 
> 
> 
> 
>El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala 
> ()
>escribió:
> 
>> On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt 
>> wrote:
>> 
>>> 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
>>> 
>>> 
>> The Royale CLI is modeled closely after the create-react-app.  The docs for
>> the alpha version is available here:
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fnpm%2Fclidata=02%7C01%7Caharui%40adobe.com%7C950f12a2b0f24cad192508d6ccaf8241%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636921451512477017sdata=4VN8JejglMeW08ZcNV6fCJ%2BdYJjOHcvfGDL099jives%3Dreserved=0
>> If I get more feedback, I am keep improving this tool.
>> 
>> Thanks,
>> Om
>> 
>> 
>> 
>>> 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.
 

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

[Alex Harui]

@Mark, I'm assuming you want something in the output that identifies the actual 
versions used.  In Royale, you may also need to identify the version of the 
transpiler as well, and maybe the version of Google Closure.  If you want to 
propose (or better yet, implement) a PAYG way to do that in Royale, please do 
so.  If other folks think this will be useful, please speak up so we get a 
sense of how important it is.  A simple hack may be to embed the pom.xml file 
in your output as a string if you are using Maven.  If you use Ant, you could 
grab the SDK version from build.properties or embed the 
flex-sdk-description.xml file.

@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 are all what you need,
so maven takes care of pulling all right dependencies you need.

@Alex, about extending IUIBase, my own experience is that beads are a very
good way to extend/compose more code you need, but extending core
interfaces like the one you said is not the case. Let me put you an
example: For Jewel I use "StyledUIBase" that extends "UIBase" to add
IClassSelectorListSupport, the css CRUD API (addClass, removeClass, etc..):

public class StyledUIBase extends UIBase implements
IClassSelectorListSupport

This makes that some components are easy to extend but others need to be
recreate. There are lots of cases in Jewel where I need to

If you search in Jewel for implements IClassSelectorListSupport
 you'll find Jewel Group, Jewel DataContainerBase and Jewel Table, are
implementing that class while, so they are not StyledUIBase in it's core
are standard UIBase and at its level we implement the interface and add
again all methods repeating the code. So we are duplicating that code all
that times.

I think this is one of the few things I don't like in Jewel, If you know
some way to do this in a better way, I can change it

thanks





El lun., 29 abr. 2019 a las 12:36, Kessler CTR Mark J
() escribió:

>  Yeah just concerned with an official build number, or date, or
> something with numbers we can use to identify a production app back to 
what
> SDK was used to compile it.  Imagine having an app released on production
> and a user reports a problem. We would need to reproduce the problem in a
> test environment.  This would include using the same SDK to compile the
> app.  Currently in Flex, we can just access its version directly which
> makes things faster.
>
> If the SDK doesn't have anything like this at the moment and we did
> add that functionality in there, I would say let's just use a date field
> since it could be automated.  Something like MMDD type format.
>
>
> -Mark K
>
>
> -Original Message-
> From: Alex Harui [mailto:aha...@adobe.com.INVALID]
> Sent: Friday, April 26, 2019 12:02 PM
> To: dev@royale.apache.org
> Subject: [Non-DoD Source] Re: Version property (was: Let's bump Royale
> version to 1.0)
>
>
>
> 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 

Re: Let's bump Royale version to 1.0

[Carlos Rovira]

Hi,

about StackOverFlow, we already discussed to start creating questions in
SOF, but finally nobody does. I think I should not create one and respond
myself right? it will be very sad to do in that way. So if someone start to
post questions in SOF, I promise to respond, at least if it's something I
can know how to respond. It could be things you already know, but we must
start in some way.

SOF is crucial for us, I talked with customers that pointed me that Apache
Royale is not on SOF, so his devs can easily search problems there. And
this is the google for developers. If we are not there, Royale will never
succeed, So if you want Royale to succeed we all should put some work, what
we can, in SOF. @dany, if you want to start this effort we can follow you.
Just let's know in a mail here so we can go to that link and respond. If
you start that your work will be follow :)

@Andrew, "Flex In a Week" is a very good idea too. I think we can work on
that, but again, we need some kind of plan. A team to work on that. Things
like that can't be create by only one man's work. Volunteers?

@Om, I not use NPM but will try Royale CLI since we need something really
fast to compete with React or others, or people will never jump to out
wagon.

thanks for all the thoughts! :)





El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala ()
escribió:

> On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt 
> wrote:
>
> > 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
> >
> >
> The Royale CLI is modeled closely after the create-react-app.  The docs for
> the alpha version is available here:
> https://github.com/apache/royale-asjs/tree/develop/npm/cli
> If I get more feedback, I am keep improving this tool.
>
> Thanks,
> Om
>
>
>
> > 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 (<
> > 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?
> > >>>
> > >>> 

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

[Carlos Rovira]

@Mark, if you use Maven, then artifacts in the poms are all what you need,
so maven takes care of pulling all right dependencies you need.

@Alex, about extending IUIBase, my own experience is that beads are a very
good way to extend/compose more code you need, but extending core
interfaces like the one you said is not the case. Let me put you an
example: For Jewel I use "StyledUIBase" that extends "UIBase" to add
IClassSelectorListSupport, the css CRUD API (addClass, removeClass, etc..):

public class StyledUIBase extends UIBase implements
IClassSelectorListSupport

This makes that some components are easy to extend but others need to be
recreate. There are lots of cases in Jewel where I need to

If you search in Jewel for implements IClassSelectorListSupport
 you'll find Jewel Group, Jewel DataContainerBase and Jewel Table, are
implementing that class while, so they are not StyledUIBase in it's core
are standard UIBase and at its level we implement the interface and add
again all methods repeating the code. So we are duplicating that code all
that times.

I think this is one of the few things I don't like in Jewel, If you know
some way to do this in a better way, I can change it

thanks





El lun., 29 abr. 2019 a las 12:36, Kessler CTR Mark J
() escribió:

>  Yeah just concerned with an official build number, or date, or
> something with numbers we can use to identify a production app back to what
> SDK was used to compile it.  Imagine having an app released on production
> and a user reports a problem. We would need to reproduce the problem in a
> test environment.  This would include using the same SDK to compile the
> app.  Currently in Flex, we can just access its version directly which
> makes things faster.
>
> If the SDK doesn't have anything like this at the moment and we did
> add that functionality in there, I would say let's just use a date field
> since it could be automated.  Something like MMDD type format.
>
>
> -Mark K
>
>
> -Original Message-
> From: Alex Harui [mailto:aha...@adobe.com.INVALID]
> Sent: Friday, April 26, 2019 12:02 PM
> To: dev@royale.apache.org
> Subject: [Non-DoD Source] Re: Version property (was: Let's bump Royale
> version to 1.0)
>
>
>
> 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
>
>

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

Build failed in Jenkins: royale-asjs_MXTests #731

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

[Kessler CTR Mark J]

 Yeah just concerned with an official build number, or date, or something 
with numbers we can use to identify a production app back to what SDK was used 
to compile it.  Imagine having an app released on production and a user reports 
a problem. We would need to reproduce the problem in a test environment.  This 
would include using the same SDK to compile the app.  Currently in Flex, we can 
just access its version directly which makes things faster.

If the SDK doesn't have anything like this at the moment and we did add 
that functionality in there, I would say let's just use a date field since it 
could be automated.  Something like MMDD type format.


-Mark K


-Original Message-
From: Alex Harui [mailto:aha...@adobe.com.INVALID]
Sent: Friday, April 26, 2019 12:02 PM
To: dev@royale.apache.org
Subject: [Non-DoD Source] Re: Version property (was: Let's bump Royale version 
to 1.0)



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

Re: Let's bump Royale version to 1.0

[OmPrakash Muppirala]

On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt 
wrote:

> 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
>
>
The Royale CLI is modeled closely after the create-react-app.  The docs for
the alpha version is available here:
https://github.com/apache/royale-asjs/tree/develop/npm/cli
If I get more feedback, I am keep improving this tool.

Thanks,
Om



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

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

[Olaf Krueger]

Hi Justin,
thanks for your amazing offer!

> ...what Alex and Carlos want to see happen...

Before others will do this I would just like to mention that no individuals
make decisions here at Apache. It's always the community! ;-)

However, I am curious about the feedback!

Thanks,
Olaf





 







--
Sent from: http://apache-royale-development.20373.n8.nabble.com/