Projects tagged ‘actionscript’ and ‘ioc’

You can use the same framework in ActionScript 1,2,3 and SSAS to deploy your RIAs.

Prana is an Inversion of Control (IoC) Container for ActionScript 3.0, and more specifically the Flex framework. It enables you to configure objects and components in a non-intrusive way by describing ... [More] them in an external xml document and having them loaded at runtime. At its core is a Spring-ish application context and IoC container. The xml dialect for the application context is aimed to be Spring compliant. Further, the framework also contains utility classes for configuring and extending Cairngorm and PureMVC applications, a Reflection API and general utilities. In the future we’ll be looking into adding AOP support and Mock objects for FlexUnit, and we’re always open for suggestions. [Less]

This library is an architectural framework extension based on VEGAS the ECMAScript & ActionScript opensource framework. AndromedAS implement a full IoC library based on an ECMAScript data exchange ... [More] notation. AndromedAS contains MVC, Object Pooling, Visitor, and more design patterns implementations to create RIAS and Web applications. [Less]

This opensource library contains a skeletal to implement rich application with VEGAS and this extensions. For the moment this library is an experimental laboratory to implements a concrete example with VEGAS.

Spring ActionScript is an offshoot of the Java-based Spring Framework written in ActionScript 3. It is targeted for the Flash, Flex and AIR platforms. The framework contains an Inversion of Control ... [More] Container, an MVCS framework, extensions for the Cairngorm and PureMVC frameworks and several other utilities. [Less]

Indigo is an architectural framework based on IOC (Spring) and developed in Actionscript 3. It provides a clean base for all developers seeking to build solid applications, scalable and maintainable ... [More] in a market in perpetual motion. Available for Flash, Flex and AIR [Less]

SmartyPants IOCWelcomeWelcome to the main repository for SmartyPants IOC, which is a dependency injection framework designed for use with Adobe Flex. Why SmartyPants?There are a few IOC frameworks ... [More] around at the moment: Prana (now Spring Actionscript) was probably the first serious DI framework for Flex to get much notice. There's also Swiz, and others. What sets Smartypants apart from these frameworks? The competition is (mostly) inspired by Spring, whereas SmartyPants is inspired by Guice. This is simply my preference, it may or may not be yours. SmartyPants-IOC is just for dependency injection. You may use any application framework you please. I recommend RobotLegs AS3. It does things the way I like, and you can even replace SmartyPants with another injector if you need to. SmartyPants defines the bindings / application structure via ActionScript code, not via XML. Again, this is a stylistic preference. Put your run-time configuration in configuration files, not in your application structure. Injection requests are specified with annotations, like Guice, Spring 2(.5?), and Swiz. You can also use a similar DSL to request instances from the injector. SmartyPants provides live injection - think "the love child of regular dependency injection and Flex data-binding" Getting startedDownload the .swc file from here, or checkout the code via SVN. The project is young, and the docs are growing, but grow they will! Check out the wiki here, or join the discussion group if you'd like to know more. The !ASDocs are currently offline but will return very shortly! A simple example [Less]

Developed for use with ActionScript 3, Flash 9 and Flex 2 projects it provides an inversion of control container for components that support dependency injection. Feature summary: Support for ... [More] constructor and setter injection, with setter injection available to public variables, setter accessors, and methods. Dependency resolution can be performed automatically through reflection or by providing: a subclass as a type-hint, a key string that a component was registered with, a function reference to return the dependency, a literal value. Component instances can be cached allowing emulation of singleton access to instances. The DI library can also detect some forms of cyclic dependency between components. Support is included for managing instances created outside of the container. Once registered they are available to any component that requests an instance. Additionally registered instances can be populated by setter injection once, every time or never when retrieved from the container. Runtime container configuration by XML is available, with additional formats easily added. Components can be registered in any order as they are only resolved when requested from the container. This allows for the loading of multiple external defintions and RSLs to load classes as required. A Reflection API is included in the DI library to address issues with the flash.utils.describeType function, and provides an API that makes the common use-cases of the DI library quick and easy. [Less]

a spring project used for flash platform

as3guice lightweight dependency injection framework for actionscript3 inspired by google-guice.