synchronize color settings across color-managed Adobe Creative Suite components. This synchronization ensures that colors look the same in all Adobe Creative Suite components.

More Help topics

Viewing and managing files on page 14 Mini Bridge on page 45 Work with Camera Raw on page 30 Manage color on page 13
Whats new in Adobe Bridge CS5
Mini Bridge Open, browse, and manage files in the Mini Bridge panel in Photoshop, InDesign, or InCopy. Mini Bridge
communicates with Adobe Bridge to create thumbnails and keep files up-to-date and synchronized. See Mini Bridge on page 45.
Export photos to JPEG Save JPEG files for sharing on the web. See Export photos to JPEG on page 29. Enhanced path bar The path bar offers more ways to navigate: Click to edit the path directly or drag an item to the
path bar to go there. See Navigate files and folders on page 14.
Batch rename New filenaming options offer greater flexibility over batch-renaming operations, allowing you to
replace all or part of a string of characters in a filename. Use regular expressions to match patterns in filenames;

Adobe Bridge

preview the new names for all the files in the batch; and save frequently used naming schemes as presets. See Batch rename files on page 21.
Enhanced web galleries and PDF contact sheets Enjoy new gallery templates, including templates by Airtight Interactive, and more options for customizing the appearance of web galleries. Add custom text and graphical watermarks to PDF contact sheets; apply finer control over layouts; and zoom in on previews. Save custom web galleries and PDF layouts as styles for easy reuse. See Create web galleries and PDFs with Adobe Output Module on page 32. View InDesign linked files View the linked files in InDesign documents in Adobe Bridge. See View linked InDesign

files on page 38.

Full-screen video and audio previews Adobe Bridge CS5 plays back full-screen previews of dynamic media files, including SWF, FLV, and F4V files. See Play full-screen previews of dynamic media files on page 28.
Adobe Bridge video tutorials
Learn how to use new features in Adobe Bridge CS5 by watching one of the following videos:
What is Adobe Bridge CS5? offers a high-level overview of many features Adobe Bridge CS5 new features overview covers batch rename (2:10), Export panel (4:40), Adobe Output Module (7:02), and Mini Bridge (8:30)

To collapse an expanded stack, click the stack number or choose Stacks > Close Stack. To collapse all stacks, choose Stacks > Collapse All Stacks. To add files to a stack, drag the files you want to add to the stack.
Note: While you can add a stack to another stack, you cannot nest stacks. Files in the added stack are grouped with the existing stack files.
To remove files from a stack, expand the stack and then drag the files out of the stack. To remove all files from a stack, select the collapsed stack and choose Stacks > Ungroup From Stack. To select all files in a collapsed stack, click the border of the stack. Alternatively, Alt-click (Windows) or Controlclick (Mac OS) the stack thumbnail.

Preview images in stacks

In stacks that contain 10 or more images, you can preview (scrub) the images at a specified frame rate and enable onion skinning, which allows you to see preceding and succeeding frames as semitransparent overlays on the current frame.
To preview a stack, hold the mouse over the stack in the Content panel until the slider appears, and then click Play, or drag the slider. If you dont see the Play button or slider, increase the thumbnail size by dragging the Thumbnail slider at the bottom of the Adobe Bridge window. To set the playback frame rate, right-click (Windows) or Control-click (Mac OS) the stack and choose a frame rate from the Stacks > Frame Rate menu. To set the default stack playback frame rate, choose a frame rate from the Stack Playback Frame Rate menu in Playback preferences. To enable onion skinning, right-click (Windows) or Control-click (Mac OS) the stack and choose Stack > Enable Onion Skin.
Working with images and dynamic media
Get photos from a digital camera or card reader
Adobe Bridge Photo Downloader A. Name of connected device B. Options for saving files C. Options for renaming files D. Options for converting and copying files E. Get Photos button
1 Connect your camera or card reader to the computer (see the documentation for the device, if necessary). 2 Do one of the following:

A B C D

Mini Bridge Browse view A. Go Back / Go Forward B. Go To Parent, Recent Items, or Favorites C. Go To Bridge D. Search E. Path bar F. Navigation pod G. Content pod H. Preview pod
Adobe Bridge on page 3 Using Photoshop CS5 Using InDesign CS5 & CS5.5 Using InCopy CS5 & CS5.5

Open Mini Bridge

Open Mini Bridge by doing any of the following in Photoshop, InDesign, or InCopy:
(Photoshop) Choose File > Browse In Mini Bridge. (Photoshop) Click the Mini Bridge button
(Photoshop) Choose Window > Extensions > Mini Bridge. (InDesign, InCopy) Choose Window > Mini Bridge. Last updated 5/17/2011

Mini Bridge

Mini Bridge preferences
Click the Settings button
on the Mini Bridge panel home page. Then, specify the following:
Bridge Launching Options to control how Mini Bridge and Adobe Bridge communicate. Appearance The User Interface Brightness slider adjusts the lightness of the Mini Bridge panel background. Image Backdrop adjusts the lightness of the Content pod and Preview pod background. Select Color Manage Panel to apply your displays ICC profile to thumbnails and image previews in Mini Bridge.
Browse files in Mini Bridge
Click the Browse Files button
on the Mini Bridge panel home page. to toggle the Navigation pod, Preview pod, and Path bar.
Click the Panel View menu button
Navigate to files using the Navigation pod, Content pod, and path bar. Or, use the Search button to find files based on criteria you specify. See Navigate files and folders on page 14 and Search for files and folders on page 16. To adjust the display of the Content pod, use either of the following:
Thumbnail slider Make thumbnails larger or smaller by dragging the slider View menu button Specify how the Content pod displays files: As Thumbnails
, As Filmstrip , As Details , or As List. Select Grid Lock to always display complete thumbnails regardless of how the Mini Bridge panel is sized. See Adjust Content panel display on page 9.
Specify what you want to see in the Content pod using the following menu buttons:

Sort Filter Select

Sort by filename, file type, creation date, and other metadata criteria. See Sort files on page 20. Filter by star ratings or labels. See Filter files on page 20. Toggle the display of rejected files, hidden files, and folders, and Select All, Deselect All, or Invert Selection.
To open or place a file using Mini Bridge, select it in the Content pod and do any of the following:
Drag it into the host application or onto the host application icon. Double-click it to open it in its preferred application. Or, right-click (Windows) or Control-click (Mac OS) the file and choose Open Image or Open With Default Application. See Change file type associations on page 16. (Photoshop) Right-click (Windows) or Control-click (Mac OS) the file and choose Open In Camera Raw. See Work with Camera Raw on page 30. Click the Tools button

and choose Place > In [Application].
(InDesign) Drag a snippet from the Content pod into a document, positioning the loaded cursor where you want the upper-left corner of the snippet to be. Snippet files have the file extension.IDMS or.INDS. To run an automated task, select one or more files, click the Tools button , and choose [Host Application] > [Automated Task]. For information about a particular command, see or search Photoshop CS5 Help or InDesign CS5 Help, as necessary.
To open a file in Adobe Bridge, click the Adobe Bridge button at the top of the Mini Bridge panel. Or, rightclick (Windows) or Control-click (Mac OS) an item in the Content pod and choose Reveal In Bridge.
Preview files in Mini Bridge
Open a panel-sized preview , a full-screen preview , a slide show preview mode. See Preview and compare images on page 25.
, or compare images in Review
Click the preview button and choose Set Slideshow Options In Bridge to specify slide show options. See View images as a slide show on page 27.
Rename files in Mini Bridge
Click a filename in the Content pod and type to rename it. Or, right-click (Windows) or Control-click (Mac OS) a file and choose Rename.
Adobe Bridge Favorites and collections appear in Mini Bridge.
To add an item to Favorites or to a collection, drag it from the Content pod to the list or collection in the Navigation pod. See Add items to Favorites on page 8 and Organize files into collections on page 17.

Mini Bridge tutorials

To learn more about using Mini Bridge, read or watch any of these tutorials:
Adobe Mini Bridge panel and InDesign CS5 (02:00) Using Mini Bridge with Photoshop CS5 Mini Bridge in Photoshop CS5 Use Mini Bridge in CS5 applications (06:09) New features in Bridge and Mini Bridge (10:17) Using Mini Bridge in Adobe Photoshop CS5

Chapter 4: Camera Raw

Introduction to Camera Raw

About camera raw files

A camera raw file contains unprocessed, uncompressed grayscale picture data from a digital cameras image sensor, along with information about how the image was captured (metadata). Photoshop Camera Raw software interprets the camera raw file, using information about the camera and the images metadata to construct and process a color image. Think of a camera raw file as your photo negative. You can reprocess the file at any time, achieving the results that you want by making adjustments for white balance, tonal range, contrast, color saturation, and sharpening. When you adjust a camera raw image, the original camera raw data is preserved. Adjustments are stored as metadata in an accompanying sidecar file, in a database, or in the file itself (in the case of DNG format). When you shoot JPEG files with your camera, the camera automatically processes the JPEG file to enhance and compress the image. You generally have little control over how this processing occurs. Shooting camera raw images with your camera gives you greater control than shooting JPEG images, because camera raw does not lock you into processing done by your camera. You can still edit JPEG and TIFF images in Camera Raw, but you will be editing pixels that were already processed by the camera. Camera raw files always contain the original, unprocessed pixels from the camera. To shoot camera raw images, you must set your camera to save files in its own camera raw file format. Note: The Photoshop Raw format (.raw) is a file format for transferring images between applications and computer platforms. Dont confuse Photoshop raw with camera raw file formats. File extensions for camera raw files vary depending on the camera manufacturer. Digital cameras capture and store camera raw data with a linear tone response curve (gamma 1.0). Both film and the human eye have a nonlinear, logarithmic response to light (gamma greater than 2). An unprocessed camera raw image viewed as a grayscale image would seem very dark, because what appears twice as bright to the photosensor and computer seems less than twice as bright to the human eye. For a list of supported cameras and for more information about Camera Raw, see Digital camera raw file support. To see a list of cameras and which version of Camera Raw each camera requires, see Camera Raw plug-in |Supported cameras (kb407111).

About Camera Raw

Camera Raw software is included as a plug-in with Adobe After Effects and Adobe Photoshop, and also adds functionality to Adobe Bridge. Camera Raw gives each of these applications the ability to import and work with camera raw files. You can also use Camera Raw to work with JPEG and TIFF files. Note: Camera Raw supports images up to 65,000 pixels long or wide and up to 512 megapixels. Camera Raw converts CMYK images to RGB upon opening. For a list of supported cameras, see Digital camera raw file support. You must have Photoshop or After Effects installed to open files in the Camera Raw dialog box from Adobe Bridge. However, if Photoshop or After Effects is not installed, you can still preview the images and see their metadata in Adobe Bridge. If another application is associated with the image file type, its possible to open the file in that application from Adobe Bridge.

Camera Raw

Using Adobe Bridge, you can apply, copy, and clear image settings, and you can see previews and metadata for camera raw files without opening them in the Camera Raw dialog box. The preview in Adobe Bridge is a JPEG image generated using the current image settings; the preview is not the raw camera data itself, which would appear as a very dark grayscale image. Note: A caution icon appears in the thumbnails and preview image in the Camera Raw dialog box while the preview is generated from the camera raw image. You can modify the default settings that Camera Raw uses for a particular model of camera. For each camera model, you can also modify the defaults for a particular ISO setting or a particular camera (by serial number). You can modify and save image settings as presets for use with other images. When you use Camera Raw to make adjustments (including straightening and cropping) to a camera raw image, the images original camera raw data is preserved. The adjustments are stored in either the Camera Raw database, as metadata embedded in the image file, or in a sidecar XMP file (a metadata file that accompanies a camera raw file). For more information, see Specify where Camera Raw settings are stored on page 77. After you process and edit a camera raw file using the Camera Raw plug-in, an icon in Adobe Bridge. appears in the image thumbnail

increase Tint to add magenta. To adjust the white balance quickly, select the White Balance tool , and then click an area in the preview image that should be a neutral gray or white. The Temperature and Tint properties adjust to make the selected color exactly neutral (if possible). If youre clicking whites, choose a highlight area that contains significant white detail rather than a specular highlight. You can double-click the White Balance tool to reset White Balance to As Shot.
Adjust tone in Camera Raw
You adjust the image tonal scale using the tone controls in the Basic tab. When you click Auto at the top of the tone controls section of the Basic tab, Camera Raw analyzes the camera raw image and makes automatic adjustments to the tone controls (Exposure, Recovery, Fill Light, Blacks, Brightness, and Contrast). You can also apply automatic settings separately for individual tone controls. To apply an automatic adjustment to an individual tone control, such as Exposure or Recovery, press Shift and double-click the slider. To return an individual tone control to its original value, double-click its slider. When you adjust tone automatically, Camera Raw ignores any adjustments previously made in other tabs (such as finetuning of tone in the Tone Curves tab). For this reason, you should usually apply automatic tone adjustments firstif at allto get an initial approximation of the best settings for your image. If you are careful during shooting and have deliberately shot with different exposures, you probably dont want to undo that work by applying automatic tone adjustments. On the other hand, you can always try clicking Auto and then undo the adjustments if you dont like them. Previews in Adobe Bridge use the default image settings. If you want the default image settings to include automatic tone adjustments, select Apply Auto Tone Adjustments in the Default Image Settings section of the Camera Raw preferences.
Note: If you are comparing images based on their previews in Adobe Bridge, you may want to leave the Apply Auto Tone Adjustments preference deselected, which is the default. Otherwise, youll be comparing images that have already been adjusted. As you make adjustments, keep an eye on the end points of the histogram, or use the shadow and highlight clipping previews. While moving the Exposure, Recovery, or Blacks slider, hold down Alt (Windows) or Option (Mac OS) to preview where highlights or shadows are clipped. Move the slider until clipping begins, and then reverse the adjustment slightly. (For more information, see Preview highlight and shadow clipping in Camera Raw on page 57.)
To manually adjust a tone control, drag the slider, type a number in the box, or select the value in the box and press the Up or Down Arrow key. To reset a value to its default, double-click the slider control.

the saturation of all lower-saturated colors with less effect on the higher-saturated colors. Vibrance also prevents skin tones from becoming oversaturated.
Saturation Adjusts the saturation of all image colors equally from -100 (monochrome) to +100 (double the

saturation).

HSL / Grayscale controls in Camera Raw
You can use the controls in the HSL / Grayscale tab to adjust individual color ranges. For example, if a red object looks too vivid and distracting, you can decrease the Reds values in the nested Saturation tab. The following nested tabs contain controls for adjusting a color component for a specific color range:
Hue Changes the color. For example, you can change a blue sky (and all other blue objects) from cyan to purple. Saturation Changes the color vividness or purity of the color. For example, you can change a blue sky from gray to

highly saturated blue.

Luminance Changes the brightness of the color range.
If you select Convert To Grayscale, you see only one nested tab:
Grayscale Mix Use controls in this tab to specify the contribution of each color range to the grayscale version of the

image.

Adjust color or tone using the Targeted Adjustment tool in Camera Raw
The Targeted Adjustment tool , sometimes called the TAT tool, allows you to make tonal and color corrections by dragging directly on a photo, rather than by using sliders in the image adjustment tabs. For some people, dragging on the image is a more intuitive way to work. Using the Targeted Adjustment tool, you can drag down on a blue sky to desaturate it, for example, or drag up on a red jacket to intensify its hue.
1 To make color adjustments with the Targeted Adjustment tool
, click it in the toolbar and choose the type of correction you want to make: Hue, Saturation, Luminance, or Grayscale Mix. Then, drag in the image.
Dragging up or right increases values; dragging down or left decreases values. Sliders for more than one color may be affected when you drag with the Targeted Adjustment tool. Selecting the Grayscale Mix Targeted Adjustment tool converts the image to grayscale.

1 Click the New Snapshot button
at the bottom of the Snapshots tab to create a snapshot.
2 Type a name in the New Snapshot dialog box and click OK.
The snapshot appears in the Snapshots tab list. When working with snapshots, you can do any of the following:
To rename a snapshot, right-click (Windows) or Control-click (Mac OS) it and choose Rename. Click a snapshot to change the current image settings to those of the selected snapshot. The image preview updates accordingly. To update, or overwrite, an existing snapshot with the current image settings, right-click (Windows) or Controlclick (Mac OS) the snapshot and choose Update With Current Settings. To undo changes made to a snapshot, click Cancel.
Important: Use caution when clicking Cancel to undo snapshot changes. All image adjustments made during the current editing session are also lost.
To delete a snapshot, select it and click the Trash button Control-click (Mac OS) the snapshot and choose Delete.
at the bottom of the tab. Or, right-click (Windows) or
Snapshots applied in Photoshop Lightroom appear and can be edited in the Camera Raw dialog box. Similarly, snapshots created in Camera Raw appear and can be edited in Lightroom.
Save, reset, and load Camera Raw settings
You can reuse the adjustments that youve made to an image. You can save all of the current Camera Raw image settings, or any subset of them, as a preset or as a new set of defaults. The default settings apply to a specific camera model, a specific camera serial number, or a specific ISO setting, depending on the settings in the Default Image Settings section of the Camera Raw preferences. Presets appear by name in the Presets tab, in the Edit > Develop Settings menu in Adobe Bridge, in the context menu for camera raw images in Adobe Bridge, and in the Apply Presets submenu of the Camera Raw Settings menu in the Camera Raw dialog box. Presets are not listed in these locations if you dont save them to the Camera Raw settings folder. However, you can use the Load Settings command to browse for and apply settings saved elsewhere. You can save and delete presets using the buttons at the bottom of the Presets tab.
Click the Camera Raw Settings menu button
and choose a command from the menu:
Save Settings Saves the current settings as a preset. Choose which settings to save in the preset, and then name and save the preset. Save New Camera Raw Defaults Saves the current settings as the new default settings for other images taken with the
same camera, with the same camera model, or with the same ISO setting. Select the appropriate options in the Default Image Settings section of the Camera Raw preferences to specify whether to associate the defaults with a specific cameras serial number or with an ISO setting.

Color management

A color management system translates colors with the help of color profiles. A profile is a mathematical description of a devices color space. For example, a scanner profile tells a color management system how your scanner sees colors. Adobe color management uses ICC profiles, a format defined by the International Color Consortium (ICC) as a crossplatform standard. Because no single color-translation method is ideal for all types of graphics, a color management system provides a choice of rendering intents, or translation methods, so that you can apply a method appropriate to a particular graphics element. For example, a color translation method that preserves correct relationships among colors in a wildlife photograph may alter the colors in a logo containing flat tints of color. Note: Dont confuse color management with color correction. A color management system wont correct an image that was saved with tonal or color balance problems. It provides an environment where you can evaluate images reliably in the context of your final output.
About color profiles on page 94 About rendering intents on page 103
Do you need color management?
Without a color management system, your color specifications are device-dependent. You might not need color management if your production process is tightly controlled for one medium only. For example, you or your print service provider can tailor CMYK images and specify color values for a known, specific set of printing conditions. The value of color management increases when you have more variables in your production process. Color management is recommended if you anticipate reusing color graphics for print and online media, using various kinds of devices within a single medium (such as different printing presses), or if you manage multiple workstations. You will benefit from a color management system if you need to accomplish any of the following:
Get predictable and consistent color output on multiple output devices including color separations, your desktop printer, and your monitor. Color management is especially useful for adjusting color for devices with a relatively limited gamut, such as a four-color process printing press. Accurately soft-proof (preview) a color document on your monitor by making it simulate a specific output device. (Soft-proofing is subject to the limitations of monitor display, and other factors such as room lighting conditions.) Accurately evaluate and consistently incorporate color graphics from many different sources if they also use color management, and even in some cases if they dont. Send color documents to different output devices and media without having to manually adjust colors in documents or original graphics. This is valuable when creating images that will eventually be used both in print and online. Print color correctly to an unknown color output device; for example, you could store a document online for consistently reproducible on-demand color printing anywhere in the world.

Choose a CMYK working space that matches your CMYK output conditions to ensure that you can accurately define and view process colors. Select colors from a color library. Adobe applications come with several standard color libraries, which you can load using the Swatches panel menu. (Illustrator, and InDesign) Turn on Overprint Preview to get an accurate and consistent preview of spot colors. (Acrobat, Illustrator, and InDesign) Use Lab values (the default) to display predefined spot colors (such as colors from the TOYO, PANTONE, DIC, and HKS libraries) and convert these colors to process colors. Using Lab values provides the greatest accuracy and guarantees the consistent display of colors across Creative Suite applications. If you want the display and output of these colors to match earlier versions of Illustrator or InDesign, use CMYK equivalent values instead. For instructions on switching between Lab values and CMYK values for spot colors, search Illustrator or InDesign Help.
Note: Color-managing spot colors provides a close approximation of a spot color on your proofing device and monitor. However, it is difficult to exactly reproduce a spot color on a monitor or proofing device because many spot color inks exist outside the gamuts of many of those devices.
Color-managing imported images
Color-managing imported images (Illustrator, InDesign)
How imported images are integrated into a documents color space depends on whether or not the image has an embedded profile:
When you import an image that contains no profile, the Adobe application uses the current document profile to define the colors in the image. When you import an image that contains an embedded profile, color policies in the Color Settings dialog box determine how the Adobe application handles the profile.
Color management policy options on page 101
Using a safe CMYK workflow
A safe CMYK workflow ensures that CMYK color numbers are preserved all the way to the final output device, as opposed to being converted by your color management system. This workflow is beneficial if you want to incrementally adopt color management practices. For example, you can use CMYK profiles to soft-proof and hardproof documents without the possibility of unintended color conversions occurring during final output. Illustrator and InDesign support a safe CMYK workflow by default. As a result, when you open or import a CMYK image with an embedded profile, the application ignores the profile and preserves the raw color numbers. If you want your application to adjust color numbers based on an embedded profile, change the CMYK color policy to Preserve Embedded Profiles in the Color Settings dialog box. You can easily restore the safe CMYK workflow by changing the CMYK color policy back to Preserve Numbers (Ignore Linked Profiles). You can override safe CMYK settings when you print a document or save it to Adobe PDF. However, doing so may cause colors to be reseparated. For example, pure CMYK black objects may be reseparated as rich black. For more information on color management options for printing and saving PDFs, search in Help.

WBMP optimization options
WBMP format is the standard format for optimizing images for mobile devices, such as cell phones. WBMP supports 1-bit color, which means that WBMP images contain only black and white pixels. The Dithering algorithm and percentage determine the method and amount of application dithering. For optimal appearance, use the lowest percentage of dither that provides the detail you require. You can select one of the following dithering methods:
No Dither Applies no dithering at all, rendering the image in purely black and purely white pixels. Diffusion Applies a random pattern that is usually less noticeable than Pattern dither. The dither effects are diffused across adjacent pixels. If you select this algorithm, specify a Dither percentage to control the amount of dithering applied to the image.
Note: Diffusion dither may cause detectable seams to appear across slice boundaries. Linking slices diffuses the dither pattern across all linked slices, and eliminates the seams.
Pattern Applies a halftone-like square pattern to determine the value of pixels. Noise Applies a random pattern similar to the Diffusion dithering, but without diffusing the pattern across adjacent pixels. No seams appear with the Noise algorithm.
SWF optimization options (Illustrator)
The Adobe Flash (SWF) file format is a vector-based graphics file format for the creation of scalable, compact graphics for the web. Because the file format is vector-based, the artwork maintains its image quality at any resolution. The SWF format is ideal for the creation of animation frames, but you can also save raster images in SWF format or mix raster and vector graphics.
Optimization settings for SWF A. File format menu B. Flash Player menu C. Export menu
Preset Specifies the preconfigured set of options you want to use for export. You can create new presets by setting
options as desired, and then choosing Save Settings from the panel menu. (To open the panel menu, click the triangle to the right of the Preset menu.)
Flash Player Version Specifies the earliest version of Flash Player that will support the exported file. Type Of Export Determines how layers are exported. Select AI File To SWF File to export the artwork to a single frame. Select Layers To SWF Frames to export the artwork on each layer to a separate SWF frame, creating an animated SWF.

1 In Adobe Dreamweaver, Flash Professional, Illustrator, InDesign, Photoshop, or Premiere Pro, do one of the

following:

Choose Window > Extensions > Access CS Live. Click the CS Live button in the application bar.
2 If necessary, click the Sign In link in the panel, enter your Adobe ID and password, and click the Sign In button.
Note: The application youre working in automatically signs you in if you provided your Adobe ID and password during the installation process.
3 (Optional) To remain signed in when you restart the application, select Stay Signed In.
For more information on using individual CS Live online services, see Using Adobe CS Live. For more information on managing your account, see the support document Adobe account, password, and login FAQ (tn_16721).

Chapter 8: CS Review

CS Review overview
CS Review is an online service in that lets you share your design content on the web so that others can provide feedback. The CS Review panel lets you create reviews and upload content to the Acrobat.com server. The CS Review panel is available in the CS5 and CS5.5 versions of Photoshop, InDesign, Illustrator, and Adobe Premiere Pro. Note: The Clip Notes feature is not included in After Effects CS5 or Adobe Premiere Pro CS5. However, you can use CS Review in Adobe Premiere Pro CS5 to create reviews of movies made in After Effects or Adobe Premiere Pro. Note: Adobe Premiere Pro CS5 requires version 5.0.2 or later to use CS Review. If necessary, visit the Adobe Product Update page and install the update before proceeding. When you upload content, a snapshot image of your content is uploaded to a personal or shared workspace on the Acrobat.com server, where participants can add comments. (If you are working from Adobe Premiere Pro, you actually upload the entire video sequence for commenting.) You and others can view the comments in the web browser and in the CS Review panel of the Creative Suite application. You can continue to add and remove snapshots of your design content, making the review dynamic.
Use the CS Review panel to create a review and upload content from InDesign, Illustrator, Photoshop, or Adobe Premiere Pro.

CS Review

Snapshots of InDesign documents are uploaded to Acrobat.com. A. Part comments B. Area comments
CS Review is part of the CS Live subscription service. A CS Live subscription is required for creating and managing reviews from Creative Suite applications. However, review participants are not required to have a CS Live subscription to view and comment on reviews. Reviewers need only a free Acrobat.com account. For more information on CS Live subscriptions, see www.adobe.com/go/cslive. For more information on CS Review, see www.adobe.com/go/csreview or watch Using CS Review to simplify the creative review process on Adobe TV.

better video quality but increase export and upload times.
Export Audio Leave this check box selected if you want to include audio in your export. Deselect this option if you
prefer video-only export.
Frame selection timeline Slide the current frame indicator to choose the frame that you want to use as the preview
thumbnail for the video part. The current frames timecode is show on the left; the total duration of the export is shown on the right.
In and Out points Choose how much of your sequence to export by adjusting the In and Out points sliders on the
timeline. You can also set In & Out points by moving the current frame indicator and clicking the In or Out point buttons.

Manage a review

You can view and edit comments and manage review settings in the CS Review panel and in the Acrobat.com organizer.

Add review participants

You invite review participants using the review window on the Acrobat.com workspace. You can allow people to participate in a review using two methods. One method is to explicitly invite them to participate. Another method is to add the review to a shared workspace on Acrobat.com. Anyone who has access rights to the shared workspace can participate in the review. Review participants do not need to have any of the Creative Suite products installed. However, they must sign up for a free Acrobat.com account, which they can do when they click the review link in the e-mail message they receive. Note: Acrobat.com is available in English, French, German, Italian, Japanese, and Spanish.
Invite individuals to participate in a review
1 Use any of the following methods to open the review in the Acrobat.com workspace:
In the CS Review panel, select the review and click Share
. The review window opens in your browser.
In the CS Review panel, click the Down Arrow by the review thumbnail and choose Share. The review window opens in your browser. In a browser, go to the Acrobat.com site, sign in using your CS Live account information, and open the review document.
2 With the review window open in your browser, click Share File in the lower-left corner, and then choose Share It
With Individuals. (Choose Share It With More Individuals if there are existing participants.)
3 Type the e-mail address of each participant, and press Tab or Enter to complete the entry.

USING THE ADOBE CREATIVE SUITE 5.5 SDK

TECHNICAL NOTE

2011 Adobe Systems Incorporated. All rights reserved.
Using the Adobe Creative Suite 5.5 SDK Adobe, the Adobe logo, Creative Suite, Dreamweaver, Fireworks, Flash, Flash Builder, Flex, InDesign, InCopy, Illustrator, Photoshop, and Premiere are either registered trademarks or trademarks of Adobe Systems Inc. in the United States and/or other countries. Microsoft and Windows are registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Apple, Mac OS, and Macintosh are trademarks of Apple Computer, Inc., registered in the United States and other countries. Java and Sun are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All other trademarks are the property of their respective owners. The information in this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Inc. Adobe Systems Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this document. The software described in this document is furnished under license and may only be used or copied in accordance with the terms of such license. Adobe Systems Inc., 345 Park Avenue, San Jose, California 95110, USA.

Contents

About Creative Suite extensions. 5
Adobe Creative Suite extensibility architecture. 6 Anatomy of an extension. 6 Extension management. 6
About the Creative Suite SDK. 7
Development environment requirements. 7 Supported applications. 8 Setting up the environment. 8
Using Adobe Creative Suite SDK. 9
Add libraries to your Flex project. 9 Create and add manifest file. 10 Import a package. 11
Creating a manifest file. 12
ExtensionManifest. 12 ExtensionList/Extension. 13 ExecutionEnvironment. HostList/Host. LocaleList/Locale. RequiredRuntimeList/RequiredRuntime. DispatchInfoList/Extension/DispatchInfo. Resources. Lifecycle. UI. 16 17
Localizing an extension. 17
Localizing the extensions manifest file. 18 Localizing the extensions Flex UI. 18
Running and debugging your extension. 19
Setting the OS debug mode. 19 Debug file for Photoshop and Dreamweaver. 20 Loading the extension. 20 Creating a debug run configuration in Flash Builder. 21 Debugging your extension in a host application. 21
Creating a hybrid extension. 21
Writing hybrid extensions. 22 Communicating between components. 22 Testing a hybrid extension. 22
Packaging and signing your extension for deployment. 23
Creating the deployment package. 23 Using UCF. 24 How signing works. 24 Packaging a hybrid extension. 25 Configuring a hybrid extension. 26 Installing a packaged and signed extension. Using Extension Manager. Testing extension installation. Troubleshooting the installation. 28 29
Running an extension. 30 Removing an extension. 30 Checking log files for errors. LogBook logs. Flash Player's built-in logging . Application logs. CS Service Manager logs. 33
Getting Started with the Adobe Creative Suite SDK
The Adobe Creative Suite SDK is a set of ActionScript libraries that make it possible to build Creative Suite Flash-based extensions in CS5 and higher. Developers can include these libraries in their projects in order to create cross-application plug-ins that use the Adobe Flex framework and AIR 2.0 API, and access the document object model (scripting DOM) of Creative Suite applications through ActionScript objects.
About Creative Suite extensions
This section provides an overview of the Adobe Creative Suite extensibility technology, which provides a common infrastructure for development and deployment of extensions that work across a set of supported Adobe Creative Suite applications. An Adobe Creative Suite extension is a set of files that together extend the capabilities of one or more Adobe Creative Suite applications. Developers can use extensions to add services and to integrate new features across the applications in the suite. The Adobe Creative Suite SDK provides developers with a consistent platform in which to develop and deploy extensions across the suite.Adobe Creative Suite extensions run in much the same way in all Adobe Creative Suite products (CS5 and higher), providing users with a rich and uniform experience. Adobe Creative Suite extensions use ActionScript to create cross-platform user interfaces. Extensions also have access to the host application's scripting interface, and can use these scripting APIs to interact with the application. Tight integration with the suite products allows extensions to be controlled as if they were built into the host applications. For example, extensions are invoked from the applications menu and, depending on the type of extension, can be docked, undocked, and provide fly-out menus. Users can add or remove extensions quickly and easily to customize Adobe Creative Suite applications to their needs. The Kuler panel, developed by Adobe and available in some products (CS5 and higher), is an example of a Adobe Creative Suite extension. Once available only as a web-hosted application for generating color themes, the Kuler extension makes the online Kuler service accessible within the suite products and allows users to access the color themes available in the web-hosted version. Kuler also integrates with the host application, allowing users to create themes that can be added, for example, to Photoshop as a swatch.

3. Decide which Flex version of the CSAW libraries to use; you can use versions compiled with Flex SDK 3.3, 3.4, or 3.5. The Flex 3.4 version is recommended, unless you have a compelling reason not to use it; for example, you have external libraries that were compiled with Flex 3.5 SDK. 4. Find the CSAW libraries associated with the chosen Creative Suite and Flex versions. The libraries are stored in this folder structure:
<CS_SDK_root>/libs/cslibs/<CSSDK version>/<Flex SDK version>/release/.
5. Add the wrapper libraries you need. Add csawlib.swc if you want to use all the application wrappers, or the product-specific wrappers if you are targeting only one or two applications (for example csaw_photoshop.swc). To do this: Select your project in the Package Explorer and choose Properties from the context menu. In the Properties dialog, select Flex Build Path. Click Add SWC, specify the desired library or libraries, and click OK. 6. If you use any wrapper libraries, you must also include apedelta.swc in your project. To do this: Select your project in the Package Explorer and choose Properties from the context menu. In the Properties dialog, select Flex Build Path. Click Add SWC, specify apedelta.swc, and click OK. Open apedelta.swc in the Library path pane and ensure that the Link Type is External. (This library defines the Flash Player API; if it is compiled into your extension, you will get run-time errors.)
Using Adobe Creative Suite SDK 10
7. Include the CSXSLibrary if you plan to send events to other extensions, execute ExtendScript code, use CSXSWindowedApplication or any other part of the CSXS API. For details, see the reference documentation for CSXSLibrary.
Create and add manifest file
A Creative Suite extension must have a manifest file, which tells the Extension Manager how to install that extension and specifies how it should be loaded and executed in the application. The extension manifest is an XML file. The Creative Suite SDK includes the complete XSD file for the Extension Manifest schema and a sample manifest file. The section Creating a manifest file on page 12 describes some of the options and capabilities. 1. Create a manifest file based on the sample. The file must be named manifest.xml.
2. Place the manifest file in your project source folder, in a package named CSXS. The build process will automatically copy the manifest to the Output folder. After you have created your manifest file, your project should look something like this in the Package Explorer:

ExtensionManifest

The root element for an extension manifest XML file:
<ExtensionManifest Version="2.0" ExtensionBundleId="com.example.simple" ExtensionBundleVersion="1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">. </ExtensionManifest>
Attributes Allowed children
The ExtensionBundleId attribute is an optional unique identifier for your extension bundle. Adobe recommends using a fully qualified namespace-like name such as com.myCompany.extension. The possible child elements of ExtensionManifest are:

Author Contact

Optional. The author of this extension bundle. Optional. A contact for this extension bundle. Required attribute mailto.
Optional. A legal notice for this extension bundle. Optional attribute href.

Abstract

Optional. An abstract for this extension bundle. Optional attribute href.
ExtensionList ExecutionEnvironment
Contains a list of extensions defined in this bundle. See details below. Contains information about which host applications can run the extension under what conditions. See details below.

DispatchInfoList

Contains an Extension element for each of the listed extensions, each of which contains a DispatchInfo element. See details below. Optional. Contains arbitrary information about this extension. It can contain data of any type. Required attribute Id associates this data with an extension defined in the ExtensionList. Optional attribute Host associates the data with a specific host application. If you have provided localization resources (see Localizing an extension on page 17), you can use the %key syntax to localize values in the ExtensionData element. Because this section contains arbitrary information about the extension, you must localize the entire XML content of the element, and include all of the alternative XML files in your project:
<ExtensionData>%ExtensionData</ExtensionData>

ExtensionData

ExtensionList/Extension
An extension bundle can contain multiple extensions, each of which is implemented by an SWF file. Each extension in the bundle must be listed here in its own Extension element, each with a unique extension identifier.
<ExtensionList> <Extension Id="com.example.simple.extension" Version="1.0" /> </ExtensionList>

Attributes

The Extension tag takes two attributes:
A unique identifier for the extension, unique within the entire CSXS system. Adobe recommends using a reverse domain name. Other tags within the manifest use this id to reference this extension. Optional, a version identifier for this extension.

Version

ExecutionEnvironment
The ExecutionEnvironment element contains information about what Creative Suite applications will run what the extension under what conditions. This element must list each of the Creative Suite host applications targeted by your extension, the supported locales, and the runtime requirements.

<ExecutionEnvironment> <HostList> <Host Name="IDSN" Version="7" /> </HostList> <LocaleList> <Locale Code="All" /> </LocaleList>
<RequiredRuntimeList> <RequiredRuntime Name="CSXS" Version="2.0" /> </RequiredRuntimeList> </ExecutionEnvironment>

HostList/Host

The HostList element contains a list of Host elements for all supported hosts. Each Host tag specifies a supported Creative Suite product. Attributes The Host tag contains the following attributes:

Name Version

Required, the host name of the host application. See Supported applications on page 8. Required. The version or versions in which this extension will work. A single version number specifies the minimum supported version; the extension works in all versions greater than or equal to this version. Specify a version range using interval notation, a comma-separated minimum and maximum version number enclosed by inclusive, [ ], or exclusive, ( ), endpoint indicators. You can mix endpoint types. For example, to target InDesign 7 and all versions up but excluding version 9, use the string "[7,9)". The entire element looks like this:
<Host Name="IDSN" Version="[7,9)" />

LocaleList/Locale

The LocaleList element contains a list of Locale elements for all supported locales. Each Locale tag contains the locale code for a supported language/locale, in the form xx_XX; for example, en_US or ja_JP. You can use the special value All to indicate that the extension supports all locales. Use a single Locale element with the special value "All" to make your extension load in the host application regardless the language used:
<LocaleList> <Locale Code="All"/> </LocaleList>
To restrict the locales your extension supports, create a Locale element for each language, whose value is a locale code. If the application locale does not match one of those specified, the application does not load the extension. For example, an extension with these settings loads when the application is running in US or British English:
<LocaleList> <Locale Code="en_US" /> <Locale Code="en_GB" /> </LocaleList>
For information on how to localize your extension, see Localizing an extension on page 17.
RequiredRuntimeList/RequiredRuntime
The RequiredRuntimes element contains a list of RequiredRuntime elements for all required runtimes; that is, executables that must be available in order for the extension to run. Currently, the only supported runtime is CSXS 2.0.
DispatchInfoList/Extension/DispatchInfo

Lifecycle

The Lifecycle element specifies the behavior at startup and shutdown. It can contain these elements:
AutoVisible StartOn/Event
Boolean, true to make the extensions UI visible automatically when launched. A set of events that can start this extension. Use fully-qualified event identifiers. For example:
<Lifecycle> <StartOn> <Event>applicationActivate</Event> </StartOn> </Lifecycle>
You can register for any of the CSXS standard events or any arbitrary CSXSEvent sent from a C++ plug-in. The standard events (which are not necessarily supported by all applications) are:
documentAfterActivate: Fired when a document has been activated. documentAfterDeactivate: Fired when the active document has been

deactivated.

applicationActivate: Fired when the application gets an "activation" event

from the OS.

documentAfterSave: Fired after the document has been saved
Localizing an extension 17
The UI element configures the appearance of the extension window. It can contain these elements:
The type of the extension controls the kind of window that displays its UI. Value is one of:
Panel ModalDialog Modeless ToolTip
The label of the menu item for this extension in the host applications Window > Extensions menu. The value can be a localization key; see Localizing the extensions manifest file on page 18. If not included, no menu item is added for the extension, and you are responsible for starting it in response to some event, by providing a Lifecycle/StartOn/Event element.

Geometry

Specifies the preferred geometry of the extension window. The host application may not support all of these preferences, and the values can be overwritten for an AIR extension, using the AIR window API. The value can be a localization key; see Localizing the extensions manifest file on page 18. The example above shows the possible elements. If you provide a size element, both the width and height value must be provided.

Icons/Icon

The Geometry element can contain this list, which identifies icons used for the extension in the host applications UI; for example, when docking an extension of type Panel. Each Icon element contains the path to the icon file (relative to the extensions root directory), and the required attribute Type, which is one of:

Normal Disabled Rollover

The path value can be a localization key; see Localizing the extensions manifest file on page 18.

Localizing an extension

In order to localize your extension, you must create resource files for your project. Your localized string resources can be used in both the Flex components that make up your UI, and in a number of places in the manifest. Define your localization string resources in a set of files that contain key/value pairs in UTF-8 format. Name each such file "messages.properties", and store it in a locale-specific subfolder of a folder called "locale" in the root folder of your project. For example:
Localizing an extension 18
#locale/es_ES/messages.properties menuTitle=Mi extension buttonLable=Mi boton.
If you have decided that your extension should run in all languages and you do not have specific support for a locale, the resources in the default file are used. The application looks for a properties file at the top level of the locale/ folder to use as the default resource file.
#locale/messages.properties menuTitle=My extension buttonLabel= My button.
If the application UI locale exactly matches one of the locale-specific folders, those resources are used in your extension interface. The match must be exact; for instance, if you have resources for fr_FR but the application locale is fr_CA, the default properties are used. You must copy the locale/ folder and its contents into the projects Output folder before you attempt to run or debug the extension.
Localizing the extensions manifest file
If you have provided localization resources, you can localize values within a manifest's DispatchInfo/UI element by replacing the value with a messages.properties key, preceded by the percent symbol. For example:
<Menu>%menuTitle</Menu>
When your extension runs, the application looks for this key in the locale-specific messages.properties file, and uses the value to display the menu item. You can use this mechanism to localize other information in the manifest file. For example, to have locale-dependent default extension geometry, or to load a different icon:
<Menu>%menuTitle</Menu> <Geometry> <Size> <Height>%height</Height> <Width>%width</Width> </Size> </Geometry> <Icons> <Icon Type="Normal">%icon</Icon> <Icon Type="RollOver">%icon</Icon> </Icons>
Localizing the extensions Flex UI

Creating a debug run configuration in Flash Builder
For each new project you want to debug with Flash Builder, you must define a debug run configuration. To do this: 1. Open your project in Flash Builder and select it in the Package Explorer. 2. In Flash Builder 4, choose Run > Debug > Other. In Flash Builder 4.5, choose Run > Debug Configurations. 3. Select Web Application and click New to create a configuration for Web Application. 4. Enter "Debug <extension_name>" in the Name box, and the name of your project in the Project box. 5. Deselect the "Use defaults" option. 6. Replace the value in the "Url or path to launch" box with about:blank. 7. Click Apply and close the dialog.
Debugging your extension in a host application
Once you have completed all of these prerequisites (setting the OS debug flag, loading the extension into the CS Service Manager, and setting up debug run configuration in Flash Builder), you are ready to start debugging. To debug your extension with Flash Builder while it is running in the target application: 1. Open and select your project in Flash Builder. 2. Set a breakpoint in your ActionScript code. 3. To start a new debug session, choose Run > Debug > your_debug_config_name. If you see a warning dialog, dismiss it and continue. 4. Launch the host application and run your extension by choosing its menu item from the Window > Extensions menu. For information about how to use the debugger in Flash Builder, see the Flex SDK documentation: http://opensource.adobe.com/wiki/display/flexsdk/Developer+Documentation.
Creating a hybrid extension
A hybrid extension is a package that combines a Creative Suite extension with an application-specific extension or plug-in that uses the native C/C++ or scripting API. This allows you to build extensions with rich Flash-based interfaces and still take advantage of the extended native API for the host application. You must package the several components of a hybrid extension into a ZXP package. The Extension Manager installs the package on the users machine as a single extension; it looks the same as any other extension to the end user.
Creating a hybrid extension 22
As an extension developer, you can choose to use application-specific C/C++ plug-ins or scripting extensions to extend Creative Suite products, in addition to your Creative Suite Flash-based component. You might want to do this, for example, when: You have legacy code that you still want to support. The feature you are developing requires a capability supported by the native scripting or C/C++ API layer, that is not accessible via your Creative Suite extension; for example, some applications allow you to create custom menus using C++ extensibility. You have CPU-intensive tasks to perform that are more suited to C++ than to ActionScript.

Writing hybrid extensions
If you are already familiar with writing Creative Suite extensions and native application extensions (for example, a Photoshop or InDesign C++ extension, a Flash Pro C extension, or a Dreamweaver JavaScript extension) there is little more you need to learn. The two parts of a hybrid extension are implemented as standalone components. Create the Creative Suite extension using Adobe Creative Suite SDK. Create your C/C++ or scripting API plug-in using the application-specific SDK and recommended tools. If you have never built a native plug-in for your host application, check the application-specific SDKs for details; see Adobe Developer Connections. The only thing you need to do is package them together so that they can be deployed in the users environment as a single extension.
Communicating between components
You must choose the mechanism you want to use to communicate between the Flash-based and native API components or your hybrid extension. For example, you can create your own socket implementation to pass messages between your native plug-in and the ActionScript code of your Creative Suite extension. Adobe offers the Application SDK Extension Toolkit that shows you how to use Adobes PlugPlug library to communicate between C/C++ and ActionScript. The toolkit provides the libraries, documentation, and samples you need to build a hybrid extension where the components communicate with each other. You can include these libraries directly in Photoshop, InDesign, and Flash Pro native plug-ins. For information on using the PlugPlug libraries in Illustrator, see the FreeGrid sample in the Illustrator SDK.
Testing a hybrid extension
During development, test the components of your hybrid extension separately. Launch and debug the Creative Suite SDK component as described in Running and debugging your extension on page 19. Install the application-specific plug-in or extension in the host as instructed in the application-specific SDK. Debug it using the recommended development tools, such as XCode or Visual Studio.
Packaging and signing your extension for deployment 23

To install the plug-in component, copy the files to the Plug-ins or Extensions folder, or point the host application to your plug-in build folder. For example, InDesign looks for its plug-ins in:
<InDesign installation location>/Plug-ins/
For details of how to package your hybrid extension for deployment, see Packaging a hybrid extension on page 25
Packaging and signing your extension for deployment
The Extension Manager package file allows you to install the extension you are developing on machines other than the one you are currently using (across platforms), to share the extension with other users, and to distribute it to customers. An Extension Manager package is an archive file with the extension.zxp, which contains: A copy of the CSXS folder containing the manifest.xmlfile. A copy of the compiled Flex project in SWF format. A copy of any other optional resources used by the extension, such as icons and localization files. For a hybrid extension, it must include the resource files for the native plug-in or scripting component. A file named mimetype, generated by the packaging and signing process.
Creating the deployment package
Adobe provides a toolkit that you can use to package and sign extensions so they can be installed in Creative Suite applications using Extension Manager. The toolkit includes: The UCF tool, a command-line tool used to create Universal Container Format (UCF) packages A document that provides the information you need to create packages for deployment: Technical Note: Packaging, Signing, and Deploying Extensions with Extension Manager. See the Adobe Creative Suite SDK page, http://www.adobe.com/devnet/creativesuite/, to download the signing and packaging toolkit. After testing your extension thoroughly, you must package and sign your extension so users can install it in their systems using Extension Manager. To prepare for this step, it is recommended that you copy all of the files in the Output folder for your extension to a staging folder for ease of packaging. Make sure the staging folder contains a subfolder named CSXS/, which contains the manifest.xml file:
<staging_folder>/CSXS/manifest.xml
You can add any extra resources to the root or to a folder within the root folder. Within the manifest file, references to these resources should use pathnames that are relative to the root. For example, if your SWF file is located at <staging folder>/Simple.swf, the path in the manifest should be specified as./Simple.swf. For a hybrid extension, you must package and sign the Creative Suite SDK component separately, then take some additional steps to package that with the native plug-in or scripting component; see Packaging a hybrid extension on page 25.
Packaging and signing your extension for deployment 24

Using UCF

To package the extension, use the Universal Container Format (UCF) command-line tool. The Adobe UCF tool is implemented in Java; the JAR file is packaged with this document. Running the tool requires that the java command is available in your shells path. UCF requires JRE 1.5 or newer to run, but JRE 6 is recommended. This is the default in Mac OS X; in Windows, you must install JRE 1.5 or better. Invoke UCF directly using the JAR file:

Packaging a hybrid extension
For a hybrid extension: Package and sign the Creative Suite SDK portion separately, as described in Creating the deployment package on page 23. Prepare the native plug-in or scripting component for packaging as described in the application-specific SDK. When all of the components are ready: 1. Create a new staging folder. 2. Add the signed package for the Creative Suite SDK extension component to the root of the staging folder. 3. Add the application-specific files to the staging folder in their platform-specific subfolders. 4. Add the MXI configuration file to the root of the staging folder; see Configuring a hybrid extension on page 26. For example, for a hybrid extension that includes a Creative Suite SDK extension component is named MyExtension, and a C++ plug-in component named MyPlugin that has Mac OS and Windows versions:
Packaging and signing your extension for deployment 26
/staging /mac/MyPlugin.plugin /win32/MyPlugin.8li /win64/MyPlugin.8li /MyExtension.zxp /MyExtension.mxi
5. Run the UCF tool on the staging folder to bundle and sign its contents into a single ZXP archive.
Configuring a hybrid extension
Extension Manager requires an XML configuration file named projectName.MXI to correctly install the extension and all its components in the user's environment. You must create this MXI file and customize it to describe your desired configuration. When you package your hybrid extension for deployment, the MXI file must be included alongside the packaged and signed Creative Suite SDK extension component. See Packaging a hybrid extension on page 25. For more information about editing the MXI file, see the document Packaging Extensions with Adobe Extension Manager (http://www.adobe.com/go/em_file_format). The MXI file looks like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <macromedia-extension name="com.example.myextension" requires-restart="true" version="1.0"> <author name="Adobe Developer Technologies"/> <description><![CDATA[The description.]]></description> <license-agreement><![CDATA[Legal Text.]]></license-agreement> <products> <product familyname="Photoshop" maxversion="" primary="true" version="12.0"/> </products> <files> <file destination="" file-type="CSXS" products="" source="MyExtension.zxp"/> <!-- ADD APPLICATION SPECIFIC FILE HERE --> </files> </macromedia-extension>

Product

To update how this information is displayed for your extension in the Extension Manager UI, you must specify the corresponding values in your project's manifest.
Troubleshooting the installation
If your package fails to install properly: Verify that you have built your extension with the correct structure, and that your extension package contains the correct files in the correct locations. Verify that the package has not been modified since being properly signed. Because the ZXP is an archive file, you can rename the package with the.zip extension to examine its contents and verify that it contains all needed files. If you change anything in it, however, the signature no longer matches the content, and the Extension Manager cannot load the package. If you need to make changes, you must create and sign a new package.
Packaging and signing your extension for deployment 30

Running an extension

Once your extension has been successfully installed, you can test in any of the applications specified in your extension's manifest file. To run your extension, open the host application and choose your extension for the list in Window > Extensions. The name that appears in this menu is the one you specified in the manifest. Here are some problems you might encounter when running an extension, and possible solutions. For further help, check the known problems section in the SDKs Readme file. Extension does not appear in the applications Window > Extensions menu Verify that the extensions manifest.xml file is set up correctly: Verify that the Host ID for your application is correct. Notice that the ID for Photoshop Extended (PHXS) is different from the ID for Photoshop (PHSP). Verify that the product locale matches the one listed in the manifest file, or that the locale is given as "All". Verify the path given in the Extension/DispatchInfo/SWFPath element. The path must be relative to the extension's root folder. Verify that the extension has been successfully copied to the CS Service Managers extensions folder. For more details, refer to Loading the extension on page 20. If the problem persists, check the applications log for possible errors; see Checking log files for errors on page 30. Extension throws a security error upon loading If your extension fails to load any of the ActionScript libraries provided with the SDK, it might throw a security error. To prevent this, make sure your SWF file is compiled using the framework linkage "Merge into code"option, rather than the "Runtime shared library (RSL)" option.

Removing an extension

You can use the Extension Manager to remove an extension. 1. Select the extension in the list of installed programs. 2. Choose File > Remove Extension. The Extension Manager removes it both from the file system, and from the displayed list of currently installed extensions.

Edit the file and add these lines:
ErrorReportingEnable=1 TraceOutputFileEnable=1
The flashlog.txt file is then generated in the platform-specific folder: In Windows XP: C:\Documents and Settings\user\Application Data\Macromedia\Flash

Player\Logs

In Windows Vista and Windows 7: C:\Users\user\AppData\Macromedia\Flash Player\Logs In Mac OS: /Users/user/Library/Preferences/Macromedia/Flash Player/Logs/

Application logs

The Adobe Creative Suite extensibility infrastructure creates a log file for each of the applications running extensions. These files provide useful debug information for extension developers. The log files are generated in the platforms temp folder, and named according to the CSXS version and host application, csxs2-HostID.log or csxs2.5-HostID.log; for example, csxs2-ILST.log for an extension running in Illustrator CS5. These logs are located at these platform-specific locations: In Windows XP: C:\Documents and Settings\<user>\Local Settings\Temp In Windows Vista: C:\Users\<user>\Locale\Temp In Windows 7: C:\Users\<user>\AppData\Local\Temp In Mac OS X: /Users/<user>/Library/Logs/CSXS If you need more detailed information, you can increase the logging level. Possible log level values are: "0": Off; no logs are generated "1": Error; preferred and default level "2": Warn "3": Info "4": Debug "5": Trace "6": All Update the LogLevel key at these platform-specific locations: In Windows Registry Editor: CS5: HKEY_CURRENT_USER/Software/Adobe/CSXS2Preferences CS5.5: HKEY_CURRENT_USER/Software/Adobe/CSXS.2.5 In Mac OS X: PLIST file in /Users/<user>/Library/Preferences/ CS5: com.adobe.CSXS2Preferences.plist CS5.5: com.adobe.CSXS.2.5.plist You must restart your application for these changes to take effect.
Packaging and signing your extension for deployment 33

CS Service Manager logs

The name of the CS Service Manager root folder (<ServiceMgr_root>) depends on the Creative Suite version. In CS5, the root folder is CS5ServiceManager. In CS5.5, the root folder is CS5.5ServiceManager. The Service Manager keeps log files at these locations: In Windows XP: C:\Documents and Settings\<user>\Application Data\Adobe\<ServiceMgr_root>\logs In Windows Vista: C:\Users\<user>\AppData\Roaming\Adobe\<ServiceMgr_root>\logs In Mac OS X: /Users/<user>/Library/Application Support/Adobe/<ServiceMgr_root>/logs