-remove-circulars

[Alex Harui]

Hi Folks,

I've spent the last day or so trying to get ASDoc to run when minified.  I
created a JSON to ValueObjects utility which helped a lot.  It still isn't
completely running, but it appears that we need to stop pruning classes
that are only used in type annotations.  This will make most apps a little
fatter, but also require all apps to use remove-circulars.

What do folks think about that?  The compiler used to prune classes from a
file's goog.requires list that were never instantiated or type-checked in
that file.  So, for ASDoc, the ASDocClass ValueObject that represents the
JSON data for the ASDoc is never instantiated by the class that consumes
it.  The instances are created by JSON.  The ASDocClass is only mentioned
in JSDoc to declare some variable as being of type ASDoc.  That enabled us
to remove that class from the requires list since that ASDocClass is never
referenced by operational code.  Removing that goog.require helped
eliminate circular goog.require references that the closure compiler
disallows.  That kicked HTMLElementWrapper out of the app for example.
But it appears that by removing that goog.require, the compiler didn't
know that the ASDocClass properties were exported and it renamed some of
them resulting in problems in js-release.  So by leaving more
goog.requires in the code we get better support against renaming, but we
also bring back more circularities and now even HelloWorld would need
-remove-circulars.

An alternative that would allow a few more apps to not need
remove-circulars is to modify a few of our examples and classes to
eliminate circularities.  HelloWorld only has 3.  But 2 of them are
IParent/IChild and IStrand/IBead.  It seems "right" to have IParent
reference IChild and vice versa.  Same for IStrand and IBead.  I'm not
quite sure what the answer is.  Maybe IParent can reference IChild, but
IChild does not reference its IParent.  I guess you could make an
IParentedChild interface with the parent property and concrete children
implement both IChild and IParentedChild.  That seems wrong and overly
complicated.

Yet another option, which is recommended by some folks in the Closure
Compiler community but doesn't fit well with the ActionScript language is
to define both IChild and IParent in the same file.  I do not want to
spend the time modifying the compiler for that.  It might be practical to
merge the files as part of the Ant and Maven builds.  But again, that will
take time as well.

That said, requiring remove-circulars always doesn't seem quite right
either.

Thoughts?
-Alex

To-do list from Wiki

[Andrew Wetmore]

Hi:

There is a to-do list from the Wiki [1] which lists a number of Flex
features that may not yet be available in Royale. Could someone review the
list and confirm whether all the entries are yet-to-be-ported?

Also, what is the status of the wiki vis-a-vis the help docs? Do we
maintain it or migrate the information?

Thanks.

[1] https://cwiki.apache.org/confluence/display/FLEX/Framework+Tasks

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Page linked to from license page no longer exists

[OmPrakash Muppirala]

I'll look into it.

Thanks,
Om

On Feb 16, 2018 8:35 AM, "Alex Harui"  wrote:

> Bummer.  Looks like WikiPedia decided to remove it.  I think Om
> contributed that, so I guess we should let him decide whether to find
> another source for the data or remove the example.
>
> My 2 cents,
> -Alex
>
> On 2/16/18, 3:17 AM, "Andrew Wetmore"  wrote:
>
> >Hi:
> >
> >on Welcome/licenses.md there is this passage:
> >
> >The map coordinates in examples/native/USStatesMap/src/MapCoords.as were
> >placed into the Public Domain by its author. See:
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fen.wikipe
> >dia.org%2Fwiki%2FFile%3AUSA_CIA_Map.svg%23file=02%
> 7C01%7Caharui%40ado
> >be.com%7C8c30db66c9c448a2a77708d5752ed58e%7Cfa7b1b5a7b34438794aed2c178de
> ce
> >e1%7C0%7C0%7C636543766369921734=EVjU7uzApzAiAIf8CoayF6n7kP6LQs
> WtxHHZ
> >zqTNb5M%3D=0
> >
> >When I click that link I get a message that the file has been deleted.
> >Since this is license-related, do we need to hunt out a replacement
> >source?
> >
> >--
> >Andrew Wetmore
> >
> >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14
> .
> >blogspot.com%2F=02%7C01%7Caharui%40adobe.com%
> 7C8c30db66c9c448a2a77708
> >d5752ed58e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636543766369921734
> >=dwjkXL%2BDCfUpUYMLL9B4Mhpw%2BIjT%2FlNEeEkpDMgMX8M%3D=0
>
>

Re: How to install Nightly build through NPM

[OmPrakash Muppirala]

You can just do npm install -g  
That should install the nightly for you.

Thanks,
Om

On Feb 16, 2018 5:49 AM, "Piotr Zarzycki"  wrote:

> Hi Guys,
>
> Is it possible to install Nightly build of Royale through NPM ? I need to
> check some scenario with Moonshine on Mac platform.
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>

Re: Website help doc links not working

[Andrew Wetmore]

Thanks!

I think I am caught up with the existing link issues, and have added some
more material. I will keep QA in mind a little better at least as we head
toward each new release and each possible bump of new website visitors.

There is lots more material to add, and I have some questions in that
regard, but I think I will start a new thread for that so the questions do
not get lost.

a



-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Website help doc links not working

[Alex Harui]

Hi Andrew,

I don't think I changed any file names.  You can always rummage through
the commit log to find out, but maybe not worth the time.  I'm not
planning to be in royale-docs over the next couple of days so feel free to
rename lots of things to the pattern you wanted.

-Alex

On 2/16/18, 2:23 AM, "Andrew Wetmore"  wrote:

>The first issues we hit are on the index.md page. I did not write this
>page
>or create the links there, so perhaps they were created before the file
>names reached their current form. I will do a link sweep.
>
>On Fri, Feb 16, 2018 at 6:07 AM, Andrew Wetmore 
>wrote:
>
>> That's interesting, as I carefully matched the links to the file names
>> when I created the links. Did the file names get changed at some point?
>>
>> On Fri, Feb 16, 2018 at 4:20 AM, Alex Harui 
>> wrote:
>>
>>> Thanks Berty,
>>>
>>> Andrew, the link has to reference the correct file name.
>>>
>>> For "Features and Concepts", the file is currently named "Features And
>>> Concepts" (note capital "A" in "And")
>>> For "A Bit of History", I only see a file called history.md
>>> For "Licenses and Policies", I only see a file called licenses.md
>>>
>>> We discussed file names such a while back, so maybe it is time for you
>>>to
>>> sweep through and fix up the links.
>>>
>>> HTH,
>>> -Alex
>>>
>>> From: Berty Tonta > berty.to...@leadstalk.pro>>
>>> Reply-To: "dev@royale.apache.org" <
>>> dev@royale.apache.org>
>>> Date: Thursday, February 15, 2018 at 9:11 PM
>>> To: "dev@royale.apache.org" <
>>> dev@royale.apache.org>
>>> Subject: Re: Website help doc links not working
>>>
>>> all links below "High Level View" not working
>>>
>>> [cid:ii_jdph8n600_1619d066ebfa59f8]
>>> ​
>>>
>>> Berty Tonta
>>> Sales Enablement Specialist
>>>
>>> 
>>>[https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.
>>>google.com%2Fuc%3Fid%3D0B8FN9ycn20KId3I3WlJkSm0taHM=02%7C01%7Caharu
>>>i%40adobe.com%7C4fb61c0c2fd74be30d7c08d5752764ea%7Cfa7b1b5a7b34438794aed
>>>2c178decee1%7C0%7C0%7C636543734414162910=xOGj2YYeFUzV5GzaOI%2Fk%2F
>>>5d%2FpGYN2eyUOIuO1KbS%2BJM%3D=0
>>> =download]
>>> 4 BENGALI STREET, BEAU BASSIN, MAURITIUS
>>> T +230 57 43 81 34 | berty.to...@leadstalk.pro>> berty.to...@leadstalk.pro> |
>>>https://na01.safelinks.protection.outlook.com/?url=WWW.LEADSTALK.PRO
>>>a=02%7C01%7Caharui%40adobe.com%7C4fb61c0c2fd74be30d7c08d5752764ea%7Cfa7b
>>>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636543734414162910=yfwdHOZR
>>>GbByB%2B7JOrMXT4rNRuGdQIDs2GFojJ5DG14%3D=0>> .safelinks.protection.outlook.com/?url=http%3A%2F%2FWWW.
>>> LEADSTALK.PRO=02%7C01%7Caharui%40adobe.com%7C8a249de
>>> a4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178decee1
>>> %7C0%7C0%7C636543610179250868=l9s%2BqwJRmavSI9pqqJQjwD%2Bpn8hkH%
>>> 2FvneEg2m4a%2BAl4%3D=0>
>>> BRN 17149323
>>>
>>> On Fri, Feb 16, 2018 at 7:19 AM, Alex Harui >> > wrote:
>>> What do you mean by "links not working".  I went to the [1], clicked on
>>> "High Level View" and ended up on a new page.
>>>
>>> -Alex
>>>
>>> On 2/15/18, 5:02 PM, "Andrew Wetmore" >> ttag...@gmail.com>> wrote:
>>>
>>> >Almost all of the links on the help docs page [1] are not working.
>>> >
>>> >More than that, I am afraid that the pattern I thought was correct for
>>> >linking from one page to another is not working; however, since I
>>>can't
>>> >get
>>> >past the first page I can't check.
>>> >
>>> >[1]
>>> >https://na01.safelinks.protection.outlook.com/?url=https%
>>> 3A%2F%2Fapache.gi
>>> >thub.io>> http%3A%2F%2Fthub.io=02%7C01%7Caharui%40adobe.com%7C8a
>>> 249dea4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178d
>>> ecee1%7C0%7C0%7C636543610179250868=6Hs%2BuQ7PH3H%
>>> 2BftLhj3A%2FRq9zMZYuF9J%2FgtdJjwQZAlc%3D=0>%
>>> 2Froyale-docs%2F=02%7C01%7Caharui%40adobe.com>> na01.safelinks.protection.outlook.com/?url=http%3A%2F%
>>> 2F40adobe.com=02%7C01%7Caharui%40adobe.com%7C8a249de
>>> a4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178decee1
>>> %7C0%7C0%7C636543610179250868=KnxJIi6qy6hA4%2FIbYmueTz
>>> c2NXpt0jjcEXlTtFjLjRM%3D=0>%7C8196919a76e24
>>> >168278c08d574d8f20d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%
>>> 7C0%7C636543397
>>> >479499116=MBzKg394LAJnmI436RNnHhj%2B13txLCjQ0WwmHcTlg
>>> Pw%3D=
>>> >0
>>> >
>>> >
>>> >--
>>> >Andrew Wetmore
>>> >
>>> >https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>> 2F%2Fcottage14.
>>> >blogspot.com>> ?url=http%3A%2F%2Fblogspot.com=02%7C01%7Caharui%
>>> 40adobe.com%7C8a249dea4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b3
>>> 4438794aed2c178decee1%7C0%7C0%7C636543610179250868=Mq6
>>> exixrepvjWqKpG%2FSrGwERSx08qv%2F02D5YNdUsYlc%3D=0>%

[GitHub] cottage14 closed pull request #8: Develop

[GitBox]

cottage14 closed pull request #8: Develop
URL: https://github.com/apache/royale-docs/pull/8
 
 
   


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 go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[GitBox]

cottage14 opened a new pull request #8: Develop
URL: https://github.com/apache/royale-docs/pull/8
 
 
   Fixing links


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 go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: How I can use multiple CSS files

[Carlos Rovira]

Hi Alex,

if as you said all pieces are in place, maybe I'm doing something wrong,
since I don't get it to work.

Can you check the current example in "feature/vivid" branch?

*First build "Vivid" project (in projects folder)*. Here only look to
"TextField" component. This component uses "TextField" type selector as
main css class. Then, it builds two subcomponents that uses "
vTextField--input" and "vTextField--label" (I'll check later when this
problem is solved what we said internal structure and see how much we can
make it as plain as possible, so this is temporal structure and mostly I'm
still experimenting to see results and implications of those results). In
this project I only want to add for now beads like a Model or
Controller...the rest View and css rules will go on theme project

*Then build theme project: VividBlueTheme (in projects folder)*. Here you
will have css rules mainly, svg, and beads that define visuals, like a View
bead. So we should not expect classes here, or only classes that create
visuals, but will have several .css files. Right now we have "defaults.css"
and "TextField.css".
I added the second along defaults to pom.xml



defaults.css
../src/main/resources/defaults.css


TextField.css
../src/main/resources/TextField.css



So the final swc has the right files. (If you unzip both files are in
place). As we solve this problem, we should see if we can merge all files
into one, to improve load performance.

*Finaly we have VividExample project (in example folder).* In this project
we are using vivid UI set in concrete 

I linked theme in pom.xml with


-theme=${basedir}/../../../frameworks/projects/VividBlueTheme/target/VividBlueTheme-${royale.framework.version}-js.swc


anad is working

This TextField should get *defaults.css* base styles (mainly model bead)
from Vivid.swc and styles from *TextField.css* (rest of css rules).

But this is not happen, since *TextField.css *in theme, although is
included in the theme .swc is not being used in the example

So I'm a bit lost at this point.

Hope you can let me know if this is a bug, or maybe I'm doing something
wrong

thanks!

Carlos




2018-02-15 10:25 GMT+01:00 Piotr Zarzycki :

> If you end up with the issue let's fill a bug on github! Let's track some
> things through the github issues.
>
> Piotr
>
> 2018-02-15 10:21 GMT+01:00 Alex Harui :
>
> > Right now, all css files are combined into one final css file.  If you
> > compile App.mxml, you will get an App.css with all selectors from all
> SWCs
> > that applied to the classes in the output.  I've actually been thinking
> > about changing that so that if you specify a css file in an fx:Style we
> > copy it as-is to the output folder.  That way you could update the source
> > CSS and copy it over and see the changes without a recompile.
> >
> > The code sure looks like if VividBlueTheme is listed in the -theme option
> > that the compiler would pick it up.  Did you actually look in the final
> > .css file?  It could be an ordering problem where some other css stomps
> on
> > the things you specified in VividBlueTheme.
> >
> > Also, unzip VividBlueTheme.swc and make sure the .css files are in the
> SWC.
> >
> > If that all looks good, post a small test case so I can look into it.
> >
> > -Alex
> >
> >
> > On 2/14/18, 11:16 PM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira"
> >  wrote:
> >
> > >Hi Alex,
> > >
> > >I'm a bit confused here. I created the thread since I'm already trying
> it.
> > >In VividBlueTheme, I added in pom.xml two 
> > >one for typical defaults.css and another for TextField.css
> > >Both, are in theme SWC thanks to maven build, at that point is ok.
> > >
> > >The problem is that final app is not using TextField.css, but is using
> > >defaults.css
> > >
> > >So I think I only need to know how defaults.css is been applied to be
> used
> > >in final example App and get Textfield.css be applied as well in the
> same
> > >way so the final user don't need to link in the final App.
> > >
> > >One thing that could be great to make this better is to make all
> > >components
> > >css files developed at "creation time" be joined into one single
> > >"defaults.css" file (or other name) for production purposes and remove
> the
> > >load of lots of css files. But this is an improvement over the first
> part
> > >
> > >thanks for looking into this
> > >
> > >
> > >
> > >
> > >2018-02-14 23:38 GMT+01:00 Alex Harui :
> > >
> > >> Hi Carlos,
> > >>
> > >> I looked at the compiler some more.  It appears that this feature
> > >>already
> > >> exists.  When I answered earlier, I was looking at code that loads
> SWCs
> > >> off the library path and the compiler only looks at defaults.css in
> > >>those
> > >> files, but I just saw that in SWCs specified as themes it will use
> every
> > >> .css file.
> > >>
> > >> Please try it and let 

Page linked to from license page no longer exists

[Andrew Wetmore]

Hi:

on Welcome/licenses.md there is this passage:

The map coordinates in examples/native/USStatesMap/src/MapCoords.as were
placed into the Public Domain by its author. See:
https://en.wikipedia.org/wiki/File:USA_CIA_Map.svg#file

When I click that link I get a message that the file has been deleted.
Since this is license-related, do we need to hunt out a replacement source?

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

[GitHub] cottage14 closed pull request #7: Develop

[GitBox]

cottage14 closed pull request #7: Develop
URL: https://github.com/apache/royale-docs/pull/7
 
 
   


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 go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[GitBox]

cottage14 opened a new pull request #7: Develop
URL: https://github.com/apache/royale-docs/pull/7
 
 
   Fixing links.


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 go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Website help doc links not working

[Andrew Wetmore]

The first issues we hit are on the index.md page. I did not write this page
or create the links there, so perhaps they were created before the file
names reached their current form. I will do a link sweep.

On Fri, Feb 16, 2018 at 6:07 AM, Andrew Wetmore  wrote:

> That's interesting, as I carefully matched the links to the file names
> when I created the links. Did the file names get changed at some point?
>
> On Fri, Feb 16, 2018 at 4:20 AM, Alex Harui 
> wrote:
>
>> Thanks Berty,
>>
>> Andrew, the link has to reference the correct file name.
>>
>> For "Features and Concepts", the file is currently named "Features And
>> Concepts" (note capital "A" in "And")
>> For "A Bit of History", I only see a file called history.md
>> For "Licenses and Policies", I only see a file called licenses.md
>>
>> We discussed file names such a while back, so maybe it is time for you to
>> sweep through and fix up the links.
>>
>> HTH,
>> -Alex
>>
>> From: Berty Tonta  berty.to...@leadstalk.pro>>
>> Reply-To: "dev@royale.apache.org" <
>> dev@royale.apache.org>
>> Date: Thursday, February 15, 2018 at 9:11 PM
>> To: "dev@royale.apache.org" <
>> dev@royale.apache.org>
>> Subject: Re: Website help doc links not working
>>
>> all links below "High Level View" not working
>>
>> [cid:ii_jdph8n600_1619d066ebfa59f8]
>> ​
>>
>> Berty Tonta
>> Sales Enablement Specialist
>>
>> [https://drive.google.com/uc?id=0B8FN9ycn20KId3I3WlJkSm0taHM
>> =download]
>> 4 BENGALI STREET, BEAU BASSIN, MAURITIUS
>> T +230 57 43 81 34 | berty.to...@leadstalk.pro> berty.to...@leadstalk.pro> | WWW.LEADSTALK.PRO> .safelinks.protection.outlook.com/?url=http%3A%2F%2FWWW.
>> LEADSTALK.PRO=02%7C01%7Caharui%40adobe.com%7C8a249de
>> a4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178decee1
>> %7C0%7C0%7C636543610179250868=l9s%2BqwJRmavSI9pqqJQjwD%2Bpn8hkH%
>> 2FvneEg2m4a%2BAl4%3D=0>
>> BRN 17149323
>>
>> On Fri, Feb 16, 2018 at 7:19 AM, Alex Harui > > wrote:
>> What do you mean by "links not working".  I went to the [1], clicked on
>> "High Level View" and ended up on a new page.
>>
>> -Alex
>>
>> On 2/15/18, 5:02 PM, "Andrew Wetmore" > ttag...@gmail.com>> wrote:
>>
>> >Almost all of the links on the help docs page [1] are not working.
>> >
>> >More than that, I am afraid that the pattern I thought was correct for
>> >linking from one page to another is not working; however, since I can't
>> >get
>> >past the first page I can't check.
>> >
>> >[1]
>> >https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fapache.gi
>> >thub.io> http%3A%2F%2Fthub.io=02%7C01%7Caharui%40adobe.com%7C8a
>> 249dea4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178d
>> ecee1%7C0%7C0%7C636543610179250868=6Hs%2BuQ7PH3H%
>> 2BftLhj3A%2FRq9zMZYuF9J%2FgtdJjwQZAlc%3D=0>%
>> 2Froyale-docs%2F=02%7C01%7Caharui%40adobe.com> na01.safelinks.protection.outlook.com/?url=http%3A%2F%
>> 2F40adobe.com=02%7C01%7Caharui%40adobe.com%7C8a249de
>> a4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178decee1
>> %7C0%7C0%7C636543610179250868=KnxJIi6qy6hA4%2FIbYmueTz
>> c2NXpt0jjcEXlTtFjLjRM%3D=0>%7C8196919a76e24
>> >168278c08d574d8f20d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%
>> 7C0%7C636543397
>> >479499116=MBzKg394LAJnmI436RNnHhj%2B13txLCjQ0WwmHcTlg
>> Pw%3D=
>> >0
>> >
>> >
>> >--
>> >Andrew Wetmore
>> >
>> >https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> 2F%2Fcottage14.
>> >blogspot.com> ?url=http%3A%2F%2Fblogspot.com=02%7C01%7Caharui%
>> 40adobe.com%7C8a249dea4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b3
>> 4438794aed2c178decee1%7C0%7C0%7C636543610179250868=Mq6
>> exixrepvjWqKpG%2FSrGwERSx08qv%2F02D5YNdUsYlc%3D=0>%
>> 2F=02%7C01%7Caharui%40adobe.com> protection.outlook.com/?url=http%3A%2F%2F40adobe.com=
>> 02%7C01%7Caharui%40adobe.com%7C8a249dea4c504c4cbe9408d5750a7
>> 7cb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63654361017
>> 9250868=KnxJIi6qy6hA4%2FIbYmueTzc2NXpt0jjcEXlTtFjLjRM%3D=0
>> >%7C8196919a76e24168278c08
>> >d574d8f20d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636
>> 543397479499116
>> >=dQZk%2Fci12V3lRl7VKbkSL965flWhdHg6ZiFS%2FkXmDEI%3D=0
>>
>>
>>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Website help doc links not working

[Andrew Wetmore]

That's interesting, as I carefully matched the links to the file names when
I created the links. Did the file names get changed at some point?

On Fri, Feb 16, 2018 at 4:20 AM, Alex Harui 
wrote:

> Thanks Berty,
>
> Andrew, the link has to reference the correct file name.
>
> For "Features and Concepts", the file is currently named "Features And
> Concepts" (note capital "A" in "And")
> For "A Bit of History", I only see a file called history.md
> For "Licenses and Policies", I only see a file called licenses.md
>
> We discussed file names such a while back, so maybe it is time for you to
> sweep through and fix up the links.
>
> HTH,
> -Alex
>
> From: Berty Tonta  pro>>
> Reply-To: "dev@royale.apache.org" <
> dev@royale.apache.org>
> Date: Thursday, February 15, 2018 at 9:11 PM
> To: "dev@royale.apache.org" <
> dev@royale.apache.org>
> Subject: Re: Website help doc links not working
>
> all links below "High Level View" not working
>
> [cid:ii_jdph8n600_1619d066ebfa59f8]
> ​
>
> Berty Tonta
> Sales Enablement Specialist
>
> [https://drive.google.com/uc?id=0B8FN9ycn20KId3I3WlJkSm0taHM;
> export=download]
> 4 BENGALI STREET, BEAU BASSIN, MAURITIUS
> T +230 57 43 81 34 | berty.to...@leadstalk.pro berty.to...@leadstalk.pro> | WWW.LEADSTALK.PRO na01.safelinks.protection.outlook.com/?url=http%3A%2F%
> 2FWWW.LEADSTALK.PRO=02%7C01%7Caharui%40adobe.com%
> 7C8a249dea4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636543610179250868=l9s%2BqwJRmavSI9pqqJQjwD%
> 2Bpn8hkH%2FvneEg2m4a%2BAl4%3D=0>
> BRN 17149323
>
> On Fri, Feb 16, 2018 at 7:19 AM, Alex Harui  mailto:aha...@adobe.com.invalid>> wrote:
> What do you mean by "links not working".  I went to the [1], clicked on
> "High Level View" and ended up on a new page.
>
> -Alex
>
> On 2/15/18, 5:02 PM, "Andrew Wetmore"  ttag...@gmail.com>> wrote:
>
> >Almost all of the links on the help docs page [1] are not working.
> >
> >More than that, I am afraid that the pattern I thought was correct for
> >linking from one page to another is not working; however, since I can't
> >get
> >past the first page I can't check.
> >
> >[1]
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fapache.gi
> >thub.io com/?url=http%3A%2F%2Fthub.io=02%7C01%7Caharui%40adobe.com%
> 7C8a249dea4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636543610179250868=6Hs%2BuQ7PH3H%2BftLhj3A%
> 2FRq9zMZYuF9J%2FgtdJjwQZAlc%3D=0>%2Froyale-docs%
> 2F=02%7C01%7Caharui%40adobe.com protection.outlook.com/?url=http%3A%2F%2F40adobe.com=
> 02%7C01%7Caharui%40adobe.com%7C8a249dea4c504c4cbe9408d5750a77cb%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636543610179250868=
> KnxJIi6qy6hA4%2FIbYmueTzc2NXpt0jjcEXlTtFjLjRM%3D=0>%
> 7C8196919a76e24
> >168278c08d574d8f20d%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636543397
> >479499116=MBzKg394LAJnmI436RNnHhj%2B13txLCjQ0WwmHcTlgPw%3D&
> reserved=
> >0
> >
> >
> >--
> >Andrew Wetmore
> >
> >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14
> .
> >blogspot.com com/?url=http%3A%2F%2Fblogspot.com=02%7C01%7Caharui%40adobe.com%
> 7C8a249dea4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636543610179250868=Mq6exixrepvjWqKpG%
> 2FSrGwERSx08qv%2F02D5YNdUsYlc%3D=0>%2F=02%7C01%7Caharui%
> 40adobe.com 2F40adobe.com=02%7C01%7Caharui%40adobe.com%
> 7C8a249dea4c504c4cbe9408d5750a77cb%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636543610179250868=KnxJIi6qy6hA4%
> 2FIbYmueTzc2NXpt0jjcEXlTtFjLjRM%3D=0>%7C8196919a76e24168278c08
> >d574d8f20d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636543397479499116
> >=dQZk%2Fci12V3lRl7VKbkSL965flWhdHg6ZiFS%2FkXmDEI%3D=0
>
>
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Website help doc links not working

[Alex Harui]

Thanks Berty,

Andrew, the link has to reference the correct file name.

For "Features and Concepts", the file is currently named "Features And 
Concepts" (note capital "A" in "And")
For "A Bit of History", I only see a file called history.md
For "Licenses and Policies", I only see a file called licenses.md

We discussed file names such a while back, so maybe it is time for you to sweep 
through and fix up the links.

HTH,
-Alex

From: Berty Tonta >
Reply-To: "dev@royale.apache.org" 
>
Date: Thursday, February 15, 2018 at 9:11 PM
To: "dev@royale.apache.org" 
>
Subject: Re: Website help doc links not working

all links below "High Level View" not working

[cid:ii_jdph8n600_1619d066ebfa59f8]
​

Berty Tonta
Sales Enablement Specialist

[https://drive.google.com/uc?id=0B8FN9ycn20KId3I3WlJkSm0taHM=download]
4 BENGALI STREET, BEAU BASSIN, MAURITIUS
T +230 57 43 81 34 | 
berty.to...@leadstalk.pro | 
WWW.LEADSTALK.PRO
BRN 17149323

On Fri, Feb 16, 2018 at 7:19 AM, Alex Harui 
> wrote:
What do you mean by "links not working".  I went to the [1], clicked on
"High Level View" and ended up on a new page.

-Alex

On 2/15/18, 5:02 PM, "Andrew Wetmore" 
> wrote:

>Almost all of the links on the help docs page [1] are not working.
>
>More than that, I am afraid that the pattern I thought was correct for
>linking from one page to another is not working; however, since I can't
>get
>past the first page I can't check.
>
>[1]
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.gi
>thub.io%2Froyale-docs%2F=02%7C01%7Caharui%40adobe.com%7C8196919a76e24
>168278c08d574d8f20d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636543397
>479499116=MBzKg394LAJnmI436RNnHhj%2B13txLCjQ0WwmHcTlgPw%3D=
>0
>
>
>--
>Andrew Wetmore
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.
>blogspot.com%2F=02%7C01%7Caharui%40adobe.com%7C8196919a76e24168278c08
>d574d8f20d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636543397479499116
>=dQZk%2Fci12V3lRl7VKbkSL965flWhdHg6ZiFS%2FkXmDEI%3D=0