Comments on: Optimizing the development process http://blog.sommestad.net/2009/03/optimizing-the-development-process-2/ Web and Cocoa development through the eyes of Kristofer Sommestad, a SWAD developer. Tue, 06 Jul 2010 11:48:28 +0000 hourly 1 http://wordpress.org/?v=3.1 By: esset http://blog.sommestad.net/2009/03/optimizing-the-development-process-2/#comment-75 esset Tue, 07 Apr 2009 13:34:14 +0000 http://reallyaced.wordpress.com/?p=70#comment-75 Another suggestion: 1. Designer/Artist creates sketch (paper or Photoshop) 2. Developer implements sketch (codewise). 3. Designer can change implementation directly, with only a few limitations. Reiterate steps 2-3. Another suggestion:

1. Designer/Artist creates sketch (paper or Photoshop)

2. Developer implements sketch (codewise).

3. Designer can change implementation directly, with only a few limitations.

Reiterate steps 2-3.

]]> By: esset http://blog.sommestad.net/2009/03/optimizing-the-development-process-2/#comment-74 esset Mon, 23 Mar 2009 15:17:28 +0000 http://reallyaced.wordpress.com/?p=70#comment-74 A development of a new View in a Flash app could look something like this: 1. Artist creates a sketch and any new assets in Flash IDE, while reusing existing components where applicable 2. Designer uses assets and components to place them in a new View in the Flash IDE 3. Developer adds functionality to the View and the new components (old components already have functionality) 4. Iterate between steps 1-2-3 in any desired order. --- 5. When done with iterations; break down the View into standalone components only, and adapt the completed layout to a new XML Layout file. The view should be able to compile using the Flex compiler (i.e. only by loading various components). A development of a new View in a Flash app could look something like this:

1. Artist creates a sketch and any new assets in Flash IDE, while reusing existing components where applicable

2. Designer uses assets and components to place them in a new View in the Flash IDE

3. Developer adds functionality to the View and the new components (old components already have functionality)

4. Iterate between steps 1-2-3 in any desired order.

—

5. When done with iterations; break down the View into standalone components only, and adapt the completed layout to a new XML Layout file.
The view should be able to compile using the Flex compiler (i.e. only by loading various components).

]]>