Hello and welcome to InEventScript 1.0.3 for Adobe (R) InDesign and InCopy CS2 (R)!

INSTALLATION

To install InEventScript, copy the InEventScript folder to the Plug-Ins folder located inside the Adobe InDesign CS2 and/or Adobe InCopy CS2 application folder.

Make sure you are installing the appropriate plug-ins for your version of InDesign/InCopy CS. Currently InEventScript supports InDesign/InCopy CS and InDesign/InCopy CS2, each with a separate set of plug-ins.  This distribution is for CS2 only. 

WHAT'S NEW IN 1.0.3

Place event now fires after the user clicks on the page with the loaded place cursor rather than after the import but before the user clicks. After place event now includes drag and drop place.

Added a custom before open document event to handle all situations when a document might be opened, including double clicking in the finder and choosing the document from the recent document menu.

Added 'Run Associated Script' to the flyout menu, which will run the script associated with the selection in the InEventScript palette.

Added a button in the About InEventScript dialog that takes the user to our website to obtain a temporary, fully functioning serial number.

Improved compatibility with WoodWing Smart Connection.

Removed the Scripts item from the Actions item since executing a script before or after a Script Action isn't supported.

Fixed the wording of the Undo action in the InEventScript palette.

Fixed the after event for some dialog actions.

WHAT'S NEW IN 1.0.2

Scripts associated with 'Document...' having "after" timing now work.

The Custom event for 'Open Document' previously executed an associated script after a document started opening, but before it was completely open. This made it impossible to write scripts that affected the document that was opened. The script will now execute after a document is completely opened.

The custom events for open and close have been renamed 'Open Document (After)' and 'Close Document (Before)' in the UI to reflect their timing.

New for CS2, paths entered into the InEventScript.xml file manually can be POSIX or Windows format regardless of the platform InDesign is running on.

The location of the plugin data has now changed. Previous versions of InEventScript stored the plug-in data in the InEventScript folder located in the InDesign application Plug-in directory. The data is now stored in the same location as the rest of the of InDesign's application and preference data. If you desire to keep the data file in the plug-in directory please see the InEventScript Manual on how to achieve this before you install.

DEMO SCRIPTS

The Scripts folder inside the InEventScript folder contains example scripts that you can try out to see InEventScript in action. These scripts are written in JavaScript and will work on either Windows or Mac OS X. When you install the InEventScript folder several of these scripts will be automatically associated with InDesign events. For instance, you will see a dialog presented when you launch InDesign provided by the AppLaunch script. You can delete these associations at any time using the InEventScript palette.

AppLaunch.js :

A simple script that can be associated with the custom 'Launch' event. Displays a message in a dialog.

DocOpenTime.js, DocCloseTime.js :

Try associating these scripts with the Custom events 'Open Document (After)' and 'Close Document (Before)'. With both of these scripts assigned to those events you will see a dialog anytime you close a document that will tell you the amount of time that has elapsed since the document was opened. 

OversetTextWarning.js :

Associate OversetTextWarning.js with the 'Print...' menu action having "before" timing. This will cause the document to be scanned for text frames with overset text whenever you print. If overset text is found, you will see a warning dialog allowing you to cancel the print action. This script is an example of using InEventScript functionality to cancel an action.

ExportContent.js :

This script is intended for association with the 'Save' menu action with "after" timing. When this script executes the content of the document will also be saved in the same directory as the document. Any tagged content will be saved to an XML file and a screen resolution PDF of the document will also be created. In addition, all the text content will be exported to separate text files for each story in the document. 

ExportAllStories.js :

This script will export all the stories in a document as separate files. A Dialog will appear asking for the format to save the files in. The exported files will be created in the parent directory of the document. Try associating this script with the 'Save' menu action.

ExportXML.js :

Associate this script with the 'Save' menu action and every time you save a document, any tagged content will be exported to an XML file in the parent directory of the document. 


DOCUMENTATION

InEventScript 1.0.3 Manual.pdf contains a description of the user interface and describes how to make event to script associations. It also details the xml data file format and how to manually define event to script associations. InDesign CS 2.0 Actions.txt lists the actions available in InDesign and their corresponding Action ID.

Thank you!

RogueSheep Incorporated


Copyright 2004-2006 RogueSheep Incorporated. All rights reserved.
