StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I normally write the code in a <code>CDATA</code> block inside the <code><mx:script/></code> tag itself. </p> <pre><code><mx:Script source="code.as"> <![CDATA[ //code here ]]> </mx:Script> </code></pre> <p>This is the way it is done in most of the tutorials and Adobe code samples out there. An mxml file represents an ActionScript <code>class</code> (the file design.mxml creates a class named <code>design</code> in the root package) and hence I believe it makes sense to put the whole code in one place (file) - this is a matter of choice though. </p> <p>If user interface parts in a component are minimal, you can create that component using just an AS file. Checkout the code for a panel with a text input and a button in it:</p> <pre><code>//MyPanel.as inside /your/folder/structure package your.folder.structure { //import appropriate classes here public class MyPanel extends Panel { [Bindable] public var txt:TextInput; [Bindable] public var btn:Button; public function MyPanel(){} override protected function createChildren():void { txt = new TextInput(); txt.text = "Default text"; txt.setStyle("color", 0xffff00); addChild(txt); btn = new Button(); btn.label = "Click me!" btn.addEventListener(MouseEvent.CLICK, handleClick); addChild(btn); } private function handleClick(e:MouseEvent):void { trace("clicked"); } } } </code></pre> <p>And the (almost) equivalent mxml code would be:</p> <pre><code> <?xml version="1.0" encoding="utf-8"?> <mx:Panel xmlns:mx="http://www.adobe.com/2006/mxml" xmlns="your.folder.structure.*"> <mx:TextInput id="txt" text="Default text" color="#ffff00"/> <mx:Button id="btn" label="Click me!" click="handleClick(event);"/> <mx:Script source="code.as"> <![CDATA[ private function handleClick(e:MouseEvent):void { trace("clicked"); } ]]> </mx:Script> </mx:Panel> </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload