Flash Builder and Flash Catalyst : the new workflow /

Mostrar otras versiones (1)

Provides information on using Flash Builder and Flash Catalyst to design effective Rich Internet Applications.

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Peeters, Steven
Formato: Electrónico eBook
Idioma:Inglés
Publicado: New York : Friends of ED : Distributed to the Book trade worldwide by Springer-Verlag, ©2010.
Temas:
Flash (Computer file)
Flex (Computer file)
Flash (Computer software)
Flex (Computer software)
Internet programming.
Application software > Development.
Web site development > Computer programs.
Programmation Internet.
Logiciels d'application > Développement.
Sites Web > Développement > Logiciels.
REFERENCE > General.
Informatique.
Internet software.
Application software > Design.
Web sites > Design > Computer software.
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)
Tabla de Contenidos:
  • Note continued: Building applications using Flash Catalyst
  • Building applications from scratch
  • Integration with Creative Suite 5
  • Round tripping between Flash Builder and Flash Catalyst
  • tool for the "devigner"
  • Building AIR applications with Flash Catalyst?
  • Summary
  • ch. 5 Choosing the Best Workflow
  • Simple Design, Simple Functionality
  • Product Manual Application
  • Conclusion
  • Simple Design, Complex Functionality
  • Photo Resizer
  • Conclusion
  • Simple Design, Connected to a Back End
  • Twitter Search Client
  • Conclusion
  • Complex Design, Simple Functionality
  • Static Website
  • Conclusion
  • Complex Design, Complex Functionality
  • Simulator
  • Conclusion
  • Complex Design, Connected to a Back End
  • Solar Panel Monitor
  • Interaction Designer Perspective
  • Developer Perspective
  • Conclusion
  • Summary
  • ch. 6 Case Study: An E-Commerce Site
  • Understanding the Project
  • Analyzing the Project
  • Functional Analysis
  • Team Composition
  • Designing the Application
  • Creating the Application's Layout Structure
  • Creating the Tabs to Log In
  • Adding Design Elements
  • Adding the Navigation Bar
  • Adding the Content
  • Contact Page
  • Login Page
  • Registration Page
  • Bringing the Application to Life
  • Components
  • Pages
  • Hooking Up the Application to the Back End
  • Creating the Database
  • Writing the Back-End API
  • Adding Dynamic Data to the Application
  • Summary
  • ch. 7 Managing RIA Projects
  • Projects and Complexity
  • Project Team
  • Team Compositions
  • Collaboration has Changed
  • Agile Development
  • Methodologies
  • Iterative Development
  • FlexPMD: A Useful Tool
  • Summary
  • ch. 8 Frameworks
  • Example Application
  • Mate
  • Code
  • Conclusion
  • PureMVC
  • Code
  • Conclusion
  • Swiz
  • Code
  • Conclusion
  • Summary.
  • Note continued: ch. 9 Best Practices
  • Project Setup
  • Use Workspaces
  • Determine the Target Platform
  • Determine the Back End Technology
  • Deploy Release Builds
  • Place External Libraries in the libs Folder
  • Use Runtime Shared Libraries
  • Externalize the Flex framework
  • Organize Code into Packages
  • Synchronize with Back End Packages
  • Plan the Illustrator/Photoshop File Structure
  • Use an Assets Directory
  • Organize Your Assets
  • Use an XML File for the Parameters
  • Coding and Naming Conventions
  • Don't Link to External Image Files
  • Name All Design Layers
  • Design Only One Item for a Data List Component
  • Create Flash Catalyst Components Before Defining View States
  • Rename Flash Catalyst Components in the Library Panel
  • Reverse Engineer the Application's URL as a Package Structure
  • Use Plural Names for Packages
  • Use Appropriate Package Names
  • Use Singular Names for Classes
  • Use Titlecase or Camelcase for Class Names
  • Append the Class Type to the Class Name
  • Consider Appending "Base" to Base Class Names
  • Consider Appending "Abstract" to Abstract Class Names
  • Maintain Order in Your Classes
  • Use Uppercase for Constants
  • Use Camelcase/Tltlecase for Variables
  • Give Variables Proper Names
  • Put an Underscore in Front of Private Variables
  • Use Implicit Getters and Setters
  • Name Implicit Getters and Setters according to the Property
  • Use Implicit Getters and Setters Internally
  • Set Argument Types and Return Types Strictly
  • Always Name the Argument of Event Handlers "Event"
  • Use a Verb in the Method Name
  • Override the Clone() Method for Custom Events
  • Keep Order in Your MXML Files
  • Use Whitespace
  • Format Your Code
  • Every Visual Component Should Have an id Attribute
  • Set the id Attribute as the First One in an MXML Tag
  • Group MXML Tag Attributes on One Line
  • Use an External CSS File.
  • Note continued: Maintain Order in Your CSS File
  • Be Consistent in Naming Styles
  • Limit the Number of CSS Files
  • Define the CSS Files in the Main Application File
  • Collaboration
  • Talk to Each Other
  • Formalize Decisions
  • Use a Source Versioning Tool
  • Only Commit Code that Actually Works
  • Mark Duplicate Assets in Your Design
  • Design on a Single Artboard
  • Give Design Layers Proper Names
  • Don't Define All Components in Your Design
  • Don't Define All Component States in Your Design
  • Create Reusable "Black Box" Components
  • Consider Using Code Generation
  • Create Library Projects
  • Create a Manifest File for Your Library
  • Test, Test, Test
  • Use Different Deployment Levels
  • Set Up a Bug Reporting/Change Request Environment
  • Use a Unit Testing Framework
  • Use an Application Framework
  • Know When Not to Use an Application Framework
  • Perform Code Reviews
  • Comment Your Code
  • Validate Input Before Sending It to the Back End
  • Use the Same Local Server Settings For Everyone
  • Configure Your Application Externally
  • Summary.

Ejemplares similares