This is an automated email from the ASF dual-hosted git repository.
joshtynjala pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 44a3f16 added some cross-links
44a3f16 is described below
commit 44a3f163c2b2bdb0291a6ddb79ca652fd8b3609f
Author: Josh Tynjala <[email protected]>
AuthorDate: Fri Apr 26 18:06:43 2019 -0700
added some cross-links
---
Welcome/Features And Concepts.md | 6 +++---
Welcome/High Level View.md | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Welcome/Features And Concepts.md b/Welcome/Features And Concepts.md
index feba029..6fb7ab6 100644
--- a/Welcome/Features And Concepts.md
+++ b/Welcome/Features And Concepts.md
@@ -30,13 +30,13 @@ Royale uses both a declarative markup language called
[MXML](Welcome/Features/MX
Royale provides a variety of component sets, each tuned towards different
applications requirements. The easiest one to learn and use is the Express
component set. It is designed for rapid-prototyping and proof-of-concept
development. You can often take code using Express into production, but
because Express components are designed to be customized in MXML, as your
application grows in size, you may find yourself wishing for smaller, faster
components.
-Royale also provides a Basic component set that is the opposite of Express.
The components are small and fast, but don't have lots of built-in
customization options. This is because Basic components are designed with a
"Pay as you go" philosophy. Only the most common functionality is built into
the component, and other options are added as plugins called Beads. You can
read more about PAYG [here](Welcome/Features/PAYG.html).
+Royale also provides a Basic component set that is the opposite of Express.
The components are small and fast, but don't have lots of built-in
customization options. This is because Basic components are designed with a
["Pay as you go"](Welcome/Features/PAYG.html) philosophy. Only the most common
functionality is built into the component, and other options are added as
plugins called Beads. You can [read more about PAYG
here](Welcome/Features/PAYG.html).
## Strands and Beads
-It turns out that the Express components are really just Basic components with
lots of Beads packed into them by default. The underlying component patterns
in most Royale components rely on a plug-in model. Instead of making large
component classes with lots of code baked in, each individual feature of a
component is designed as its own class with an interface marking it as a
"Bead", and then the component itself is called a "Strand" and Beads are placed
on the Strand to compose a Roya [...]
+It turns out that the Express components are really just Basic components with
lots of Beads packed into them by default. The underlying component patterns
in most Royale components rely on a plug-in model. Instead of making large
component classes with lots of code baked in, each individual feature of a
component is designed as its own class with an interface marking it as a
"Bead", and then the component itself is called a "Strand" and Beads are placed
on the Strand to compose a Roya [...]
## Calling to/from external JavaScript code
-Sometimes you may want your Royale application to call an external piece of
JavaScript that is also hosted in your web page, or even for some extenal
JavaScript from your page to call into the Royale application. In the Flex (and
Flash) world, there was the possibility to use the "ExternalInterface" class to
achieve this functionality. If you want this in Royale, there are some options
available that you can read about
[here](Welcome/Features/external-interface.html).
+Sometimes you may want your Royale application to call an external piece of
JavaScript that is also hosted in your web page, or even for some extenal
JavaScript from your page to call into the Royale application. In the Flex (and
Flash) world, there was the possibility to use the "ExternalInterface" class to
achieve this functionality. If you want this in Royale, there are some options
available that you can [read about
here](Welcome/Features/external-interface.html).
diff --git a/Welcome/High Level View.md b/Welcome/High Level View.md
index 9dbb125..1db6987 100644
--- a/Welcome/High Level View.md
+++ b/Welcome/High Level View.md
@@ -27,8 +27,8 @@ While Flex may work using Flash in browsers or within AIR on
computers with trad
Beyond that, it is becoming clear that Royale can provide significant
developer productivity gains for new projects. Flex made it easy and efficient
to create robust applications. Like Flex, Royale provides:
-- Declarative Language (MXML) - Declarative languages provide a schematic, or
diagram. of the pieces of the application, and are more terse than options like
JavaScript.
-- Semi-Structured Language (ActionScript) - ActionScript deploys classes and
interfaces, so it can do a better job of enforcing correct use of APIs than
JavaScript can.
+- Declarative Language ([MXML](Welcome/Features/MXML.html)) - Declarative
languages provide a schematic, or diagram. of the pieces of the application,
and are more terse than options like JavaScript.
+- Semi-Structured Language ([ActionScript](Welcome/Features/AS3.html)) -
ActionScript deploys classes and interfaces, so it can do a better job of
enforcing correct use of APIs than JavaScript can.
- Runtime Verifier - The verifier catches errors at runtime so you can address
them before packaging a release.
- Choice of IDEs - You can choose the IDE that suits you best, and the IDEs
can provide better code assistance because the coding language is structured.
@@ -39,7 +39,7 @@ These features help you make fewer mistakes when writing
code, and that saves ti
<!-- Coming soon: LINK TO OM's UPDATED SLIDE SHOW
http://events.linuxfoundation.org/sites/events/files/slides/FlexJS_ApacheCon_2015.pdf
-->
## How it works
-Because both ActionScript and JavaScript are based on the same language,
ECMAScript, most code you write in AS translates well to JS. One significant
difference is that AS uses the concepts of classes and objects to structure how
your code functions, while pure JavaScript does not have those concepts. When
you get ready to compile and run your application, the Royale compiler
translates AS-specific code into JS code organized into pseudo-classes, which
then run just fine in a JavaScript world.
+Because both [ActionScript](Welcome/Features/AS3.html) and JavaScript are
based on the same language, ECMAScript, most code you write in AS translates
well to JS. One significant difference is that AS uses the concepts of classes
and objects to structure how your code functions, while pure JavaScript does
not have those concepts. When you get ready to compile and run your
application, the Royale compiler translates AS-specific code into JS code
organized into pseudo-classes, which then r [...]
That takes care of pretty much everything except the user interface. For that,
Royale provides a set of UI containers and controls that do the work that the
pure Flex containers and controls required the Flash engine to do.
