Re: Royale Examples Blog proposal to all the team

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

How I can use multiple CSS files

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,

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

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

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

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

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

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

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

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 >

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

See

Re: ASDoc, Routing, Releases

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

Build failed in Jenkins: royale-typedefs #144

See Changes: [harbs] Changed download references for extern files -- Started by an SCM change Building in workspace

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

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

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

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

Re: Royale Examples Blog proposal to all the team

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

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

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

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

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

Build failed in Jenkins: royale-typedefs #145

See Changes: [harbs] This should fix the ant build -- Started by an SCM change Building in workspace

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

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

Re: Royale Examples Blog proposal to all the team

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

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

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!

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

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

Re: Royale Examples Blog proposal to all the team

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

Re: Royale Examples Blog proposal to all the team

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

Re: Royale Examples Blog proposal to all the team

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

Re: ASDoc, Routing, Releases

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

Re: ASDoc, Routing, Releases

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

Re: ASDoc, Routing, Releases

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

Re: Royale Examples Blog proposal to all the team

>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

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

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 *

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

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

Build failed in Jenkins: royale-asjs_jsonly #295

See -- [...truncated 654.68 KB...] [exec] D test/com/google/javascript/jscomp/regex/CharRangesTest.java [exec] D

Re: Royale Examples Blog proposal to all the team

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.

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

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

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

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"

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

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

Re: Royale Examples Blog proposal to all the team

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

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

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"

Re: How I can use multiple CSS files

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

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

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

Re: ASDoc, Routing, Releases

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

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

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

Re: How I can use multiple CSS files

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

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

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

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

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.

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

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

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

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/

[DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

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

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

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

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

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

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

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,

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

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

Re: Royale Examples Blog proposal to all the team

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.

Re: Royale Examples Blog proposal to all the team

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

[GitHub] cottage14 closed pull request #5: Develop

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

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

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,

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

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,

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

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

Re: Royale Examples Blog proposal to all the team

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

Re: Royale Examples Blog proposal to all the team

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

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

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

Re: Royale Examples Blog proposal to all the team

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

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

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

Build failed in Jenkins: royale-asjs_jsonly #296

See -- [...truncated 651.83 KB...] [exec] D test/com/google/javascript/jscomp/regex/CharRangesTest.java [exec] D

Build failed in Jenkins: royale-typedefs #148

See -- [...truncated 110.35 KB...] [exec] D test/com/google/javascript/jscomp/parsing/TypeSyntaxTest.java [exec] D

[ANNOUNCE] Apache Royale 0.9.1 Released

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