Re: Royale in 10 minutes (was Re: Proposed table of contents for Royale help documentation)

Hi Andrew, I took a quick peek at the Adobe doc. I'm not sure "Development Phases" should be the first thing under "Create an application", especially given how the Adobe doc says that some of those sub-topics are not phases. Also, I think there is more than one way to develop an application.

Re: Royale in 10 minutes (was Re: Proposed table of contents for Royale help documentation)

Good morning. Least thing first: Does the Apache header absolutely need to be in short lines with hard line breaks so it takes up so much vertical space in the file? Please look at test-apache-header.md and see whether the header laid out on fewer lines and trusting to line wrapping works. I am

Re: Help docs ToC and links

I’m trying to find my bearings after following lightly for a couple of weeks. I’m really excited by all the work that’s been going on vis a vis docs lately. I think it’s really important work and really glad it’s happening. How do I view the current status of the work on docs? I see there’s a

Re: DropDownList with ArrayList

Yup. And an Express version should probably use a bead which can handle either Array or ICollection dataProviders. > On Jan 26, 2018, at 3:32 PM, Peter Ent wrote: > > In PAYG fashion we/you would need to create a new set of beads that work > with ICollectionView rather

Re: Images and other assets?

Got it, I think. On Fri, Jan 26, 2018 at 10:04 AM, Andrew Wetmore wrote: > No. All I would need to know is where the website repo is, and how to link > from the docs to an image stored there. > > On Fri, Jan 26, 2018 at 9:55 AM, Gabe Harbs wrote: >

Build failed in Jenkins: royale-asjs_jsonly #197

See -- [...truncated 926.58 KB...] [java] WARNING: [http]:24: WARNING - accessing name require in externs has no effect. Perhaps you forgot to add a

Links to sites outside of help docs

Hi: Peeling this into its own thread. I looked at index.md and the syntax for popping a new tab does not seem to work. See attached image, where the "target" instructions appear in the visible text. This discussion [1] proffers several solutions, including using just plain HTML. I have tried

Re: Images and other assets?

I think relative links would work. (Although I could be missing something) Harbs > On Jan 26, 2018, at 4:04 PM, Andrew Wetmore wrote: > > No. All I would need to know is where the website repo is, and how to link > from the docs to an image stored there. > > On Fri, Jan

Re: DropDownList with ArrayList

In PAYG fashion we/you would need to create a new set of beads that work with ICollectionView rather than generalizing. ‹peter On 1/25/18, 5:36 PM, "Gabe Harbs" wrote: >Yeah. Maybe. In my case, I just used Array instead of ArrayList, but that >shouldn¹t really be

Re: Images and other assets?

I would assume that images for the website would go in the website repo and doc images would go in the docs repo. Any reason why that would be problematic? Harbs > On Jan 26, 2018, at 3:50 PM, Andrew Wetmore wrote: > > Where are we hosting images and other assets for the

***UNCHECKED*** Re: Help docs ToC and links

The develop branch is built by our CI server. The results are here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Stagin g/lastSuccessfulBuild/artifact/_site/index.html Theoretically, when we merge develop into master, GH pages will process it and it will show up here:

Re: Links to sites outside of help docs

Hi Andrew, Attachments often get stripped by Apache mailing lists. Try using paste.apache.org or pastebin and post a link. I'm confused by your email. Links in a .md file won't pop a new window, but the result in the .html file after Jekyll processes it should have the right target. I just

Re: ***UNCHECKED*** Re: Help docs ToC and links

Hi Alex, I think we should wait for something more suited for production. At least work on the presentation and have a minimum content. 2018-01-26 18:20 GMT+01:00 Alex Harui : > The develop branch is built by our CI server. The results are here: > >

Re: Proposed table of contents for Royale help documentation

I'll try that route and see what I get. I'll be back with my results. 2018-01-26 3:15 GMT+01:00 Alex Harui : > Hi Carlos, > > I don't know how big the changes you are thinking of and how much time you > have, but you could mock up something in your WP instance or post

Re: Royale in 10 minutes (was Re: Proposed table of contents for Royale help documentation)

Hi Andrew, Responses in-line. On 1/26/18, 2:48 AM, "Andrew Wetmore" wrote: >Good morning. > >Least thing first: Does the Apache header absolutely need to be in short >lines with hard line breaks so it takes up so much vertical space in the >file? Please look at

Re: Images and other assets?

Links from royale-docs to the royale website on royale.a.o would require absolute links. Right now the template is still picking up an asset for Carlos's site and probably should change to pick it up from royale.a.o. I don't think we've done any links to images specific to royale-docs. Jekyll

Re: Images and other assets?

I think we should host the royale docs images and assets in the same roayle-docs repo. For example, if we want to use a royale logo for royale docs, I'll be preparing the logo use for this concrete set of pages, and hosted with them. Maybe the header could have a concrete image designed only for

Re: Images and other assets?

Okay, so I should upload the first image I am playing with to a new "assets" folder in the help docs structure. I'll try that. On Fri, Jan 26, 2018 at 2:11 PM, Carlos Rovira wrote: > I think we should host the royale docs images and assets in the same > roayle-docs

Re: Links to sites outside of help docs

Where do you suggest I put screenshots I want to share? What I was concerned with is that, in the .md view I see ... If you are looking for the API Reference, click here

help text and background image

Hi: If you look at a help doc page that has a bunch of text, like "Migrate from Flex" [1], the background image renders the text on the right of the screen almost unreadable. [1]

Re: ***UNCHECKED*** Re: Help docs ToC and links

I would like to hold off on merging for a few more days, until we have worked out the kinks we know of and have a few pages that have significant information. a On Fri, Jan 26, 2018 at 1:20 PM, Alex Harui wrote: > The develop branch is built by our CI server. The

Re: Royale in 10 minutes (was Re: Proposed table of contents for Royale help documentation)

I don't think we need to build out the full ToC up front, rather than PAYG haha. There are tons of pages that I have not yet listed in the Google doc, and several decisions we have to make. For example, we have an Express set of controls and MDL and who knows what else. I presume we need to

Re: Royale in 10 minutes (was Re: Proposed table of contents for Royale help documentation)

On 1/26/18, 11:43 AM, "Andrew Wetmore" wrote: >I don't think we need to build out the full ToC up front, rather than PAYG >haha. There are tons of pages that I have not yet listed in the Google >doc, >and several decisions we have to make. > >For example, we have an

Re: Links to sites outside of help docs

On 1/26/18, 11:31 AM, "Andrew Wetmore" wrote: >Where do you suggest I put screenshots I want to share? Most folks post the screenshot externally and put a link to it in the email. You can try posting the screenshot at paste.apache.org, pastebin, dropbox, etc. >What I

Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

Breaking out a separate thread on this... Thinking about this some more, I think I can generate an interactive control with Jekyll, but I don't know how to make it retain state. I think that might require cookies and/or frames. For example, let's say the TOC looked like: Welcome --High Level

Royale Documentation Page Layout Proposal

Hi, I'm playing with this concept https://royale.codeoscopic.com/documentation-page-example/ Here I use: * The website page header * Royale logo white use * There's an alternate menu to configure (main website, blog, GitHub,...) * Search for docs (important) In content: * Main page doc title

Re: Royale Documentation Page Layout Proposal

Cool!! :) 2018-01-26 21:18 GMT+01:00 Carlos Rovira : > Hi, > > I'm playing with this concept > > https://royale.codeoscopic.com/documentation-page-example/ > > Here I use: > > * The website page header > * Royale logo white use > * There's an alternate menu to configure

Re: help text and background image

I am cool with it for now as my main activity is input, not reading. On Fri, Jan 26, 2018 at 4:30 PM, Alex Harui wrote: > Yep. I'm waiting for Carlos's input on what the doc screens really should > look like. Part of me is tempted to try CSS Regions and get the text

Re: Royale Documentation Page Layout Proposal

Hi Alex, 2018-01-26 21:40 GMT+01:00 Alex Harui : > Yes, looks great! My only thought is whether the red background should > just be a rectangle or may less height on the right so we can bring the > first line of text up higher and save more screen space. IOW, try to

Re: Royale Documentation Page Layout Proposal

Yes, looks great! My only thought is whether the red background should just be a rectangle or may less height on the right so we can bring the first line of text up higher and save more screen space. IOW, try to fit a few more lines of documentation on the screen. Also, what if the title is

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

See