TopNav Blog Company Over TopNav Blog Over TopNav Blog Company rest TopNav Company Over TopNav Company rest TopNav Company Team Over TopNav Home Over TopNav Home Rest TopNav Home Services Over TopNav Home Over TopNav Services Home Over TopNav Services Training Over TopNav Team Over TopNav Team rest TopNav Team Company Over TopNav Team Training Over TopNav Training Over TopNav Training Rest TopNav Training Services Over TopNav Training Team Over

Posts Tagged ‘Adobe Training’

Skills in Motion: Shared Libraries Simplify Graphic Asset Management in Adobe Flash

Monday, May 18th, 2009

Learn more about Flash in our Flash class!

Learn more about Flash in our Flash class!

Graphics and animations for eLearning and training content often build on each other as new graphic concepts are layered onto foundational concepts.  This layering of ideas can result in multiple composite graphic files that share common underlying graphical elements.  As the number of graphics in a project increases, the challenge of managing these files becomes increasingly complex.  This is particularly true when changes in an underlying graphic cascade to all graphics that share the common underlying element.
At SkillQ, many of our graphics and animations are designed in Flash CS4. To keep track of the files and assets used in a project and simplify the change process, we frequently use “shared libraries”.  Among many other uses, shared libraries are a means of accessing and managing the graphics and action script used on a project. Instead of embedding graphic elements in multiple Flash project documents (FLAs) in which they are used, categories of graphics may be shared and dynamically linked with each project.

A shared library is external and can be linked to many projects.  This can be helpful when changes are required for graphics that have many instances.  For example, lets assume you need to update a logo graphic that is an element of several animations used in multiple lessons.  If the graphic is contained in a shared library, it can be updated in one location and all Flash projects that reference that file will also be changed.

Shared libraries that are used by other Flash documents should be kept in a folder apart from the other Flash documents, preferably higher up in the directory structure hierarchy. Only the graphic elements that are unique to a specific document will be kept in that document’s internal library.

The benefit of using an External Flash Library is that you can store and categorize your graphics in one place and use them in as many projects as you need. Additionally, changes to underlying graphics are immediately reflected in all the Flash projects that contain instances of a graphic. You only have to re-publish the flash document that reference the library.

For more information on this topic sign up for an upcoming Adobe Flash Basics class.