ActionScript developer's guide to Robotlegs
Robotlegs is a standout among the ActionScript 3 development frameworks available today. With it, Flash, Flex, and AIR developers can create well-architected, testable, and flexible Rich Internet Applications-fast. This concise guide shows you how the light footprint and focused scope of this open...
| Autor principal: | |
|---|---|
| Otros Autores: | |
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Beijing ; Sebastopol, California :
O'Reilly
[2011]
|
| Edición: | First edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009628343706719 |
Tabla de Contenidos:
- Table of Contents; Preface; Robotlegs: Something a little bit special; Who this book is for; Who this book is not for; Conventions used in this book; Using code examples; Safari® Books Online; How to contact us; Acknowledgments; Chapter 1. Robotlegs is a lightweight framework for ActionScript 3; What does Robotlegs actually do?; Robotlegs is a communication-and-cooperation framework; Direct conversation; Passing messages; Robotlegs helps with direct conversations and message passing; Robotlegs makes use of three object-oriented architectural patterns; Do you need a framework at all?
- Reasons to use a frameworkConsistency; Common understanding brings easier collaboration; Peer-reviewed solutions; A well-tested skeleton; Less code to write; Reasons not to use a framework; Framework learning curve; Terminology confusion; Performance tradeoffs; Framework coupling; 'Black box' code is hard to debug; Robotlegs aims to amp up the pros and minimize the cons; Less boilerplate code is a good thing...; Chapter 2. The Robotlegs dream...; 80% of the problems can be solved with 20% of the API; Coding for Robotlegs shouldn't tie you to the framework
- Robotlegs aims to enable and not dictateMost AS3 applications benefit from the MVCS approach; Testing, testing! (We test, and we make it easy for you to test); Some final things every Robotlegs cadet should know; Chapter 3. Anatomy of a Robotlegs application; Joel's Personal Kanban; Lindz's Mosaic Design Tool; How a Robotlegs application gets things done; Architecture begins with Events and Commands; Getting to grips with Robotlegs architecture; The 'context' is the heart of your Robotlegs application; Your models and services are 'Actors' in your app
- The MediatorMap provides a way to join your views to your app layerRobotlegs mediators are bridges, not view controllers; The CommandMap makes things happen; The shared event dispatcher joins everything together; ... and it goes a little something like this (event flow); User stories as implemented in Robotlegs; Personal Kanban example: Moving a task from 'backlog' to 'doing'; Mosaic Design Tool example: Saving a design; The same but different; All of this is possible because of the Robotlegs Injector; Chapter 4. Automated Dependency Injection
- So, what exactly is Automated Dependency Injection?A dependency is just a requirement to use another object; You can fulfil a dependency in three different ways; You already use Dependency Injection; There are different ways to inject dependencies; Statics and globals make code rigid, brittle, hard to test, and prone to memory leaks; Locator patterns push extra responsibilities on your classes; Automated DI gets around the need to 'pass the parcel', but keeps code flexible; How does Robotlegs Injection work?; Automated DI is a handshake; You can specify an injection point in three ways
- And you also have to tell the injector what you would like it to do
