ExtendScript of the Week: Close All Files in a Book without Saving

Wednesday, November 16 2011 @ 5:07 AM, By anarora

 

Continuing with the series ‘Extendscript of the week’, we are providing an extendscript to Close All Files in a Book without Saving. This will show how to use FrameMaker ESTK to traverse a hierarchical book and perform operations on its components.

Download the zip file from CloseAllFilesInBookScript and unzip the content to local disk.

About the Script

  • It contains 3 scripts, CloseAllFilesInBook.jsx which is the caller function to handle the complete workflow, BookIterator.jsx which is used to iterate over the book components and BookCloseAllUtils.jsx that has utility functions used in the automation
  • The script works on all file types (FM/MIF/XML/Ditamap), nested books and its components as well as on the hierarchical components (Folders templates). Parameters have been defined in the main function according to which the components types will be acted upon (to process or leave unprocessed) making it a configurable setting.
  • The script traverses through all the open files in the book and closes it without prompting the user for Save dialog.  By default no file is saved.

Steps to use the Script?

  • Launch FrameMaker
  • Open any book (or use the file Sample.book from the samples provided here: CloseAllFilesInBookSampleFiles)
  • With focus on book, run the script CloseAllFilesInBook.jsx. This will create a new menu item in Book Menu
  • Goto File->Utilities->Close All Files in Book Without Saving
  • All open book files will now be closed without any prompt

This script will help reduce the painful task on clicking on the dialog each time on closing multiple files. It can be easily modified to Save all the files by default.

 

Regards,
Anchal Arora

FrameMaker Engineering Team

(Resources: CloseAllFilesInBookScriptCloseAllFilesInBookSampleFiles)

  • Categories

  • Archives

  • Authors

  • Useful Links

  • Recent Comments

    • Joel: Thanks for fixing the links guys!
    • Maxwell Hoffmann: Ted, one aspect of the blog that may have escaped your notice; you can launch the HTML5 version in...
    • Maxwell Hoffmann: Joel, per comments made above, I discovered that the original URLs were incorrect with pointers to...
    • Maxwell Hoffmann: Paul, as I indicated in the comments below, the original blog had links that pointed to a...
    • Maxwell Hoffmann: I apologize to all concerned regarding my suggestion to “clear the cache” … it...