This is an automated email from the ASF dual-hosted git repository. andreww 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 b3337c8 Update mxml.md b3337c8 is described below commit b3337c89d362ea01d74acfc40a64bdf0a01ef284 Author: Andrew Wetmore <and...@cottage14.com> AuthorDate: Sat Apr 25 20:08:38 2020 -0300 Update mxml.md More to come --- features/mxml.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/features/mxml.md b/features/mxml.md index 974bb0d..ecaa000 100644 --- a/features/mxml.md +++ b/features/mxml.md @@ -91,7 +91,7 @@ The more complex the application is, the more things the main MXML file needs to Your main MXML file has two essential elements: -**the header**: In the example above, the header tag `<?xml version="1.0" encoding="utf-8"?>` has two parts: +**The header**: In the example above, the header tag `<?xml version="1.0" encoding="utf-8"?>` has two parts: - **XML declaration**: this tells the compiler what version of XML the file is using. 1.0 is the default; but since other versions exist, you have to specify it. - **The encoding**: this tells the compiler what text encoding to use to translate the bits of code into letters and numbers to display in the UI. The default is `utf-8`, but some applications use different encodings that suit their specific needs. @@ -121,7 +121,13 @@ A lot happens inside the main tag, and things can get complicated. The following **Metadata**: Add additional information to classes, properties, or methods to use at runtime inside the `<fx:Metadata>...</fx:Metadata>` tag. <a href="https://apache.github.io/royale-docs/features/as3/metadata">Learn more</a>. +**Styles**: Declare the styles the app uses in the `<fx:Styles>...</fx:Styles>` tag. + **Functions, property definitions, and other features**: Declare properties, instantiate components, and write functions inside the `<fx:Script>...</fx:Script>` tag. In the component example above, we declare an _event handler_, a function that does things when you click one of the buttons in the user interface. +**Beads**: Royale components generally follow the <a href="https://apache.github.io/royale-docs/features/payg" target="_blank">PAYG</a> principle of starting out with just enough functionality to do the basic things you would expect of them. If you want a component to do more, you add a <a href="https://apache.github.io/royale-docs/features/strands-and-beads" target="_blank">bead</a> with extra functions to it, as if the component were a thread. This way, only the components that need a [...] + +**User interface**: +