Home / Articles / Building Adobe WorkflowLab, Part 6: Development

Building Adobe WorkflowLab, Part 6: Development

Article Description

In part 6 of their series on the design and creation of WorkflowLab, Aaron Pedersen, James Polanco, and Doug Winnie, the authors of Adobe Flash Platform from Start to Finish: Working Collaboratively Using Adobe Creative Suite 5, discuss the development of the WorkflowLab codebase. Based on the wireframes (and later comps) and architecture discussions, the team now could begin constructing the application, bringing Adobe’s vision to life.
Application Framework

Application Framework

Based on the application framework architecture, the development team began construction on the foundation of the code base. The first step was to create a new project in Flash Builder based on a Flex AIR project. From there, the initial package structure was created to define the location of various project assets such as images, CSS, configuration files, and files related to the code base. Once complete, the project was checked into Subversion and shared with the rest of the development team.

With a base project in place, the team started splitting up tasks and began constructing the application's base functionality. Initial functionality included menu systems for Mac OS and Windows as well as a preference system to keep track of WorkflowLab's dimensions and placement in the application window on the user's desktop.

The initial Command Action Delegation and Data Map system were set up using the DevelopmentArc Core framework. With this framework in place, the team began construction of logic to read and write WFX files to and from the application (see Figure 1). Files that were read and parsed into the application were stored in data objects (in Flash, they're often called value objects) and placed in the application's model for storage and future reference within the application.

Figure 1 Translating architecture into code.

3. Component Development | Next Section Previous Section