Projects tagged ‘air’ and ‘as2’

Tweener (caurina.transitions.Tweener) is a Class used to create tweenings and other transitions via ActionScript code for projects built on the Flash platform. It's released and maintained for these ... [More] versions: ActionScript 2.0, for Flash 7+ and Flash Lite 2.0+ ActionScript 2.0, for Flash 8+ ActionSctipt 3.0, for Flash 9+ Ported/inspired versions for other languages are also available: haXe version (ported by Baluta Cristian) JavaScript version (ported by Yuichi Tateno) JavaScript version (ported by Michael MacMillan) vvvv version using nodes vvvv version using a native C# dll (faster) (ported by by Rene Westhof) Python version (ported by Benjamin Harling) C++ version (ported by Wesley Marques) In layman's terms, Tweener helps you move things around on the screen using only code, instead of the timeline. The general idea of a tweening Class is that dynamic animation and transitions (created by code) are easier to maintain and control, and more stable than animation based on the regular Flash timeline, since you can control it by time rather than by frames. Aimed both for designers and advanced developers, the Tweener syntax is created with simplicity of use in mind, while still allowing access to more advanced features. Because of this, it follows a 'one-line' design mentality when creating new tweenings, with no instancing required (as it's a static Class) and a set of optional parameters. Also, there are no initialization methods required by Tweener, other than the mandatory 'import' command. Its fluid syntax allows it to be used to tween any numeric property of any object of any class, so it is not tied to specific properties of built-in Classes such as MovieClips or TextFields. This flexibility grants a wider control on how transitions are performed, and makes creating complex sequential transitions on any kind of object easier. Small file overhead is also one of the main goals of Tweener - once included on SWF movies, Tweener currently takes 8.8kb (AS2 FL2), 9.2kb (AS2) or 10.4kb (AS3) of the total compiled file size. It can be compiled with the Flash IDE, MTASC, or Flex SDK (even with strict rules on), with no errors or warnings thrown during compilation. Tweener is also the spiritual successor to MC Tween. However, it follows ActionScript's more strict OOP rules, and gets rid of the fixed parameter order syntax imposed by MC Tween. As a result, code written with Tweener is a lot more readable even for developers not versed on the Class. Development wise, modularity is one of the main aspects of Tweener. The code is built in a way that new features such as transitions and special tweenings can be added (or removed) easily: for example, properties that are only acessible through methods and functions can be tweened by creating and registering new special properties. Expanding the feature set of the original Class can be done on a per-project basis, with no change to the original files. From this page, you can download the latest stable (heavily tested) version of Tweener, check out a few examples with source, or read the documentation. There's also a mailing list for Tweener discussion. If you prefer, you can also get the very latest versions from Subversion, before they're considered stable and featured on the download list (the changelog is available here). The repository can also be viewed with a web browser. [Less]

AS3 rich graphic and geometric opensource library based on the Maashaack and VEGAS frameworks.

Network, media, text and display advanced tool library based on Maashaack and VEGAS.

KRONos is an OpenSource Framework based on ECMASCript and ActionScript technologies. This framework contains all time, date, calendar, appointment, task tools. SVN and sources comming soon !

UPDATE - Check out this project too: http://code.google.com/p/as3-commoncode/ Keep in mind this project is mainly for projects with just "Pure Actionscript" at heart, this project would need some ... [More] modifications to work within the "Adobe Flex Framework." It's setup more for a project with the IDE and .fla files. For the most part this project implements the Model, View, Controller - a Design Pattern that is scalable for most projects using an OOP process. It's a basic MVC structure with a method to apply, with assistance from the Preloader and Application classes. It's also very handy for productive workflow; as a good practice you can setup your model logic and application logic first once your data is ready. Then it's just a matter of displaying and controlling the representation of that model. So if needed, more than one developer can work on an application. Each developer can work on different views or components or states of the overall view. Without depending on controllers or other views, each view just has to listen for what it wants to from the model. Preloader The Preloader for the Application class best practice is to extend this class for your own preloader class and then add the frame command to your own application class which is extended from org.simplemvc.core.Application. Look at the example flash application directory for further explanation. Application This is the specific class that starts an application. It adds all the necessary views and sets the model up. This is where you will pass to the model what data to use and you will also pass the model to all the views in their own constructors. Model The Model component of the MVC design pattern handles and stores the data and application logic for the interface. It is recommended that the Model utilize a push only dispatching protocol in which it dispatches information to it's listeners through the event object. This happens without any knowledge of who or what is listening. It is recommended that this class is sub classed in order to communicate and manage application logic, however you can use it directly as well. View The View component of the MVC design pattern is a distinct representation of a Model's data and or logic. A view listens too and represents changes to the model for states of the application or logic. It is recommended that the views in an MVC system be unaware of the inner workings of the system's Model (ie. utilize a push only dispatching protocol in which the Model pushes information to it's listeners through the event object). It is the responsibility of each view to make sure it has a controller. The controller can either be passed in to the constructor or it will be automatically made by the view's. To create an MVC relationship; a model is created and a view is created which is then added as a listener of its associated model. The view primarily creates its own controller, but can use an existing one, this is not recommended. It will be necessary to extend this View class and the core controller method in order to make more specific view objects for specific view/controller pairings. Controller The Controller component of the MVC design pattern responds to user inputs by modifying the Model. A controller listens too its view for user inputs. If the data submitted by the view, affect the data and logic, it will report that information up to the model. Otherwise it should act directly back upon it's view ( i.e. onRollOver ). A Controller has a direct relationship with its view and the model the View represents. A Controller is generally only created by a View that will accept user input, and in some cases the View won't have the need for a Controller. If a view does not accept user input, and the default controller method is called, a null controller will be returned. [Less]

ThunderBoltOverview:ThunderBolt is a lightweight logger extension for ActionScript 2 and 3 applications using Firebug. For logging without Firebug, especially for AIR applications, check out the ... [More] ThunderBolt AS3 Console. For more information about ThunderBolt AS2 and ThunderBolt AS3 check out the Wiki. The ThunderBolt project based on the Mozilla Public License 1.1.. News + Updates:News and updates about ThunderBolt AS3 by Jens Krause on Twitter: 03/10/09: ThunderBolt? AS3 Console has been updated to version 2.2.1! issue 11 has been fixed 03/08/09: ThunderBolt? AS3 version 2.2! Logging of package names + class names + code line numbers (Flash Debug Player required), ThunderBoltTarget improved, SWC for Flex 4 (Gumbo) updated, all examples + documentation updated 03/06/09: ThunderBolt? AS3 Console has been updated to version 2.2! Updated to Adobe AIR 1.5.1, certificate of Thawte included - sponsored by Adobe - thanks!, version no. is visible at options, issue 10 has been fixed 08/23/08: ThunderBolt AS3 Console has been updated to version 2.1! new panel called "option " including new feature "always in front", auto update 08/03/08: ThunderBolt AS3 version 2.0 has been released! Firefox 3.0 supported Gumbo (Flex 4) supported ThunderBolt AS3 Console official release added. Happy Logging ;-) 06/01/08: ThunderBolt AS3 version 2.0 Beta has been released for logging Flex, AIR or Flash CS3 apps without Firebug using the new ThunderBolt AS3 Console. All examples based on Flex and Flash CS 3 has been updated too. Happy Logging ;-) 10/14/07: ThunderBolt AS3 version 1.0 has been released with new examples using Flex 2 and Flash CS 3 based on AS3. New features added (memory snapshot, stop logging flag) as well. Features:ThunderBolt AS3: Log levels: INFO, WARN, ERROR, DEBUG (FATAL, ALL) Tree view for complex object structures such as class identifier and its properties Logging of package names, class names, code line numbers (Flash Debug Player required) Custom LogTarget based on Flex Logging API including filters memory snapshot stop logging flag SWC components for logging using Flex 2/3/4, AIR or Flash CS3 ThunderBolt AS2: Detailed information (class, file, line number, time, frame) Log levels (info, warning, error, fatal) Interactive tree view for complex object structures Profiling (time spend during code execution) Collapsible grouped output Filter log by classes and packages Interactive console (inspect and modify object on runtime) Screenshot (ThunderBolt AS3 Console) Screenshot (ThunderBolt AS2) ContactThunderBolt AS2: Martin Kleppe - mail ThunderBolt AS3 + ThunderBolt AS3 Console: Jens Krause (aka sectore) - WEBSECTOR.DE [Less]

Ludicast is starting here a project for decompiling flash documents. We have 4 milestones: The generation of ASDocs based on filtered categories. The decompilation of SWFs previous to Flash 9. The ... [More] decompilation of Flash 9 SWFs. This will include a parser for the abc intermediate bytecode language. An obfuscator based on the previous steps. Basically, since every swf in the wild is decompilable (Adobe: this means Buzzword & Photoshop Express), and Intellectual Property is the lifeblood of most startups, we are doing this project to help the Flash community, not hurt it. One key aspect of this project is that it is written as a Flex/AIR project, making it easy for those who benefit from it to contribute. We feel that the sooner we have a working decompiler released, the sooner we will be able to provide a working obfuscator. Plus a working decompiler will alert developers of the risks inherent in publishing their SWFs prematurely. This will allow them to better gameplan their release schedule. Any questions, feel free to email Nate Kidwell. Some obvious projects we are drawing inspiration and sources from are: swfassist, tamarin, hurlant's decompiler. If anybody knows of any other relevant projects, let us know. Feel free to use this decompiler in any of your projects. If you want to contribute, there are three key ways: Pick a tag in the tags directory and start coding. Each tag describes a bit of flash functionality, such as actionscript, font infomation, embedded images and so forth. Something probably matches with your skillset Instrument the embedded webkit webbrowser to have a swfcatcher-like interface making it easier to capture swfs with a single click. This would require a bit of javascript magic. Research other projects such as swfassist for code that can be used. [Less]

AirTalkr

AS2, AS3, Air Code Library of the Swiss Flash User Group