Build failed in Jenkins: royale-asjs #4

See Changes: -- [...truncated 1.35 MB...] [mxmlc] scanning for overrides: IApplicationView [mxmlc] scanning for overrides: IValuesImpl [mxmlc]

Build failed in Jenkins: royale-asjs #3

See Changes: -- [...truncated 1.35 MB...] [mxmlc] scanning for overrides: IApplicationView [mxmlc] scanning for overrides: IValuesImpl [mxmlc]

Build failed in Jenkins: royale-asjs #2

See Changes: -- [...truncated 1.34 MB...] [mxmlc] scanning for overrides: IApplicationView [mxmlc] scanning for overrides: IValuesImpl [mxmlc]

Build failed in Jenkins: royale-asjs #1

See Changes: -- [...truncated 145.79 KB...] create-config: [copy] Copying 1 file to

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

See

Build failed in Jenkins: royale-asjs_jsonly #3

See Changes: -- [...truncated 1.66 MB...] [java] public static var waitForExcludes:Boolean = false; [java] ^ [java] [java]

Build failed in Jenkins: royale-asjs_jsonly #2

pacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/projects/*/src/main/royale> clean: super-clean: [delete] Deleting directory <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Spark> create-descrip

Build failed in Jenkins: royale-asjs_jsonly #1

s2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output> [echo] compiler.source-path = <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/projects/*/src/main/royale> clean: super-clean: create-description: [echo] build.numbe

New apache-royale questions for Oct 8 - Stack Exchange

***2 new questions in [ApacheRoyale Tag Notifications filter]() on stackexchange.com*** [issue with material-icons : no picture icon on Apache

Re: Acceptance of Royale by Flex Developers

The migration page I linked to earlier attempts to help people get started with MXRoyale and SparkRoyale (by changing the namespaces). After that, the goal is for the components to work similar to the Flex components, so from an ASDoc standpoint, they “should” be able to use the Flex ASDoc and

maven fails on build royale-asjs 0.9.7-SNAPSHOT

Hi, just trying to build as usual, but now with new 0.9.7-SNAPSHOT when reach royale-asjs try to build with: mvn clean install -Pgenerate-swcs-for-swf,main -DskipTests and getting this error: https://paste.apache.org/kt8wi Maybe I miss some latest change? thanks -- Carlos Rovira

Re: Acceptance of Royale by Flex Developers

Hi I think we could remove one level or even two. Have at first level MIGRATE AN EXISTING APPLICATION (instead of inside CREATE AN APPLICATION ) then MIGRATE FROM FLEX

Re: Release 0.9.6 Announce for web post?

Hi website is updated. @Piotr Zarzycki do you want to share 0.9.6 in social media? or wait for announcement? thanks El mar., 8 oct. 2019 a las 20:03, Carlos Rovira () escribió: > Hi Andrew, > > if you don't mind I take into account for next release, since I'm this > days a bit out of time.

Re: Release 0.9.6 Announce for web post?

Hi Andrew, if you don't mind I take into account for next release, since I'm this days a bit out of time. Thanks for taking the review. I'll try to publish now Carlos El mar., 8 oct. 2019 a las 18:57, Andrew Wetmore () escribió: > I have edited the release. The only thing I would improve, if

Re: Release 0.9.6 Announce for web post?

I have edited the release. The only thing I would improve, if I could, is the graphic at the top. The release number appears as "v0.9.6". I am pretty sure it would be better as "v. 0.9.6", but this is obviously not something to delay the release for. Andrew On Tue, Oct 8, 2019 at 11:56 AM Andrew

Re: Acceptance of Royale by Flex Developers

I'm going to try to address all of Chris Velevitch's several threads from today in this response. We have a page on Migrating Flex Apps here: https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html But it is hard to find (took me several clicks

Re: Pay as You Go (PAYG) Suggestion

The compiler is theoretically designed to allow for different Emitters and Publishers that can output different JS to support other module and minification systems. Volunteers are welcome to work on those. However, the Strands and Beads idea is not about minification for Google Closure or

Re: Nightly Build Server going offline

I am definitely planning to start rebuilding the server today. Keep your fingers crossed. -Alex On 10/7/19, 8:47 AM, "Alex Harui" wrote: I think the merge happened, so I am going to try to do the rebuild this week, probably on my Tuesday if I can finish up some fixes to

Re: Pay as You Go (PAYG) Suggestion

It is worth mentioning that Royale uses Google's Closure compiler when creating release builds. Closure compiler does very advanced JavaScript code analysis that eliminates unused code from the final output, so it has a very similar effect to tree shaking. The ability to integrate into a webpack

Re: How to skin components

Hi Chris, before going far beyond, I want that you consider the way you are referring to the concepts you don't share. Talk about that as "silly" seems not very appropriate. We try to respect as much as possible, the work and proposals from others. You can disagree, but please maintain a level of

Re: Acceptance of Royale by Flex Developers

Hi, I mean that like RO, that's a non visual component used to perform communications, we have other "components" or "code" that can be implemented as beads or strands. The concept behind is that Royale have the minimum code needed for functionality, and compose other parts (whatever the purpose

Re: Component Sets

Hi Chris, although we get a much better docswith the work in the latest months, there's still many missing points to cover, some with its own reserved place, but still empty, and others will need to reserve its place. As always we'll try our best to cover it as soon as possible. To be fastest we

Re: Release 0.9.6 Announce for web post?

Got it! Thanks! On Tue, Oct 8, 2019 at 10:49 AM Carlos Rovira wrote: > Yes! that's it :) > > > El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki (< > piotrzarzyck...@gmail.com>) > escribió: > > > I think that would be the link: > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/ >

Re: Release 0.9.6 Announce for web post?

Yes! that's it :) El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki () escribió: > I think that would be the link: > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/ > > wt., 8 paź 2019 o 16:29 Andrew Wetmore napisał(a): > > > @Carlos Rovira where is the draft post? I had > a > >

Re: Release 0.9.6 Announce for web post?

I think that would be the link: https://royale.codeoscopic.com/apache-royale-v0-9-6-released/ wt., 8 paź 2019 o 16:29 Andrew Wetmore napisał(a): > @Carlos Rovira where is the draft post? I had a > hard disk failure this past weekend and am slowly rebuilding my system. > Have to find all my

Re: Release 0.9.6 Announce for web post?

@Carlos Rovira where is the draft post? I had a hard disk failure this past weekend and am slowly rebuilding my system. Have to find all my links again. a On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore wrote: > I can do this in a couple of hours > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira,

Re: Release 0.9.6 Announce for web post?

I can do this in a couple of hours On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, wrote: > Hi Piotr, > > I'll wait Andrew's review and then will publish it. If Andrew make his > changes this afternoon, I can follow up and publish it. > Then we can post on social networks next or wait to tomorrow >

Re: Release 0.9.6 Announce for web post?

Hi Piotr, I'll wait Andrew's review and then will publish it. If Andrew make his changes this afternoon, I can follow up and publish it. Then we can post on social networks next or wait to tomorrow El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki () escribió: > Just to make sure that you

Re: Release 0.9.6 Announce for web post?

Just to make sure that you understand why I asked you to post download links on website along with source code. I will announce on dev, users and announce list - someone who read email - will have two options: 1) Can click in that email on royale.apache.org 2) Can download directly binaries or

Re: Release 0.9.6 Announce for web post?

This is the goal of syncing everything tomorrow. I asked you to publish first link and source code on website, cause my announce probably go first one and I didn't want to mislead with what will be on website. However if you wanted to do that differently I'm fine - Couple of hours of misleading

Re: Release 0.9.6 Announce for web post?

Hi, ok, is normal, as people following our dev, are as well using links to 0.9.6 releases. The update of links in website is more about to announce to the rest of the world that is not as close to us as the rest of community. So it's important to communicate in the most organized way we can.

Re: Release 0.9.6 Announce for web post?

Just FYI: npm stuff and Maven artifacts are being published for couple of days already, so people are using released 0.9.6 trough npm. - It's happen automatically in case of npm. wt., 8 paź 2019 o 10:48 Piotr Zarzycki napisał(a): > Fine with me. I make announce tomorrow morning and review what

Re: Release 0.9.6 Announce for web post?

Fine with me. I make announce tomorrow morning and review what was your change and update Draft. wt., 8 paź 2019 o 10:46 Carlos Rovira napisał(a): > Hi, Piotr, > > I think we should update all at the same time, since we want to post in > twitter, Facebook and linkedin. > Doesn't have sense to

Re: Release 0.9.6 Announce for web post?

Hi, Piotr, I think we should update all at the same time, since we want to post in twitter, Facebook and linkedin. Doesn't have sense to me upload just a few links since almost nobody will notice it (and are already in GitHub releases). If we need to wait a day to send the official announcement

Re: Release 0.9.6 Announce for web post?

Download and source code websites looks good to me. In blog post you have broken github links - review them and fix. Apart of that publish only Download and Source code. Blog post should be publish after I think official announce on dev, users and announce mailing list. I'm going to do that

Re: Component Sets

There is not such a document yet, no. Help creating one would be welcome. On Tue, Oct 8, 2019 at 4:22 AM Chris Velevitch wrote: > There doesn't seem to be an all-encompassing document describing, MX, > Spark and Jewel components and as well as the pros and cons of each > nor is there a

Re: Release 0.9.6 Announce for web post?

Hi, Thanks Piotr, for the link :) I just updated website on pre site please take a quick look and I'll publish it: https://royale.codeoscopic.com/apache-royale-v0-9-6-released/ https://royale.codeoscopic.com/download/ https://royale.codeoscopic.com/source-code/ thanks El mar., 8 oct. 2019 a

Component Sets

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

Re: Acceptance of Royale by Flex Developers

So you are suggesting a RemoteObject is a headless component who's base class only supports the model and controller plugins and that UI classes extend the headless component to add in the view? On Tue, 8 Oct 2019 at 15:52, Carlos Rovira wrote: > > Hi Chris, > > thanks for sharing your thoughts.

Re: Release 0.9.6 Announce for web post?

Sorry it meant to be on dev. wt., 8 paź 2019 o 10:11 Piotr Zarzycki napisał(a): > Carlos, > > Here you have link to pony archive [1] and if you prefer nabble [2] > > [1] > https://lists.apache.org/thread.html/3eb43d9ad3796179965ce7e91bee1e6cf864bf17044db3c6201adcbd@%3Cdev.royale.apache.org%3E >

Re: Release 0.9.6 Announce for web post?

Hi, I'm updating all website in pre. I changed download and source code pages. I'm going to do the blog post, for this I need the Annoucment, but I can't see it in my mail client. @Piotr Zarzycki can you send me that email off list? I'm going to start from the 0.9.4 one in the meanwhile thanks

Pay as You Go (PAYG) Suggestion

If the whole point of PAYG is to eliminate unused code from being included in the final app distribution, then I'd like to suggest that we take advantage of the tools the JavaScript ecosystem already has for eliminating unused code. I think we should take a look at Webpack [1] and create a

Re: Release 0.9.6 Announce for web post?

Carlos, Let me know if you have problems with updating links on website. If yes I will try to figure out how to do that. Thanks, Piotr wt., 8 paź 2019 o 06:54 Piotr Zarzycki napisał(a): > Hey Andrew, > > Thank you! > > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore wrote: > >> I looked over

Re: Acceptance of Royale by Flex Developers

Hi Chris, thanks for sharing your thoughts. IMHO, not always a "strand" is a "visual component". This relation is not always true. a strand could be a non visual component (for example the implementation of RemoteObject in the Network library). And a bead could be a strand itself. I think the

How to skin components

When I was going through the documentation and code to get my head around this silly notation of "beads" and "strands", I realised the component plugins are very similar to the concept of skinning components that Adobe Flex talks about. And there doesn't seem to be any discussions on how to skin a

Re: issues with Sourcetree in Mac

Hi Piotr, no, I'll do from command line now, and will check the source tree issue later. Just asking to see if was something I was missing thanks

Re: Heads up on XML

Hi Greg, Questions inline. pon., 7 paź 2019 o 01:49 Greg Dove napisał(a): > Hi Piotr, just a quick follow-up to let you know that was all good, I had > already tested the merge and conflict resolution myself and was ready to > step in and help with that if that was necessary, but you already

Acceptance of Royale by Flex Developers

The use of the terms "strands" and "beads" still doesn't make sense to me because they are concepts I have never heard before and it is creating a barrier to acceptance and deepens the learning curve. As far as I can tell, it's something to do with visual/UI components. The section "Strands and

Build failed in Jenkins: royale-asjs_MXTests #1223

See -- [...truncated 1.01 MB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning