Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

OK, please remove it from the release/0.9.0 branch. Thanks, -Alex On 1/16/18, 10:06 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >On Jan 16, 2018 8:47 PM, "Alex Harui" wrote: > > > >On 1/16/18,

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

On Jan 16, 2018 8:47 PM, "Alex Harui" wrote: On 1/16/18, 1:13 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: > >+1 to exclude the MDL examples from this release. Let's find a good way >to >fix the

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

Hi Justin, We have it now and are doing the correct thing in a natural way. An Apache Member who was on my first PMC has explained the situation well. He calls it “cups and saucers” when we discovered a single GPL file had been in a few releases we removed it. It is best effort and sometimes

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

Hi, > Can you provide a link to that discussion? Sure here [1] As discussed in that thread I asked them to clarity what license the files are under [2] (way back in October 2016) and got no response. Other people since then have asked the same question (including Om yesterday) and not got any

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

On 1/16/18, 1:13 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: > >+1 to exclude the MDL examples from this release. Let's find a good way >to >fix the IP issues in our next release. Speaking of removing examples... What's

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

On 1/16/18, 3:32 PM, "Justin Mclean" wrote: > >Yes is is unfortunate that the PMC failed to notice this issue. The issue >had actually been brought up before the MDL code was checked in to a repo >and there was some discussion about the issues but it wasn’t fully

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

Hi, > After Justin pointed out that there is CSS under CC-BY-4.0 in > MDLBlogExample, I took a closer look > and realized that really, I think these two examples are just ports of > Google's examples and thus should remain under Google's copyright Yep I agree with that. > There is also a

Re: [Royale] ICollectionView

Now that I've checked in TreeGrid and my changes to DataGrid (not much) I can look into this with you. I created an interface, IDataGridColumn so that TreeGrid and DataGrid can share a lot of the same code, although the two are separate at the moment. I want TreeGrid to be able to use most of the

[Royale] TreeGrid

Hi, I've committed/pushed code that makes TreeGrid work. You can look at TreeExample to see how to use it. Basically, TreeGrid is just like DataGrid except it works with HierarchicalData. You define which column you want to hold the tree using a description. For the other columns use . You

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

On Tue, Jan 16, 2018 at 1:10 PM, Alex Harui wrote: > Thanks Olaf! Good to know that we don't have that restriction anymore. > > I'd like to get Piotr and Carlos's opinions about removing the MDL > examples since they worked so hard on it. I'm finishing up changing the

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

Ah yes, that's a bug that has already been fixed for RC2. It doesn't happen when you first run a build in the source folder but now you are running a build for the second time. Try deleting the apache-royale-0.9.0-src/royale-asjs/lib and apache-royale-0.9.0-src/royale-asjs/js/lib folders and try

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

Hi Alex, I've stumbled over the next issue [1]. It seems to me that externc is not available? Any ideas? Thanks, Olaf [1] download: C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-asjs Expanding:

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

Olaf is correct. He can just try hand-patching the files that have been downloaded and expanded in the folder where he is running ApproveRoyale.xml. There should be an apache-royals-0.9.0-src folder with a royale-asjs/examples/royale/DataBindingExample_Flat subfolder. Running the "build" target

Re: Github Documentation (Re: Apache Royale website is live!!)

We decided a while back to use GH Pages instead of a wiki for our user-facing documentation. Royale is part of the Apache organization on GH, so there might be more restrictions on what we can and can't do. AIUI, it is all HTML and CSS in the end. I'm not opposed to switching to using Jekyll

Re: [Royale] ICollectionView

Sorry for the delay; yesterday was a company holiday here in the States. I was catching up on other things. I figured this would come up; we need to have a plan for style names that is consistent. What we have now isn't working right all the time. I was trying to give the columns additional class

Re: Github Documentation (Re: Apache Royale website is live!!)

Hi Carlos, >I think we should have control over this in order to modify to our needs and not having to bother >anyone for something so easy Agree! >I need to know now, how I can tweak the theme to our needs This should do the trick [1] Thanks for working on this!! Olaf [1]

Re: Github Documentation (Re: Apache Royale website is live!!)

Cayman is a Github official theme. So I suppose is totally right to use it as an starting point. But in the end: We don't want to use Cayman!, we want to create a theme that has our branding (fonts, colors and some image backgrounds) 2018-01-16 13:23 GMT+01:00 Piotr Zarzycki

Re: Github Documentation (Re: Apache Royale website is live!!)

Hi, I created my own test repo, and is very easy. https://github.com/carlosrovira/royale-pages-test/blob/master/README.md https://carlosrovira.github.io/royale-pages-test/ So we need for infra to config the Github repo. I think we should have control over this in order to modify to our needs

Re: Github Documentation (Re: Apache Royale website is live!!)

Carlos, What's with the license of Cayman. Maybe we should choose some theme compatible with Apache ? Only one from the list seems to be, but I'm not an expert [1] [1] https://github.com/pages-themes/primer Thanks, Piotr 2018-01-16 13:14 GMT+01:00 Carlos Rovira : >

Re: Github Documentation (Re: Apache Royale website is live!!)

Just created the ticket here: https://issues.apache.org/jira/browse/INFRA-15845 2018-01-16 13:03 GMT+01:00 Carlos Rovira : > Hi, > > yes, I think the best way is to use markdown, GitHub pages and some > template (e.j: Cayman) as an starting point to change styles to

Re: Github Documentation (Re: Apache Royale website is live!!)

Hi, yes, I think the best way is to use markdown, GitHub pages and some template (e.j: Cayman) as an starting point to change styles to match or Royale website styles As we all doesn't have experience, I'll try to investigate and talk with infra to see if they need to make some tweak. I want to

Re: Github Documentation (Re: Apache Royale website is live!!)

Hi Piotr, >I don't think we need Wiki on the docs repository. I agree that we should start directly with GH pages. >We just need to correct all the things which you have on your repo It is not so much content at the end. I guess we have to rewrite it anyway, so don't care about it ;-) >It is

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

Piotr, I guess this time I understand what to do...hopefully ;-): Alex made a change at one of the examples at the release/0.9.0 branch. Because the distribution server does not contain this change I can't continue testing. So, in order to continue testing I have to adopt Alex change to my local

Re: Github Documentation (Re: Apache Royale website is live!!)

There is possibility that we may have to ask infra to switch something etc. I don't think we need Wiki on the docs repository. It should be possible make pull requests to that repository by anyone. We just need to correct all the things which you have on your repo, than make transformation to the

Re: Github Documentation (Re: Apache Royale website is live!!)

Olaf, Ad. 1) I personally don't want wiki for documentation. That is only the proposition to use wiki on your repository in order to simplify things and investigate whether we can transform it to the GitHub pages. Do you know the way how to do this ? Ad. 2) I think Carlos need help with run even

Re: Github Documentation (Re: Apache Royale website is live!!)

Hi, >How do we create navigation that shows up on each page of the >documentation To be clear: There are two common ways of creating a documentation by using GitHub: 1) Using the GitHub Wiki 2) Using GitHub pages 1) Here the navigation is provided by using the Wikis' sidebar. You have to put

Re: Github Documentation (Re: Apache Royale website is live!!)

Hi Carlos, >But there's no such file, so my main question is, is royale-docs a Github >pages repo so I can customize it with a Github Pages Theme? >From my understanding, any GitHub repo is able to process/provide GitHub pages. >Add the following to your site's _config.yml: IIRIC, GitHub