DOCSLIB.ORG

Actionscript 3 Language Specification

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Actionscript 3 Language Specification Actionscript 3 Language Specification Editor: Jeff Dyer Co-editors: Edwin Smith Gary Grossman Francis Cheng Revision History: November 14, 2005 Intial proposal submited to Ecma TC39/TG1 Purpose and status of this document This document defines the Actionscript 3 (AS3) language that is designed to be forward compatible with the next edition of ECMA-262. It serves as Macromedia’s initial proposal for the definition of Ecma-262 edition 4. Actionscript 3 Language Specification 1 of 139 Macromedia, Inc. Contents 1 Tutorial introduction .............................................................................................................................................. 7 1.1 Hello world ....................................................................................................................................................... 7 1.2 Expressions ....................................................................................................................................................... 7 1.3 Statements ......................................................................................................................................................... 7 1.4 Variables ............................................................................................................................................................ 7 1.5 Functions ........................................................................................................................................................... 8 1.6 Classes ................................................................................................................................................................ 8 1.7 Interfaces ........................................................................................................................................................... 8 1.8 Packages ............................................................................................................................................................ 9 1.9 Namespaces ...................................................................................................................................................... 9 2 Design perspective ............................................................................................................................................... 11 2.1 Compatibility with existing programs ........................................................................................................ 11 2.2 Compatibility with existing object models ................................................................................................. 11 2.3 Controlling the visibility of names .............................................................................................................. 11 2.4 Choosing between reliability and flexibility .............................................................................................. 11 3 Phases and dialects of interpretation ................................................................................................................. 13 3.1 Parsing ............................................................................................................................................................. 13 3.2 Verifying .......................................................................................................................................................... 13 3.2.1 Compile time constant expressions ...................................................................................................... 13 3.3 Evaluating ....................................................................................................................................................... 13 3.4 Strict verification ............................................................................................................................................ 13 3.4.1 Type errors ................................................................................................................................................ 14 3.4.2 Strict errors ............................................................................................................................................... 14 4 Fundamental Concepts ........................................................................................................................................ 15 4.1 Notation ........................................................................................................................................................... 15 4.2 Data .................................................................................................................................................................. 15 4.2.1 Objects ....................................................................................................................................................... 15 4.2.2 Names ........................................................................................................................................................ 15 4.2.3 Prototypes and delegates ........................................................................................................................ 15 4.2.4 Properties .................................................................................................................................................. 15 4.2.5 Slots ............................................................................................................................................................ 15 4.2.6 Traits .......................................................................................................................................................... 16 4.2.7 Methods .................................................................................................................................................... 17 4.2.8 Lexical environment ................................................................................................................................ 17 4.2.9 References ................................................................................................................................................. 17 4.2.10 Native classes ........................................................................................................................................... 18 4.3 Procedures ....................................................................................................................................................... 19 4.3.1 Reading ..................................................................................................................................................... 19 4.3.2 Writing ...................................................................................................................................................... 20 4.3.3 Calling ....................................................................................................................................................... 20 4.3.4 Constructing ............................................................................................................................................. 21 4.3.5 Deleting ..................................................................................................................................................... 22 4.3.6 Naming ...................................................................................................................................................... 22 4.3.7 Typing ....................................................................................................................................................... 23 4.3.8 Converting ................................................................................................................................................ 23 4.3.9 Checking ................................................................................................................................................... 24 4.3.10 Operating .................................................................................................................................................. 24 5 Names .................................................................................................................................................................... 28 5.1 Definition names ............................................................................................................................................ 28 5.2 Reference names ............................................................................................................................................. 28 5.3 Name lookup .................................................................................................................................................. 29 5.3.1 Object references ...................................................................................................................................... 29 5.3.2 Lexical references ..................................................................................................................................... 30 6 Types ...................................................................................................................................................................... 32 6.1 Run time versus compile time type ............................................................................................................
Load more

Recommended publications
  • Haxe Game Development Essentials
    F re e S a m p le Community Experience Distilled Haxe Game Development Essentials Create games on multiple platforms from a single codebase using Haxe and the HaxeFlixel engine Jeremy McCurdy In this package, you will find: The author biography A preview chapter from the book, Chapter 1 'Getting Started' A synopsis of the book’s content More information on Haxe Game Development Essentials About the Author Jeremy McCurdy is a game developer who has been making games using ActionScript, C#, and Haxe for over four years. He has developed games targeted at iOS, Android, Windows, OS X, Flash, and HTML5. He has worked on games that have had millions of gameplay sessions, and has built games for many major North American television networks. He is the games technical lead at REDspace, an award-winning interactive studio that has worked for some of the world's largest brands. They are located in Nova Scotia, Canada, and have been building awesome experiences for 15 years. Preface Developing games that can reach a wide audience can often be a serious challenge. A big part of the problem is fi guring out how to make a game that will work on a wide range of hardware and operating systems. This is where Haxe comes in. Over the course of this book, we'll look at getting started with Haxe and the HaxeFlixel game engine, build a side-scrolling shooter game that covers the core features you need to know, and prepare the game for deployment to multiple platforms. After completing this book, you will have the skills you need to start producing your own cross-platform Haxe-driven games! What this book covers Chapter 1, Getting Started, explains setting up the Haxe and HaxeFlixel development environment and doing a quick Hello World example to ensure that everything is working.
    [Show full text]
  • Rich Internet Applications
    Rich Internet Applications (RIAs) A Comparison Between Adobe Flex, JavaFX and Microsoft Silverlight Master of Science Thesis in the Programme Software Engineering and Technology CARL-DAVID GRANBÄCK Department of Computer Science and Engineering CHALMERS UNIVERSITY OF TECHNOLOGY UNIVERSITY OF GOTHENBURG Göteborg, Sweden, October 2009 The Author grants to Chalmers University of Technology and University of Gothenburg the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the Work electronically and make it accessible on the Internet. Rich Internet Applications (RIAs) A Comparison Between Adobe Flex, JavaFX and Microsoft Silverlight CARL-DAVID GRANBÄCK © CARL-DAVID GRANBÄCK, October 2009. Examiner: BJÖRN VON SYDOW Department of Computer Science and Engineering Chalmers University of Technology SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 Department of Computer Science and Engineering Göteborg, Sweden, October 2009 Abstract This Master's thesis report describes and compares the three Rich Internet Application !RIA" frameworks Adobe Flex, JavaFX and Microsoft Silverlight.
    [Show full text]
  • Framework Overview with UML Diagrams
    Framework Overview with UML Diagrams Learn to Build Robust, Scalable and Maintainable Applications using PureMVC Framework Overview This document discusses the classes and interfaces of the PureMVC framework; illustrating their roles, responsibilities and collaborations with simple UML (Unified Modeling Language) diagrams. The PureMVC framework has a very narrow goal. That is to help you separate your application’s coding concerns into three discrete tiers; Model, View and Controller. In this implementation of the classic MVC design meta-pattern, the application tiers are represented by three Singletons (a class where only one instance may be created). A fourth Singleton, the Façade, simplifies development by providing a single interface for communications throughout the application. The Model caches named references to Proxies, which expose an API for manipulating the Data Model (including data retrieved from remote services). The View primarily caches named references to Mediators, which adapt and steward the View Components that make up the user interface. The Controller maintains named mappings to Command classes, which are stateless, and only created when needed. The Façade initializes and caches the Core actors (Model, View and Controller), and provides a single place to access all of their public methods. AUTHOR: Cliff Hall <[email protected]> LAST MODIFIED: 3/05/2008 Façade and Core The Façade class makes it possible for the Proxies, Mediators and Commands that make up most of our final application to talk to each other in a loosely coupled way, without having to import or work directly with the Core framework actors. When we create a concrete Façade implementation for our application, we are able to use the Core actors ‘out of the box’, incidental to our interaction with the Façade, minimizing the amount of API knowledge the developer needs to have to be successful with the framework.
    [Show full text]
  • Actionscript 3.0 from the Ground up Tour
    Adobe Presents Colin Moock’s ActionScript 3.0 From the Ground Up Tour Materials provided by O’Reilly Media, Inc. Welcome Key Learning Welcome to the ActionScript 3.0: From the Ground Up Tour! In collaboration with Colin Moock, FITC Design and Technology The following table lists some of today’s most important concepts. Events, O’Reilly, and participating academic institutions around the world, Adobe is thrilled to bring you this world-class day of training. Following the tradition of Flex Camp (http://flex.org/camp/) and the onAIR bus tour (http://onair.adobe.com/), this Concept Example lecture is an important part of Adobe’s ongoing initiative to bring knowledge to the development community. Classes are blueprints for objects. class VirtualPet { At Adobe, we understand that a tool is only useful when you know how to use it. And we’re committed to helping you gain that knowledge. So sit back, get ready for a high-paced day of learning, and most of all have fun! } Objects (or instances) are the things in a program, new VirtualPet() Links and Resources such as a number, a car, a button, a point in time The entire set of notes for today’s lecture are available at: Some classes are built into ActionScript, others are MovieClip, TextField, Sound, String custom-made. http://moock.org/lectures/groundUpAS3 A package contains a class so its name doesn’t package zoo { The code for the virtual zoo application can be obtained at: conflict with other names. class VirtualPet { http://moock.org/eas3/examples/moock_eas3_examples/virtualzoo_final } For a prose version of today’s lecture in book form, see Colin Moock’s Essential ActionScript 3.0 (O’Reilly, 2007).
    [Show full text]
  • Slideshowpro for Flash Customization Guide
    SlideShowPro for Flash Customization Guide (Version 1.8.x) Contents Introduction.......................................................................................................................................................................................3 Customization.basics....................................................................................................................................................................4 How.to:.SlideShowPro.for.Flash.Button.Packs..................................................................................................................5 How.to:.Custom.navigation.buttons...................................................................................................................................... 7 How.to:.Embed.SWF.in.a.separate.HTML.document.....................................................................................................9 How.to:.External.navigation.....................................................................................................................................................12 How.To:.Change.default.English.text....................................................................................................................................13 How.to:.Prevent.XML.caching................................................................................................................................................. 14 How.to:.Dynamically.assign.an.XML.file..............................................................................................................................15
    [Show full text]
  • Enterprise Development with Flex
    Enterprise Development with Flex Enterprise Development with Flex Yakov Fain, Victor Rasputnis, and Anatole Tartakovsky Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo Enterprise Development with Flex by Yakov Fain, Victor Rasputnis, and Anatole Tartakovsky Copyright © 2010 Yakov Fain, Victor Rasputnis, and Anatole Tartakovsky.. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mary E. Treseler Indexer: Ellen Troutman Development Editor: Linda Laflamme Cover Designer: Karen Montgomery Production Editor: Adam Zaremba Interior Designer: David Futato Copyeditor: Nancy Kotary Illustrator: Robert Romano Proofreader: Sada Preisch Printing History: March 2010: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Enterprise Development with Flex, the image of red-crested wood-quails, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information con- tained herein.
    [Show full text]
  • Here Are the Slides
    Working with SWX: The Native Data Format for the Flash Platform R. Jon MacDonald http://jonnymac.com/blog 1 Welcome to Working with SWX - The Native Data Format for the Flash Platform I’m Jon MacDonald and... ...I’ve been working with SWX since its first beta release. [NEXT] Who Am I? • Director, JonnyMac Interactive • Interactive Development Manager, XPLANE • Open Source Contributor • Project Manager and Lead of SWX 2 But... Who Am I? I’m the Director of JonnyMac Interactive. We are a collective of interactive designers and developers out of Portland, Oregon in the United States I am also the Interactive Development Manager for XPLANE... ...a company that visualizes complex information and processes for Fortune 500 companies. I am an avid open source consumer... ...and contributor... ...to projects such as SWX, SWFAddress and more. Lastly, I am the Project Manager and Lead of the SWX project. [NEXT] What is SWX? • Data format for Flash • Native • Data is delivered in a SWF shell • The SWX format is a subset of the SWF format (just like JSON is a subset of JavaScript) 3 So... what is SWX? SWX is a data format for Flash. SWX is native. It is the MOST native format for Flash -- because SWX stores its data inside a SWF “shell”. You can think of the SWX format as a subset of the SWF format... ...just like JSON is a subset of JavaScript. [NEXT] Why SWX? • Nothing to deserialize, parse, massage • Simple mash-ups via free public gateway • Support for several APIs • Flickr, Twitter, Nabaztag, more • Runs on any platform that supports Flash 6+ 4 Let’s talk about why SWX was started..
    [Show full text]
  • How to Get Started with Actionscript Actionscript 3.0 Is the Scripting Language of Adobe Flash Professional
    Adobe Flash Professional Guide How to get started with ActionScript ActionScript 3.0 is the scripting language of Adobe Flash Professional. You can use ActionScript to add complex interactivity, playback control, and data display to your application. For example, you might want to animate a picture of a boy walking. By adding ActionScript, you could have the animated boy follow the pointer around the screen, stopping whenever he collides with a piece of animated furniture. ActionScript is an object-oriented programming language. Object-oriented programming is a way to organize the code in a program, using code to define objects and then sending messages back and forth between those objects. You don’t have to be a programmer to take advantage of ActionScript (see “Using Script Assist mode” later in this guide). But the following concepts will help: • Class: The code that defines an object. This code consists of properties, methods, and events. Think of the blueprint of a house: you can’t live in the blueprint, but you need it so you can build the house. You use classes to create objects. • Object: An instance of a class. When you instantiate an object (create an instance of it), you declare what class it is created from and set its properties. You can create as many objects as you want from a single class—if you have a bicycle class, you can create many bicycle objects, each with its own properties (one bicycle might be red while another might be green). • Property: One of the pieces of data bundled together in an object.
    [Show full text]
  • Puremvc Actionscript 3 Framework User Guide
    FoxR PureMVC ActionScript 3 Framework User Guide Version 0.2.1 Copyright 2009 Jeff Fox. Last Updated 12/9/2009 Outline Basic Info • Requirements • License Agreement • Change Log • Credits Installation • Downloading FoxR • Installation Instructions • Upgrading from an Previous Version • Troubleshooting Introduction • Getting Started • At a Glance • Supported Features • Application Flow Chart • Model-View-Controller • Architectural Goals • Roadmap General Topics • Code vs. Visual Architecture • Configuring FoxR (Global, Local and FlashVars) • Element and CompoundElement • Global Variables and Constants • Using CSS • Setting Fonts and copy • Visual Configuration • Analytics • Logging • Adapters • Utilities • Component Library • Media Library • Images • Working with XML Building Flash Web Sites with FoxR Building RIAs with FoxR I. Basic Info Requirements • Knowledge or proficiency with ActionScript 3 programming • Flash Compiler o Flex SDK (version 4 recommended for all users) o Eclipse w Flex Builder Plug-in o Flex Builder 2 or 3 OR Flash Builder 4 o HaXe compiler (www.haxe.org) • Knowledge or proficiency with MVC design and programming and the PureMVC Framework. (STRONGLY RECOMMENDED) • ActionScript IDE (RECOMMENDED) o Flash Develop (Win) o Eclipse with Flex Plug-in OR Flex/Flash Builder (Mac/Unix) o Flash CS3 or higher License Agreement The MIT License Copyright (c) 2009 Jeff Fox Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
    [Show full text]
  • ADOBE® CREATIVE SUITE® 3 WEB STANDARD Streamline Web Design, Development, and Maintenance
    Datasheet ADOBE® CREATIVE SUITE® 3 WEB STANDARD StreaMLine web design, deveLOPMent, and Maintenance Adobe Creative Suite 3 Web Standard software is the basic toolkit for web designers and developers. It offers all-new versions of fundamental tools for creating and maintaining interactive websites, applications, and mobile device content. Prototype your projects, design assets, and build and maintain professional web experiences. Get the fundamental tools Enjoy the latest workflows Move from concept to completion with Use the integrated tools in Creative Suite 3 Adobe Creative Suite 3 Web Standard software. Web Standard to refine your current skillset Adobe Creative Suite 3 Web Standard combines Adobe Bridge Design assets and build your prototype with while expanding into exciting new techniques CS3, Adobe Version Cue® CS3, Adobe Fireworks® CS3 software. Bring your and technologies. Catch the wave of online Adobe Device Central CS3, Adobe project to life with Adobe Dreamweaver® CS3 video with sophisticated web video tools, or Stock Photos, and Adobe Acrobat® and Adobe Flash® CS3 Professional, the preferred explore new opportunities in mobile content Connect™ with: web design and development tools. Easily design. Reach into development with the Spry • Adobe Dreamweaver CS3 maintain the final project and integrate user- framework for Ajax and new ActionScript™ 3.0 • Adobe Flash CS3 Professional generated content with Adobe Contribute® language for Flash. With Creative Suite 3 Web • Adobe Fireworks CS3 • Adobe Contribute CS3 CS3. Creative Suite 3 Web Standard combines Standard, the future is yours. the fundamental web tools, all in one place. Consider Adobe Creative Suite 3 Discover intelligent integration Web Premium Take advantage of tight integration between Adobe Creative Suite 3 Web your core tools, so you can forget the software Premium software is a complete and focus on the project.
    [Show full text]
  • Flashdetect: Actionscript 3 Malware Detection
    FlashDetect: ActionScript 3 malware detection Timon Van Overveldt1, Christopher Kruegel23, and Giovanni Vigna23 1 Katholieke Universiteit Leuven, Belgium, [email protected] 2 University of California, Santa Barbara, USA, {chris,vigna}@cs.ucsb.edu 3 Lastline, Inc. Abstract. Adobe Flash is present on nearly every PC, and it is in- creasingly being targeted by malware authors. Despite this, research into methods for detecting malicious Flash files has been limited. Similarly, there is very little documentation available about the techniques com- monly used by Flash malware. Instead, most research has focused on JavaScript malware. This paper discusses common techniques such as heap spraying, JIT spraying, and type confusion exploitation in the context of Flash mal- ware. Where applicable, these techniques are compared to those used in malicious JavaScript. Subsequently, FlashDetect is presented, an off- line Flash file analyzer that uses both dynamic and static analysis, and that can detect malicious Flash files using ActionScript 3. FlashDetect classifies submitted files using a naive Bayesian classifier based on a set of predefined features. Our experiments show that FlashDetect has high classification accuracy, and that its efficacy is comparable with that of commercial anti-virus products. Keywords: Flash exploit analysis, malicious ActionScript 3 detection, Flash type confusion 1 Introduction Adobe Flash is a technology that provides advanced video playback and anima- tion capabilities to developers through an advanced scripting language. The files played by Flash, called SWFs, are often embedded into webpages to be played by a browser plugin, or are embedded into a PDF file to be played by a copy of the Flash Player included in Adobe’s Acrobat Reader.
    [Show full text]
  • ADOBE® CREATIVE SUITE® 3 WEB PREMIUM Redefine the Extraordinary in Web Design and Development
    Datasheet ADOBE® CREATIVE SUITE® 3 WEB PREMIUM RedeFINE THE EXtraordiNarY IN web desigN AND deveLopmeNT Adobe Creative Suite 3 Web Premium software is a complete solution for creating interactive websites, applications, user interfaces, presentations, mobile device content, and other digital experiences. Get everything you need to prototype your project, design assets, build web experiences, and efficiently maintain and update content. Get the essential tools compatibility between Dreamweaver and Finally, all your favorite tools are in one Contribute. Organize your assets with Adobe Adobe Creative Suite 3 Web solution. Design core assets and build your Bridge CS3, and coordinate your team with Premium combines Adobe Bridge prototype with Adobe Photoshop® CS3 Adobe Version Cue CS3. CS3, Adobe Version Cue® CS3, Extended, Adobe Illustrator® CS3, and Adobe Enjoy the latest workflows Adobe Device Central CS3, Adobe Fireworks® CS3 software. Then bring your Never before have there been so many Stock Photos, and Adobe Acrobat® project to life with Adobe Dreamweaver® CS3 opportunities for designers and developers to Connect™ with: and Adobe Flash® CS3 Professional, the • Adobe Dreamweaver CS3 refine their current skillset while expanding industry-leading web design and development • Adobe Flash CS3 Professional into exciting new techniques and technologies. • Adobe Photoshop CS3 Extended tools. Use Adobe Acrobat® 8 Professional Immerse yourself in online video creation • Adobe Illustrator CS3 software to quickly share design ideas and with sophisticated web video tools. • Adobe Fireworks CS3 collect feedback from colleagues and clients, • Adobe Acrobat 8 Professional Follow best practices with new CSS tools. and easily maintain the final project with • Adobe Contribute CS3 Explore the possibilities in mobile content Adobe Contribute® CS3.
    [Show full text]