Re: Issues with top level LICENSE

Yes, looks like we missed a few things there. I don't think this changed from RC1 to RC2 so too bad this wasn't found before RC2 was posted. The license contains a sentence saying the paths are relative to royale-asjs. I'm not seeing the Externs in the packages so unless you find them I think

Issues with top level LICENSE

Hi, All three repos are now being included in the src release but it looks like the top level LICENSE file wasn’t updated to take this into account. 1. Paths to files mentioned in the top level license are incorrect and missing "royale-asjs” from the front of them. 2. Top level license is

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC2

Hi, Not sure what might be wrong (and could be something on my end) but in trying out the staged release I’m getting the following error when trying to compile a simple project: Downloading: https://repo.maven.apache.org/maven2/org/apache/royale/framework/Basic/0.9.0/Basic-0.9.0.pom [WARNING]

Re: Migrating existing FlexJS documentation to Royale

Here is how Electron does it with Github pages: Documentation result page: https://electronjs.org/docs/api/accelerator Source code: https://github.com/electron/electron/blob/master/docs/api/accelerator.md Some documentation on how this works:

Re: Migrating existing FlexJS documentation to Royale

This is for doc, not code so I'm not sure the issue I raised matters. That said, I've been reading this [1] and it seems like we should be able to set up a few templates sort of like we did flex.a.o and not worry so much about customizing a third-party theme. [1] https://jekyllrb.com/docs On

Re: Migrating existing FlexJS documentation to Royale

Carlos, I like your findings jeckyll theme doc. It looks like we may have again similar issue with license as we have in MDLExample. Can someone raise jira for both cases? Alex raises question on legal couple of days ago. No responses. Let's not wait block us with it - push things forward. Jira

Re: Migrating existing FlexJS documentation to Royale

Hi, > I think this looks very good and seems to be responsive > > [1]http://mistic100.github.io/jekyll-bootstrap-doc > [2] https://github.com/allejo/jekyll-docs-theme From a quick look this contains CSS code licensed under CC-BY-3.0 (looks like it comes from bootstrap docs). That may or may

Re: Migrating existing FlexJS documentation to Royale

Hi, One option you might want to look into is using this [1] and using maven to build the site and auto publish when changes are made in GitHub via jenkins. We’re doing this on the PLC4X incubating project [2] (so it’s still a work in progress), it's not using markdown but is using asiidoc

Re: Migrating existing FlexJS documentation to Royale

Hi, > please check this link for licenses [1] and let me know if is ok for us to > use this theme as base I would double check carefully from a quick look it contains a number of differently licensed components including ALv2, MIT and BSD licensed files.(Which should all be all fine) There

Re: Migrating existing FlexJS documentation to Royale

Yes, that looks fine. On Thu, Jan 18, 2018 at 8:30 PM, Carlos Rovira wrote: > Hi This is another one [1] based in MIT. Check girhub repo [2] > > I think this looks very good and seems to be responsive > > > [1]http://mistic100.github.io/jekyll-bootstrap-doc > [2]

Re: Migrating existing FlexJS documentation to Royale

Hi This is another one [1] based in MIT. Check girhub repo [2] I think this looks very good and seems to be responsive [1]http://mistic100.github.io/jekyll-bootstrap-doc [2] https://github.com/allejo/jekyll-docs-theme 2018-01-19 1:22 GMT+01:00 Carlos Rovira : > Hi

Re: Migrating existing FlexJS documentation to Royale

Hi Dave, FWIS there, this is the website, with info about how to develop, mailing list, support. For me this match our current website right?, but I think, not the documentation of the project. do you have a link to the documentation to see how is done? 2018-01-19 0:57 GMT+01:00 Dave Fisher

Re: Migrating existing FlexJS documentation to Royale

Hi - I’m sure you guys will figure it out. Here is how Apache OpenOffice did it about 6 years ago using the Apache CMS. (Now discouraged, but possible) Markdown is good and you can do something complex. Take a look. https://openoffice.apache.org/website-local.html

Re: Migrating existing FlexJS documentation to Royale

@Alex, please check this link for licenses [1] and let me know if is ok for us to use this theme as base The results can be seen in [2] I see others as well that are MIT only and very few that are ALv2. I assume that both are ok for us. My intention is configure royale-docs to use that theme

Re: Migrating existing FlexJS documentation to Royale

Hi Alex, 2018-01-19 0:44 GMT+01:00 Alex Harui : > OK, I'm sure you will figure it out. But if we all agree on MarkDown, I > think we can start writing content in MarkDown and committing it? Then > later, the theme will just magically appear or maybe we have to add a

Re: Migrating existing FlexJS documentation to Royale

I am fine with using MarkDown if someone can assure me that there will, eventually, be a way to display a navigable index that will help the reader jump around through the pages. On Thu, Jan 18, 2018 at 7:44 PM, Alex Harui wrote: > OK, I'm sure you will figure it out.

Re: Migrating existing FlexJS documentation to Royale

Hi, Alex: As you were writing your note, I was posting this on https://github.com/apache/royale-asjs/issues/110 I am thinking about a structure for our documentation that helps people who are new to Royale move into using the framework with satisfaction, and that helps people who are already

Re: Migrating existing FlexJS documentation to Royale

OK, I'm sure you will figure it out. But if we all agree on MarkDown, I think we can start writing content in MarkDown and committing it? Then later, the theme will just magically appear or maybe we have to add a tag or two to each page? -Alex On 1/18/18, 3:36 PM, "carlos.rov...@gmail.com on

Re: Migrating existing FlexJS documentation to Royale

Hi Alex, I'm right now fighting with Jekyll and themes. I have working a minimal example localy and trying to see how to: * Jekyll themes work in order to configure a basic one with basic website royale branding (fonts, colors and sizes) * How this means for ease of development, I'm still trying

[DISCUSS] Discuss Release Apache Royale 0.9.0 RC2

This is the discussion thread. Changes in this RC include: Removed AngularExample, MDLBlogExample, MDLExample. Maven POM versions should be synced up now. Thanks, Alex Harui

[VOTE] Release Apache Royale 0.9.0 RC2

Hi, This is vote for the 0.9.0 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc2/ Before voting please review the section,'What are the ASF requirements on approving a release?', at:

Re: Migrating existing FlexJS documentation to Royale

Hi Andrew, I've been thinking that we don't want to directly copy the FlexJS pages to GH Pages. I think it needs better organization. I think the question for you is how much time you have and what you would like to do with your time. I'm hoping to spend some time on doc once RC2 is posted. I

Re: [Royale] DataGrid default configuration proposal

Peter, You changes working in my example. One thought is that It is a bit odd to me that we need to add also style DataGrid once we add DynamicDataGrid. I can live with that. Thank you 2018-01-18 22:45 GMT+01:00 Piotr Zarzycki : > Wonderful! > > I will refresh

Re: [Royale] DataGrid default configuration proposal

Hi, I just pushed changes to the DataGrid and TreeGrid that should make things work. I included upgrades to the DataGridExample and TreeExample. Doing: should work fine. You should include the "DataGrid" style so that it picks up any missing default values. The "DynamicDataGrid" style is part

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

OK, I am going to prepare RC2. On 1/18/18, 3:23 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi Alex, > >it's ok to remove both. We need to get a first release as soon as >possible. >People on twitter is ask us

Re: About Royale MDL Examples

Hi Piotr, for me it's ok. My opinion is that example should be accesible but outside this project for two reasons: 1.- Could be important for people currently using MDL library. 2.- As I stated, I want to concentrate our energies in new Royale UI Set that eventually has an MDL theme. So maybe

Re: About Royale MDL Examples

Hi Carlos, I don't mind if you do this. I will personally for sure add those examples to my own repo as I stated in the RC thread - IF Legal won't allow as to use it. By won't allow I mean the situation where we will have to do some magic to have that example. Legal discussion is in progress, so

About Royale MDL Examples

Hi, separating MDL examples problem from release so we can get that done soon with less noise. I want to ask here if it would be ok to upload both conflictive examples to my own github account so people interested can access it. Let me know in order to proceed. -- Carlos Rovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

Hi Alex, it's ok to remove both. We need to get a first release as soon as possible. People on twitter is ask us for this. So First things first. Thanks 2018-01-18 11:00 GMT+01:00 Alex Harui : > Hi Carlos, > > I don't doubt that MDLExample is referred to often, however

Re: Migrating existing FlexJS documentation to Royale

Hi Andrew, I think the initial approach is ok. We need to work all together since we need: * Technical info that is accurate to help people get started or solve a problem with some part of Royale * Be as clear as possible in terms of organization (how to organize the content), grammatical

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

Hi Carlos, I don't doubt that MDLExample is referred to often, however it may not be ok for us to bundle it in Royale releases. The problem is not the images, it is the bits of CSS and maybe some text content from HTML files that is the issue. Are you ok with us removing MDLExample and