The document discusses different types of assets that can be used to build applications faster, including SWCs (Software Component), embedded SWFs (Shockwave Flash), and loaded SWFs. It provides examples of using each type and notes their advantages and disadvantages. SWCs allow for code completion and reuse of existing components but can be larger in file size. Embedded SWFs execute timeline code directly but require two frames. Loaded SWFs have a smaller initial footprint but require more code. The summary recommends using the right tool for the job and thinking ahead about organization and potential issues.

1. Build Applications Faster with SWCs Chris Black

2. Overview Asset overview

3. Beyond the button

4. Examples Images

5. Components

6. Vector art Summary

7. What's an Asset? An image, animation or graphical element used in creating an application.

8. Examples: JPEG, PNG, GIF

9. Vector art

10. SWF animation or interactive components

11. How are they used? Designs are created in Photoshop, Illustrator and Fireworks

12. Flash IDE and Flash Catalyst (coming soon) for asset production

13. Flash Builder 4 (Flex Builder 3), and Flash Develop for coding

14. Why are they Important? Flash CS4 + Code = BAD

15. Flash Builder Flex Framework great for existing components (buttons, grids, drop downs...)

16. Time consuming for new components

17. ActionScript only projects + Flash IDE = AWESOME

18. Use the right tool for the job

19. Types of Assets Loaded Assets Small initial footprint

20. Many loading stages

21. Larger apps and dynamic content Embedded Assets Larger footprint

22. Single loading stage

23. Smaller apps and core content

24. Beyond the Button http://www.ammap.com http://www.greensock.com/

25. Images in SWCs Compress transparent PNGs

26. Simplify code