Re: Github Pages (was Re: Github wikis)

Hmm, can you try doing a reply-all to the moderation email? That should fix this issue. If that doesnt work, I can switch. Thanks, Om On Tue, Oct 3, 2017 at 8:43 PM, Alex Harui wrote: > Om, this email is ending up in moderation. Can you subscribe this email > or

Re: Nightly Builds Available

If you are committing any changes use for example: "my commit message (reference #issuenumber)" - Than we will see on github all commits under issue and can review it. Piotr 2017-10-03 17:20 GMT+02:00 Alex Harui : > I"m not sure what you mean by "use issue number".

Re: Github Pages (was Re: Github wikis)

OK, put in a request for royale-docs. On 10/3/17, 1:07 AM, "Piotr Zarzycki" wrote: >Hi Alex, > >+1 for royale-docs. If I would like to make something like Olaf [1] >started >and move all his already gathered information in that structure where in >your opinion guys

Re: [Royale] Flex to FlexJS migration path

OK, maybe wait until royale-docs is up and try GH Pages? Or if it is better as plain HTML, put it on royale.a.o? -Alex On 10/3/17, 1:13 PM, "Harbs" wrote: >Definitely on the right path. > >I thought I’d try and copy this into the Github wiki, but wowsers! Tables >are

Re: [Royale] Flex to FlexJS migration path

GH Pages is likely the way to go. Maybe we could make the comparison an interactive Royale app… ;-) > On Oct 3, 2017, at 11:18 PM, Alex Harui wrote: > > OK, maybe wait until royale-docs is up and try GH Pages? Or if it is > better as plain HTML, put it on royale.a.o? > >

Re: Github Pages (was Re: Github wikis)

Royale-docs has been created. Can someone put in some initial content? I'm buried in the rename and don't want to stop to figure out GH Pages. Then we ask Infra to hook it up as our project's pages. Thanks, -Alex On 10/3/17, 1:17 PM, "Alex Harui" wrote: >OK, put in a

Re: [Royale] Flex to FlexJS migration path

Sounds worth a try. Note that Royale ASDoc is currently a Royale app. Also note that regular Flex used [Alternative] metadata to point from MX components to Spark components. I think we want the opposite, though, and point from Royale components back to MX and Spark components. I believe that

Re: Github Pages (was Re: Github wikis)

Done. Do I need to make a gh-pages branch? > On Oct 3, 2017, at 11:35 PM, Alex Harui wrote: > > Royale-docs has been created. Can someone put in some initial content? > I'm buried in the rename and don't want to stop to figure out GH Pages. > Then we ask Infra to hook

Re: [Royale] Flex to FlexJS migration path

We'd need a map back to the Flex components. That would not be too hard as long as we don't need any or much commentary about the Flex side. That's what I was going for in the table. I put in a couple of extra components but do not want to take writing out everything in an HTML table without

Re: [Royale] Flex to FlexJS migration path

Definitely on the right path. I thought I’d try and copy this into the Github wiki, but wowsers! Tables are *hard* in Markdown, and it seems like multiline tables are hard or impossible on Github wiki pages. :-( > On Oct 3, 2017, at 8:30 PM, Peter Ent wrote: > > I have a

Re: [Royale] Flex to FlexJS migration path

Hmm. Thinking about it some more, I’m thinking that a Royale app to display the data could be a very good idea. It could solve the real estate problem and make finding options very easy. Basically, you could either browse for search for a mx or spark component and you could then get a picker

How could we work with GitHub

Hi Guys, I thought that would be could to share some vision about how could we work with our GitHub repository. COMMITS: This parts is only regards when we have issue raised. Each commit should have description and issue number. I will use as an example our issue raised for renaming. [1] If you

Re: Github Pages (was Re: Github wikis)

Hi, I see that we have repo for docs [1] and gh-pages working [2]. I would like to start putting somewhere information in the Olaf's structure [3], of course let's change whatever you think to have better one. The question is - Where such things should landed in royale-docs or in royale-asjs -

Re: Github Pages (was Re: Github wikis)

Not sure. I notified infra per their instructions. Get Outlook for Android From: Harbs Sent: Tuesday, October 3, 2017 1:46:14 PM To: dev@royale.apache.org Subject: Re: Github Pages (was Re: Github wikis) Done. Do I

RE: Struggling with resource files

I'm not an expert, but I feel that a plain JS object is conceptually closer to the SWF way. That said, I have no idea on how a binary value (Class, Image) could be stored in such an object (but there are people around there who certainly know!). TypedArray maybe ? I agree that the core

Re: Github Pages (was Re: Github wikis)

Hi Alex, +1 for royale-docs. If I would like to make something like Olaf [1] started and move all his already gathered information in that structure where in your opinion guys should it go ? Into the royale-docs as gh pages or into royale-asjs as Wiki ? Does anyone is against to have it Olaf's

Re: Github Pages (was Re: Github wikis)

Hi, I started work on a Quick Start guide [1] to bridge the gap between the README (source setup and build) and any in-depth documentation. It will simply be the steps I took to get a project compiling on my machine. I had to gather the information from various places and I thought it'd be nice

Re: Github Pages (was Re: Github wikis)

I prefer royale-docs Thanks, Om On Oct 2, 2017 11:04 PM, "Alex Harui" wrote: > Per Infra: "Pages are not enabled until we have some content to point to. > Best thing I think is to create a new royale-pages repository (or whatever > name) and I'll enable it on that -

Re: Nightly Builds Available

Alex, If you start renaming under some branch etc. please use issue number (reference #number) - we will have everything under our created issue. It help a lot with reviewing. I have found that is much worse for me looking into the emails than on github right now. Thanks, Piotr 2017-10-03 7:25

Re: Github Pages (was Re: Github wikis)

royale-docs is good. > On Oct 3, 2017, at 9:36 AM, OmPrakash Muppirala wrote: > > I prefer royale-docs > > Thanks, > Om > > On Oct 2, 2017 11:04 PM, "Alex Harui" wrote: > >> Per Infra: "Pages are not enabled until we have some content to

Re: [royale-asjs.wiki] branch master updated: Give it a bit more body

Hi Erik, Since your quick start is how to use VSCode with Royale I believe you should also change title which states about that. We have also Moonshine where Quick start will look very different. Piotr 2017-10-03 11:22 GMT+02:00 : > This is an automated email from the

Re: Possible license issue with new web site

Hi Carlos, Yes! Once you have something you like then we evaluate. We have a wiki going so it will all depend on what we host and what we release. What's wiki and what is the site. We cannot release category X. There is a boundary but it is not a first or second level concern for you. It is

Re: [royale-asjs.wiki] branch master updated: Give it a bit more body

Work in progress, just collecting steps and trying to get to terms with git -> GitHub Wiki -> MarkDown quicks :-) My idea is to have a general landing page and then a selection of IDEs as a submenu, with separate quick start steps for each. I will take care of the VSCode steps, others can fill

FileReference implementation

We use FileReference a lot in our Flex apps (data import functionalities, export functionalities). With FP, it has been possible (since FP 11 if I am correct) to have local read and write access (provided the access is "controlled" by a dialog that the user has to validate) from the user's

Re: Nightly Builds Available

I think he means cross references between issues and commits. It’s also possible to have a list of issues within and issue.[1] Harbs [1]https://guides.github.com/features/issues/ > On Oct 3, 2017, at 6:20 PM, Alex Harui

Re: Nightly Builds Available

I"m not sure what you mean by "use issue number". Where am I supposed to use it? -Alex On 10/3/17, 1:02 AM, "Piotr Zarzycki" wrote: >Alex, > >If you start renaming under some branch etc. please use issue number >(reference #number) - we will have everything under

Re: Nightly Builds Available

Maybe I didn't get enough sleep last night. There is already an issue open, yes? Am I supposed to type that issue# in the commit message or something like that? I didn't see that from the link you posted. -Alex On 10/3/17, 8:42 AM, "Harbs" wrote: >I think he means

Re: Nightly Builds Available

Not sure what Piotr meant. > On Oct 3, 2017, at 6:46 PM, Alex Harui wrote: > > Maybe I didn't get enough sleep last night. There is already an issue > open, yes? Am I supposed to type that issue# in the commit message or > something like that? I didn't see that from

Re: Github Pages (was Re: Github wikis)

This should make things simpler: https://github.com/blog/2228-simpler-github-pages-publishing Thanks, Om On Tue, Oct 3, 2017 at 2:57 PM, Alex Harui wrote: > Not sure. I notified infra per their instructions. > > Get Outlook for Android > >

Re: Struggling with resource files

Hi Nicolas, Thanks for the ideas. A Class in JS is not a binary value, so ClassReference just link in the JS for the class and resolves to the class reference at runtime. We are not currently supporting embedded images, so images are just URLs to external images right now. We haven't worried

Re: Github Pages (was Re: Github wikis)

IMO, flex-docs is for user-facing documentation. IOW, how to use Royale. The repo wikis are for how to be a developer of the code in the wiki. Build instructions, release guides, etc. The wikis won't have very much polish. Most of what is in the Flex Wiki for FlexJS can end up in the repo wikis

Re: Github Pages (was Re: Github wikis)

Om, this email is ending up in moderation. Can you subscribe this email or switch to one that is subscribed? Thanks, -Alex On 10/3/17, 4:46 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >This should make things simpler: