]> ActionScript Manual V0.1 Gnash Introduction In this document, the term 'ActionScript class' refers to the C++ class which is instantiated by Gnash when some ActionScript code instantiates a corresponding class. The C++ class stores instance data and implements the methods which are called on the object in the ActionScript code. Object Creation Overview When Gnash starts, the class_init() method for each ActionScript class (listed in Global.cpp) is called. This method constructs a prototype, which is implemented as an as_object. In addition, the method registers the constructor to be used for future object creation, and attaches methods and properties to the prototype. When a new object is needed, instance data is added to the methods and properties inherited from the prototype. Adding New ActionScript Class Adding a new ActionScript class is relatively simple, but the process is complicated by the fact that the interface has evolved over time and the current code base represents several different formats. This document describes the current interface. The Boolean class should be considered the authoritative example of a modern ActionScript class. ActionScript classes contain a header file and a C++ implementation. The name is usually the name of the class as it is called in the ActionScript specifications; for instance Boolean.cpp for the Boolean class. In the CVS source tree, there is a utility file named gen-asclass.sh which can be used to create the header file and a C++ source file stub for an ActionScript class. Prototype In ActionScript, a prototype is a base object which contains all the methods that an instantiated object will contain. In short, it contains every part of the class except for the portions dealing with the storage of instance data. In Gnash, the prototype of an ActionScript object is implemented as an as_object. At startup, the methods and properties of the ActionScript class are attached to the as_object. The following example demonstrates how methods can be attached: static void attachBooleanInterface(as_object& o) { o.init_member("toString", new builtin_function(boolean_tostring)); o.init_member("valueOf", new builtin_function(boolean_valueof)); } This code was generated using gen-asclass.sh. Typically, you will need to customize the attach method to include any new methods you add to the class. Static properties can also be added to the ActionScript prototype (dynamic properties (see ) are addressed later). They are attached in a similar way: o.init_member("myProperty", as_value("HelloWorld")); Properties which have been added in this manner can be directly accessed in ActionScript code without a function call, as this piece of ActionScript code compiled by Ming's makeswf compiler demonstrates: // Get the value of the myProperty property if (node.myProperty == "HelloWorld") { trace("MATCHED"); } Declaration A new class should derive from as_object, which is the base class of every ActionScript object in Gnash. The class declaration will also be generated when you use gen-asclass.sh. Instantiation The class should contain an init method; this is included in the stub when gen-asclass.sh is used. The init method should be called in the constructor in Global.cpp, where all other ActionScript classes are similarly referenced. Methods Every method you implement and attach (see ) will receive an fn_call data structure as an argument when it is called. Accessing Arguments The arguments stored in fn_call should be accessed using arg(). For instance, the first element can be popped with fn.arg(0). The element popped off the stack is an as_value object (see ). Returning a Value to ActionScript The return value should be an as_value object (see ). For example: return as_value('Goodbye, cruel world.'); Additional fn_call Members There are two other useful members of the fn_call structure, namely this_ptr and nargs. The former points to the class which is invoking this method, while the latter is a count of the number of arguments in the stack (see ). You may also see instances of the env pointer being used. This is being deprecated. Instances which could be replaced with arg() (see ) are already deprecated; other uses will be deprecated in the near future. Beyond the arg() (see ) method, there is one method of note. dump_args() can be used in debugging to output the entire argument stack. Dynamic Properties This section describes accessors to dynamic properties. Read-only properties are described in the prototype (see ) section. Dynamic properties are not created by the gen-asclass.sh script. Accessors should be written as a single get/set method. Previously this was done by overriding get_member() and set_member(), but this practice is deprecated. The accessor is written so that it sets the property if it is called with an argument, and puts the property in the fn_call (see ) result pointer (see ). For instance: void MyClass::myProperty_getset(const fn_call& fn) { boost::intrusive_ptr<MyClass> ptr = ensureType<MyClass>(fn.this_ptr); // setter if ( fn.nargs > 0 ) { bool h = fn.arg(0).to_bool(); ptr->MyMethod(h); return; } // getter bool h = ptr->MyMethod(); fn.result->set_bool(h); } It has not yet been decided whether properties should be set in the exported interface (see ) or attached to instances of the class. A property is attached in the following manner: boost::intrusive_ptr<builtin_function> gettersetter; gettersetter = new builtin_function(&MyClass::myProperty_getset, NULL); o.init_property("myProperty", *gettersetter, *gettersetter); The as_value Object Type The as_value class is used throughout the interpreter to create generic objects to hold data. Data Types The following data types are supported: NULLTYPE, BOOLEAN, STRING, NUMBER, OBJECT, AS_FUNCTION, and MOVIECLIP (sprite). The type C_FUNCTION is being deprecated. Determining the Type Several methods allow you to determine if a value stored in as_value is of a specific type. These follow the form of is_TYPE, for example is_as_function() and is_number(). In general, the type names match the data types (see ) listed above, with the exception of the type MOVIECLIP which has a method is_sprite(). Fetching the Value Another set of methods will return a representation of the value as a particular type. They follow the to_TYPE naming convention. Examples are to_number() and to_bool(). The type names are as listed (see ) earlier, except for MOVIECLIP, which uses to_sprite(). Setting the Value and Type Finally, there is the set_TYPE series of methods. They change the type to the type specified in the method name, and set the value to the one given as an argument. It is also possible to accomplish the same thing with the = operator. Again, type names match those named earlier (see ), except in the case of MOVIECLASS. Its method is called set_sprite(). Further Reading Please refer to as_value.h or the Doxygen documentation (see 'Processing The Documentation' in the Gnash manual for instructions on generating documents with Doxygen) for more information about which methods are available for the as_value object. GNU Free Documentation License 0. PREAMBLE The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. A "Secondary Section" is a named appendix or a front-matter section of the Document (see ) that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The "Invariant Sections" are certain Secondary Sections (see ) whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document (see ) is released under this License. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document (see ) is released under this License. A "Transparent" copy of the Document (see ) means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text. 2. VERBATIM COPYING You may copy and distribute the Document (see ) in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3 (see ). You may also lend copies, under the same conditions stated above, and you may publicly display copies. 3. COPYING IN QUANTITY If you publish printed copies of the Document (see ) numbering more than 100, and the Document's license notice requires Cover Texts (see ), you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document (see ) and satisfy these conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. If you publish or distribute Opaque (see ) copies of the Document (see ) numbering more than 100, you must either include a machine-readable Transparent (see ) copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of the Document (see ) well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version (see ) of the Document (see ) under the conditions of sections 2 (see ) and 3 (see ) above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: A. Use in the TitlePage (see ) (and on the covers, if any) a title distinctfrom that of the Document (see ), and from those ofprevious versions (which should, if there were any, belisted in the History section of the Document). You mayuse the same title as a previous version if the originalpublisher of that version gives permission. B. List on the TitlePage (see ), as authors, one or more persons or entitiesresponsible for authorship of the modifications in theModified Version (see ),together with at least five of the principal authors ofthe Document (see ) (all ofits principal authors, if it has less than five). C. State on the TitlePage (see ) the name of the publisher of the Modified Version (see ), as thepublisher. D. Preserve all the copyright notices of the Document (see ). E. Add an appropriate copyright notice for your modificationsadjacent to the other copyright notices. F. Include, immediately after the copyright notices, alicense notice giving the public permission to use theModified Version (see ) underthe terms of this License, in the form shown in theAddendum below. G. Preserve in that license notice the full lists of Invariant Sections (see ) andrequired CoverTexts (see ) given in the Document's (see ) license notice. H. Include an unaltered copy of this License. I. Preserve the section entitled "History", andits title, and add to it an item stating at least thetitle, year, new authors, and publisher of the Modified Version (see )as given onthe Title Page (see ). Ifthere is no section entitled "History" in theDocument (see ), create onestating the title, year, authors, and publisher of theDocument as given on its Title Page, then add an itemdescribing the Modified Version as stated in the previoussentence. J. Preserve the network location, if any, given in the Document (see ) for public accessto a Transparent (see )copy of the Document, and likewise the network locationsgiven in the Document for previous versions it was basedon. These may be placed in the "History"section. You may omit a network location for a work thatwas published at least four years before the Documentitself, or if the original publisher of the version itrefers to gives permission. K. In any section entitled "Acknowledgements" or"Dedications", preserve the section's title,and preserve in the section all the substance and tone ofeach of the contributor acknowledgements and/ordedications given therein. L. Preserve all the InvariantSections (see ) of the Document (see ), unaltered in theirtext and in their titles. Section numbers or theequivalent are not considered part of the section titles. M. Delete any section entitled"Endorsements". Such a section may not beincluded in the ModifiedVersion (see ). N. Do not retitle any existing section as"Endorsements" or to conflict in title withany InvariantSection (see ). If the Modified Version (see ) includes new front-matter sections or appendices that qualify as Secondary Sections (see ) and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections (see ) in the Modified Version's license notice. These titles must be distinct from any other section titles. You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version (see ) by various parties–for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. You may add a passage of up to five words as a Front-Cover Text (see ), and a passage of up to 25 words as a Back-Cover Text (see ), to the end of the list of Cover Texts (see ) in the Modified Version (see ). Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document (see ) already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. The author(s) and publisher(s) of the Document (see ) do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version (see ). 5. COMBINING DOCUMENTS You may combine the Document (see ) with other documents released under this License, under the terms defined in section 4 (see ) above for modified versions, provided that you include in the combination all of the Invariant Sections (see ) of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice. The combined work need only contain one copy of this License, and multiple identical Invariant Sections (see ) may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgements", and any sections entitled "Dedications". You must delete all sections entitled "Endorsements." 6. COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document (see ) and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document (see ) or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version (see ) of the Document, provided no compilation copyright is claimed for the compilation. Such a compilation is called an "aggregate", and this License does not apply to the other self-contained works thus compiled with the Document , on account of their being thus compiled, if they are not themselves derivative works of the Document. If the Cover Text (see ) requirement of section 3 (see ) is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate. 8. TRANSLATION Translation is considered a kind of modification, so you may distribute translations of the Document (see ) under the terms of section 4 (see ). Replacing Invariant Sections (see ) with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail. 9. TERMINATION You may not copy, modify, sublicense, or distribute the Document (see ) except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. Each version of the License is given a distinguishing version number. If the Document (see ) specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. Addendum To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: Copyright YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections (see ) being LIST THEIR TITLES, with the Front-Cover Texts (see ) being LIST, and with the Back-Cover Texts (see ) being LIST. A copy of the license is included in the section entitled "GNU Free Documentation License". If you have no Invariant Sections (see ), write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts (see ), write "no Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise for Back-Cover Texts (see ). If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.