Transcript
What’s New in Adobe InDesign CS4 Products SDK For the benefit of previous users, this document summarizes the changes to the SDK in this release.
C++ IDE Requirements On Windows®, the required C++ development environment is now Visual Studio 2005, Service Pack 1. On Mac OS®, the required C++ development environment is XCode 2.4.1 for MacOS 10.4.x or XCode 3.1 for MacOS 10.5.x.
Porting Content Porting content was developed to help you transition to InDesign CS4. Adobe InDesign CS4 Porting Guide discusses the main changes to the InDesign API, and porting procedures. The changes to the InDesign CS4 API discussed in that document include links-architecture restructuring, scripting undo, gSession removal, user-interface changes, and other minor changes.
IDML IDML is an XML-based format for representing InDesign content. Essentially, it is a major revision of INX, InDesign's previous XML-based file format. IDML addresses INX shortcomings, in an effort to represent InDesign content in a human-readable format—something that can be reasonably assembled and disassembled by a competent XML programmer. The INXErrorLogging sample project provides a reference implementation of the IINXErrorHandler error-logging interface. This implementation writes all error and warning messages during INX and IDML import and export to a log file. IDMLTools is a Java package that provides APIs, tools, and sample code that demonstrates how to work with IDML. The package is in the following directory and described more thoroughly in the ReadMe file in this directory: SDK/devtools/sdktools/idmltools
The SDK also includes two new IDML documents: ➤
IDML File Format Specification formally describes the IDML file format.
➤
Adobe InDesign Markup Language (IDML) Cookbook provides practical, but less formal, information about working with IDML.
1
What’s New in Adobe InDesign CS4 Products SDK
Links
2
Links A new links sample, ExtendedLinks, was written to demonstrate the improved capabilities of the restructured links architecture. This sample pushes the bounds of the links APIs by implementing some useful features not directly supported by the product. Most notably, the sample demonstrates the use of the links architecture on a range of text (using XML features to identify the range). It also demonstrates the implementation of links from an ODBC data source. The goal is to demonstrate bi-directional update of data fields (like prices) in a catalog directly to and from a data source. Instructions for using MySQL and FileMaker Pro databases are provided. Links added by the ExtendedLinks plug-in are displayed by the ExtendedLinksUI plug-in. The plug-in implements its own panel, separate from the LinksUI panel. The ExtendedLinksUI panel contains a tree view that groups links based on a link's URI. The previous links sample (CustomDataLink) was updated for CS4.
Flex User Interface The FlexUIStroke sample is new in CS4. This sample demonstrates two-way communication between a Flash/Flex SWF and an InDesign plug-in. The sample's plug-in has a panel that contains an OWLFlashPlayerWidget and aggregates a SelectionObserver. The SelectionObserver notifies Flash when the selection changes in InDesign, and Flash notifies the observer when its combo-box selection changes. The FlexUIBasicScriptUI sample is new in CS4. This sample demonstrates two-way communication between a Flash/Flex SWF and an InDesign JavaScript script. The script creates a ScriptUI panel containing a flashplayer component. The flashplayer component provides a communication channel between the JavaScript and the SWF. This sample also demonstrates the use of scripting events to observe change; however, model and selection change events are not available to scripting, so the panel cannot maintain an updated state like a C++ plug-in panel can.
Preflight We added initial sample code and documentation for the new preflight architecture. The PreflightRule sample plug-in demonstrates creating custom preflight rules. This new architecture is documented in the chapter on “Implementing Preflight Rules” in Adobe InDesign CS4 Products Programming Guide.
Code Snippets SnpExportDynamicDocument is a new code snippet that shows how to programmatically export dynamic InDesign content to SWF. The snippet creates a multi-page document with several buttons and exports it to SWF. SnpManipulateConditionalText is a new code snippet that shows how to manipulate a document's conditional text. The snippet allows you to create, delete, and modify conditional-text tags and their visual attributes.
What’s New in Adobe InDesign CS4 Products SDK
Plug-ins
3
Plug-ins The FrameLabel sample was enhanced for CS4. Now you can specify a font color and label position (top, right, left, or bottom of the frame). The FrameLabelUI now supports mixed-mode operations; i.e., operations on frames with different FrameLabel settings. The Watermark sample is new for CS4. It demonstrates implementing a document watermark using a draw event handler. The sample allows you to set the watermark's text, font, color, opacity, rotation, and position.
New APIs for PDF Form XObjects PDF Form XObjects allow content to be added to a PDF file once and used later by reference. This is more efficient than duplicating static content. InDesign CS4's PDF export supports PDF Form XObjects. The IPDFFormXObjectData interface on the PDF export command (kPDFExportCmdBoss) is used to add groups of static page items to the exported PDF as Form XObjects. Two InDesign features leverage this capability: Master Pages and Data Merge. All non-text, master page items are considered static content; therefore, they are added as Form XObjects. The text feature set supports dynamic features (like page numbers) in master text frames, which makes it hard to determine if a text frame is truly static; therefore, InDesign does not add master text frames to Form XObjects. If you can determine that a master text frame is static, you can use the IPDFFormXOjectData interface to add it to a PDF Form XObject, but be sure the content really is static; otherwise, it will be used incorrectly. Data merge now supports exporting directly to PDF without creating a document. This new feature creates Form XObjects for all static content (including text). Both features use an implementation of IPDFFormXObjectSetupProvider to populate the IPDFFormXOjectData. This is done through a service provider that provides the kPDFFormXObjectSetupService. A default implementation of this service provider is provided by the kPDFFormXObjectSetupServiceImpl implementation. It is not possible to participate in the data-merge collection, even if you implement such a service. This is because data merge queries the service by ClassID. You can, however, participate in the standard PDF export by providing such a service. It is unlikely you will want to interact with the master-page feature's use of Form XObjects. You might consider building a feature that parallels data merge. In this case, you may want to re-use the service-provider approach to populate your data. The interfaces discussed above are found in the following locations: sdk/source/public/interfaces/graphics/IPDFFormXObjectData.h sdk/source/public/interfaces/graphics/IPDFFormXObjectSetupProvider.h
Open Folder The SDK now contains source code for several InDesign user-interface plug-ins. The source code is saved under sdk/source/open. The actual project files are saved in the same directory as the SDK samples, but they contain .open. in their filenames.
What’s New in Adobe InDesign CS4 Products SDK
Improved DollyXs
4
Improved DollyXs The plug-in generation tool, DollyXs, was improved with the addition of 64-bit Windows project settings and preflight code generation. To learn more about DollyXs, see the DollyXs ReadMe file (devtools/sdktools/dollyxs/Readme.txt).
InDesign Server 64-bit Support (Windows only) The Windows version of this SDK includes 64-bit libraries for InDesign Server development. It also includes information on building 64-bit plug-ins in Adobe InDesign Server CS4 Plug-in Techniques. For your convenience, DollyXs now produce 64-bit targets in Windows project files.
Documentation Reorganization The documents in the docs/guides folder were reorganized to allow for better online searching. Prior versions of the SDK contained many Working with ... documents. These documents were combined into one new document, Adobe InDesign CS4 Solutions. Several other documents were added to Adobe InDesign CS4 Products Programming Guide. The root of the SDK also now contains a new document, Getting Started with the Adobe InDesign CS4 Products SDK.
What’s New in Adobe InDesign CS4 Products SDK
Documentation Reorganization 5
© 2008 Adobe Systems Incorporated. All rights reserved. If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. Any references to company names in sample templates are for demonstration purposes only and are not intended to refer to any actual organization. Adobe, the Adobe logo, Creative Suite, InCopy, and InDesign are either registered trademarks or trademarks of Adobe Systems Inc. in the United States and/or other countries. Windows is either a registered trademark or a trademark of Microsoft Corp. in the United States and/or other countries. Mac OS is a trademark of Apple Computer, Inc., registered in the United States and other countries. Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA. Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101, consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein. Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA 95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of 1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60, 60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.
