[ANNOUNCE] Apache Royale 0.9.1 Released

[Alex Harui]

The Apache Royale community is pleased to announce the release of Apache
Royale 0.9.1.

The Apache Royale project is a continuation of the previous effort called
FlexJS to produce a next-generation of the Apache Flex SDK that enables
developers to use MXML and ActionScript to generate HTML/JS/CSS
applications which can run natively in browsers. The cross-compiled code
can also be used in Apache Cordova (Adobe PhoneGap) mobile applications.


(Apache Flex is a highly productive, open source application framework for
building and maintaining expressive applications that deploy on Adobe
Flash and Adobe AIR to provide a consistent experience on all major
browsers, desktops and devices.)

This release should be considered ‘beta' quality. The purpose of this
release is to gather feedback about the features and implementation
strategies, and to recruit new contributors. We hope to grow the code base
into an SDK and tool chain that delivers the highest productivity when
developing applications that can run on many platforms. Beta releases may
not handle production needs.

Please file bugs at:

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

If you happen to know it is a compiler issue, please use:

  https://github.com/apache/royale-compiler/issues

For questions about how to use Royale, send email to
us...@royale.apache.org.  For questions and feedback on the development of
the source code in the release, send email to dev@royale.apache.org.

Apache Royale is available in source and binary form from the Apache
mirrors:

Source:
http://www.apache.org/dyn/closer.lua/royale/0.9.1/apache-royale-0.9.1-src.t
ar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.1/apache-royale-0.9.1-src.z
ip

Binary:
http://www.apache.org/dyn/closer.lua/royale/0.9.1/binaries/apache-royale-0.
9.1-bin-js.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.1/binaries/apache-royale-0.
9.1-bin-js.zip

Binary with SWF support:
http://www.apache.org/dyn/closer.lua/royale/0.9.1/binaries/apache-royale-0.
9.1-bin-js-swf.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.1/binaries/apache-royale-0.
9.1-bin-js-swf.zip

When downloading from a mirror site, please remember to verify the
downloads using signatures or MD5 hashes.

The binary packages can also be installed via NPM.

Mac:

  sudo npm install @apache-royale/royale-js -g

Or for SWF Support:

  sudo npm install @apache-royale/royale-js-swf -g



Windows:

  npm install @apache-royale/royale-js -g

Or for SWF Support:

  npm install @apache-royale/royale-js-swf -g



See the README for more information. The language reference (ASDoc) is
here:

  http://royale.apache.org/asdoc/

Additional documentation is here:

  https://apache.github.io/royale-docs/

The documentation is still a work in progress.  Volunteers are welcome to
help improve it.  Visit http://royale.apache.org/ for links to other
resources.

Please try Royale and become involved in shaping the future of application
development.

The Apache Royale Community

Build failed in Jenkins: royale-typedefs #148

[apacheroyaleci]

See 


--
[...truncated 110.35 KB...]
 [exec] D   test/com/google/javascript/jscomp/parsing/TypeSyntaxTest.java
 [exec] D   
test/com/google/javascript/jscomp/parsing/parser/FeatureSetTest.java
 [exec] D   
test/com/google/javascript/jscomp/parsing/parser/util/format/SimpleFormatTest.java
 [exec] D   test/com/google/javascript/jscomp/regex/CharRangesTest.java
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/array_pattern_test.js
 [exec] D   test/com/google/javascript/jscomp/runtime_tests/arrow_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/async_function_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_block_scope_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_computed_getter_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_exported_getter_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_getter_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_in_goog_module_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_no_constructor_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_spread_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_static_getter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_static_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_super_return_test.js
 [exec] D   test/com/google/javascript/jscomp/runtime_tests/class_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/collections_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/computed_properties_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/default_param_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/es3_style_class.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/extend_es3_test.js
 [exec] D   test/com/google/javascript/jscomp/runtime_tests/for_of_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/generator_allow_call_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/generator_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/identifier_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/inherit_sets_superClass_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/inheritance_with_overriden_function_prototype_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/let_const_loop_typecheck_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/let_const_rename_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/mixed_destructuring_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/mocking_class_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/class_inherits_protected.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/dot_dot_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/export_from_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/export_spec_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_class_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_default_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_mixed_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_namespace_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_star_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_with_js_extension_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_order_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_runtime_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/classProtectedMethod.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_a.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportClass.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportDefault.js
 [exec] D   

Build failed in Jenkins: royale-asjs_jsonly #296

[apacheroyaleci]

See 


--
[...truncated 651.83 KB...]
 [exec] D   test/com/google/javascript/jscomp/regex/CharRangesTest.java
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/array_pattern_test.js
 [exec] D   test/com/google/javascript/jscomp/runtime_tests/arrow_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/async_function_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_block_scope_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_computed_getter_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_exported_getter_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_getter_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_in_goog_module_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_no_constructor_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_spread_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_static_getter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_static_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_super_return_test.js
 [exec] D   test/com/google/javascript/jscomp/runtime_tests/class_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/collections_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/computed_properties_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/default_param_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/es3_style_class.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/extend_es3_test.js
 [exec] D   test/com/google/javascript/jscomp/runtime_tests/for_of_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/generator_allow_call_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/generator_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/identifier_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/inherit_sets_superClass_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/inheritance_with_overriden_function_prototype_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/let_const_loop_typecheck_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/let_const_rename_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/mixed_destructuring_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/mocking_class_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/class_inherits_protected.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/dot_dot_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/export_from_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/export_spec_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_class_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_default_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_mixed_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_namespace_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_star_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_with_js_extension_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_order_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_runtime_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/classProtectedMethod.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_a.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportClass.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportDefault.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportDefaultClass.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportDefaultOldStyleClass.js
 [exec] D   

[GitHub] cottage14 closed pull request #5: Develop

[GitBox]

cottage14 closed pull request #5: Develop
URL: https://github.com/apache/royale-docs/pull/5
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] cottage14 opened a new pull request #5: Develop

[GitBox]

cottage14 opened a new pull request #5: Develop
URL: https://github.com/apache/royale-docs/pull/5
 
 
   Made some edits to the files in the "Get Started" package.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Royale Examples Blog proposal to all the team

[Jason Guild]

Carlos:

Looks great. In the code snippets that appear with the examples, it 
would be good to make it as easy as possible for people to copy and 
paste the code into their own project so they can try it out. Right now 
it's too easy to end up copying the line numbers shown next to the 
sample code.


Suggest applying "user-select: none" CSS property [1] to the 
"line-numbers" class.


Thanks for your hard work on this.
Jason

[1] https://developer.mozilla.org/en-US/docs/Web/CSS/user-select

On 2/13/2018 12:45 PM, Carlos Rovira wrote:

Hi all,

just let you know that I updated the Hello World with :

* working example (loaded below in Iframe)
* added more explanations
* Updated styled in code to look better.

I think we have the final base for the rest of blog examples

https://royale.apache.org/creating-a-hello-world-in-apache-royale/


hope you liked the final result :)



2018-02-13 22:42 GMT+01:00 Carlos Rovira :


Hi Alex,

I can make another blog post with Express, based on the first one. I look
at it tomorrow :)


2018-02-13 18:36 GMT+01:00 Alex Harui :


I just looked at the Hello World example.  IMO, these examples should use
Express, not Basic, and then the code would be even shorter.

My 2 cents,
-Alex

On 2/13/18, 9:21 AM, "Alex Harui"  wrote:


Having an Examples blog is a great thing.

I saw the calendar invite.  I couldn't see the calendar I think because
default to logging in under a different email and don't really want this
stuff mixed into to my default calendar.

My only concern is the scheduling.  IMO, scheduling is difficult with
volunteers.  Folks get busy with their $dayjob and may run out of time.
We should accept entries from anyone, even non-committers, at any time.
So what if we get a burst here and it goes quiet for a while?  Carlos, if
you want to volunteer to keep track of the last post date, then if a week
goes by without a new post you could ask on the mailing list for a
volunteer to write the next post.  And anyone reading this email is
welcome to write a post or suggest a topic.  That will likely be the
biggest question for me: what should I write about?

Anyway, thanks for getting this started.

My 2 cents,
-Alex

On 2/13/18, 3:09 AM, "carlos.rov...@gmail.com on behalf of Carlos

Rovira"

 wrote:


Hi Olaf

2018-02-13 11:31 GMT+01:00 Olaf Krueger :


I'd like to read thoughts from others in the team.

This is a really good idea, Carlos!
If I understand you right you'd like to say that we want to publish a
post
every two weeks and because we're about 10 to 15 people who will
contribute
this means that anybody of us has to write an article approx every 6
months?!
And you want us to manage the scheduling of the blog posts by using

the

google calendar?


That's right! I think if we all participate will 10-11, and about 6
months
between repeat author.
Maybe, as examples are very easy to do we can talk more later if we do
this
each week...we'll see as we develop it right?



Below the source code, we should have the result displayed in an

iframe.
+1

Another suggestion:
Peter de Haan posts always contain some simple explanations.
Regarding the "Hello world" post, I think it would be interesting for
people
to learn something about the code, e.g. for what is
"js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
Maybe it makes sense to link something to the docs or to add some
simple
explanation?


That's a very good idea. I'll try to update the hello world with this
suggestions :)



I'll check out the google calendar...

Thanks,
Olaf









--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%

3A%2F%2Fapache-r

o
yale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%

40adobe.co

m
%7Cd2453e80427a4a2db4a708d572d259e3%7Cfa7b1b5a7b34438794a

ed2c178decee1%7

C
0%7C0%7C636541170132357067=IW1I%2BZebS7gSyrBako0WCH

BAG8eo1b3NPVnfC

%
2BvUyTA%3D=0




--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%

3A%2F%2Fabout.me%

2
Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cd2453e80

427a4a2db4a708d

5
72d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365

41170132357067&

s
data=YBsn0zhxZd98toKr%2BrZP1GwprmRzcmM5NesejiabbJo%3D=0




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






--
Jason Guild
Analyst/Programmer V
State of Alaska - Department of Transportation & Public Facilities
Information Systems and Services Division
820 E. 15th Ave.
Anchorage, Alaska 99501

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

[Jason Guild]

Please pull the first sentence from the 0.9.0 blog announcement that 
Carlos recently worked on.

It reads better and is grammatically correct.

On 2/13/2018 12:15 PM, Alex Harui wrote:

We will wait a bit for other feedback and let the mirrors finish
propagating.  I'll post it in about 8 hours if no other feedback.

-Alex

On 2/13/18, 1:00 PM, "Piotr Zarzycki"  wrote:


Go on and announce. I will fill GitHub release once it will be done! :)

Thanks,
Piotr

2018-02-13 21:57 GMT+01:00 Andrew Wetmore :


This announcement seems clear and inviting.

On Tue, Feb 13, 2018 at 3:06 PM, Alex Harui 
wrote:


Please comment on the draft below.

Thoughts?
-Alex




--
Andrew Wetmore


https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14
.blogspot.com%2F=02%7C01%7Caharui%40adobe.com%7Cd4c77f7efac24c43527b
08d57324d7ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541524457865
491=i2PjCF4AaKmM70dq489Z60snqnKXjufTQU6iTKe34Jg%3D=0




--

Piotr Zarzycki

Patreon:
*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
eon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7Cd4c77f7efac24c
43527b08d57324d7ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365415244
57865491=4K39eoxbjwFxRmtuduLgUulDCCVtPnrkQHxQ1UIIO%2F4%3D=0

Re: Royale Examples Blog proposal to all the team

[Gabe Harbs]

Looks great!

> On Feb 13, 2018, at 11:45 PM, Carlos Rovira  wrote:
> 
> Hi all,
> 
> just let you know that I updated the Hello World with :
> 
> * working example (loaded below in Iframe)
> * added more explanations
> * Updated styled in code to look better.
> 
> I think we have the final base for the rest of blog examples
> 
> https://royale.apache.org/creating-a-hello-world-in-apache-royale/
> 
> 
> hope you liked the final result :)
> 
> 
> 
> 2018-02-13 22:42 GMT+01:00 Carlos Rovira :
> 
>> Hi Alex,
>> 
>> I can make another blog post with Express, based on the first one. I look
>> at it tomorrow :)
>> 
>> 
>> 2018-02-13 18:36 GMT+01:00 Alex Harui :
>> 
>>> I just looked at the Hello World example.  IMO, these examples should use
>>> Express, not Basic, and then the code would be even shorter.
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> On 2/13/18, 9:21 AM, "Alex Harui"  wrote:
>>> 
 Having an Examples blog is a great thing.
 
 I saw the calendar invite.  I couldn't see the calendar I think because
 default to logging in under a different email and don't really want this
 stuff mixed into to my default calendar.
 
 My only concern is the scheduling.  IMO, scheduling is difficult with
 volunteers.  Folks get busy with their $dayjob and may run out of time.
 We should accept entries from anyone, even non-committers, at any time.
 So what if we get a burst here and it goes quiet for a while?  Carlos, if
 you want to volunteer to keep track of the last post date, then if a week
 goes by without a new post you could ask on the mailing list for a
 volunteer to write the next post.  And anyone reading this email is
 welcome to write a post or suggest a topic.  That will likely be the
 biggest question for me: what should I write about?
 
 Anyway, thanks for getting this started.
 
 My 2 cents,
 -Alex
 
 On 2/13/18, 3:09 AM, "carlos.rov...@gmail.com on behalf of Carlos
>>> Rovira"
  wrote:
 
> Hi Olaf
> 
> 2018-02-13 11:31 GMT+01:00 Olaf Krueger :
> 
>>> I'd like to read thoughts from others in the team.
>> 
>> This is a really good idea, Carlos!
>> If I understand you right you'd like to say that we want to publish a
>> post
>> every two weeks and because we're about 10 to 15 people who will
>> contribute
>> this means that anybody of us has to write an article approx every 6
>> months?!
>> And you want us to manage the scheduling of the blog posts by using
>>> the
>> google calendar?
>> 
> 
> That's right! I think if we all participate will 10-11, and about 6
> months
> between repeat author.
> Maybe, as examples are very easy to do we can talk more later if we do
> this
> each week...we'll see as we develop it right?
> 
> 
>> 
>>> Below the source code, we should have the result displayed in an
>> iframe.
>> +1
>> 
>> Another suggestion:
>> Peter de Haan posts always contain some simple explanations.
>> Regarding the "Hello world" post, I think it would be interesting for
>> people
>> to learn something about the code, e.g. for what is
>> "js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
>> Maybe it makes sense to link something to the docs or to add some
>> simple
>> explanation?
>> 
> 
> That's a very good idea. I'll try to update the hello world with this
> suggestions :)
> 
> 
>> 
>> I'll check out the google calendar...
>> 
>> Thanks,
>> Olaf
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> --
>> Sent from:
>> https://na01.safelinks.protection.outlook.com/?url=http%
>>> 3A%2F%2Fapache-r
>> o
>> yale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%
>>> 40adobe.co
>> m
>> %7Cd2453e80427a4a2db4a708d572d259e3%7Cfa7b1b5a7b34438794a
>>> ed2c178decee1%7
>> C
>> 0%7C0%7C636541170132357067=IW1I%2BZebS7gSyrBako0WCH
>>> BAG8eo1b3NPVnfC
>> %
>> 2BvUyTA%3D=0
>> 
> 
> 
> 
> --
> Carlos Rovira
> https://na01.safelinks.protection.outlook.com/?url=http%
>>> 3A%2F%2Fabout.me%
> 2
> Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cd2453e80
>>> 427a4a2db4a708d
> 5
> 72d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365
>>> 41170132357067&
> s
> data=YBsn0zhxZd98toKr%2BrZP1GwprmRzcmM5NesejiabbJo%3D=0
 
>>> 
>>> 
>> 
>> 
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>> 
>> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

Question for (I think) Alex:

How does this target work?






What sets the ROYALE_DOWNLOAD_CACHE and what saves the files there?

> On Feb 13, 2018, at 11:41 PM, Gabe Harbs  wrote:
> 
> I’m not sure I’m going to get to this tonight. If not, I’ll try to fix the 
> builds first thing in the morning.
> 
> I’m going to put back the unzipping of the externs and I’m replacing the 
> specific ones which need editing. I should be able to fix both the ant and 
> maven builds.
> 
> Harbs
> 
>> On Feb 13, 2018, at 10:49 PM, Piotr Zarzycki  
>> wrote:
>> 
>> Where is the conclusion, cause I lost a bit track with that. What are you
>> going to do next Harbs ? Should I still spent some time on Maven ?
>> 
>> 2018-02-13 19:45 GMT+01:00 Gabe Harbs :
>> 
>>> Ultimately, using those files is probably the way to go, but I’ll go back
>>> to overwriting individual files for now…
>>> 
>>> I’ll work on this a bit later.
>>> 
>>> Harbs
>>> 
 On Feb 13, 2018, at 8:04 PM, Alex Harui 
>>> wrote:
 
 I think we are working against an older closure-compiler.  Volunteers are
 welcome to move us to the latest.
 
 I think we only patch a dozen files or so, so yes, even if you coned the
 originals to royale-extras, I thought you would just cherry pick the few
 files we need.  IMO, you can do that and get both Maven and Ant working
 with less hassle.
 
 My 2 cents,
 -Alex
 
 On 2/13/18, 9:45 AM, "Gabe Harbs"  wrote:
 
> BTW, when I switched to the newer extern files that turned upon some
>>> more
> bugs with them.
> 
> I’m not ure at what point the newer externs are/will be included in the
> closure-compiler download, but more files will become an issue at
> whatever point they do.
> 
>> On Feb 13, 2018, at 7:40 PM, Gabe Harbs  wrote:
>> 
>> You mean just download the specific files we need?
>> 
>> I figured we might as well just get all the files from the same repo.
>> 
>>> On Feb 13, 2018, at 7:28 PM, Alex Harui >> > wrote:
>>> 
>>> I don't understand what is wrong with the way it worked.  Isn't the
>>> idea
>>> that you are overlaying files from royale-extras?  Why can't the
>>> current
>>> build expand the externs from closure-compiler and then your stuff can
>>> overlay it?
>>> 
>>> Thoughts?
>> -Alex
>>> 
>>> On 2/13/18, 5:26 AM, "Gabe Harbs" >> > wrote:
>>> 
 Maybe. I didn’t realize changing the typedefs was going to end up
 being
 so complicated.
 
 I just changed the ant build to use git instead of svn. It takes
 about a
 minute the first time the repo is needed to be ownloaded, but it’s
 pretty quick afterwards.
 
 I’m not sure which method is best for Maven.
 
> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki
> >
> wrote:
> 
> Btw. Maybe you should move your changes to separate branch. We will
> have
> emails with fails for a long time now. Unless someone else look into
> the
> Maven.
> 
> 2018-02-13 13:03 GMT+01:00 Gabe Harbs  
> >>:
> 
>> FWIW, here’s some other options for downloading a specific folder
>> from
>> Github:
>> 
>> 
>> https://na01.safelinks.protection.outlook.com/?url=
>>> https%3A%2F%2Fstac
>> kov
>> >> https%3A%2F%2Fsta
>> ckov>
>> erflow.com
>> >> http%3A%2F%2Ferfl
>> ow.com%2F=02%7C01%7Caharui%40adobe.com%
>>> 7Cd1228ae32eca45e43ce208d
>> 57309af91%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C63654140779893
>> 6061=zxNWE%2BwbCzZDK1diTruXDmroGk%
>>> 2BxVzdwIVm%2Bxxg4LAc%3D
>> ved=0>%2Fa%2F18194523=02%7C01%7Caharui%40adobe.com
>> >> http%3A%2F%2F40ad
>> obe.com%2F=02%7C01%7Caharui%40adobe.com%
>>> 7Cd1228ae32eca45e43ce208
>> d57309af91%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C6365414077989
>> 36061=rZuwf0WjH2xZAOacIz7ECWcohPvCLU
>>> IJg471M7Yhs%2Fc%3D
>> =0>%7C2fc7071c44
>> 
>> 6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C6
>> 365
>> 
>> 41251966892882=hv35Ja58vctUc%2BCbeuID%
>>> 2FiH9hRZ1gDnv0gumtvfrQ2Y%

Re: Royale Examples Blog proposal to all the team

[Carlos Rovira]

Hi all,

just let you know that I updated the Hello World with :

* working example (loaded below in Iframe)
* added more explanations
* Updated styled in code to look better.

I think we have the final base for the rest of blog examples

https://royale.apache.org/creating-a-hello-world-in-apache-royale/


hope you liked the final result :)



2018-02-13 22:42 GMT+01:00 Carlos Rovira :

> Hi Alex,
>
> I can make another blog post with Express, based on the first one. I look
> at it tomorrow :)
>
>
> 2018-02-13 18:36 GMT+01:00 Alex Harui :
>
>> I just looked at the Hello World example.  IMO, these examples should use
>> Express, not Basic, and then the code would be even shorter.
>>
>> My 2 cents,
>> -Alex
>>
>> On 2/13/18, 9:21 AM, "Alex Harui"  wrote:
>>
>> >Having an Examples blog is a great thing.
>> >
>> >I saw the calendar invite.  I couldn't see the calendar I think because
>> >default to logging in under a different email and don't really want this
>> >stuff mixed into to my default calendar.
>> >
>> >My only concern is the scheduling.  IMO, scheduling is difficult with
>> >volunteers.  Folks get busy with their $dayjob and may run out of time.
>> >We should accept entries from anyone, even non-committers, at any time.
>> >So what if we get a burst here and it goes quiet for a while?  Carlos, if
>> >you want to volunteer to keep track of the last post date, then if a week
>> >goes by without a new post you could ask on the mailing list for a
>> >volunteer to write the next post.  And anyone reading this email is
>> >welcome to write a post or suggest a topic.  That will likely be the
>> >biggest question for me: what should I write about?
>> >
>> >Anyway, thanks for getting this started.
>> >
>> >My 2 cents,
>> >-Alex
>> >
>> >On 2/13/18, 3:09 AM, "carlos.rov...@gmail.com on behalf of Carlos
>> Rovira"
>> > wrote:
>> >
>> >>Hi Olaf
>> >>
>> >>2018-02-13 11:31 GMT+01:00 Olaf Krueger :
>> >>
>> >>> >I'd like to read thoughts from others in the team.
>> >>>
>> >>> This is a really good idea, Carlos!
>> >>> If I understand you right you'd like to say that we want to publish a
>> >>>post
>> >>> every two weeks and because we're about 10 to 15 people who will
>> >>>contribute
>> >>> this means that anybody of us has to write an article approx every 6
>> >>> months?!
>> >>> And you want us to manage the scheduling of the blog posts by using
>> the
>> >>> google calendar?
>> >>>
>> >>
>> >>That's right! I think if we all participate will 10-11, and about 6
>> >>months
>> >>between repeat author.
>> >>Maybe, as examples are very easy to do we can talk more later if we do
>> >>this
>> >>each week...we'll see as we develop it right?
>> >>
>> >>
>> >>>
>> >>> >Below the source code, we should have the result displayed in an
>> >>>iframe.
>> >>> +1
>> >>>
>> >>> Another suggestion:
>> >>> Peter de Haan posts always contain some simple explanations.
>> >>> Regarding the "Hello world" post, I think it would be interesting for
>> >>> people
>> >>> to learn something about the code, e.g. for what is
>> >>> "js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
>> >>> Maybe it makes sense to link something to the docs or to add some
>> >>>simple
>> >>> explanation?
>> >>>
>> >>
>> >>That's a very good idea. I'll try to update the hello world with this
>> >>suggestions :)
>> >>
>> >>
>> >>>
>> >>> I'll check out the google calendar...
>> >>>
>> >>> Thanks,
>> >>> Olaf
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Sent from:
>> >>>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fapache-r
>> >>>o
>> >>>yale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%
>> 40adobe.co
>> >>>m
>> >>>%7Cd2453e80427a4a2db4a708d572d259e3%7Cfa7b1b5a7b34438794a
>> ed2c178decee1%7
>> >>>C
>> >>>0%7C0%7C636541170132357067=IW1I%2BZebS7gSyrBako0WCH
>> BAG8eo1b3NPVnfC
>> >>>%
>> >>>2BvUyTA%3D=0
>> >>>
>> >>
>> >>
>> >>
>> >>--
>> >>Carlos Rovira
>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fabout.me%
>> >>2
>> >>Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cd2453e80
>> 427a4a2db4a708d
>> >>5
>> >>72d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365
>> 41170132357067&
>> >>s
>> >>data=YBsn0zhxZd98toKr%2BrZP1GwprmRzcmM5NesejiabbJo%3D=0
>> >
>>
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


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

Re: Royale Examples Blog proposal to all the team

[Carlos Rovira]

Hi Alex,

I can make another blog post with Express, based on the first one. I look
at it tomorrow :)


2018-02-13 18:36 GMT+01:00 Alex Harui :

> I just looked at the Hello World example.  IMO, these examples should use
> Express, not Basic, and then the code would be even shorter.
>
> My 2 cents,
> -Alex
>
> On 2/13/18, 9:21 AM, "Alex Harui"  wrote:
>
> >Having an Examples blog is a great thing.
> >
> >I saw the calendar invite.  I couldn't see the calendar I think because
> >default to logging in under a different email and don't really want this
> >stuff mixed into to my default calendar.
> >
> >My only concern is the scheduling.  IMO, scheduling is difficult with
> >volunteers.  Folks get busy with their $dayjob and may run out of time.
> >We should accept entries from anyone, even non-committers, at any time.
> >So what if we get a burst here and it goes quiet for a while?  Carlos, if
> >you want to volunteer to keep track of the last post date, then if a week
> >goes by without a new post you could ask on the mailing list for a
> >volunteer to write the next post.  And anyone reading this email is
> >welcome to write a post or suggest a topic.  That will likely be the
> >biggest question for me: what should I write about?
> >
> >Anyway, thanks for getting this started.
> >
> >My 2 cents,
> >-Alex
> >
> >On 2/13/18, 3:09 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> > wrote:
> >
> >>Hi Olaf
> >>
> >>2018-02-13 11:31 GMT+01:00 Olaf Krueger :
> >>
> >>> >I'd like to read thoughts from others in the team.
> >>>
> >>> This is a really good idea, Carlos!
> >>> If I understand you right you'd like to say that we want to publish a
> >>>post
> >>> every two weeks and because we're about 10 to 15 people who will
> >>>contribute
> >>> this means that anybody of us has to write an article approx every 6
> >>> months?!
> >>> And you want us to manage the scheduling of the blog posts by using the
> >>> google calendar?
> >>>
> >>
> >>That's right! I think if we all participate will 10-11, and about 6
> >>months
> >>between repeat author.
> >>Maybe, as examples are very easy to do we can talk more later if we do
> >>this
> >>each week...we'll see as we develop it right?
> >>
> >>
> >>>
> >>> >Below the source code, we should have the result displayed in an
> >>>iframe.
> >>> +1
> >>>
> >>> Another suggestion:
> >>> Peter de Haan posts always contain some simple explanations.
> >>> Regarding the "Hello world" post, I think it would be interesting for
> >>> people
> >>> to learn something about the code, e.g. for what is
> >>> "js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
> >>> Maybe it makes sense to link something to the docs or to add some
> >>>simple
> >>> explanation?
> >>>
> >>
> >>That's a very good idea. I'll try to update the hello world with this
> >>suggestions :)
> >>
> >>
> >>>
> >>> I'll check out the google calendar...
> >>>
> >>> Thanks,
> >>> Olaf
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Sent from:
> >>>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-r
> >>>o
> >>>yale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%
> 40adobe.co
> >>>m
> >>>%7Cd2453e80427a4a2db4a708d572d259e3%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7
> >>>C
> >>>0%7C0%7C636541170132357067=IW1I%2BZebS7gSyrBako0WCHBAG8eo1b3NP
> VnfC
> >>>%
> >>>2BvUyTA%3D=0
> >>>
> >>
> >>
> >>
> >>--
> >>Carlos Rovira
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%
> >>2
> >>Fcarlosrovira=02%7C01%7Caharui%40adobe.com%
> 7Cd2453e80427a4a2db4a708d
> >>5
> >>72d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636541170132357067&
> >>s
> >>data=YBsn0zhxZd98toKr%2BrZP1GwprmRzcmM5NesejiabbJo%3D=0
> >
>
>


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

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

I’m not sure I’m going to get to this tonight. If not, I’ll try to fix the 
builds first thing in the morning.

I’m going to put back the unzipping of the externs and I’m replacing the 
specific ones which need editing. I should be able to fix both the ant and 
maven builds.

Harbs

> On Feb 13, 2018, at 10:49 PM, Piotr Zarzycki  
> wrote:
> 
> Where is the conclusion, cause I lost a bit track with that. What are you
> going to do next Harbs ? Should I still spent some time on Maven ?
> 
> 2018-02-13 19:45 GMT+01:00 Gabe Harbs :
> 
>> Ultimately, using those files is probably the way to go, but I’ll go back
>> to overwriting individual files for now…
>> 
>> I’ll work on this a bit later.
>> 
>> Harbs
>> 
>>> On Feb 13, 2018, at 8:04 PM, Alex Harui 
>> wrote:
>>> 
>>> I think we are working against an older closure-compiler.  Volunteers are
>>> welcome to move us to the latest.
>>> 
>>> I think we only patch a dozen files or so, so yes, even if you coned the
>>> originals to royale-extras, I thought you would just cherry pick the few
>>> files we need.  IMO, you can do that and get both Maven and Ant working
>>> with less hassle.
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> On 2/13/18, 9:45 AM, "Gabe Harbs"  wrote:
>>> 
 BTW, when I switched to the newer extern files that turned upon some
>> more
 bugs with them.
 
 I’m not ure at what point the newer externs are/will be included in the
 closure-compiler download, but more files will become an issue at
 whatever point they do.
 
> On Feb 13, 2018, at 7:40 PM, Gabe Harbs  wrote:
> 
> You mean just download the specific files we need?
> 
> I figured we might as well just get all the files from the same repo.
> 
>> On Feb 13, 2018, at 7:28 PM, Alex Harui > > wrote:
>> 
>> I don't understand what is wrong with the way it worked.  Isn't the
>> idea
>> that you are overlaying files from royale-extras?  Why can't the
>> current
>> build expand the externs from closure-compiler and then your stuff can
>> overlay it?
>> 
>> Thoughts?
> -Alex
>> 
>> On 2/13/18, 5:26 AM, "Gabe Harbs" > > wrote:
>> 
>>> Maybe. I didn’t realize changing the typedefs was going to end up
>>> being
>>> so complicated.
>>> 
>>> I just changed the ant build to use git instead of svn. It takes
>>> about a
>>> minute the first time the repo is needed to be ownloaded, but it’s
>>> pretty quick afterwards.
>>> 
>>> I’m not sure which method is best for Maven.
>>> 
 On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki
 >
 wrote:
 
 Btw. Maybe you should move your changes to separate branch. We will
 have
 emails with fails for a long time now. Unless someone else look into
 the
 Maven.
 
 2018-02-13 13:03 GMT+01:00 Gabe Harbs 
 >>:
 
> FWIW, here’s some other options for downloading a specific folder
> from
> Github:
> 
> 
> https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fstac
> kov
> > https%3A%2F%2Fsta
> ckov>
> erflow.com
> > http%3A%2F%2Ferfl
> ow.com%2F=02%7C01%7Caharui%40adobe.com%
>> 7Cd1228ae32eca45e43ce208d
> 57309af91%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C63654140779893
> 6061=zxNWE%2BwbCzZDK1diTruXDmroGk%
>> 2BxVzdwIVm%2Bxxg4LAc%3D
> ved=0>%2Fa%2F18194523=02%7C01%7Caharui%40adobe.com
> > http%3A%2F%2F40ad
> obe.com%2F=02%7C01%7Caharui%40adobe.com%
>> 7Cd1228ae32eca45e43ce208
> d57309af91%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6365414077989
> 36061=rZuwf0WjH2xZAOacIz7ECWcohPvCLU
>> IJg471M7Yhs%2Fc%3D
> =0>%7C2fc7071c44
> 
> 6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6
> 365
> 
> 41251966892882=hv35Ja58vctUc%2BCbeuID%
>> 2FiH9hRZ1gDnv0gumtvfrQ2Y%
> 3D&
> reserved=0
> 
>> On Feb 13, 2018, at 1:57 PM, Gabe Harbs > > wrote:
>> 
>> If you use Git, you need to download the entire repo which
>> includes
>> all
> the bits for the actual compiler.
>> 
>> Github supports svn 

Re: Royale Examples Blog proposal to all the team

[Carlos Rovira]

Hi Alex,

please write me offline and let me know what email account you prefer to
change it.

About scheduling: I think we have lots of time between one post and another
(around 6 months), and people can make more than one if they want. Or make
one to post, and few days make another if they want. Posts will be drafts
and can be published when we want (taking into account our schedule)
About contributors, I already said that others outside the team can post as
well, so that option is open.
But as well, I like your idea of asking here if we need to post something.
As well, maybe some weeks we could stop publishing. I think we must take
this with some schedule to guide us, but as an OS project, we are ready to
postpone it if we need it.

About what to write. We are all day working with Royale. Know many things
about how things are done. Here we want to share tips, few lines of code
that shows something running that is simple. For example, some days ago,
Peter post a mail on how to make absolute positioning with and without
scrolling. That was two snippets of code. I think that fits. perfecly.

Is the same Peter Dehaan did with blog flex examples. And that makes people
trying to start with royale more ready to learn and use it.



2018-02-13 18:21 GMT+01:00 Alex Harui :

> Having an Examples blog is a great thing.
>
> I saw the calendar invite.  I couldn't see the calendar I think because
> default to logging in under a different email and don't really want this
> stuff mixed into to my default calendar.
>
> My only concern is the scheduling.  IMO, scheduling is difficult with
> volunteers.  Folks get busy with their $dayjob and may run out of time.
> We should accept entries from anyone, even non-committers, at any time.
> So what if we get a burst here and it goes quiet for a while?  Carlos, if
> you want to volunteer to keep track of the last post date, then if a week
> goes by without a new post you could ask on the mailing list for a
> volunteer to write the next post.  And anyone reading this email is
> welcome to write a post or suggest a topic.  That will likely be the
> biggest question for me: what should I write about?
>
> Anyway, thanks for getting this started.
>
> My 2 cents,
> -Alex
>
> On 2/13/18, 3:09 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi Olaf
> >
> >2018-02-13 11:31 GMT+01:00 Olaf Krueger :
> >
> >> >I'd like to read thoughts from others in the team.
> >>
> >> This is a really good idea, Carlos!
> >> If I understand you right you'd like to say that we want to publish a
> >>post
> >> every two weeks and because we're about 10 to 15 people who will
> >>contribute
> >> this means that anybody of us has to write an article approx every 6
> >> months?!
> >> And you want us to manage the scheduling of the blog posts by using the
> >> google calendar?
> >>
> >
> >That's right! I think if we all participate will 10-11, and about 6 months
> >between repeat author.
> >Maybe, as examples are very easy to do we can talk more later if we do
> >this
> >each week...we'll see as we develop it right?
> >
> >
> >>
> >> >Below the source code, we should have the result displayed in an
> >>iframe.
> >> +1
> >>
> >> Another suggestion:
> >> Peter de Haan posts always contain some simple explanations.
> >> Regarding the "Hello world" post, I think it would be interesting for
> >> people
> >> to learn something about the code, e.g. for what is
> >> "js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
> >> Maybe it makes sense to link something to the docs or to add some simple
> >> explanation?
> >>
> >
> >That's a very good idea. I'll try to update the hello world with this
> >suggestions :)
> >
> >
> >>
> >> I'll check out the google calendar...
> >>
> >> Thanks,
> >> Olaf
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Sent from:
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-ro
> >>yale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%
> 40adobe.com
> >>%7Cd2453e80427a4a2db4a708d572d259e3%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C
> >>0%7C0%7C636541170132357067=IW1I%2BZebS7gSyrBako0WCHBAG8eo1b3NP
> VnfC%
> >>2BvUyTA%3D=0
> >>
> >
> >
> >
> >--
> >Carlos Rovira
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2
> >Fcarlosrovira=02%7C01%7Caharui%40adobe.com%
> 7Cd2453e80427a4a2db4a708d5
> >72d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636541170132357067
> >data=YBsn0zhxZd98toKr%2BrZP1GwprmRzcmM5NesejiabbJo%3D=0
>
>


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

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

[Alex Harui]

We will wait a bit for other feedback and let the mirrors finish
propagating.  I'll post it in about 8 hours if no other feedback.

-Alex

On 2/13/18, 1:00 PM, "Piotr Zarzycki"  wrote:

>Go on and announce. I will fill GitHub release once it will be done! :)
>
>Thanks,
>Piotr
>
>2018-02-13 21:57 GMT+01:00 Andrew Wetmore :
>
>> This announcement seems clear and inviting.
>>
>> On Tue, Feb 13, 2018 at 3:06 PM, Alex Harui 
>> wrote:
>>
>> > Please comment on the draft below.
>> >
>> > Thoughts?
>> > -Alex
>> >
>> >
>>
>>
>> --
>> Andrew Wetmore
>>
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14
>>.blogspot.com%2F=02%7C01%7Caharui%40adobe.com%7Cd4c77f7efac24c43527b
>>08d57324d7ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541524457865
>>491=i2PjCF4AaKmM70dq489Z60snqnKXjufTQU6iTKe34Jg%3D=0
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>Patreon: 
>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7Cd4c77f7efac24c
>43527b08d57324d7ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365415244
>57865491=4K39eoxbjwFxRmtuduLgUulDCCVtPnrkQHxQ1UIIO%2F4%3D=0
>eon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7Cd4c77f7efac24c
>43527b08d57324d7ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365415244
>57865491=4K39eoxbjwFxRmtuduLgUulDCCVtPnrkQHxQ1UIIO%2F4%3D=0
>>*

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

[Piotr Zarzycki]

Go on and announce. I will fill GitHub release once it will be done! :)

Thanks,
Piotr

2018-02-13 21:57 GMT+01:00 Andrew Wetmore :

> This announcement seems clear and inviting.
>
> On Tue, Feb 13, 2018 at 3:06 PM, Alex Harui 
> wrote:
>
> > Please comment on the draft below.
> >
> > Thoughts?
> > -Alex
> >
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>



-- 

Piotr Zarzycki

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

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

[Andrew Wetmore]

This announcement seems clear and inviting.

On Tue, Feb 13, 2018 at 3:06 PM, Alex Harui 
wrote:

> Please comment on the draft below.
>
> Thoughts?
> -Alex
>
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Piotr Zarzycki]

Where is the conclusion, cause I lost a bit track with that. What are you
going to do next Harbs ? Should I still spent some time on Maven ?

2018-02-13 19:45 GMT+01:00 Gabe Harbs :

> Ultimately, using those files is probably the way to go, but I’ll go back
> to overwriting individual files for now…
>
> I’ll work on this a bit later.
>
> Harbs
>
> > On Feb 13, 2018, at 8:04 PM, Alex Harui 
> wrote:
> >
> > I think we are working against an older closure-compiler.  Volunteers are
> > welcome to move us to the latest.
> >
> > I think we only patch a dozen files or so, so yes, even if you coned the
> > originals to royale-extras, I thought you would just cherry pick the few
> > files we need.  IMO, you can do that and get both Maven and Ant working
> > with less hassle.
> >
> > My 2 cents,
> > -Alex
> >
> > On 2/13/18, 9:45 AM, "Gabe Harbs"  wrote:
> >
> >> BTW, when I switched to the newer extern files that turned upon some
> more
> >> bugs with them.
> >>
> >> I’m not ure at what point the newer externs are/will be included in the
> >> closure-compiler download, but more files will become an issue at
> >> whatever point they do.
> >>
> >>> On Feb 13, 2018, at 7:40 PM, Gabe Harbs  wrote:
> >>>
> >>> You mean just download the specific files we need?
> >>>
> >>> I figured we might as well just get all the files from the same repo.
> >>>
>  On Feb 13, 2018, at 7:28 PM, Alex Harui   > wrote:
> 
>  I don't understand what is wrong with the way it worked.  Isn't the
>  idea
>  that you are overlaying files from royale-extras?  Why can't the
>  current
>  build expand the externs from closure-compiler and then your stuff can
>  overlay it?
> 
>  Thoughts?
> >>> -Alex
> 
>  On 2/13/18, 5:26 AM, "Gabe Harbs"   > wrote:
> 
> > Maybe. I didn’t realize changing the typedefs was going to end up
> > being
> > so complicated.
> >
> > I just changed the ant build to use git instead of svn. It takes
> > about a
> > minute the first time the repo is needed to be ownloaded, but it’s
> > pretty quick afterwards.
> >
> > I’m not sure which method is best for Maven.
> >
> >> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki
> >> >
> >> wrote:
> >>
> >> Btw. Maybe you should move your changes to separate branch. We will
> >> have
> >> emails with fails for a long time now. Unless someone else look into
> >> the
> >> Maven.
> >>
> >> 2018-02-13 13:03 GMT+01:00 Gabe Harbs  >> 
> >> >>:
> >>
> >>> FWIW, here’s some other options for downloading a specific folder
> >>> from
> >>> Github:
> >>>
> >>>
> >>> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fstac
> >>> kov
> >>>  https%3A%2F%2Fsta
> >>> ckov>
> >>> erflow.com
> >>>  http%3A%2F%2Ferfl
> >>> ow.com%2F=02%7C01%7Caharui%40adobe.com%
> 7Cd1228ae32eca45e43ce208d
> >>> 57309af91%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C63654140779893
> >>> 6061=zxNWE%2BwbCzZDK1diTruXDmroGk%
> 2BxVzdwIVm%2Bxxg4LAc%3D
> >>> ved=0>%2Fa%2F18194523=02%7C01%7Caharui%40adobe.com
> >>>  http%3A%2F%2F40ad
> >>> obe.com%2F=02%7C01%7Caharui%40adobe.com%
> 7Cd1228ae32eca45e43ce208
> >>> d57309af91%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365414077989
> >>> 36061=rZuwf0WjH2xZAOacIz7ECWcohPvCLU
> IJg471M7Yhs%2Fc%3D
> >>> =0>%7C2fc7071c44
> >>>
> >>> 6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6
> >>> 365
> >>>
> >>> 41251966892882=hv35Ja58vctUc%2BCbeuID%
> 2FiH9hRZ1gDnv0gumtvfrQ2Y%
> >>> 3D&
> >>> reserved=0
> >>>
>  On Feb 13, 2018, at 1:57 PM, Gabe Harbs   > wrote:
> 
>  If you use Git, you need to download the entire repo which
> includes
>  all
> >>> the bits for the actual compiler.
> 
>  Github supports svn checkouts as well which allows you to checkout
>  a
> >>> specific folder within a repo.[1]
> 
>  The following command will get the extern files we need from
> >>> Github:
> 
>  svn checkout
> 
>  https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgit
>  hub
>   https%3A%2F%2Fgi
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Andrew Wetmore]

Hi:

I made a tiny change in develop and then merged it into master with no
problem, yay!

On Tue, Feb 13, 2018 at 2:32 PM, Alex Harui 
wrote:

> Hi Andrew,
>
> I went and did the merge so I can make sure it is ok and reference it from
> the announcement.  Feel free to make some edits in develop and merge to
> master just to make sure you can do so in case we find some error to
> address.
>
> Thanks,
> -Alex
>
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

[GitHub] cottage14 opened a new pull request #4: added a note about documentation being incomplete.

[GitBox]

cottage14 opened a new pull request #4: added a note about documentation being 
incomplete.
URL: https://github.com/apache/royale-docs/pull/4
 
 
   Added a short note, and merging to master to make sure that I can.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] cottage14 closed pull request #4: added a note about documentation being incomplete.

[GitBox]

cottage14 closed pull request #4: added a note about documentation being 
incomplete.
URL: https://github.com/apache/royale-docs/pull/4
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

[Alex Harui]

FYI, I just noticed that the "Get Started" section in the docs needs
filling out so I'm working on that now.

-Alex

On 2/13/18, 11:06 AM, "Alex Harui"  wrote:

>Please comment on the draft below.
>
>Thoughts?
>-Alex
>
>---
>
>The Apache Royale community is pleased to announce the release of Apache
>Royale 0.9.1.
>
>Apache Royale is a new project that took over the work on what was being
>called FlexJS, a next-generation of the Apache Flex SDK that enables
>developers to use MXML and ActionScript to generated HTML/JS/CSS so
>applications can run natively in browsers.  The cross-compiled code can
>also be used in Apache Cordova (Adobe PhoneGap) mobile applications.
>
>(Apache Flex is a highly productive, open source application framework for
>building and maintaining expressive applications that deploy on Adobe
>Flash and Adobe AIR to provide a consistent experience on all major
>browsers, desktops and devices.)
>
>This release should be considered ‘beta' quality. The purpose of this
>release is to gather feedback about the features and implementation
>strategies, and to recruit new contributors. We hope to grow the code base
>into an SDK and tool chain that delivers the highest productivity when
>developing applications that can run on many platforms. Beta releases may
>not handle production needs.
>
>Please file bugs at:
>
>
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
>m%2Fapache%2Froyale-asjs%2Fissues=02%7C01%7Caharui%40adobe.com%7C2273
>6e8d6ce54840debe08d57314f283%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C
>636541456165875401=ImcdqdNBgRo2U0yH6Ghf3xXv1%2BWjpcMV7Ujopt6Ng1g%3D&
>reserved=0
>
>If you happen to know it is a compiler issue, please use:
>
>
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
>m%2Fapache%2Froyale-compiler%2Fissues=02%7C01%7Caharui%40adobe.com%7C
>22736e8d6ce54840debe08d57314f283%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C
>0%7C636541456165875401=tsBApKYx0KtS0p92WswX8RkJ3Isi7Gvy3ka6LqcBKTM%3
>D=0
>
>For questions about how to use Royale, send email to
>us...@royale.apache.org.  For questions and feedback on the development of
>the source code in the release, send email to dev@royale.apache.org.
>
>Apache Royale is available in source and binary form from the Apache
>mirrors:
>
>Source:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache
>.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.1%2Fapache-royale-0.9.1-src.t=
>02%7C01%7Caharui%40adobe.com%7C22736e8d6ce54840debe08d57314f283%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636541456165875401=rAxWxZQHEQK2jk
>9lo5jxhFw7SgjaXnV7El8U3YqIHtc%3D=0
>ar.gz
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache
>.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.1%2Fapache-royale-0.9.1-src.z=
>02%7C01%7Caharui%40adobe.com%7C22736e8d6ce54840debe08d57314f283%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636541456165875401=Ze4b6er8m1UZii
>QNWFuSzllRRYGlWoapoV2p46DiDwM%3D=0
>ip
>
>Binary:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache
>.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.1%2Fbinaries%2Fapache-royale-0
>=02%7C01%7Caharui%40adobe.com%7C22736e8d6ce54840debe08d57314f283%7Cfa7b1b5
>a7b34438794aed2c178decee1%7C0%7C0%7C636541456165875401=03uehFllnQOS0
>nb6CD%2FhNm1VgKXA0IJTf%2FxpeZ1x7NA%3D=0.
>9.1-bin-js.tar.gz
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache
>.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.1%2Fbinaries%2Fapache-royale-0
>=02%7C01%7Caharui%40adobe.com%7C22736e8d6ce54840debe08d57314f283%7Cfa7b1b5
>a7b34438794aed2c178decee1%7C0%7C0%7C636541456165875401=03uehFllnQOS0
>nb6CD%2FhNm1VgKXA0IJTf%2FxpeZ1x7NA%3D=0.
>9.1-bin-js.zip
>
>Binary with SWF support:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache
>.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.1%2Fbinaries%2Fapache-royale-0
>=02%7C01%7Caharui%40adobe.com%7C22736e8d6ce54840debe08d57314f283%7Cfa7b1b5
>a7b34438794aed2c178decee1%7C0%7C0%7C636541456165875401=03uehFllnQOS0
>nb6CD%2FhNm1VgKXA0IJTf%2FxpeZ1x7NA%3D=0.
>9.1-bin-js-swf.tar.gz
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache
>.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.1%2Fbinaries%2Fapache-royale-0
>=02%7C01%7Caharui%40adobe.com%7C22736e8d6ce54840debe08d57314f283%7Cfa7b1b5
>a7b34438794aed2c178decee1%7C0%7C0%7C636541456165875401=03uehFllnQOS0
>nb6CD%2FhNm1VgKXA0IJTf%2FxpeZ1x7NA%3D=0.
>9.1-bin-js-swf.zip
>
>When downloading from a mirror site, please remember to verify the
>downloads using signatures or MD5 hashes.
>
>The binary packages can also be installed via NPM.
>
>Mac:
>
>  sudo npm install @apache-royale/royale-js -g
>
>Or for SWF Support:
>
>  sudo npm install @apache-royale/royale-js-swf -g
>
>
>
>Windows:
>
>  npm install @apache-royale/royale-js -g
>
>Or for SWF Support:
>
>  npm install @apache-royale/royale-js-swf -g
>
>
>
>See the README for more information. The language reference (ASDoc) is

[DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

[Alex Harui]

Please comment on the draft below.

Thoughts?
-Alex

---

The Apache Royale community is pleased to announce the release of Apache
Royale 0.9.1.

Apache Royale is a new project that took over the work on what was being
called FlexJS, a next-generation of the Apache Flex SDK that enables
developers to use MXML and ActionScript to generated HTML/JS/CSS so
applications can run natively in browsers.  The cross-compiled code can
also be used in Apache Cordova (Adobe PhoneGap) mobile applications.

(Apache Flex is a highly productive, open source application framework for
building and maintaining expressive applications that deploy on Adobe
Flash and Adobe AIR to provide a consistent experience on all major
browsers, desktops and devices.)

This release should be considered ‘beta' quality. The purpose of this
release is to gather feedback about the features and implementation
strategies, and to recruit new contributors. We hope to grow the code base
into an SDK and tool chain that delivers the highest productivity when
developing applications that can run on many platforms. Beta releases may
not handle production needs.

Please file bugs at:

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

If you happen to know it is a compiler issue, please use:

https://github.com/apache/royale-compiler/issues

For questions about how to use Royale, send email to
us...@royale.apache.org.  For questions and feedback on the development of
the source code in the release, send email to dev@royale.apache.org.

Apache Royale is available in source and binary form from the Apache
mirrors:

Source:
http://www.apache.org/dyn/closer.lua/royale/0.9.1/apache-royale-0.9.1-src.t
ar.gz

http://www.apache.org/dyn/closer.lua/royale/0.9.1/apache-royale-0.9.1-src.z
ip

Binary:
http://www.apache.org/dyn/closer.lua/royale/0.9.1/binaries/apache-royale-0.
9.1-bin-js.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.1/binaries/apache-royale-0.
9.1-bin-js.zip

Binary with SWF support:
http://www.apache.org/dyn/closer.lua/royale/0.9.1/binaries/apache-royale-0.
9.1-bin-js-swf.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.1/binaries/apache-royale-0.
9.1-bin-js-swf.zip

When downloading from a mirror site, please remember to verify the
downloads using signatures or MD5 hashes.

The binary packages can also be installed via NPM.

Mac:

  sudo npm install @apache-royale/royale-js -g

Or for SWF Support:

  sudo npm install @apache-royale/royale-js-swf -g



Windows:

  npm install @apache-royale/royale-js -g

Or for SWF Support:

  npm install @apache-royale/royale-js-swf -g



See the README for more information. The language reference (ASDoc) is
here:

  http://royale.apache.org/asdoc/

Additional documentation is here:

  https://apache.github.io/royale-docs/

The documentation is still a work in progress.  Volunteers are welcome to
help improve it.  Visit http://royale.apache.org/ for links to other
resources.

Please try Royale and become involved in shaping the future of application
development.

The Apache Royale Community

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

Ultimately, using those files is probably the way to go, but I’ll go back to 
overwriting individual files for now…

I’ll work on this a bit later.

Harbs

> On Feb 13, 2018, at 8:04 PM, Alex Harui  wrote:
> 
> I think we are working against an older closure-compiler.  Volunteers are
> welcome to move us to the latest.
> 
> I think we only patch a dozen files or so, so yes, even if you coned the
> originals to royale-extras, I thought you would just cherry pick the few
> files we need.  IMO, you can do that and get both Maven and Ant working
> with less hassle.
> 
> My 2 cents,
> -Alex
> 
> On 2/13/18, 9:45 AM, "Gabe Harbs"  wrote:
> 
>> BTW, when I switched to the newer extern files that turned upon some more
>> bugs with them.
>> 
>> I’m not ure at what point the newer externs are/will be included in the
>> closure-compiler download, but more files will become an issue at
>> whatever point they do.
>> 
>>> On Feb 13, 2018, at 7:40 PM, Gabe Harbs  wrote:
>>> 
>>> You mean just download the specific files we need?
>>> 
>>> I figured we might as well just get all the files from the same repo.
>>> 
 On Feb 13, 2018, at 7:28 PM, Alex Harui > wrote:
 
 I don't understand what is wrong with the way it worked.  Isn't the
 idea
 that you are overlaying files from royale-extras?  Why can't the
 current
 build expand the externs from closure-compiler and then your stuff can
 overlay it?
 
 Thoughts?
>>> -Alex
 
 On 2/13/18, 5:26 AM, "Gabe Harbs" > wrote:
 
> Maybe. I didn’t realize changing the typedefs was going to end up
> being
> so complicated.
> 
> I just changed the ant build to use git instead of svn. It takes
> about a
> minute the first time the repo is needed to be ownloaded, but it’s
> pretty quick afterwards.
> 
> I’m not sure which method is best for Maven.
> 
>> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki
>> >
>> wrote:
>> 
>> Btw. Maybe you should move your changes to separate branch. We will
>> have
>> emails with fails for a long time now. Unless someone else look into
>> the
>> Maven.
>> 
>> 2018-02-13 13:03 GMT+01:00 Gabe Harbs > 
>> >>:
>> 
>>> FWIW, here’s some other options for downloading a specific folder
>>> from
>>> Github:
>>> 
>>> 
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstac
>>> kov 
>>> >> ckov>
>>> erflow.com 
>>> >> ow.com%2F=02%7C01%7Caharui%40adobe.com%7Cd1228ae32eca45e43ce208d
>>> 57309af91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63654140779893
>>> 6061=zxNWE%2BwbCzZDK1diTruXDmroGk%2BxVzdwIVm%2Bxxg4LAc%3D
>>> ved=0>%2Fa%2F18194523=02%7C01%7Caharui%40adobe.com
>>> >> obe.com%2F=02%7C01%7Caharui%40adobe.com%7Cd1228ae32eca45e43ce208
>>> d57309af91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365414077989
>>> 36061=rZuwf0WjH2xZAOacIz7ECWcohPvCLUIJg471M7Yhs%2Fc%3D
>>> =0>%7C2fc7071c44
>>> 
>>> 6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6
>>> 365
>>> 
>>> 41251966892882=hv35Ja58vctUc%2BCbeuID%2FiH9hRZ1gDnv0gumtvfrQ2Y%
>>> 3D&
>>> reserved=0
>>> 
 On Feb 13, 2018, at 1:57 PM, Gabe Harbs > wrote:
 
 If you use Git, you need to download the entire repo which includes
 all
>>> the bits for the actual compiler.
 
 Github supports svn checkouts as well which allows you to checkout
 a
>>> specific folder within a repo.[1]
 
 The following command will get the extern files we need from
>>> Github:
 
 svn checkout
 
 https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit
 hub 
 
 
 .com%2Froyale-extras%2Fclosure-compiler%2F=02%7C01%7Caharui%40a
 dob
 e.com 
  

Re: How I can use multiple CSS files

[Gabe Harbs]

Why not just use MXML files?

You can use MXML files to subclass components and specify the CSS in the 
 section.

> On Feb 13, 2018, at 1:20 PM, Carlos Rovira  wrote:
> 
> Hi,
> 
> I'm organizing CSS files in Vivid (new ui set) - VividBlueTheme (first
> theme) - VividExample (example to show all working)
> 
> I want to develop each component look-and-feel and style in a single file
> in the theme project:
> 
> default.css (this could hold global styling like body, headers, background
> color, and more)
> TextField.css (all css to make a TextField be represented in a particular
> way)
> Button.css
> Slider.css
> ...
> 
> in my theme pom I have:
> 
> 
> 
> defaults.css
> ../src/main/resources/defaults.css
> 
> 
> TextField.css
> ../src/main/resources/TextField.css
> 
> 
> 
> and I check the resulting VividBlueTheme.swc and has default.css and
> TextField.css
> 
> * First question here is: Can I collapse all css content in multiple files
> in a single .css (i.e: defaults.css or themename.css)?
> 
> Then in vivid example how CSS in theme projects are referenced? I see
> "defaults.css" is begin applied, but "TextField.css" is not
> 
> * Second question how to apply a included .css file to be used in example
> 
> Notice that if we get all css in one single file we don't need the second
> part.
> 
> Hope you could help me on this in order to continue progress with this
> effort
> 
> thanks
> 
> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Alex Harui]

Hi Andrew,

I went and did the merge so I can make sure it is ok and reference it from
the announcement.  Feel free to make some edits in develop and merge to
master just to make sure you can do so in case we find some error to
address.

Thanks,
-Alex

On 2/12/18, 11:40 PM, "Alex Harui"  wrote:

>Andrew, please merge royale-docs develop branch to master.  If you don't
>have time, I will do it, but I want to make sure you are set up to do so.
>
>-Alex
>
>On 2/12/18, 10:11 PM, "Alex Harui"  wrote:
>
>>OK, I fixed up and ran the releasecandidate script and it says it posted
>>the bits to npm.
>>
>>I believe all branches are merged and appropriately versioned.  On to the
>>next release!
>>
>>-Alex
>>
>>On 2/12/18, 12:29 PM, "omup...@gmail.com on behalf of OmPrakash
>>Muppirala"
>> wrote:
>>
>>>On Mon, Feb 12, 2018 at 12:22 PM, Alex Harui 
>>>wrote:
>>>
 The steps that publish NPM are in releasecandidate.xml.  It does not
muck
 with the packages.  It looked like your change was to the package.json
 that is already in the package.

>>>
>>>Yes that is correct.  When publishing, the publish script uses the raw
>>>package.json file.
>>>Look here:
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.
>>>c
>>>o
>>>m%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.1%2Fnpm%2Frelease-script
>>>s
>>>%
>>>2Fpublish.js%23L66=02%7C01%7Caharui%40adobe.com%7Ca8ef5cf25db649d00
>>>e
>>>0
>>>d08d572575efa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365406419405
>>>6
>>>9
>>>827=a0mEtMg9H7fAujqGHKKowVFFKtA0SDwPuEaAUoLyFrg%3D=0
>>>
>>>So, all you need to do is keep the tarball as is, but get my latest
>>>changes
>>>on release/0.9.1 before publishing to npm.
>>>
>>>Please try that and let me know how it goes.
>>>
>>>If this does not fix the issue, the next release should.  But lets give
>>>this a shot, at least.
>>>
>>>Thanks,
>>>Om
>>>
>>>

 -Alex

 On 2/12/18, 12:08 PM, "omup...@gmail.com on behalf of OmPrakash
Muppirala"
  wrote:

 >On Feb 12, 2018 11:58 AM, "Alex Harui" 
wrote:
 >
 >
 >
 >On 2/12/18, 10:42 AM, "omup...@gmail.com on behalf of OmPrakash
 Muppirala"
 > wrote:
 >
 >>On Feb 12, 2018 10:13 AM, "Alex Harui" 
wrote:
 >>
 >>AIUI, js-swf did not work via NPM as generated from the source
package.
 >>I
 >>thought you tweaked it before publishing.
 >>
 >>Am I wrong about that?
 >>
 >>
 >>That is correct.   Are you planning on doing the same this time?
 >
 >I'm thinking of publishing the js-swf package as-is and see if
anybody
 >complains.  If you want to do whatever you did last time, that's ok
with
 >me.  My goal is to spend the least amount of time possible being an
RM
and
 >create new features and fixes so even more folks will want to grab
the
 >next release after this one.  I'm ok with rough edges as long as we
 >incrementally make things better.
 >
 >
 >Instead you could pull my last commit and then run my npm publish
script.
 >That will overwrite the one that is in the tarball during the publish
 >process.
 >
 >I want to take this opportunity to make sure the npm publish script
works
 >seamlessly for release managers as well.
 >
 >Thanks,
 >Om
 >
 >
 >
 >-Alex
 >
 >
 >>
 >>On 2/12/18, 10:10 AM, "omup...@gmail.com on behalf of OmPrakash
 >>Muppirala"
 >> wrote:
 >>
 >>>On Feb 12, 2018 8:24 AM, "Alex Harui" 
wrote:
 >>>
 >>>Voters,
 >>>
 >>>Apparently some of you have not quite bought into the new
philosophy
of
 >>>"better than last release and not illegal".
 >>>
 >>>
 >>>
 >>>The npm install that worked in the last release will be broken by
this
 >>>new
 >>>release.  Please explain how this is better than last release?
 >>>
 >>>Thanks,
 >>>Om
 >>>
 >>>
 >>>The cost of a new RC is
 >>>non-trivial.  We have some users who are asking for help to port
their
 >>>apps against a deadline.  To me, that is way more important than
fixing
 >>>js-swf for NPM in this release because js-swf was broken in the
prior
 >>>release.  This release is "better than the last release and not
 >>>illegal".
 >>>The next release is will be in 30 days or less.
 >>>
 >>>Someone hand-patched package.json and provided it on npm in the
last
 >>>release.  It can probably be done for this release.  I'll bet there
will
 >>>be a big bug in every release 

Re: How I can use multiple CSS files

[Alex Harui]

Hi Carlos,

I looked around and don't see any support for multiple CSS files in the
compiler.  I could add it, but I'd rather spend my time on other things.
I'm unclear what the return on investment is.

If you do decide to change the compiler, it appears that CSS has an
@import statement, so I would recommend starting by trying to implement
support for that.  An alternative approach would be to have the compiler
try to find all .css files in a SWC.  Right now it only looks for
defaults.css.

And, of course, you could probably find a Maven and Ant way of
concatenating all of the files during the build.

Remember that Royale lets you extend the set of Type Selectors so you can
(and should) have selectors with the same name as the component.  And then
I think it is relatively easy to find a component's selector in the
defaults.css or guess what selector name to use in your fx:Styel block.

I don't know if your work will end up generating class selectors as well
as type selectors, but if it does, having one file might make it easier to
avoid collisions in class selector names.

Good luck,
-Alex

On 2/13/18, 3:20 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi,
>
>I'm organizing CSS files in Vivid (new ui set) - VividBlueTheme (first
>theme) - VividExample (example to show all working)
>
>I want to develop each component look-and-feel and style in a single file
>in the theme project:
>
>default.css (this could hold global styling like body, headers, background
>color, and more)
>TextField.css (all css to make a TextField be represented in a particular
>way)
>Button.css
>Slider.css
>...
>
>in my theme pom I have:
>
>
>
>defaults.css
>../src/main/resources/defaults.css
>
>
>TextField.css
>../src/main/resources/TextField.css
>
>
>
>and I check the resulting VividBlueTheme.swc and has default.css and
>TextField.css
>
>* First question here is: Can I collapse all css content in multiple files
>in a single .css (i.e: defaults.css or themename.css)?
>
>Then in vivid example how CSS in theme projects are referenced? I see
>"defaults.css" is begin applied, but "TextField.css" is not
>
>* Second question how to apply a included .css file to be used in example
>
>Notice that if we get all css in one single file we don't need the second
>part.
>
>Hope you could help me on this in order to continue progress with this
>effort
>
>thanks
>
>
>
>
>-- 
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C02c48a3da9454fde800508d5
>72d3d2d4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541176461226993
>data=BVn%2Fx1e8QtZ4%2F8evAsM2VZsrHNapak2itoeahhWpnRY%3D=0

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Alex Harui]

I think we are working against an older closure-compiler.  Volunteers are
welcome to move us to the latest.

I think we only patch a dozen files or so, so yes, even if you coned the
originals to royale-extras, I thought you would just cherry pick the few
files we need.  IMO, you can do that and get both Maven and Ant working
with less hassle.

My 2 cents,
-Alex

On 2/13/18, 9:45 AM, "Gabe Harbs"  wrote:

>BTW, when I switched to the newer extern files that turned upon some more
>bugs with them.
>
>I’m not ure at what point the newer externs are/will be included in the
>closure-compiler download, but more files will become an issue at
>whatever point they do.
>
>> On Feb 13, 2018, at 7:40 PM, Gabe Harbs  wrote:
>> 
>> You mean just download the specific files we need?
>> 
>> I figured we might as well just get all the files from the same repo.
>> 
>>> On Feb 13, 2018, at 7:28 PM, Alex Harui >>> wrote:
>>> 
>>> I don't understand what is wrong with the way it worked.  Isn't the
>>>idea
>>> that you are overlaying files from royale-extras?  Why can't the
>>>current
>>> build expand the externs from closure-compiler and then your stuff can
>>> overlay it?
>>> 
>>> Thoughts?
>> -Alex
>>> 
>>> On 2/13/18, 5:26 AM, "Gabe Harbs" >>> wrote:
>>> 
 Maybe. I didn’t realize changing the typedefs was going to end up
being
 so complicated.
 
 I just changed the ant build to use git instead of svn. It takes
about a
 minute the first time the repo is needed to be ownloaded, but it’s
 pretty quick afterwards.
 
 I’m not sure which method is best for Maven.
 
> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki
>>
> wrote:
> 
> Btw. Maybe you should move your changes to separate branch. We will
>have
> emails with fails for a long time now. Unless someone else look into
>the
> Maven.
> 
> 2018-02-13 13:03 GMT+01:00 Gabe Harbs 
> >>:
> 
>> FWIW, here’s some other options for downloading a specific folder
>>from
>> Github:
>> 
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstac
>>kov 
>>>ckov>
>> erflow.com 
>>>ow.com%2F=02%7C01%7Caharui%40adobe.com%7Cd1228ae32eca45e43ce208d
>>57309af91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63654140779893
>>6061=zxNWE%2BwbCzZDK1diTruXDmroGk%2BxVzdwIVm%2Bxxg4LAc%3D
>>ved=0>%2Fa%2F18194523=02%7C01%7Caharui%40adobe.com
>>>obe.com%2F=02%7C01%7Caharui%40adobe.com%7Cd1228ae32eca45e43ce208
>>d57309af91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365414077989
>>36061=rZuwf0WjH2xZAOacIz7ECWcohPvCLUIJg471M7Yhs%2Fc%3D
>>=0>%7C2fc7071c44
>> 
>>6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6
>>365
>> 
>>41251966892882=hv35Ja58vctUc%2BCbeuID%2FiH9hRZ1gDnv0gumtvfrQ2Y%
>>3D&
>> reserved=0
>> 
>>> On Feb 13, 2018, at 1:57 PM, Gabe Harbs >>> wrote:
>>> 
>>> If you use Git, you need to download the entire repo which includes
>>> all
>> the bits for the actual compiler.
>>> 
>>> Github supports svn checkouts as well which allows you to checkout
>>>a
>> specific folder within a repo.[1]
>>> 
>>> The following command will get the extern files we need from
>>Github:
>>> 
>>> svn checkout
>>> 
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit
>>>hub 
>>>>>thub>
>>> 
>>>.com%2Froyale-extras%2Fclosure-compiler%2F=02%7C01%7Caharui%40a
>>>dob
>>> e.com 
>>>>>om%2F=02%7C01%7Caharui%40adobe.com%7Cd1228ae32eca45e43ce208d573
>>>09af91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365414077989360
>>>61=yVBu16vJcUCAJTzE3X1rlZkoYJlbigRCDkVT%2Bph4zFg%3D=0
%7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178de
>>> 
>>>cee1%7C0%7C0%7C636541251966892882=a6YLnJTMAiiWgneJukkWb4ErTKLQ
>>>4MR
>>> cFMpdNE%2Bhoz8%3D=0
>> branches/royale/externs
>> 
>>>hub 
>>>hub>
>> .com%Froyale-=02%7C01%7Caharui%40adobe.com

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

BTW, when I switched to the newer extern files that turned upon some more bugs 
with them.

I’m not sure at what point the newer externs are/will be included in the 
closure-compiler download, but more files will become an issue at whatever 
point they do.

> On Feb 13, 2018, at 7:40 PM, Gabe Harbs  wrote:
> 
> You mean just download the specific files we need?
> 
> I figured we might as well just get all the files from the same repo.
> 
>> On Feb 13, 2018, at 7:28 PM, Alex Harui > > wrote:
>> 
>> I don't understand what is wrong with the way it worked.  Isn't the idea
>> that you are overlaying files from royale-extras?  Why can't the current
>> build expand the externs from closure-compiler and then your stuff can
>> overlay it?
>> 
>> Thoughts?
>> -Alex
>> 
>> On 2/13/18, 5:26 AM, "Gabe Harbs" > > wrote:
>> 
>>> Maybe. I didn’t realize changing the typedefs was going to end up being
>>> so complicated.
>>> 
>>> I just changed the ant build to use git instead of svn. It takes about a
>>> minute the first time the repo is needed to be downloaded, but it’s
>>> pretty quick afterwards.
>>> 
>>> I’m not sure which method is best for Maven.
>>> 
 On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki >
 wrote:
 
 Btw. Maybe you should move your changes to separate branch. We will have
 emails with fails for a long time now. Unless someone else look into the
 Maven.
 
 2018-02-13 13:03 GMT+01:00 Gabe Harbs 
 >>:
 
> FWIW, here’s some other options for downloading a specific folder from
> Github:
> 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackov 
> 
> erflow.com 
> %2Fa%2F18194523=02%7C01%7Caharui%40adobe.com 
> %7C2fc7071c44
> 6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365
> 41251966892882=hv35Ja58vctUc%2BCbeuID%2FiH9hRZ1gDnv0gumtvfrQ2Y%3D&
> reserved=0
> 
>> On Feb 13, 2018, at 1:57 PM, Gabe Harbs > > wrote:
>> 
>> If you use Git, you need to download the entire repo which includes
>> all
> the bits for the actual compiler.
>> 
>> Github supports svn checkouts as well which allows you to checkout a
> specific folder within a repo.[1]
>> 
>> The following command will get the extern files we need from Github:
>> 
>> svn checkout 
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub 
>> 
>> .com%2Froyale-extras%2Fclosure-compiler%2F=02%7C01%7Caharui%40adob
>> e.com 
>> %7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C636541251966892882=a6YLnJTMAiiWgneJukkWb4ErTKLQ4MR
>> cFMpdNE%2Bhoz8%3D=0
> branches/royale/externs
>  
> .com%2Froyale-=02%7C01%7Caharui%40adobe.com 
> %7C2fc7071c446245d833120
> 8d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541251966892
> 882=ywlYp7LPHuU2TSAxQxldMfkPbAJsoFVVqkpzlySK%2Fmc%3D=0
>  
> .com%2Froyale-=02%7C01%7Caharui%40adobe.com 
> %7C2fc7071c446245d833120
> 8d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541251966892
> 882=ywlYp7LPHuU2TSAxQxldMfkPbAJsoFVVqkpzlySK%2Fmc%3D=0>
> extras/closure-compiler/branches/royale/externs>
>> 
>> Harbs
>> 
>> 
>> [1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhel 
>> 
>> p.github.com 
>> %2Farticles%2Fsupport-for-subversion-clients%2F=02%7C0
>> 1%7Caharui%40adobe.com 
>> %7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b3
>> 4438794aed2c178decee1%7C0%7C0%7C636541251966892882=NCtayjW5QNM5UY
>> 9mclARGl0Jxyw3FwMzg74vVncpmAQ%3D=0
>> > .
>> github.com 
>> %2Farticles%2Fsupport-for-subversion-clients%2F=02%7C01%
>> 7Caharui%40adobe.com 
>> 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

You mean just download the specific files we need?

I figured we might as well just get all the files from the same repo.

> On Feb 13, 2018, at 7:28 PM, Alex Harui  wrote:
> 
> I don't understand what is wrong with the way it worked.  Isn't the idea
> that you are overlaying files from royale-extras?  Why can't the current
> build expand the externs from closure-compiler and then your stuff can
> overlay it?
> 
> Thoughts?
> -Alex
> 
> On 2/13/18, 5:26 AM, "Gabe Harbs"  > wrote:
> 
>> Maybe. I didn’t realize changing the typedefs was going to end up being
>> so complicated.
>> 
>> I just changed the ant build to use git instead of svn. It takes about a
>> minute the first time the repo is needed to be downloaded, but it’s
>> pretty quick afterwards.
>> 
>> I’m not sure which method is best for Maven.
>> 
>>> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki 
>>> wrote:
>>> 
>>> Btw. Maybe you should move your changes to separate branch. We will have
>>> emails with fails for a long time now. Unless someone else look into the
>>> Maven.
>>> 
>>> 2018-02-13 13:03 GMT+01:00 Gabe Harbs >> >>:
>>> 
 FWIW, here’s some other options for downloading a specific folder from
 Github:
 
 https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackov 
 
 erflow.com 
 %2Fa%2F18194523=02%7C01%7Caharui%40adobe.com 
 %7C2fc7071c44
 6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365
 41251966892882=hv35Ja58vctUc%2BCbeuID%2FiH9hRZ1gDnv0gumtvfrQ2Y%3D&
 reserved=0
 
> On Feb 13, 2018, at 1:57 PM, Gabe Harbs  > wrote:
> 
> If you use Git, you need to download the entire repo which includes
> all
 the bits for the actual compiler.
> 
> Github supports svn checkouts as well which allows you to checkout a
 specific folder within a repo.[1]
> 
> The following command will get the extern files we need from Github:
> 
> svn checkout 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub 
> 
> .com%2Froyale-extras%2Fclosure-compiler%2F=02%7C01%7Caharui%40adob
> e.com 
> %7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636541251966892882=a6YLnJTMAiiWgneJukkWb4ErTKLQ4MR
> cFMpdNE%2Bhoz8%3D=0
 branches/royale/externs
 
 .com%2Froyale-=02%7C01%7Caharui%40adobe.com 
 %7C2fc7071c446245d833120
 8d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541251966892
 882=ywlYp7LPHuU2TSAxQxldMfkPbAJsoFVVqkpzlySK%2Fmc%3D=0
 
 .com%2Froyale-=02%7C01%7Caharui%40adobe.com 
 %7C2fc7071c446245d833120
 8d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541251966892
 882=ywlYp7LPHuU2TSAxQxldMfkPbAJsoFVVqkpzlySK%2Fmc%3D=0>
 extras/closure-compiler/branches/royale/externs>
> 
> Harbs
> 
> 
> [1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhel 
> 
> p.github.com 
> %2Farticles%2Fsupport-for-subversion-clients%2F=02%7C0
> 1%7Caharui%40adobe.com 
> %7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b3
> 4438794aed2c178decee1%7C0%7C0%7C636541251966892882=NCtayjW5QNM5UY
> 9mclARGl0Jxyw3FwMzg74vVncpmAQ%3D=0
>  .
> github.com 
> %2Farticles%2Fsupport-for-subversion-clients%2F=02%7C01%
> 7Caharui%40adobe.com 
> %7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b344
> 38794aed2c178decee1%7C0%7C0%7C636541251966892882=NCtayjW5QNM5UY9m
> clARGl0Jxyw3FwMzg74vVncpmAQ%3D=0> <
 
 https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.gi 
 
 thub.com 
 %2Farticles%2Fsupport-for-subversion-clients%2F=02%7C01%7Ca
 harui%40adobe.com 
 %7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b3443879

Re: Royale Examples Blog proposal to all the team

[Alex Harui]

I just looked at the Hello World example.  IMO, these examples should use
Express, not Basic, and then the code would be even shorter.

My 2 cents,
-Alex

On 2/13/18, 9:21 AM, "Alex Harui"  wrote:

>Having an Examples blog is a great thing.
>
>I saw the calendar invite.  I couldn't see the calendar I think because
>default to logging in under a different email and don't really want this
>stuff mixed into to my default calendar.
>
>My only concern is the scheduling.  IMO, scheduling is difficult with
>volunteers.  Folks get busy with their $dayjob and may run out of time.
>We should accept entries from anyone, even non-committers, at any time.
>So what if we get a burst here and it goes quiet for a while?  Carlos, if
>you want to volunteer to keep track of the last post date, then if a week
>goes by without a new post you could ask on the mailing list for a
>volunteer to write the next post.  And anyone reading this email is
>welcome to write a post or suggest a topic.  That will likely be the
>biggest question for me: what should I write about?
>
>Anyway, thanks for getting this started.
>
>My 2 cents,
>-Alex
>
>On 2/13/18, 3:09 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> wrote:
>
>>Hi Olaf
>>
>>2018-02-13 11:31 GMT+01:00 Olaf Krueger :
>>
>>> >I'd like to read thoughts from others in the team.
>>>
>>> This is a really good idea, Carlos!
>>> If I understand you right you'd like to say that we want to publish a
>>>post
>>> every two weeks and because we're about 10 to 15 people who will
>>>contribute
>>> this means that anybody of us has to write an article approx every 6
>>> months?!
>>> And you want us to manage the scheduling of the blog posts by using the
>>> google calendar?
>>>
>>
>>That's right! I think if we all participate will 10-11, and about 6
>>months
>>between repeat author.
>>Maybe, as examples are very easy to do we can talk more later if we do
>>this
>>each week...we'll see as we develop it right?
>>
>>
>>>
>>> >Below the source code, we should have the result displayed in an
>>>iframe.
>>> +1
>>>
>>> Another suggestion:
>>> Peter de Haan posts always contain some simple explanations.
>>> Regarding the "Hello world" post, I think it would be interesting for
>>> people
>>> to learn something about the code, e.g. for what is
>>> "js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
>>> Maybe it makes sense to link something to the docs or to add some
>>>simple
>>> explanation?
>>>
>>
>>That's a very good idea. I'll try to update the hello world with this
>>suggestions :)
>>
>>
>>>
>>> I'll check out the google calendar...
>>>
>>> Thanks,
>>> Olaf
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from: 
>>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-r
>>>o
>>>yale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.co
>>>m
>>>%7Cd2453e80427a4a2db4a708d572d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7
>>>C
>>>0%7C0%7C636541170132357067=IW1I%2BZebS7gSyrBako0WCHBAG8eo1b3NPVnfC
>>>%
>>>2BvUyTA%3D=0
>>>
>>
>>
>>
>>-- 
>>Carlos Rovira
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>>2
>>Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cd2453e80427a4a2db4a708d
>>5
>>72d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541170132357067&
>>s
>>data=YBsn0zhxZd98toKr%2BrZP1GwprmRzcmM5NesejiabbJo%3D=0
>

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Alex Harui]

I don't understand what is wrong with the way it worked.  Isn't the idea
that you are overlaying files from royale-extras?  Why can't the current
build expand the externs from closure-compiler and then your stuff can
overlay it?

Thoughts?
-Alex

On 2/13/18, 5:26 AM, "Gabe Harbs"  wrote:

>Maybe. I didn’t realize changing the typedefs was going to end up being
>so complicated.
>
>I just changed the ant build to use git instead of svn. It takes about a
>minute the first time the repo is needed to be downloaded, but it’s
>pretty quick afterwards.
>
>I’m not sure which method is best for Maven.
>
>> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki 
>>wrote:
>> 
>> Btw. Maybe you should move your changes to separate branch. We will have
>> emails with fails for a long time now. Unless someone else look into the
>> Maven.
>> 
>> 2018-02-13 13:03 GMT+01:00 Gabe Harbs >>:
>> 
>>> FWIW, here’s some other options for downloading a specific folder from
>>> Github:
>>> 
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackov
>>>erflow.com%2Fa%2F18194523=02%7C01%7Caharui%40adobe.com%7C2fc7071c44
>>>6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365
>>>41251966892882=hv35Ja58vctUc%2BCbeuID%2FiH9hRZ1gDnv0gumtvfrQ2Y%3D&
>>>reserved=0
>>> 
 On Feb 13, 2018, at 1:57 PM, Gabe Harbs  wrote:
 
 If you use Git, you need to download the entire repo which includes
all
>>> the bits for the actual compiler.
 
 Github supports svn checkouts as well which allows you to checkout a
>>> specific folder within a repo.[1]
 
 The following command will get the extern files we need from Github:
 
 svn checkout 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub
.com%2Froyale-extras%2Fclosure-compiler%2F=02%7C01%7Caharui%40adob
e.com%7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178de
cee1%7C0%7C0%7C636541251966892882=a6YLnJTMAiiWgneJukkWb4ErTKLQ4MR
cFMpdNE%2Bhoz8%3D=0
>>> branches/royale/externs
>>>>>.com%2Froyale-=02%7C01%7Caharui%40adobe.com%7C2fc7071c446245d833120
>>>8d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541251966892
>>>882=ywlYp7LPHuU2TSAxQxldMfkPbAJsoFVVqkpzlySK%2Fmc%3D=0
>>>>>.com%2Froyale-=02%7C01%7Caharui%40adobe.com%7C2fc7071c446245d833120
>>>8d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541251966892
>>>882=ywlYp7LPHuU2TSAxQxldMfkPbAJsoFVVqkpzlySK%2Fmc%3D=0>
>>> extras/closure-compiler/branches/royale/externs>
 
 Harbs
 
 
[1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhel
p.github.com%2Farticles%2Fsupport-for-subversion-clients%2F=02%7C0
1%7Caharui%40adobe.com%7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b3
4438794aed2c178decee1%7C0%7C0%7C636541251966892882=NCtayjW5QNM5UY
9mclARGl0Jxyw3FwMzg74vVncpmAQ%3D=0
 <
>>> 
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.gi
>>>thub.com%2Farticles%2Fsupport-for-subversion-clients%2F=02%7C01%7Ca
>>>harui%40adobe.com%7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b3443879
>>>4aed2c178decee1%7C0%7C0%7C636541251966892882=NCtayjW5QNM5UY9mclARG
>>>l0Jxyw3FwMzg74vVncpmAQ%3D=0
>>>>>ithub.com%2Farticles%2Fsupport-for-subversion-clients%2F=02%7C01%7C
>>>aharui%40adobe.com%7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b344387
>>>94aed2c178decee1%7C0%7C0%7C636541251966892882=NCtayjW5QNM5UY9mclAR
>>>Gl0Jxyw3FwMzg74vVncpmAQ%3D=0>>
 
> On Feb 13, 2018, at 1:54 PM, Piotr Zarzycki
>
>>> >>
>>>wrote:
> 
> Actually why are you talking about svn ? You mean GIT actually ?
> 
> 2018-02-13 12:47 GMT+01:00 Gabe Harbs  >> harbs.li...@gmail.com >>:
> 
>> BTW, there’s a mojo for svn checkout:
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmave
>>n.apache.org%2Fscm%2Fmaven-scm-plugin%2Fcheckout-mojo.html=02%7C
>>01%7Caharui%40adobe.com%7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a
>>7b34438794aed2c178decee1%7C0%7C0%7C636541251966892882=uPfqPQs5I
>>IvQkKBizSgVxKpueZbtrIK%2B73IDdBaqti4%3D=0

Re: Royale Examples Blog proposal to all the team

[Alex Harui]

Having an Examples blog is a great thing.

I saw the calendar invite.  I couldn't see the calendar I think because
default to logging in under a different email and don't really want this
stuff mixed into to my default calendar.

My only concern is the scheduling.  IMO, scheduling is difficult with
volunteers.  Folks get busy with their $dayjob and may run out of time.
We should accept entries from anyone, even non-committers, at any time.
So what if we get a burst here and it goes quiet for a while?  Carlos, if
you want to volunteer to keep track of the last post date, then if a week
goes by without a new post you could ask on the mailing list for a
volunteer to write the next post.  And anyone reading this email is
welcome to write a post or suggest a topic.  That will likely be the
biggest question for me: what should I write about?

Anyway, thanks for getting this started.

My 2 cents,
-Alex

On 2/13/18, 3:09 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Olaf
>
>2018-02-13 11:31 GMT+01:00 Olaf Krueger :
>
>> >I'd like to read thoughts from others in the team.
>>
>> This is a really good idea, Carlos!
>> If I understand you right you'd like to say that we want to publish a
>>post
>> every two weeks and because we're about 10 to 15 people who will
>>contribute
>> this means that anybody of us has to write an article approx every 6
>> months?!
>> And you want us to manage the scheduling of the blog posts by using the
>> google calendar?
>>
>
>That's right! I think if we all participate will 10-11, and about 6 months
>between repeat author.
>Maybe, as examples are very easy to do we can talk more later if we do
>this
>each week...we'll see as we develop it right?
>
>
>>
>> >Below the source code, we should have the result displayed in an
>>iframe.
>> +1
>>
>> Another suggestion:
>> Peter de Haan posts always contain some simple explanations.
>> Regarding the "Hello world" post, I think it would be interesting for
>> people
>> to learn something about the code, e.g. for what is
>> "js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
>> Maybe it makes sense to link something to the docs or to add some simple
>> explanation?
>>
>
>That's a very good idea. I'll try to update the hello world with this
>suggestions :)
>
>
>>
>> I'll check out the google calendar...
>>
>> Thanks,
>> Olaf
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Sent from: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ro
>>yale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.com
>>%7Cd2453e80427a4a2db4a708d572d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C
>>0%7C0%7C636541170132357067=IW1I%2BZebS7gSyrBako0WCHBAG8eo1b3NPVnfC%
>>2BvUyTA%3D=0
>>
>
>
>
>-- 
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cd2453e80427a4a2db4a708d5
>72d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541170132357067
>data=YBsn0zhxZd98toKr%2BrZP1GwprmRzcmM5NesejiabbJo%3D=0

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Alex Harui]

Hi Carlos,

Yes, the goal is to create an Ant script so that anyone volunteering to be
an Release Manager (RM) can create a release without having to read and
interpret a long list of instructions.  I will probably be RM for 0.9.2
and try to use my Windows machine to make sure it works there as well.
Then we will need others to try it out and find out where any assumptions
were made about the machines I use.  I will consider it a success when we
have folks, especially new committers, volunteering to be the RM.  If you
are reading this and nervous about being an RM, that means we haven't made
it simple enough yet.

Please update the Downloads and Source Code pages on the website.  This is
another reason I want to write our website in Royale.  Then the updating
of those pages could be done by the Ant script so you don't forget.  Or we
could find a way to create a web-service that can tell us what the latest
release is and convert those pages to be filled out from the webservice.
I think GitHub API has a way to do that.  We did post our bits on GH for
0.9.0.  Should we post on the GH releases page for all of our releases?
If so, we may want to add that to the script as well.

We want to do at least one release a month and maybe two if there is a hot
fix or someone finishes some important code and doesn't want to wait a
month.  Is that too much for the blog?  The blog announcement could be
short and point to some longer announcement somewhere.  But I think an
announcement per release makes us sound active.

My 2 cents,
-Alex

On 2/13/18, 1:50 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>One more question. We should update the website with each release like
>this
>one right?
>I understand that I must change:
>
>* Downloads page. Should we maintain a list of recent versions? or we
>should only update to show latest (in this case 0.9.1)
>* Source Code page. The same as in Downloads page
>* New Blog Post. About the new release, to announce and reflect that we
>launch this release. Maybe if we plan to release monthly this is good, if
>we plan to release more...maybe bad since we fill the blog with minor
>releases...
>
>something more?
>
>Thought?
>
>
>
>
>2018-02-13 10:03 GMT+01:00 Carlos Rovira :
>
>> Hi Alex, that's so cool, that means that you have almost automated the
>> process of a new royale release and that will make it very easy to do ?
>> If is that I think that's a great work since releasing easily seems we
>>can
>> make lots of releases a make this project be more alive than ever
>> thanks!
>>
>> 2018-02-13 7:11 GMT+01:00 Alex Harui :
>>
>>> OK, I fixed up and ran the releasecandidate script and it says it
>>>posted
>>> the bits to npm.
>>>
>>> I believe all branches are merged and appropriately versioned.  On to
>>>the
>>> next release!
>>>
>>> -Alex
>>>
>>> On 2/12/18, 12:29 PM, "omup...@gmail.com on behalf of OmPrakash
>>> Muppirala"
>>>  wrote:
>>>
>>> >On Mon, Feb 12, 2018 at 12:22 PM, Alex Harui
>>>
>>> >wrote:
>>> >
>>> >> The steps that publish NPM are in releasecandidate.xml.  It does not
>>> >>muck
>>> >> with the packages.  It looked like your change was to the
>>>package.json
>>> >> that is already in the package.
>>> >>
>>> >
>>> >Yes that is correct.  When publishing, the publish script uses the raw
>>> >package.json file.
>>> >Look here:
>>> >https://na01.safelinks.protection.outlook.com/?url=https%
>>> 3A%2F%2Fgithub.co
>>> >m%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.1%2Fnpm%
>>> 2Frelease-scripts%
>>> >2Fpublish.js%23L66=02%7C01%7Caharui%40adobe.com%7Ca8ef
>>> 5cf25db649d00e0
>>> >d08d572575efa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>> 7C636540641940569
>>> >827=a0mEtMg9H7fAujqGHKKowVFFKtA0SDwPuEaAUoLyFrg%3D=0
>>> >
>>> >So, all you need to do is keep the tarball as is, but get my latest
>>> >changes
>>> >on release/0.9.1 before publishing to npm.
>>> >
>>> >Please try that and let me know how it goes.
>>> >
>>> >If this does not fix the issue, the next release should.  But lets
>>>give
>>> >this a shot, at least.
>>> >
>>> >Thanks,
>>> >Om
>>> >
>>> >
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 2/12/18, 12:08 PM, "omup...@gmail.com on behalf of OmPrakash
>>> >>Muppirala"
>>> >>  wrote:
>>> >>
>>> >> >On Feb 12, 2018 11:58 AM, "Alex Harui" 
>>> >>wrote:
>>> >> >
>>> >> >
>>> >> >
>>> >> >On 2/12/18, 10:42 AM, "omup...@gmail.com on behalf of OmPrakash
>>> >> Muppirala"
>>> >> > wrote:
>>> >> >
>>> >> >>On Feb 12, 2018 10:13 AM, "Alex Harui" 
>>> >>wrote:
>>> >> >>
>>> >> >>AIUI, js-swf did not work via NPM as generated from the source
>>> >>package.
>>> >> >>I
>>> >> >>thought you tweaked it before publishing.
>>> >> 

Re: ASDoc, Routing, Releases

[Alex Harui]

The link is: http://royale.apache.org/asdoc/

I think it took GitPubSub a while push it all to the production web server.

I agree that documentation is important, but to me, everything is a
trade-off.  I could stop coding and spend days on improving ASDoc, or I
can use that same time to provide functionality that helps someone migrate
their app to Royale.  I tend to choose the latter because I think lots
more folks are capable of helping improve the ASDoc than are capable of
providing virtual lists and editable data grids.  Now that our ASDoc looks
better, I will try to make sure there is at least minimal ASDoc for new
APIs.  But it would be great if some volunteers could go scrub what we
have.

I suppose we could keep a copy of ASDoc per release on the website.  But
would that help or hurt Search Engine rankings (assuming we can get ASDoc
indexed in the first place)?  There is already an ASDoc directive
(@productversion) we should be using to annotate when an API first
appeared and we could add functionality to ASDoc to filter on that.  The
thing is that in a hurry, folks often copy an existing ASDoc block and may
forget to update @productversion.  That's what I meant by being diligent.

If we add filtering to the UX, we need to consider whether filtering
should be part of the routing URL.

My 2 cents,
-Alex

On 2/13/18, 12:59 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>I tried the link royale.apache.org/asdoc but it doesn't work. Is that link
>right?
>For versions I think ASDocs has sense if we all focus in create right
>ASDoc. I'm trying to do it with Vivid, and did with MDL times. This is
>important and makes us to take care of the code we make. The code is not
>ready after we make it, is ready  when we try to think far beyond of what
>it does and what people needs from it in terms of documentation, ease of
>use, ...
>So if we all create good ASDoc, I think is ok to release with each
>release.
>With time, and more releases, people will want to check ASDoc from
>specific
>version.
>I think we will need to store that versions so people could check it, and
>will be easily discovered by url.
>For example: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.apa
>che.org%2Fasdoc%2F0.9.0%2F=02%7C01%7Caharui%40adobe.com%7C820b1d29d9e
>b4c90d1cf08d572c0248f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365410
>91942987055=jqIfArjx5Jop3Ac77gYIc2IOqB4r2AGF1mHoVOJzKgM%3D=
>0...
>
>
>
>2018-02-13 9:47 GMT+01:00 Piotr Zarzycki :
>
>> I think simplicity is the key here. Pushing after release ASDoc - I like
>> the idea. The filtering could also appear, but I would still stay with
>> pushing after every release instead all the time.
>>
>> Thanks,
>> Piotr
>>
>> 2018-02-13 9:32 GMT+01:00 Alex Harui :
>>
>> > Filtering by version is certainly possible, but would require that we
>>are
>> > diligent about specifying the correct version when entering data.
>> >
>> > -Alex
>> >
>> > On 2/12/18, 11:53 PM, "Gabe Harbs"  wrote:
>> >
>> > >Yes. Having it as part of the release process makes sense.
>> > >
>> > >Another way to go about it would be to have some way to limit which
>> > >version data is displayed, so if unreleased data is set to display,
>>it
>> > >would show up, but by default the ASDoc app would only show data
>>that is
>> > >relevant to the latest release.
>> > >
>> > >> On Feb 13, 2018, at 9:43 AM, Alex Harui 
>> > >>wrote:
>> > >>
>> > >> I pushed an Ant script that copies ASDoc from the CI server and
>>copies
>> > >>it
>> > >> to the asdoc folder on the site.
>> > >> I also pushed the ASDoc.
>> > >>
>> > >> I was going to hook this up to a CI build but am having second
>> thoughts.
>> > >> Maybe we should only update after a release.  Otherwise, folks may
>> find
>> > >> stuff in ASDoc that is only in the nightly and hasn't been
>>released.
>> > >>
>> > >> Thoughts?
>> > >> -Alex
>> > >>
>> > >> On 2/6/18, 12:38 AM, "carlos.rov...@gmail.com
>> > >> on behalf of Carlos Rovira"
>> > >>  on behalf
>> of
>> > >>carlosrov...@apache.org > wrote:
>> > >>
>> > >>> Hi Alex,
>> > >>>
>> > >>> in fact I think that's what it should be :)
>> > >>> don't know if as part of the website or in the royale-docs live
>>url.
>> > >>> Anyway the proposed url is ok.
>> > >>>
>> > >>> When I updated the website I overlay the folder with changes, as
>>in
>> the
>> > >>> website there's no "/asdoc/" url it will be untouched by my
>>changes
>> > >>>
>> > >>> thanks
>> > >>>
>> > >>>
>> > >>>
>> > >>>
>> > >>>
>> > >>>
>> > >>> 2018-02-06 6:29 GMT+01:00 Alex Harui :
>> > >>>
>> >  ASDoc is looking better.  I was looking into tools to understand
>>how
>> >  google 

Re: Build failed in Jenkins: royale-asjs_jsonly #295

[Gabe Harbs]

I don’t understand this failure.

This seems to indicate that the directory is there and up to date:
 [exec] Your branch is up to date with 'origin/royale'.
 [exec] Already on 'royale'
 [exec] Already up to date.

> On Feb 13, 2018, at 4:11 PM, apacheroyal...@gmail.com wrote:
> 
> See 
> 
> 
> --
> [...truncated 654.68 KB...]
> [exec] D  test/com/google/javascript/jscomp/regex/CharRangesTest.java
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/array_pattern_test.js
> [exec] D  test/com/google/javascript/jscomp/runtime_tests/arrow_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/async_function_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_block_scope_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_computed_getter_setter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_exported_getter_setter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_getter_setter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_in_goog_module_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_no_constructor_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_spread_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_static_getter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_static_setter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_super_return_test.js
> [exec] D  test/com/google/javascript/jscomp/runtime_tests/class_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/collections_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/computed_properties_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/default_param_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/es3_style_class.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/extend_es3_test.js
> [exec] D  test/com/google/javascript/jscomp/runtime_tests/for_of_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/generator_allow_call_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/generator_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/identifier_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/inherit_sets_superClass_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/inheritance_with_overriden_function_prototype_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/let_const_loop_typecheck_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/let_const_rename_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/mixed_destructuring_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/mocking_class_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/class_inherits_protected.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/dot_dot_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/export_from_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/export_spec_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_class_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_default_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_mixed_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_namespace_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_star_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_with_js_extension_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_order_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_runtime_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/classProtectedMethod.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_a.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportClass.js
> [exec] D  
> 

Build failed in Jenkins: royale-asjs_jsonly #295

[apacheroyaleci]

See 


--
[...truncated 654.68 KB...]
 [exec] D   test/com/google/javascript/jscomp/regex/CharRangesTest.java
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/array_pattern_test.js
 [exec] D   test/com/google/javascript/jscomp/runtime_tests/arrow_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/async_function_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_block_scope_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_computed_getter_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_exported_getter_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_getter_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_in_goog_module_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_no_constructor_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_spread_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_static_getter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_static_setter_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/class_super_return_test.js
 [exec] D   test/com/google/javascript/jscomp/runtime_tests/class_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/collections_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/computed_properties_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/default_param_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/es3_style_class.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/extend_es3_test.js
 [exec] D   test/com/google/javascript/jscomp/runtime_tests/for_of_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/generator_allow_call_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/generator_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/identifier_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/inherit_sets_superClass_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/inheritance_with_overriden_function_prototype_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/let_const_loop_typecheck_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/let_const_rename_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/mixed_destructuring_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/mocking_class_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/class_inherits_protected.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/dot_dot_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/export_from_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/export_spec_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_class_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_default_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_mixed_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_namespace_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_star_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/import_with_js_extension_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_order_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_runtime_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/classProtectedMethod.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_a.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_test.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportClass.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportDefault.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportDefaultClass.js
 [exec] D   
test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportDefaultOldStyleClass.js
 [exec] D   

Jenkins build is back to normal : royale-typedefs #147

[apacheroyaleci]

See 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

Maybe. I didn’t realize changing the typedefs was going to end up being so 
complicated.

I just changed the ant build to use git instead of svn. It takes about a minute 
the first time the repo is needed to be downloaded, but it’s pretty quick 
afterwards.

I’m not sure which method is best for Maven.

> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki  wrote:
> 
> Btw. Maybe you should move your changes to separate branch. We will have
> emails with fails for a long time now. Unless someone else look into the
> Maven.
> 
> 2018-02-13 13:03 GMT+01:00 Gabe Harbs  >:
> 
>> FWIW, here’s some other options for downloading a specific folder from
>> Github:
>> https://stackoverflow.com/a/18194523
>> 
>>> On Feb 13, 2018, at 1:57 PM, Gabe Harbs  wrote:
>>> 
>>> If you use Git, you need to download the entire repo which includes all
>> the bits for the actual compiler.
>>> 
>>> Github supports svn checkouts as well which allows you to checkout a
>> specific folder within a repo.[1]
>>> 
>>> The following command will get the extern files we need from Github:
>>> 
>>> svn checkout https://github.com/royale-extras/closure-compiler/
>> branches/royale/externs > 
>> extras/closure-compiler/branches/royale/externs>
>>> 
>>> Harbs
>>> 
>>> [1]https://help.github.com/articles/support-for-subversion-clients/ 
>>>  <
>> https://help.github.com/articles/support-for-subversion-clients/ 
>> >
>>> 
 On Feb 13, 2018, at 1:54 PM, Piotr Zarzycki 
>> >> wrote:
 
 Actually why are you talking about svn ? You mean GIT actually ?
 
 2018-02-13 12:47 GMT+01:00 Gabe Harbs  > harbs.li...@gmail.com >>:
 
> BTW, there’s a mojo for svn checkout:
> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>  <
>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>> > <
> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>  <
>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>> >>
> 
> Maybe you can use that.
> 
> Harbs
> 
>> On Feb 13, 2018, at 1:41 PM, Gabe Harbs > 
>> >> wrote:
>> 
>> We need to download all the files from here:
>> https://github.com/royale-  
>> >
> extras/closure-compiler/tree/royale/externs/ <
>> https://github.com/royale-  
>> >
> extras/closure-compiler/tree/royale/externs/> to js/target/downloads.
>> 
>> Svn seems like the easiest way to do that, but you can use any method
> that works.
>> 
>> Harbs
>> 
>>> On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com  
>> >
>  
> > wrote:
>>> 
>>> Can we avoid using svn ? Or it was used before ? I'm not familiar
>> with
> that
>>> logic.
>>> 
>>> 2018-02-13 12:37 GMT+01:00 Harbs >>  > ha...@in-tools.com >  ha...@in-tools.com   >> 
 We need to add svn checkout of the externs like I did in the ant
> script.
 
> On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
 jenk...@builds.apache.org  
 >
>>  
>> > wrote:
> 
> The Apache Jenkins build system has built Royale-typedefs (build
>> #34)
> 
> Status: Failure
> 
> Check console output at 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Piotr Zarzycki]

Btw. Maybe you should move your changes to separate branch. We will have
emails with fails for a long time now. Unless someone else look into the
Maven.

2018-02-13 13:03 GMT+01:00 Gabe Harbs :

> FWIW, here’s some other options for downloading a specific folder from
> Github:
> https://stackoverflow.com/a/18194523
>
> > On Feb 13, 2018, at 1:57 PM, Gabe Harbs  wrote:
> >
> > If you use Git, you need to download the entire repo which includes all
> the bits for the actual compiler.
> >
> > Github supports svn checkouts as well which allows you to checkout a
> specific folder within a repo.[1]
> >
> > The following command will get the extern files we need from Github:
> >
> > svn checkout https://github.com/royale-extras/closure-compiler/
> branches/royale/externs  extras/closure-compiler/branches/royale/externs>
> >
> > Harbs
> >
> > [1]https://help.github.com/articles/support-for-subversion-clients/ <
> https://help.github.com/articles/support-for-subversion-clients/>
> >
> >> On Feb 13, 2018, at 1:54 PM, Piotr Zarzycki  > wrote:
> >>
> >> Actually why are you talking about svn ? You mean GIT actually ?
> >>
> >> 2018-02-13 12:47 GMT+01:00 Gabe Harbs >:
> >>
> >>> BTW, there’s a mojo for svn checkout:
> >>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html <
> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html> <
> >>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html <
> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html>>
> >>>
> >>> Maybe you can use that.
> >>>
> >>> Harbs
> >>>
>  On Feb 13, 2018, at 1:41 PM, Gabe Harbs  > wrote:
> 
>  We need to download all the files from here:
> https://github.com/royale- 
> >>> extras/closure-compiler/tree/royale/externs/ <
> https://github.com/royale- 
> >>> extras/closure-compiler/tree/royale/externs/> to js/target/downloads.
> 
>  Svn seems like the easiest way to do that, but you can use any method
> >>> that works.
> 
>  Harbs
> 
> > On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com 
> >>> >>
> wrote:
> >
> > Can we avoid using svn ? Or it was used before ? I'm not familiar
> with
> >>> that
> > logic.
> >
> > 2018-02-13 12:37 GMT+01:00 Harbs   >>> ha...@in-tools.com >>:
> >
> >> We need to add svn checkout of the externs like I did in the ant
> >>> script.
> >>
> >>> On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
> >> jenk...@builds.apache.org 
> >>
> wrote:
> >>>
> >>> The Apache Jenkins build system has built Royale-typedefs (build
> #34)
> >>>
> >>> Status: Failure
> >>>
> >>> Check console output at https://builds.apache.org/job/ <
> https://builds.apache.org/job/> <
> >>> https://builds.apache.org/job/ >
> >> Royale-typedefs/34/ to view the results.
> >>
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki <
> https://www.patreon.com/piotrzarzycki> <
> >>> https://www.patreon.com/piotrzarzycki  piotrzarzycki>>
> >  piotrzarzycki> 
> >>> piotrzarzycki>>*
> 
> >>>
> >>>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki <
> https://www.patreon.com/piotrzarzycki>
> >>  piotrzarzycki>>*
> >
>
>


-- 

Piotr Zarzycki

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

Build failed in Jenkins: royale-typedefs #145

[apacheroyaleci]

See 


Changes:

[harbs] This should fix the ant build

--
Started by an SCM change
Building in workspace 

 > git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url 
 > https://github.com/apache/royale-typedefs.git # timeout=10
Fetching upstream changes from https://github.com/apache/royale-typedefs.git
 > git.exe --version # timeout=10
 > git.exe fetch --tags --progress 
 > https://github.com/apache/royale-typedefs.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git.exe rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10
 > git.exe rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 57c5f5fe08127e55ac26b05c54e588b2e8653ccc 
(refs/remotes/origin/develop)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 57c5f5fe08127e55ac26b05c54e588b2e8653ccc
Commit message: "This should fix the ant build"
 > git.exe rev-list --no-walk 748008eacfd6ca84c481f2fef1d638bfd925f419 # 
 > timeout=10
[royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat main && 
exit %%ERRORLEVEL%%"
Buildfile: 


main:

download:
 [echo] 


BUILD FAILED
:52:
 The following error occurred while executing this line:
:85:
 Execute failed: java.io.IOException: Cannot run program "svn" (in directory 
":
 CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at java.lang.Runtime.exec(Runtime.java:620)
at 
org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:58)
at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:426)
at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:440)
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:629)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:670)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:496)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
at 
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1260)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
at org.apache.tools.ant.Project.executeTarget(Project.java:1376)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1260)
at org.apache.tools.ant.Main.runBuild(Main.java:857)
at org.apache.tools.ant.Main.startAnt(Main.java:236)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:287)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:113)
Caused by: java.io.IOException: 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

FWIW, here’s some other options for downloading a specific folder from Github:
https://stackoverflow.com/a/18194523

> On Feb 13, 2018, at 1:57 PM, Gabe Harbs  wrote:
> 
> If you use Git, you need to download the entire repo which includes all the 
> bits for the actual compiler.
> 
> Github supports svn checkouts as well which allows you to checkout a specific 
> folder within a repo.[1]
> 
> The following command will get the extern files we need from Github:
> 
> svn checkout 
> https://github.com/royale-extras/closure-compiler/branches/royale/externs 
> 
> 
> Harbs
> 
> [1]https://help.github.com/articles/support-for-subversion-clients/ 
> 
> 
>> On Feb 13, 2018, at 1:54 PM, Piotr Zarzycki > > wrote:
>> 
>> Actually why are you talking about svn ? You mean GIT actually ?
>> 
>> 2018-02-13 12:47 GMT+01:00 Gabe Harbs > >:
>> 
>>> BTW, there’s a mojo for svn checkout:
>>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>>>  <
>>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>>> >
>>> 
>>> Maybe you can use that.
>>> 
>>> Harbs
>>> 
 On Feb 13, 2018, at 1:41 PM, Gabe Harbs > wrote:
 
 We need to download all the files from here: https://github.com/royale- 
 
>>> extras/closure-compiler/tree/royale/externs/ >> 
>>> extras/closure-compiler/tree/royale/externs/> to js/target/downloads.
 
 Svn seems like the easiest way to do that, but you can use any method
>>> that works.
 
 Harbs
 
> On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki  
>>> >> 
>>> wrote:
> 
> Can we avoid using svn ? Or it was used before ? I'm not familiar with
>>> that
> logic.
> 
> 2018-02-13 12:37 GMT+01:00 Harbs   >> ha...@in-tools.com >>:
> 
>> We need to add svn checkout of the externs like I did in the ant
>>> script.
>> 
>>> On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
>> jenk...@builds.apache.org  
>> >> 
>> wrote:
>>> 
>>> The Apache Jenkins build system has built Royale-typedefs (build #34)
>>> 
>>> Status: Failure
>>> 
>>> Check console output at https://builds.apache.org/job/ 
>>>  <
>>> https://builds.apache.org/job/ >
>> Royale-typedefs/34/ to view the results.
>> 
>> 
> 
> 
> --
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki 
>  <
>>> https://www.patreon.com/piotrzarzycki 
>>> >
>    
>>> piotrzarzycki>>*
 
>>> 
>>> 
>> 
>> 
>> -- 
>> 
>> Piotr Zarzycki
>> 
>> Patreon: *https://www.patreon.com/piotrzarzycki 
>> 
>> > >*
> 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

If you use Git, you need to download the entire repo which includes all the 
bits for the actual compiler.

Github supports svn checkouts as well which allows you to checkout a specific 
folder within a repo.[1]

The following command will get the extern files we need from Github:

svn checkout 
https://github.com/royale-extras/closure-compiler/branches/royale/externs

Harbs

[1]https://help.github.com/articles/support-for-subversion-clients/ 


> On Feb 13, 2018, at 1:54 PM, Piotr Zarzycki  wrote:
> 
> Actually why are you talking about svn ? You mean GIT actually ?
> 
> 2018-02-13 12:47 GMT+01:00 Gabe Harbs :
> 
>> BTW, there’s a mojo for svn checkout:
>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html <
>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html>
>> 
>> Maybe you can use that.
>> 
>> Harbs
>> 
>>> On Feb 13, 2018, at 1:41 PM, Gabe Harbs  wrote:
>>> 
>>> We need to download all the files from here: https://github.com/royale-
>> extras/closure-compiler/tree/royale/externs/ > extras/closure-compiler/tree/royale/externs/> to js/target/downloads.
>>> 
>>> Svn seems like the easiest way to do that, but you can use any method
>> that works.
>>> 
>>> Harbs
>>> 
 On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki > > wrote:
 
 Can we avoid using svn ? Or it was used before ? I'm not familiar with
>> that
 logic.
 
 2018-02-13 12:37 GMT+01:00 Harbs  ha...@in-tools.com>>:
 
> We need to add svn checkout of the externs like I did in the ant
>> script.
> 
>> On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
> jenk...@builds.apache.org > wrote:
>> 
>> The Apache Jenkins build system has built Royale-typedefs (build #34)
>> 
>> Status: Failure
>> 
>> Check console output at https://builds.apache.org/job/ <
>> https://builds.apache.org/job/>
> Royale-typedefs/34/ to view the results.
> 
> 
 
 
 --
 
 Piotr Zarzycki
 
 Patreon: *https://www.patreon.com/piotrzarzycki <
>> https://www.patreon.com/piotrzarzycki>
 > piotrzarzycki>>*
>>> 
>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> *

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Piotr Zarzycki]

Actually why are you talking about svn ? You mean GIT actually ?

2018-02-13 12:47 GMT+01:00 Gabe Harbs :

> BTW, there’s a mojo for svn checkout:
> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html <
> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html>
>
> Maybe you can use that.
>
> Harbs
>
> > On Feb 13, 2018, at 1:41 PM, Gabe Harbs  wrote:
> >
> > We need to download all the files from here: https://github.com/royale-
> extras/closure-compiler/tree/royale/externs/  extras/closure-compiler/tree/royale/externs/> to js/target/downloads.
> >
> > Svn seems like the easiest way to do that, but you can use any method
> that works.
> >
> > Harbs
> >
> >> On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki  > wrote:
> >>
> >> Can we avoid using svn ? Or it was used before ? I'm not familiar with
> that
> >> logic.
> >>
> >> 2018-02-13 12:37 GMT+01:00 Harbs >:
> >>
> >>> We need to add svn checkout of the externs like I did in the ant
> script.
> >>>
>  On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
> >>> jenk...@builds.apache.org > wrote:
> 
>  The Apache Jenkins build system has built Royale-typedefs (build #34)
> 
>  Status: Failure
> 
>  Check console output at https://builds.apache.org/job/ <
> https://builds.apache.org/job/>
> >>> Royale-typedefs/34/ to view the results.
> >>>
> >>>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki <
> https://www.patreon.com/piotrzarzycki>
> >>  piotrzarzycki>>*
> >
>
>


-- 

Piotr Zarzycki

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

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Piotr Zarzycki]

I will see what Maven offer in that matter. Can you raise Issue for me,
cause I'm not sure if I will be able to do this today/tomorrow.

Thanks,
Piotr

2018-02-13 12:41 GMT+01:00 Gabe Harbs :

> We need to download all the files from here: https://github.com/royale-
> extras/closure-compiler/tree/royale/externs/  extras/closure-compiler/tree/royale/externs/> to js/target/downloads.
>
> Svn seems like the easiest way to do that, but you can use any method that
> works.
>
> Harbs
>
> > On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki 
> wrote:
> >
> > Can we avoid using svn ? Or it was used before ? I'm not familiar with
> that
> > logic.
> >
> > 2018-02-13 12:37 GMT+01:00 Harbs :
> >
> >> We need to add svn checkout of the externs like I did in the ant script.
> >>
> >>> On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
> >> jenk...@builds.apache.org> wrote:
> >>>
> >>> The Apache Jenkins build system has built Royale-typedefs (build #34)
> >>>
> >>> Status: Failure
> >>>
> >>> Check console output at https://builds.apache.org/job/
> >> Royale-typedefs/34/ to view the results.
> >>
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
>
>


-- 

Piotr Zarzycki

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

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

BTW, there’s a mojo for svn checkout:
https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 


Maybe you can use that.

Harbs

> On Feb 13, 2018, at 1:41 PM, Gabe Harbs  wrote:
> 
> We need to download all the files from here: 
> https://github.com/royale-extras/closure-compiler/tree/royale/externs/ 
>  to 
> js/target/downloads.
> 
> Svn seems like the easiest way to do that, but you can use any method that 
> works.
> 
> Harbs
> 
>> On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki > > wrote:
>> 
>> Can we avoid using svn ? Or it was used before ? I'm not familiar with that
>> logic.
>> 
>> 2018-02-13 12:37 GMT+01:00 Harbs > >:
>> 
>>> We need to add svn checkout of the externs like I did in the ant script.
>>> 
 On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
>>> jenk...@builds.apache.org > wrote:
 
 The Apache Jenkins build system has built Royale-typedefs (build #34)
 
 Status: Failure
 
 Check console output at https://builds.apache.org/job/ 
 
>>> Royale-typedefs/34/ to view the results.
>>> 
>>> 
>> 
>> 
>> -- 
>> 
>> Piotr Zarzycki
>> 
>> Patreon: *https://www.patreon.com/piotrzarzycki 
>> 
>> > >*
> 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Piotr Zarzycki]

Can we avoid using svn ? Or it was used before ? I'm not familiar with that
logic.

2018-02-13 12:37 GMT+01:00 Harbs :

> We need to add svn checkout of the externs like I did in the ant script.
>
> > On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
> >
> > The Apache Jenkins build system has built Royale-typedefs (build #34)
> >
> > Status: Failure
> >
> > Check console output at https://builds.apache.org/job/
> Royale-typedefs/34/ to view the results.
>
>


-- 

Piotr Zarzycki

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

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Harbs]

We need to add svn checkout of the externs like I did in the ant script.

> On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server 
>  wrote:
> 
> The Apache Jenkins build system has built Royale-typedefs (build #34)
> 
> Status: Failure
> 
> Check console output at https://builds.apache.org/job/Royale-typedefs/34/ to 
> view the results.

How I can use multiple CSS files

[Carlos Rovira]

Hi,

I'm organizing CSS files in Vivid (new ui set) - VividBlueTheme (first
theme) - VividExample (example to show all working)

I want to develop each component look-and-feel and style in a single file
in the theme project:

default.css (this could hold global styling like body, headers, background
color, and more)
TextField.css (all css to make a TextField be represented in a particular
way)
Button.css
Slider.css
...

in my theme pom I have:



defaults.css
../src/main/resources/defaults.css


TextField.css
../src/main/resources/TextField.css



and I check the resulting VividBlueTheme.swc and has default.css and
TextField.css

* First question here is: Can I collapse all css content in multiple files
in a single .css (i.e: defaults.css or themename.css)?

Then in vivid example how CSS in theme projects are referenced? I see
"defaults.css" is begin applied, but "TextField.css" is not

* Second question how to apply a included .css file to be used in example

Notice that if we get all css in one single file we don't need the second
part.

Hope you could help me on this in order to continue progress with this
effort

thanks




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

Re: Royale Examples Blog proposal to all the team

[Carlos Rovira]

Hi Olaf

2018-02-13 11:31 GMT+01:00 Olaf Krueger :

> >I'd like to read thoughts from others in the team.
>
> This is a really good idea, Carlos!
> If I understand you right you'd like to say that we want to publish a post
> every two weeks and because we're about 10 to 15 people who will contribute
> this means that anybody of us has to write an article approx every 6
> months?!
> And you want us to manage the scheduling of the blog posts by using the
> google calendar?
>

That's right! I think if we all participate will 10-11, and about 6 months
between repeat author.
Maybe, as examples are very easy to do we can talk more later if we do this
each week...we'll see as we develop it right?


>
> >Below the source code, we should have the result displayed in an iframe.
> +1
>
> Another suggestion:
> Peter de Haan posts always contain some simple explanations.
> Regarding the "Hello world" post, I think it would be interesting for
> people
> to learn something about the code, e.g. for what is
> "js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
> Maybe it makes sense to link something to the docs or to add some simple
> explanation?
>

That's a very good idea. I'll try to update the hello world with this
suggestions :)


>
> I'll check out the google calendar...
>
> Thanks,
> Olaf
>
>
>
>
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



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

Build failed in Jenkins: royale-typedefs #144

[apacheroyaleci]

See 


Changes:

[harbs] Changed download references for extern files

--
Started by an SCM change
Building in workspace 

 > git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url 
 > https://github.com/apache/royale-typedefs.git # timeout=10
Fetching upstream changes from https://github.com/apache/royale-typedefs.git
 > git.exe --version # timeout=10
 > git.exe fetch --tags --progress 
 > https://github.com/apache/royale-typedefs.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git.exe rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10
 > git.exe rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 748008eacfd6ca84c481f2fef1d638bfd925f419 
(refs/remotes/origin/develop)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 748008eacfd6ca84c481f2fef1d638bfd925f419
Commit message: "Changed download references for extern files"
 > git.exe rev-list --no-walk 792581e45154deb3bc80c003923d57089f593bed # 
 > timeout=10
[royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat main && 
exit %%ERRORLEVEL%%"
Buildfile: 


main:

BUILD FAILED
:52:
 The following error occurred while executing this line:
:151:
 The string "--" is not permitted within comments.

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
Build step 'Invoke Ant' marked build as failure

Re: Royale Examples Blog proposal to all the team

[Carlos Rovira]

Hi Harbs,

you're right, we must put a "viewer" with results. I'll look how to do it
and update the hello world with that.
thanks

About calendar I sent invitations but maybe I use user for you didn't reach
the notification I'll try to sent the url to you right now

2018-02-13 11:12 GMT+01:00 Gabe Harbs :

> Great initiative. Yes. I’d be interested in contributing.
>
> One suggestion: Below the source code, we should have the result displayed
> in an iframe.
>
> I’m not sure what you mean by calendar.
>
> Harbs
>
> > On Feb 13, 2018, at 11:54 AM, Carlos Rovira 
> wrote:
> >
> > Thanks Piotr :)
> >
> > @Harbs, link are here:
> >
> >
> >   - http://royale.apache.org/blog/
> >
> >
> > The first one:
> >
> >
> >   - http://royale.apache.org/creating-a-hello-world-in-apache-royale/
> >
> >
> >
> >   - https://twitter.com/ApacheRoyale/status/963092003075575810
> >
> >
> >
> >   - https://www.facebook.com/ApacheRoyaleSDK/  (in facebook can't find
> the
> >   exact url)
> >
> >
> >
> > Did you get the calendar I did to organize blog post?
> >
> >
> > thanks!
> >
> > 2018-02-13 10:48 GMT+01:00 Gabe Harbs :
> >
> >> Do you have a link?
> >>
> >>> On Feb 13, 2018, at 11:44 AM, Carlos Rovira 
> >> wrote:
> >>>
> >>> Hi just let you know yesterday I make final touched to "Hello World"
> blog
> >>> post example (it had already flexjs namespace refs)
> >>> and make it live in twitter and facebook.
> >>>
> >>> This is the first of our blog post that shows easy tips to show how
> easy
> >> is
> >>> to make things in Royale
> >>>
> >>> I'd like to read thoughts from others in the team. What do you think
> >> about
> >>> this effort, Alex, Peter, Harbs, Erik, Olaf,... will you participate in
> >> it?
> >>>
> >>> it's only 1 tiny blog post each 6 months. I think is affordable for any
> >> of
> >>> us...
> >>>
> >>> ...and make us to be of social networks each two weeks, (a part from
> >> other
> >>> appearances about releases, articles, and other things we want to
> >> promote)
> >>>
> >>> Thanks!
> >>>
> >>> Carlos
> >>>
> >>>
> >>>
> >>> 2018-02-09 13:19 GMT+01:00 Andrew Wetmore :
> >>>
>  I see the calendar!
> 
>  On Fri, Feb 9, 2018 at 5:04 AM, Carlos Rovira <
> carlosrov...@apache.org>
>  wrote:
> 
> > Hi Just created the shared calendar and send invitations
> >
> > please let me know if you received yours. As well, I created events
> >> with
> > each name on Mondays each 2 weeks.
> >
> > We can start this Monday with the already posted "Hello World in
> >> Royale"
> > and share it vía twitter and facebook.
> >
> > Please review the calendar and take into account that as we are a
> huge
>  team
> > we have lots of time to make this real.
> >
> > If anyone doesn't like the idea or don't want to participate, let us
> >> know
> > to make the calendar adjustments
> >
> > thanks!
> >
> > Carlos
> >
> >
> >
> >
> >
> > 2018-02-09 9:47 GMT+01:00 Carlos Rovira :
> >
> >> Great Om!,
> >>
> >> we can create the post as drafts and a shared calendar. As people
> ends
> > his
> >> post, we can schedule for the right day of publication (2 weeks per
> > post).
> >>
> >> I'll be creating a calendar and sharing with you all.
> >>
> >> Anyone out there that wants to share something like this can join
> this
> >> thread and talk about it. I think we don't want to close this effort
>  only
> >> to royale team members
> >>
> >> thanks!
> >>
> >>
> >>
> >> 2018-02-09 4:29 GMT+01:00 OmPrakash Muppirala  >:
> >>
> >>> Great idea, Carlos.
> >>>
> >>> Here is one I volunteer to write about: Getting started with Royale
> >> on
> > npm
> >>>
> >>> I will write this over the weekend and share it here.  We can post
>  after
> >>> Andrew (and others) makes a sweep over it :-)
> >>>
> >>> Thanks,
> >>> Om
> >>>
> >>> On Thu, Feb 8, 2018 at 3:25 AM, Andrew Wetmore <
> cottag...@gmail.com>
> >>> wrote:
> >>>
>  This sounds really good. I will be glad to help people who have
>  strong
>  Royale skills but are uncomfortable writing for publication in
> > English.
> 
>  a
> 
>  On Thu, Feb 8, 2018 at 7:11 AM, Carlos Rovira <
> > carlosrov...@apache.org>
>  wrote:
> 
> > Hi,
> >
> > I want to propose to start introducing some "pearls" (beads? ;))
>  of
> >>> quick
> > knowledge about Royale in our blog (Peter de Haan's flex examples
> > blog
> > style, remember it?)
> >
> > *This will make the effect that each post will be published in
> >>> Facebook
>  and
> > Twitter and will 

Re: Build failed in Jenkins: royale-typedefs #139

[Gabe Harbs]

I changed the extern files directly and changed the download locations.

I have one question though:

There are a whole group of externs under 
https://github.com/royale-extras/closure-compiler/tree/royale/externs 
.

These have been downloaded as part of the closure-compiler and unzipped into 
the downloads folder. There’s a few ways we can handle this.

1. One is to use svn checkout 
https://github.com/royale-extras/closure-compiler/branches/royale/externs to 
download the full folder structure from Github. I think both ant and maven 
support calling svn. The only issue I see with this is that svn needs to be 
installed.
2. We can check out the entire git repo and copy the externs from that.
3. We can loop through the files and download each on explicitly. (This is how 
it’s being done for the node.js externs.)

I’m leaning towards option #1 considering it’s over 70 files.

Thoughts?

Harbs


> On Feb 13, 2018, at 11:48 AM, Gabe Harbs  wrote:
> 
> I created royale-extras and cloned closure-compiler there.[1]
> 
> I believe closure-compiler has all the typedefs we are currently using. The 
> version of svg.js that’s hosted there[2] seems to be vastly improved over the 
> version we’re currently downloading.[3] It looks to me that all the patching 
> we are doing on sag.js is not necessary with the newer version.
> 
> es3.js and es6.js have patches as well I’m unclear on whether those changes 
> need to be applied. I think yes.
> 
> Harbs
> 
> [1]https://github.com/royale-extras/closure-compiler/ 
> 
> [2]https://github.com/royale-extras/closure-compiler/blob/master/contrib/externs/svg.js
>  
> 
> [3]https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/closureidl/svg.js
>  
> 
> 
>> On Feb 13, 2018, at 8:26 AM, Gabe Harbs > > wrote:
>> 
>> We could make a non-Apache organization for Royale-related stuff which is 
>> not strictly part of our repos. Kind of like what I did for flex-extras[1]
>> 
>> [1]https://github.com/flex-extras 
>> 
>>> On Feb 13, 2018, at 8:06 AM, Alex Harui >> > wrote:
>>> 
>>> Where would the fork live?
>>> 
>>> You might also have to verify that all of the things we patch are
>>> available on GH or Git.
>>> 
>>> Seems like a good possibility,
>>> -Alex
>>> 
>>> On 2/12/18, 1:46 PM, "Gabe Harbs" >> > wrote:
>>> 
 We could fork the Google externs on Github and update those. If we pull
 from the forked repo, we would be able to quickly make changes that we
 need and make PRs back to Google. That would also make it easy to pull in
 changes that are made to Google’s repo.
 
 Harbs
 
> On Feb 12, 2018, at 10:00 PM, Alex Harui  >
> wrote:
> 
> For js.patch, see the js/build.xml in royale-typedefs and the make_patch
> target.
> 
> Lately, I've been thinking about finding some other way of dealing with
> this.  We used patches so we didn't have to host 3rd-party files in our
> source tree.  I think we may now have 3rd-party files elsewhere in our
> source tree so we could just put patched versions in our source tree and
> update LICENSE and headers appropriately.  There is an issue with
> staying
> synced up with the master 3rd-party file.  And, we could make
> pull-requests on the 3rd-party file in some cases.
> 
> Thoughts?
> -Alex 
> 
> On 2/12/18, 11:23 AM, "Gabe Harbs"  
> >> wrote:
> 
>> Where is that and how do I add to the patches?
>> 
>>> On Feb 12, 2018, at 7:31 PM, Alex Harui >> >
>>> wrote:
>>> 
>>> Patch files are auto-generated by the Ant script, verified by a build,
>>> then committed to the src/main/patch/js.patch so that the Maven build
>>> can
>>> use it.  If we choose to try to manually maintain the patch files, we
>>> should comment out the auto-generation in the Ant build, otherwise as
>>> soon
>>> as someone uses it, it will blow away manual changes.  And if you had
>>> auto-generated the patch file, it probably wouldn't have had
>>> formatting
>>> issues.
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 2/12/18, 8:26 AM, "Yishay Weiss" >> 

Re: Royale Examples Blog proposal to all the team

[Olaf Krueger]

>I'd like to read thoughts from others in the team. 

This is a really good idea, Carlos!
If I understand you right you'd like to say that we want to publish a post
every two weeks and because we're about 10 to 15 people who will contribute
this means that anybody of us has to write an article approx every 6
months?!
And you want us to manage the scheduling of the blog posts by using the
google calendar?

>Below the source code, we should have the result displayed in an iframe. 
+1

Another suggestion:
Peter de Haan posts always contain some simple explanations.
Regarding the "Hello world" post, I think it would be interesting for people
to learn something about the code, e.g. for what is
"js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
Maybe it makes sense to link something to the docs or to add some simple
explanation?

I'll check out the google calendar...

Thanks,
Olaf









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

Re: Royale Examples Blog proposal to all the team

[Gabe Harbs]

Great initiative. Yes. I’d be interested in contributing.

One suggestion: Below the source code, we should have the result displayed in 
an iframe.

I’m not sure what you mean by calendar.

Harbs

> On Feb 13, 2018, at 11:54 AM, Carlos Rovira  wrote:
> 
> Thanks Piotr :)
> 
> @Harbs, link are here:
> 
> 
>   - http://royale.apache.org/blog/
> 
> 
> The first one:
> 
> 
>   - http://royale.apache.org/creating-a-hello-world-in-apache-royale/
> 
> 
> 
>   - https://twitter.com/ApacheRoyale/status/963092003075575810
> 
> 
> 
>   - https://www.facebook.com/ApacheRoyaleSDK/  (in facebook can't find the
>   exact url)
> 
> 
> 
> Did you get the calendar I did to organize blog post?
> 
> 
> thanks!
> 
> 2018-02-13 10:48 GMT+01:00 Gabe Harbs :
> 
>> Do you have a link?
>> 
>>> On Feb 13, 2018, at 11:44 AM, Carlos Rovira 
>> wrote:
>>> 
>>> Hi just let you know yesterday I make final touched to "Hello World" blog
>>> post example (it had already flexjs namespace refs)
>>> and make it live in twitter and facebook.
>>> 
>>> This is the first of our blog post that shows easy tips to show how easy
>> is
>>> to make things in Royale
>>> 
>>> I'd like to read thoughts from others in the team. What do you think
>> about
>>> this effort, Alex, Peter, Harbs, Erik, Olaf,... will you participate in
>> it?
>>> 
>>> it's only 1 tiny blog post each 6 months. I think is affordable for any
>> of
>>> us...
>>> 
>>> ...and make us to be of social networks each two weeks, (a part from
>> other
>>> appearances about releases, articles, and other things we want to
>> promote)
>>> 
>>> Thanks!
>>> 
>>> Carlos
>>> 
>>> 
>>> 
>>> 2018-02-09 13:19 GMT+01:00 Andrew Wetmore :
>>> 
 I see the calendar!
 
 On Fri, Feb 9, 2018 at 5:04 AM, Carlos Rovira 
 wrote:
 
> Hi Just created the shared calendar and send invitations
> 
> please let me know if you received yours. As well, I created events
>> with
> each name on Mondays each 2 weeks.
> 
> We can start this Monday with the already posted "Hello World in
>> Royale"
> and share it vía twitter and facebook.
> 
> Please review the calendar and take into account that as we are a huge
 team
> we have lots of time to make this real.
> 
> If anyone doesn't like the idea or don't want to participate, let us
>> know
> to make the calendar adjustments
> 
> thanks!
> 
> Carlos
> 
> 
> 
> 
> 
> 2018-02-09 9:47 GMT+01:00 Carlos Rovira :
> 
>> Great Om!,
>> 
>> we can create the post as drafts and a shared calendar. As people ends
> his
>> post, we can schedule for the right day of publication (2 weeks per
> post).
>> 
>> I'll be creating a calendar and sharing with you all.
>> 
>> Anyone out there that wants to share something like this can join this
>> thread and talk about it. I think we don't want to close this effort
 only
>> to royale team members
>> 
>> thanks!
>> 
>> 
>> 
>> 2018-02-09 4:29 GMT+01:00 OmPrakash Muppirala :
>> 
>>> Great idea, Carlos.
>>> 
>>> Here is one I volunteer to write about: Getting started with Royale
>> on
> npm
>>> 
>>> I will write this over the weekend and share it here.  We can post
 after
>>> Andrew (and others) makes a sweep over it :-)
>>> 
>>> Thanks,
>>> Om
>>> 
>>> On Thu, Feb 8, 2018 at 3:25 AM, Andrew Wetmore 
>>> wrote:
>>> 
 This sounds really good. I will be glad to help people who have
 strong
 Royale skills but are uncomfortable writing for publication in
> English.
 
 a
 
 On Thu, Feb 8, 2018 at 7:11 AM, Carlos Rovira <
> carlosrov...@apache.org>
 wrote:
 
> Hi,
> 
> I want to propose to start introducing some "pearls" (beads? ;))
 of
>>> quick
> knowledge about Royale in our blog (Peter de Haan's flex examples
> blog
> style, remember it?)
> 
> *This will make the effect that each post will be published in
>>> Facebook
 and
> Twitter and will make us to be "on the air" and reach more people
> that
> would eventually join us. Is not only about make it easy to learn
>>> Royale,
> but to make people out there know us!)*
> 
> To make this happen I propose to publish one tiny example each 2
>>> weeks,
 and
> each time from a different team member.
> 
> Since we are around 10-15 people supporting this project, we can
> make
> calendar with publish dates, so we all know when we must publish.
> 
> In this way each one will be publishing each 6 month (approx.),

Re: Royale Examples Blog proposal to all the team

[Carlos Rovira]

Thanks Piotr :)

@Harbs, link are here:


   - http://royale.apache.org/blog/


The first one:


   - http://royale.apache.org/creating-a-hello-world-in-apache-royale/



   - https://twitter.com/ApacheRoyale/status/963092003075575810



   - https://www.facebook.com/ApacheRoyaleSDK/  (in facebook can't find the
   exact url)



Did you get the calendar I did to organize blog post?


thanks!

2018-02-13 10:48 GMT+01:00 Gabe Harbs :

> Do you have a link?
>
> > On Feb 13, 2018, at 11:44 AM, Carlos Rovira 
> wrote:
> >
> > Hi just let you know yesterday I make final touched to "Hello World" blog
> > post example (it had already flexjs namespace refs)
> > and make it live in twitter and facebook.
> >
> > This is the first of our blog post that shows easy tips to show how easy
> is
> > to make things in Royale
> >
> > I'd like to read thoughts from others in the team. What do you think
> about
> > this effort, Alex, Peter, Harbs, Erik, Olaf,... will you participate in
> it?
> >
> > it's only 1 tiny blog post each 6 months. I think is affordable for any
> of
> > us...
> >
> > ...and make us to be of social networks each two weeks, (a part from
> other
> > appearances about releases, articles, and other things we want to
> promote)
> >
> > Thanks!
> >
> > Carlos
> >
> >
> >
> > 2018-02-09 13:19 GMT+01:00 Andrew Wetmore :
> >
> >> I see the calendar!
> >>
> >> On Fri, Feb 9, 2018 at 5:04 AM, Carlos Rovira 
> >> wrote:
> >>
> >>> Hi Just created the shared calendar and send invitations
> >>>
> >>> please let me know if you received yours. As well, I created events
> with
> >>> each name on Mondays each 2 weeks.
> >>>
> >>> We can start this Monday with the already posted "Hello World in
> Royale"
> >>> and share it vía twitter and facebook.
> >>>
> >>> Please review the calendar and take into account that as we are a huge
> >> team
> >>> we have lots of time to make this real.
> >>>
> >>> If anyone doesn't like the idea or don't want to participate, let us
> know
> >>> to make the calendar adjustments
> >>>
> >>> thanks!
> >>>
> >>> Carlos
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> 2018-02-09 9:47 GMT+01:00 Carlos Rovira :
> >>>
>  Great Om!,
> 
>  we can create the post as drafts and a shared calendar. As people ends
> >>> his
>  post, we can schedule for the right day of publication (2 weeks per
> >>> post).
> 
>  I'll be creating a calendar and sharing with you all.
> 
>  Anyone out there that wants to share something like this can join this
>  thread and talk about it. I think we don't want to close this effort
> >> only
>  to royale team members
> 
>  thanks!
> 
> 
> 
>  2018-02-09 4:29 GMT+01:00 OmPrakash Muppirala :
> 
> > Great idea, Carlos.
> >
> > Here is one I volunteer to write about: Getting started with Royale
> on
> >>> npm
> >
> > I will write this over the weekend and share it here.  We can post
> >> after
> > Andrew (and others) makes a sweep over it :-)
> >
> > Thanks,
> > Om
> >
> > On Thu, Feb 8, 2018 at 3:25 AM, Andrew Wetmore 
> > wrote:
> >
> >> This sounds really good. I will be glad to help people who have
> >> strong
> >> Royale skills but are uncomfortable writing for publication in
> >>> English.
> >>
> >> a
> >>
> >> On Thu, Feb 8, 2018 at 7:11 AM, Carlos Rovira <
> >>> carlosrov...@apache.org>
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> I want to propose to start introducing some "pearls" (beads? ;))
> >> of
> > quick
> >>> knowledge about Royale in our blog (Peter de Haan's flex examples
> >>> blog
> >>> style, remember it?)
> >>>
> >>> *This will make the effect that each post will be published in
> > Facebook
> >> and
> >>> Twitter and will make us to be "on the air" and reach more people
> >>> that
> >>> would eventually join us. Is not only about make it easy to learn
> > Royale,
> >>> but to make people out there know us!)*
> >>>
> >>> To make this happen I propose to publish one tiny example each 2
> > weeks,
> >> and
> >>> each time from a different team member.
> >>>
> >>> Since we are around 10-15 people supporting this project, we can
> >>> make
> >>> calendar with publish dates, so we all know when we must publish.
> >>>
> >>> In this way each one will be publishing each 6 month (approx.),
> >> and
> >>> I
> >> think
> >>> this is very affordable for all of us
> >>>
> >>> what do you think?
> >>>
> >>> (btw, we can introduce the content in WP and schedule for
> >>> publication
> > the
> >>> day and hour we want, and then make it live royal.a.o)
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>>
> >>
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Carlos Rovira]

One more question. We should update the website with each release like this
one right?
I understand that I must change:

* Downloads page. Should we maintain a list of recent versions? or we
should only update to show latest (in this case 0.9.1)
* Source Code page. The same as in Downloads page
* New Blog Post. About the new release, to announce and reflect that we
launch this release. Maybe if we plan to release monthly this is good, if
we plan to release more...maybe bad since we fill the blog with minor
releases...

something more?

Thought?




2018-02-13 10:03 GMT+01:00 Carlos Rovira :

> Hi Alex, that's so cool, that means that you have almost automated the
> process of a new royale release and that will make it very easy to do ?
> If is that I think that's a great work since releasing easily seems we can
> make lots of releases a make this project be more alive than ever
> thanks!
>
> 2018-02-13 7:11 GMT+01:00 Alex Harui :
>
>> OK, I fixed up and ran the releasecandidate script and it says it posted
>> the bits to npm.
>>
>> I believe all branches are merged and appropriately versioned.  On to the
>> next release!
>>
>> -Alex
>>
>> On 2/12/18, 12:29 PM, "omup...@gmail.com on behalf of OmPrakash
>> Muppirala"
>>  wrote:
>>
>> >On Mon, Feb 12, 2018 at 12:22 PM, Alex Harui 
>> >wrote:
>> >
>> >> The steps that publish NPM are in releasecandidate.xml.  It does not
>> >>muck
>> >> with the packages.  It looked like your change was to the package.json
>> >> that is already in the package.
>> >>
>> >
>> >Yes that is correct.  When publishing, the publish script uses the raw
>> >package.json file.
>> >Look here:
>> >https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fgithub.co
>> >m%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.1%2Fnpm%
>> 2Frelease-scripts%
>> >2Fpublish.js%23L66=02%7C01%7Caharui%40adobe.com%7Ca8ef
>> 5cf25db649d00e0
>> >d08d572575efa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636540641940569
>> >827=a0mEtMg9H7fAujqGHKKowVFFKtA0SDwPuEaAUoLyFrg%3D=0
>> >
>> >So, all you need to do is keep the tarball as is, but get my latest
>> >changes
>> >on release/0.9.1 before publishing to npm.
>> >
>> >Please try that and let me know how it goes.
>> >
>> >If this does not fix the issue, the next release should.  But lets give
>> >this a shot, at least.
>> >
>> >Thanks,
>> >Om
>> >
>> >
>> >>
>> >> -Alex
>> >>
>> >> On 2/12/18, 12:08 PM, "omup...@gmail.com on behalf of OmPrakash
>> >>Muppirala"
>> >>  wrote:
>> >>
>> >> >On Feb 12, 2018 11:58 AM, "Alex Harui" 
>> >>wrote:
>> >> >
>> >> >
>> >> >
>> >> >On 2/12/18, 10:42 AM, "omup...@gmail.com on behalf of OmPrakash
>> >> Muppirala"
>> >> > wrote:
>> >> >
>> >> >>On Feb 12, 2018 10:13 AM, "Alex Harui" 
>> >>wrote:
>> >> >>
>> >> >>AIUI, js-swf did not work via NPM as generated from the source
>> >>package.
>> >> >>I
>> >> >>thought you tweaked it before publishing.
>> >> >>
>> >> >>Am I wrong about that?
>> >> >>
>> >> >>
>> >> >>That is correct.   Are you planning on doing the same this time?
>> >> >
>> >> >I'm thinking of publishing the js-swf package as-is and see if anybody
>> >> >complains.  If you want to do whatever you did last time, that's ok
>> >>with
>> >> >me.  My goal is to spend the least amount of time possible being an RM
>> >>and
>> >> >create new features and fixes so even more folks will want to grab the
>> >> >next release after this one.  I'm ok with rough edges as long as we
>> >> >incrementally make things better.
>> >> >
>> >> >
>> >> >Instead you could pull my last commit and then run my npm publish
>> >>script.
>> >> >That will overwrite the one that is in the tarball during the publish
>> >> >process.
>> >> >
>> >> >I want to take this opportunity to make sure the npm publish script
>> >>works
>> >> >seamlessly for release managers as well.
>> >> >
>> >> >Thanks,
>> >> >Om
>> >> >
>> >> >
>> >> >
>> >> >-Alex
>> >> >
>> >> >
>> >> >>
>> >> >>On 2/12/18, 10:10 AM, "omup...@gmail.com on behalf of OmPrakash
>> >> >>Muppirala"
>> >> >> wrote:
>> >> >>
>> >> >>>On Feb 12, 2018 8:24 AM, "Alex Harui" 
>> >>wrote:
>> >> >>>
>> >> >>>Voters,
>> >> >>>
>> >> >>>Apparently some of you have not quite bought into the new philosophy
>> >>of
>> >> >>>"better than last release and not illegal".
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>The npm install that worked in the last release will be broken by
>> >>this
>> >> >>>new
>> >> >>>release.  Please explain how this is better than last release?
>> >> >>>
>> >> >>>Thanks,
>> >> >>>Om
>> >> >>>
>> >> >>>
>> >> >>>The cost of a new RC is
>> >> >>>non-trivial.  We have some users who are asking for help to port
>> 

Re: Royale Examples Blog proposal to all the team

[Piotr Zarzycki]

Hi Carlos,

I like the idea. I think I will join to the effort with something. :)

Thanks, Piotr

2018-02-13 10:44 GMT+01:00 Carlos Rovira :

> Hi just let you know yesterday I make final touched to "Hello World" blog
> post example (it had already flexjs namespace refs)
> and make it live in twitter and facebook.
>
> This is the first of our blog post that shows easy tips to show how easy is
> to make things in Royale
>
> I'd like to read thoughts from others in the team. What do you think about
> this effort, Alex, Peter, Harbs, Erik, Olaf,... will you participate in it?
>
> it's only 1 tiny blog post each 6 months. I think is affordable for any of
> us...
>
> ...and make us to be of social networks each two weeks, (a part from other
> appearances about releases, articles, and other things we want to promote)
>
> Thanks!
>
> Carlos
>
>
>
> 2018-02-09 13:19 GMT+01:00 Andrew Wetmore :
>
> > I see the calendar!
> >
> > On Fri, Feb 9, 2018 at 5:04 AM, Carlos Rovira 
> > wrote:
> >
> > > Hi Just created the shared calendar and send invitations
> > >
> > > please let me know if you received yours. As well, I created events
> with
> > > each name on Mondays each 2 weeks.
> > >
> > > We can start this Monday with the already posted "Hello World in
> Royale"
> > > and share it vía twitter and facebook.
> > >
> > > Please review the calendar and take into account that as we are a huge
> > team
> > > we have lots of time to make this real.
> > >
> > > If anyone doesn't like the idea or don't want to participate, let us
> know
> > > to make the calendar adjustments
> > >
> > > thanks!
> > >
> > > Carlos
> > >
> > >
> > >
> > >
> > >
> > > 2018-02-09 9:47 GMT+01:00 Carlos Rovira :
> > >
> > > > Great Om!,
> > > >
> > > > we can create the post as drafts and a shared calendar. As people
> ends
> > > his
> > > > post, we can schedule for the right day of publication (2 weeks per
> > > post).
> > > >
> > > > I'll be creating a calendar and sharing with you all.
> > > >
> > > > Anyone out there that wants to share something like this can join
> this
> > > > thread and talk about it. I think we don't want to close this effort
> > only
> > > > to royale team members
> > > >
> > > > thanks!
> > > >
> > > >
> > > >
> > > > 2018-02-09 4:29 GMT+01:00 OmPrakash Muppirala  >:
> > > >
> > > >> Great idea, Carlos.
> > > >>
> > > >> Here is one I volunteer to write about: Getting started with Royale
> on
> > > npm
> > > >>
> > > >> I will write this over the weekend and share it here.  We can post
> > after
> > > >> Andrew (and others) makes a sweep over it :-)
> > > >>
> > > >> Thanks,
> > > >> Om
> > > >>
> > > >> On Thu, Feb 8, 2018 at 3:25 AM, Andrew Wetmore  >
> > > >> wrote:
> > > >>
> > > >> > This sounds really good. I will be glad to help people who have
> > strong
> > > >> > Royale skills but are uncomfortable writing for publication in
> > > English.
> > > >> >
> > > >> > a
> > > >> >
> > > >> > On Thu, Feb 8, 2018 at 7:11 AM, Carlos Rovira <
> > > carlosrov...@apache.org>
> > > >> > wrote:
> > > >> >
> > > >> > > Hi,
> > > >> > >
> > > >> > > I want to propose to start introducing some "pearls" (beads? ;))
> > of
> > > >> quick
> > > >> > > knowledge about Royale in our blog (Peter de Haan's flex
> examples
> > > blog
> > > >> > > style, remember it?)
> > > >> > >
> > > >> > > *This will make the effect that each post will be published in
> > > >> Facebook
> > > >> > and
> > > >> > > Twitter and will make us to be "on the air" and reach more
> people
> > > that
> > > >> > > would eventually join us. Is not only about make it easy to
> learn
> > > >> Royale,
> > > >> > > but to make people out there know us!)*
> > > >> > >
> > > >> > > To make this happen I propose to publish one tiny example each 2
> > > >> weeks,
> > > >> > and
> > > >> > > each time from a different team member.
> > > >> > >
> > > >> > > Since we are around 10-15 people supporting this project, we can
> > > make
> > > >> > > calendar with publish dates, so we all know when we must
> publish.
> > > >> > >
> > > >> > > In this way each one will be publishing each 6 month (approx.),
> > and
> > > I
> > > >> > think
> > > >> > > this is very affordable for all of us
> > > >> > >
> > > >> > > what do you think?
> > > >> > >
> > > >> > > (btw, we can introduce the content in WP and schedule for
> > > publication
> > > >> the
> > > >> > > day and hour we want, and then make it live royal.a.o)
> > > >> > >
> > > >> > > --
> > > >> > > Carlos Rovira
> > > >> > > http://about.me/carlosrovira
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Andrew Wetmore
> > > >> >
> > > >> > http://cottage14.blogspot.com/
> > > >> >
> > > >>
> > > >> --
> > > >> Carlos Rovira
> > > >> http://about.me/carlosrovira
> > > >>
> > > >>
> > > >>
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> 

Re: Royale Examples Blog proposal to all the team

[Gabe Harbs]

Do you have a link?

> On Feb 13, 2018, at 11:44 AM, Carlos Rovira  wrote:
> 
> Hi just let you know yesterday I make final touched to "Hello World" blog
> post example (it had already flexjs namespace refs)
> and make it live in twitter and facebook.
> 
> This is the first of our blog post that shows easy tips to show how easy is
> to make things in Royale
> 
> I'd like to read thoughts from others in the team. What do you think about
> this effort, Alex, Peter, Harbs, Erik, Olaf,... will you participate in it?
> 
> it's only 1 tiny blog post each 6 months. I think is affordable for any of
> us...
> 
> ...and make us to be of social networks each two weeks, (a part from other
> appearances about releases, articles, and other things we want to promote)
> 
> Thanks!
> 
> Carlos
> 
> 
> 
> 2018-02-09 13:19 GMT+01:00 Andrew Wetmore :
> 
>> I see the calendar!
>> 
>> On Fri, Feb 9, 2018 at 5:04 AM, Carlos Rovira 
>> wrote:
>> 
>>> Hi Just created the shared calendar and send invitations
>>> 
>>> please let me know if you received yours. As well, I created events with
>>> each name on Mondays each 2 weeks.
>>> 
>>> We can start this Monday with the already posted "Hello World in Royale"
>>> and share it vía twitter and facebook.
>>> 
>>> Please review the calendar and take into account that as we are a huge
>> team
>>> we have lots of time to make this real.
>>> 
>>> If anyone doesn't like the idea or don't want to participate, let us know
>>> to make the calendar adjustments
>>> 
>>> thanks!
>>> 
>>> Carlos
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 2018-02-09 9:47 GMT+01:00 Carlos Rovira :
>>> 
 Great Om!,
 
 we can create the post as drafts and a shared calendar. As people ends
>>> his
 post, we can schedule for the right day of publication (2 weeks per
>>> post).
 
 I'll be creating a calendar and sharing with you all.
 
 Anyone out there that wants to share something like this can join this
 thread and talk about it. I think we don't want to close this effort
>> only
 to royale team members
 
 thanks!
 
 
 
 2018-02-09 4:29 GMT+01:00 OmPrakash Muppirala :
 
> Great idea, Carlos.
> 
> Here is one I volunteer to write about: Getting started with Royale on
>>> npm
> 
> I will write this over the weekend and share it here.  We can post
>> after
> Andrew (and others) makes a sweep over it :-)
> 
> Thanks,
> Om
> 
> On Thu, Feb 8, 2018 at 3:25 AM, Andrew Wetmore 
> wrote:
> 
>> This sounds really good. I will be glad to help people who have
>> strong
>> Royale skills but are uncomfortable writing for publication in
>>> English.
>> 
>> a
>> 
>> On Thu, Feb 8, 2018 at 7:11 AM, Carlos Rovira <
>>> carlosrov...@apache.org>
>> wrote:
>> 
>>> Hi,
>>> 
>>> I want to propose to start introducing some "pearls" (beads? ;))
>> of
> quick
>>> knowledge about Royale in our blog (Peter de Haan's flex examples
>>> blog
>>> style, remember it?)
>>> 
>>> *This will make the effect that each post will be published in
> Facebook
>> and
>>> Twitter and will make us to be "on the air" and reach more people
>>> that
>>> would eventually join us. Is not only about make it easy to learn
> Royale,
>>> but to make people out there know us!)*
>>> 
>>> To make this happen I propose to publish one tiny example each 2
> weeks,
>> and
>>> each time from a different team member.
>>> 
>>> Since we are around 10-15 people supporting this project, we can
>>> make
>>> calendar with publish dates, so we all know when we must publish.
>>> 
>>> In this way each one will be publishing each 6 month (approx.),
>> and
>>> I
>> think
>>> this is very affordable for all of us
>>> 
>>> what do you think?
>>> 
>>> (btw, we can introduce the content in WP and schedule for
>>> publication
> the
>>> day and hour we want, and then make it live royal.a.o)
>>> 
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>> 
>> 
>> 
>> 
>> --
>> Andrew Wetmore
>> 
>> http://cottage14.blogspot.com/
>> 
> 
> --
> Carlos Rovira
> http://about.me/carlosrovira
> 
> 
> 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>> 
>> 
>> 
>> 
>> --
>> Andrew Wetmore
>> 
>> http://cottage14.blogspot.com/
>> 
> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Carlos Rovira]

Hi Alex, that's so cool, that means that you have almost automated the
process of a new royale release and that will make it very easy to do ?
If is that I think that's a great work since releasing easily seems we can
make lots of releases a make this project be more alive than ever
thanks!

2018-02-13 7:11 GMT+01:00 Alex Harui :

> OK, I fixed up and ran the releasecandidate script and it says it posted
> the bits to npm.
>
> I believe all branches are merged and appropriately versioned.  On to the
> next release!
>
> -Alex
>
> On 2/12/18, 12:29 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
>  wrote:
>
> >On Mon, Feb 12, 2018 at 12:22 PM, Alex Harui 
> >wrote:
> >
> >> The steps that publish NPM are in releasecandidate.xml.  It does not
> >>muck
> >> with the packages.  It looked like your change was to the package.json
> >> that is already in the package.
> >>
> >
> >Yes that is correct.  When publishing, the publish script uses the raw
> >package.json file.
> >Look here:
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.co
> >m%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.1%
> 2Fnpm%2Frelease-scripts%
> >2Fpublish.js%23L66=02%7C01%7Caharui%40adobe.com%
> 7Ca8ef5cf25db649d00e0
> >d08d572575efa%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636540641940569
> >827=a0mEtMg9H7fAujqGHKKowVFFKtA0SDwPuEaAUoLyFrg%3D=0
> >
> >So, all you need to do is keep the tarball as is, but get my latest
> >changes
> >on release/0.9.1 before publishing to npm.
> >
> >Please try that and let me know how it goes.
> >
> >If this does not fix the issue, the next release should.  But lets give
> >this a shot, at least.
> >
> >Thanks,
> >Om
> >
> >
> >>
> >> -Alex
> >>
> >> On 2/12/18, 12:08 PM, "omup...@gmail.com on behalf of OmPrakash
> >>Muppirala"
> >>  wrote:
> >>
> >> >On Feb 12, 2018 11:58 AM, "Alex Harui" 
> >>wrote:
> >> >
> >> >
> >> >
> >> >On 2/12/18, 10:42 AM, "omup...@gmail.com on behalf of OmPrakash
> >> Muppirala"
> >> > wrote:
> >> >
> >> >>On Feb 12, 2018 10:13 AM, "Alex Harui" 
> >>wrote:
> >> >>
> >> >>AIUI, js-swf did not work via NPM as generated from the source
> >>package.
> >> >>I
> >> >>thought you tweaked it before publishing.
> >> >>
> >> >>Am I wrong about that?
> >> >>
> >> >>
> >> >>That is correct.   Are you planning on doing the same this time?
> >> >
> >> >I'm thinking of publishing the js-swf package as-is and see if anybody
> >> >complains.  If you want to do whatever you did last time, that's ok
> >>with
> >> >me.  My goal is to spend the least amount of time possible being an RM
> >>and
> >> >create new features and fixes so even more folks will want to grab the
> >> >next release after this one.  I'm ok with rough edges as long as we
> >> >incrementally make things better.
> >> >
> >> >
> >> >Instead you could pull my last commit and then run my npm publish
> >>script.
> >> >That will overwrite the one that is in the tarball during the publish
> >> >process.
> >> >
> >> >I want to take this opportunity to make sure the npm publish script
> >>works
> >> >seamlessly for release managers as well.
> >> >
> >> >Thanks,
> >> >Om
> >> >
> >> >
> >> >
> >> >-Alex
> >> >
> >> >
> >> >>
> >> >>On 2/12/18, 10:10 AM, "omup...@gmail.com on behalf of OmPrakash
> >> >>Muppirala"
> >> >> wrote:
> >> >>
> >> >>>On Feb 12, 2018 8:24 AM, "Alex Harui" 
> >>wrote:
> >> >>>
> >> >>>Voters,
> >> >>>
> >> >>>Apparently some of you have not quite bought into the new philosophy
> >>of
> >> >>>"better than last release and not illegal".
> >> >>>
> >> >>>
> >> >>>
> >> >>>The npm install that worked in the last release will be broken by
> >>this
> >> >>>new
> >> >>>release.  Please explain how this is better than last release?
> >> >>>
> >> >>>Thanks,
> >> >>>Om
> >> >>>
> >> >>>
> >> >>>The cost of a new RC is
> >> >>>non-trivial.  We have some users who are asking for help to port
> >>their
> >> >>>apps against a deadline.  To me, that is way more important than
> >>fixing
> >> >>>js-swf for NPM in this release because js-swf was broken in the prior
> >> >>>release.  This release is "better than the last release and not
> >> >>>illegal".
> >> >>>The next release is will be in 30 days or less.
> >> >>>
> >> >>>Someone hand-patched package.json and provided it on npm in the last
> >> >>>release.  It can probably be done for this release.  I'll bet there
> >>will
> >> >>>be a big bug in every release for a while.  As long as it isn't a
> >>major
> >> >>>regression, we should ship it and move on.
> >> >>>
> >> >>>My 2 cents,
> >> >>>-Alex
> >> >>>
> >> >>>On 2/12/18, 1:50 AM, "Gabe Harbs"  wrote:
> >> >>>
> >> BTW, I 

Re: ASDoc, Routing, Releases

[Carlos Rovira]

Hi Alex,

I tried the link royale.apache.org/asdoc but it doesn't work. Is that link
right?
For versions I think ASDocs has sense if we all focus in create right
ASDoc. I'm trying to do it with Vivid, and did with MDL times. This is
important and makes us to take care of the code we make. The code is not
ready after we make it, is ready  when we try to think far beyond of what
it does and what people needs from it in terms of documentation, ease of
use, ...
So if we all create good ASDoc, I think is ok to release with each release.
With time, and more releases, people will want to check ASDoc from specific
version.
I think we will need to store that versions so people could check it, and
will be easily discovered by url.
For example: http://royale.apache.org/asdoc/0.9.0/...



2018-02-13 9:47 GMT+01:00 Piotr Zarzycki :

> I think simplicity is the key here. Pushing after release ASDoc - I like
> the idea. The filtering could also appear, but I would still stay with
> pushing after every release instead all the time.
>
> Thanks,
> Piotr
>
> 2018-02-13 9:32 GMT+01:00 Alex Harui :
>
> > Filtering by version is certainly possible, but would require that we are
> > diligent about specifying the correct version when entering data.
> >
> > -Alex
> >
> > On 2/12/18, 11:53 PM, "Gabe Harbs"  wrote:
> >
> > >Yes. Having it as part of the release process makes sense.
> > >
> > >Another way to go about it would be to have some way to limit which
> > >version data is displayed, so if unreleased data is set to display, it
> > >would show up, but by default the ASDoc app would only show data that is
> > >relevant to the latest release.
> > >
> > >> On Feb 13, 2018, at 9:43 AM, Alex Harui 
> > >>wrote:
> > >>
> > >> I pushed an Ant script that copies ASDoc from the CI server and copies
> > >>it
> > >> to the asdoc folder on the site.
> > >> I also pushed the ASDoc.
> > >>
> > >> I was going to hook this up to a CI build but am having second
> thoughts.
> > >> Maybe we should only update after a release.  Otherwise, folks may
> find
> > >> stuff in ASDoc that is only in the nightly and hasn't been released.
> > >>
> > >> Thoughts?
> > >> -Alex
> > >>
> > >> On 2/6/18, 12:38 AM, "carlos.rov...@gmail.com
> > >> on behalf of Carlos Rovira"
> > >>  on behalf
> of
> > >>carlosrov...@apache.org > wrote:
> > >>
> > >>> Hi Alex,
> > >>>
> > >>> in fact I think that's what it should be :)
> > >>> don't know if as part of the website or in the royale-docs live url.
> > >>> Anyway the proposed url is ok.
> > >>>
> > >>> When I updated the website I overlay the folder with changes, as in
> the
> > >>> website there's no "/asdoc/" url it will be untouched by my changes
> > >>>
> > >>> thanks
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> 2018-02-06 6:29 GMT+01:00 Alex Harui :
> > >>>
> >  ASDoc is looking better.  I was looking into tools to understand how
> >  google crawls sites and found that I can't use them on Jenkins.  I
> > also
> >  saw in another thread that there is a way to get ASF Jenkins to push
> >  changes to a gitpubsub site.  Also, the ASDoc URL is long and ugly.
> > 
> >  So, I'm thinking we should create a Jenkins job to copy ASDoc to
> >  royale.a.o.  Does anybody have any reason we shouldn't publish ASDoc
> > on
> >  royale.a.o?  Also, what folder should we use?  royale.a.o/asdoc/?
> > 
> >  Thoughts?
> >  -Alex
> > 
> >  On 2/5/18, 9:44 AM, "Gabe Harbs"  wrote:
> > 
> > >> What did you clean out?
> > >
> > > Everything.
> > >
> > > I deleted the entire contents of the three repo folders except the
> > >.git
> > > folder.
> > >
> > > I then stashed my local “changes" and pulled develop to bring my
> repo
> > > into a clean up-to-date state.
> > >
> > > I’m not sure what the problem was.
> > >
> > > Harbs
> > >
> > >> On Feb 5, 2018, at 7:37 PM, Alex Harui 
> >  wrote:
> > >>
> > >> What did you clean out?  It might help others if you update the
> >  scripts
> > >> to
> > >> clean up better.  I thought it was working correctly.
> > >>
> > >> When things get renamed, the scripts don't always clean out the
> old
> > >> folders.
> > >>
> > >> -Alex
> > >>
> > >> On 2/5/18, 9:29 AM, "Gabe Harbs"  > >> > wrote:
> > >>
> > >>> I manually cleaned out my repo folders, pulled again and now it
> >  seems
> > >>> to
> > >>> be working.
> > >>>
> > >>> It looks like ant wipe-all on the compiler and ant clean all on
> >  asjs,
> > >>> doesn’t quite clean 

Re: ASDoc, Routing, Releases

[Piotr Zarzycki]

I think simplicity is the key here. Pushing after release ASDoc - I like
the idea. The filtering could also appear, but I would still stay with
pushing after every release instead all the time.

Thanks,
Piotr

2018-02-13 9:32 GMT+01:00 Alex Harui :

> Filtering by version is certainly possible, but would require that we are
> diligent about specifying the correct version when entering data.
>
> -Alex
>
> On 2/12/18, 11:53 PM, "Gabe Harbs"  wrote:
>
> >Yes. Having it as part of the release process makes sense.
> >
> >Another way to go about it would be to have some way to limit which
> >version data is displayed, so if unreleased data is set to display, it
> >would show up, but by default the ASDoc app would only show data that is
> >relevant to the latest release.
> >
> >> On Feb 13, 2018, at 9:43 AM, Alex Harui 
> >>wrote:
> >>
> >> I pushed an Ant script that copies ASDoc from the CI server and copies
> >>it
> >> to the asdoc folder on the site.
> >> I also pushed the ASDoc.
> >>
> >> I was going to hook this up to a CI build but am having second thoughts.
> >> Maybe we should only update after a release.  Otherwise, folks may find
> >> stuff in ASDoc that is only in the nightly and hasn't been released.
> >>
> >> Thoughts?
> >> -Alex
> >>
> >> On 2/6/18, 12:38 AM, "carlos.rov...@gmail.com
> >> on behalf of Carlos Rovira"
> >>  on behalf of
> >>carlosrov...@apache.org > wrote:
> >>
> >>> Hi Alex,
> >>>
> >>> in fact I think that's what it should be :)
> >>> don't know if as part of the website or in the royale-docs live url.
> >>> Anyway the proposed url is ok.
> >>>
> >>> When I updated the website I overlay the folder with changes, as in the
> >>> website there's no "/asdoc/" url it will be untouched by my changes
> >>>
> >>> thanks
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> 2018-02-06 6:29 GMT+01:00 Alex Harui :
> >>>
>  ASDoc is looking better.  I was looking into tools to understand how
>  google crawls sites and found that I can't use them on Jenkins.  I
> also
>  saw in another thread that there is a way to get ASF Jenkins to push
>  changes to a gitpubsub site.  Also, the ASDoc URL is long and ugly.
> 
>  So, I'm thinking we should create a Jenkins job to copy ASDoc to
>  royale.a.o.  Does anybody have any reason we shouldn't publish ASDoc
> on
>  royale.a.o?  Also, what folder should we use?  royale.a.o/asdoc/?
> 
>  Thoughts?
>  -Alex
> 
>  On 2/5/18, 9:44 AM, "Gabe Harbs"  wrote:
> 
> >> What did you clean out?
> >
> > Everything.
> >
> > I deleted the entire contents of the three repo folders except the
> >.git
> > folder.
> >
> > I then stashed my local “changes" and pulled develop to bring my repo
> > into a clean up-to-date state.
> >
> > I’m not sure what the problem was.
> >
> > Harbs
> >
> >> On Feb 5, 2018, at 7:37 PM, Alex Harui 
>  wrote:
> >>
> >> What did you clean out?  It might help others if you update the
>  scripts
> >> to
> >> clean up better.  I thought it was working correctly.
> >>
> >> When things get renamed, the scripts don't always clean out the old
> >> folders.
> >>
> >> -Alex
> >>
> >> On 2/5/18, 9:29 AM, "Gabe Harbs"  >> > wrote:
> >>
> >>> I manually cleaned out my repo folders, pulled again and now it
>  seems
> >>> to
> >>> be working.
> >>>
> >>> It looks like ant wipe-all on the compiler and ant clean all on
>  asjs,
> >>> doesn’t quite clean everything…
> >>>
>  On Feb 5, 2018, at 7:13 PM, Gabe Harbs 
>  wrote:
> 
>  It looks like I needed to set some env vars.
> 
>  I did so, and I’m getting some JSON files, but not the full thing.
> 
>  I just updated my repos and did ant clean all. I’m now getting a
>  failed
>  build of Royale and I’m not sure why...
> 
>  royale.royaletasks.jar:
> 
>  jar:
> 
>  main:
> 
>  main:
> 
>  download:
> [echo] /Apache/royale-asjs
>    [unjar] Expanding:
>  /Apache/royale-asjs/js/lib/google/closure-compiler/compiler.jar
>  into
>  /Apache/royale-typedefs/js/target/temp/externs
>    [unzip] Expanding:
>  /Apache/royale-typedefs/js/target/temp/externs/externs.zip into
>  /Apache/royale-typedefs/js/target/downloads
>  [get] Getting:
> 
>  https://na01.safelinks.protection.outlook.com/?url=
>  https%3A%2F%2Fstorag
> 

Re: ASDoc, Routing, Releases

[Alex Harui]

Filtering by version is certainly possible, but would require that we are
diligent about specifying the correct version when entering data.

-Alex

On 2/12/18, 11:53 PM, "Gabe Harbs"  wrote:

>Yes. Having it as part of the release process makes sense.
>
>Another way to go about it would be to have some way to limit which
>version data is displayed, so if unreleased data is set to display, it
>would show up, but by default the ASDoc app would only show data that is
>relevant to the latest release.
>
>> On Feb 13, 2018, at 9:43 AM, Alex Harui 
>>wrote:
>> 
>> I pushed an Ant script that copies ASDoc from the CI server and copies
>>it
>> to the asdoc folder on the site.
>> I also pushed the ASDoc.
>> 
>> I was going to hook this up to a CI build but am having second thoughts.
>> Maybe we should only update after a release.  Otherwise, folks may find
>> stuff in ASDoc that is only in the nightly and hasn't been released.
>> 
>> Thoughts?
>> -Alex
>> 
>> On 2/6/18, 12:38 AM, "carlos.rov...@gmail.com
>> on behalf of Carlos Rovira"
>>  on behalf of
>>carlosrov...@apache.org > wrote:
>> 
>>> Hi Alex,
>>> 
>>> in fact I think that's what it should be :)
>>> don't know if as part of the website or in the royale-docs live url.
>>> Anyway the proposed url is ok.
>>> 
>>> When I updated the website I overlay the folder with changes, as in the
>>> website there's no "/asdoc/" url it will be untouched by my changes
>>> 
>>> thanks
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 2018-02-06 6:29 GMT+01:00 Alex Harui :
>>> 
 ASDoc is looking better.  I was looking into tools to understand how
 google crawls sites and found that I can't use them on Jenkins.  I
also
 saw in another thread that there is a way to get ASF Jenkins to push
 changes to a gitpubsub site.  Also, the ASDoc URL is long and ugly.
 
 So, I'm thinking we should create a Jenkins job to copy ASDoc to
 royale.a.o.  Does anybody have any reason we shouldn't publish ASDoc
on
 royale.a.o?  Also, what folder should we use?  royale.a.o/asdoc/?
 
 Thoughts?
 -Alex
 
 On 2/5/18, 9:44 AM, "Gabe Harbs"  wrote:
 
>> What did you clean out?
> 
> Everything.
> 
> I deleted the entire contents of the three repo folders except the
>.git
> folder.
> 
> I then stashed my local “changes" and pulled develop to bring my repo
> into a clean up-to-date state.
> 
> I’m not sure what the problem was.
> 
> Harbs
> 
>> On Feb 5, 2018, at 7:37 PM, Alex Harui 
 wrote:
>> 
>> What did you clean out?  It might help others if you update the
 scripts
>> to
>> clean up better.  I thought it was working correctly.
>> 
>> When things get renamed, the scripts don't always clean out the old
>> folders.
>> 
>> -Alex
>> 
>> On 2/5/18, 9:29 AM, "Gabe Harbs" > > wrote:
>> 
>>> I manually cleaned out my repo folders, pulled again and now it
 seems
>>> to
>>> be working.
>>> 
>>> It looks like ant wipe-all on the compiler and ant clean all on
 asjs,
>>> doesn’t quite clean everything…
>>> 
 On Feb 5, 2018, at 7:13 PM, Gabe Harbs 
 wrote:
 
 It looks like I needed to set some env vars.
 
 I did so, and I’m getting some JSON files, but not the full thing.
 
 I just updated my repos and did ant clean all. I’m now getting a
 failed
 build of Royale and I’m not sure why...
 
 royale.royaletasks.jar:
 
 jar:
 
 main:
 
 main:
 
 download:
[echo] /Apache/royale-asjs
   [unjar] Expanding:
 /Apache/royale-asjs/js/lib/google/closure-compiler/compiler.jar
 into
 /Apache/royale-typedefs/js/target/temp/externs
   [unzip] Expanding:
 /Apache/royale-typedefs/js/target/temp/externs/externs.zip into
 /Apache/royale-typedefs/js/target/downloads
 [get] Getting:
 
 https://na01.safelinks.protection.outlook.com/?url=
 https%3A%2F%2Fstorag
 e
 .
 googleapis.com
 
%
 2Fg
 

Re: ASDoc, Routing, Releases

[Gabe Harbs]

Yes. Having it as part of the release process makes sense.

Another way to go about it would be to have some way to limit which version 
data is displayed, so if unreleased data is set to display, it would show up, 
but by default the ASDoc app would only show data that is relevant to the 
latest release.

> On Feb 13, 2018, at 9:43 AM, Alex Harui  wrote:
> 
> I pushed an Ant script that copies ASDoc from the CI server and copies it
> to the asdoc folder on the site.
> I also pushed the ASDoc.
> 
> I was going to hook this up to a CI build but am having second thoughts.
> Maybe we should only update after a release.  Otherwise, folks may find
> stuff in ASDoc that is only in the nightly and hasn't been released.
> 
> Thoughts?
> -Alex
> 
> On 2/6/18, 12:38 AM, "carlos.rov...@gmail.com 
>  on behalf of Carlos Rovira"
>  on behalf of 
> carlosrov...@apache.org > wrote:
> 
>> Hi Alex,
>> 
>> in fact I think that's what it should be :)
>> don't know if as part of the website or in the royale-docs live url.
>> Anyway the proposed url is ok.
>> 
>> When I updated the website I overlay the folder with changes, as in the
>> website there's no "/asdoc/" url it will be untouched by my changes
>> 
>> thanks
>> 
>> 
>> 
>> 
>> 
>> 
>> 2018-02-06 6:29 GMT+01:00 Alex Harui :
>> 
>>> ASDoc is looking better.  I was looking into tools to understand how
>>> google crawls sites and found that I can't use them on Jenkins.  I also
>>> saw in another thread that there is a way to get ASF Jenkins to push
>>> changes to a gitpubsub site.  Also, the ASDoc URL is long and ugly.
>>> 
>>> So, I'm thinking we should create a Jenkins job to copy ASDoc to
>>> royale.a.o.  Does anybody have any reason we shouldn't publish ASDoc on
>>> royale.a.o?  Also, what folder should we use?  royale.a.o/asdoc/?
>>> 
>>> Thoughts?
>>> -Alex
>>> 
>>> On 2/5/18, 9:44 AM, "Gabe Harbs"  wrote:
>>> 
> What did you clean out?
 
 Everything.
 
 I deleted the entire contents of the three repo folders except the .git
 folder.
 
 I then stashed my local “changes" and pulled develop to bring my repo
 into a clean up-to-date state.
 
 I’m not sure what the problem was.
 
 Harbs
 
> On Feb 5, 2018, at 7:37 PM, Alex Harui 
>>> wrote:
> 
> What did you clean out?  It might help others if you update the
>>> scripts
> to
> clean up better.  I thought it was working correctly.
> 
> When things get renamed, the scripts don't always clean out the old
> folders.
> 
> -Alex
> 
> On 2/5/18, 9:29 AM, "Gabe Harbs"  > wrote:
> 
>> I manually cleaned out my repo folders, pulled again and now it
>>> seems
>> to
>> be working.
>> 
>> It looks like ant wipe-all on the compiler and ant clean all on
>>> asjs,
>> doesn’t quite clean everything…
>> 
>>> On Feb 5, 2018, at 7:13 PM, Gabe Harbs 
>>> wrote:
>>> 
>>> It looks like I needed to set some env vars.
>>> 
>>> I did so, and I’m getting some JSON files, but not the full thing.
>>> 
>>> I just updated my repos and did ant clean all. I’m now getting a
>>> failed
>>> build of Royale and I’m not sure why...
>>> 
>>> royale.royaletasks.jar:
>>> 
>>> jar:
>>> 
>>> main:
>>> 
>>> main:
>>> 
>>> download:
>>>[echo] /Apache/royale-asjs
>>>   [unjar] Expanding:
>>> /Apache/royale-asjs/js/lib/google/closure-compiler/compiler.jar
>>> into
>>> /Apache/royale-typedefs/js/target/temp/externs
>>>   [unzip] Expanding:
>>> /Apache/royale-typedefs/js/target/temp/externs/externs.zip into
>>> /Apache/royale-typedefs/js/target/downloads
>>> [get] Getting:
>>> 
>>> https://na01.safelinks.protection.outlook.com/?url=
>>> https%3A%2F%2Fstorag
>>> e
>>> >> https%3A%2F%2Fstora
>>> ge>.
>>> googleapis.com
>>> >> http%3A%2F%2Fgoogle
>>> apis.com%2F=02%7C01%7Caharui%40adobe.com%
>>> 7Cea3588c69d96467c165f08d
>>> 56cc01d3d%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%
>>> 7C6365344947393196
>>> 87=wz0mlDPXSNb9R9uIL55hVuaRVCE1Qsxa5EN5XZoF1K4%3D=0>%
>>> 2Fg
>>> oogle-code-archive-downloads%2Fv2%2Fcode.google.com
>>> >> http%3A%2F%2F2fcode
>>> .google.com%2F=02%7C01%7Caharui%40adobe.com%
>>> 7Cea3588c69d96467c165f
>>> 08d56cc01d3d%7C71f1da39c0a84d5a8d88a67b23c3
>>> 0bf4%7C0%7C0%7C6365344947393
>>> 19687=kkKyUtW7yWmIlI2YaMM2084mFatUbp
>>> lmnr6PBa26PDU%3D=0>%
>>> 2Fc
>>>