First I’ll explain what it is all about, and then I’ll dive into some practical scenarios to show you how you can use the Script Label to save lots of time. Most of the info in this blog post is applicable to Mac and Windows versions of InDesign CS, CS2, CS3 or CS4.<\/p>\n
1. Big Word of the Day: Meta-Information<\/h3>\n
In most companies or institutions, ‘Adobe InDesign’ does not live on an island. It’s a cog in a bigger system.<\/p>\n
There is a natural ‘flow’ of information throughout the company – orders or requests come in, and somewhere along the line, designers build or modify InDesign documents based on information they receive one way or another – a project brief, a meeting, an e-mail, a telephone call…<\/p>\n
Then they pass the result of their work on to the next person or system down the line – as an InDesign file, an InCopy file, a PDF file, a web page, a stack of physical paper,…<\/p>\n
In some companies, this flow of information is informal and unstructured.<\/p>\n
In other companies (typically larger ones), the flow of information has more or less structure. There are rules and procedures and regulations. You’ll hear about things like ‘order forms’ or ‘job tickets’ or ‘job jackets’ being passed around.<\/p>\n
Sometimes there are tangible envelopes or manilla folders with stuff in them, sometimes there is just electronic data being passed around via a central computer system…<\/p>\n
In all this hustle and bustle, having a way to keep some tidbits of extra information about an InDesign document inside the document can come in very handy.<\/p>\n
This extra info is not meant to be part of the printed end-result. Instead it provides you with critical info about the document: who is the customer? By when is it due? Who should you ring if you have questions? What inks can you use? What is the target resolution? How many pages can you have? And so on…<\/p>\n
All such information is sometimes referred to as meta-information – it’s information about how to treat the information in the document.<\/p>\n
Having the answers to questions like the ones above readily available ‘inside’ the InDesign document can make a world of difference. No need to ring around in order to figure something out if the info is right there for you to read, inside the document.<\/p>\n
There are many ways to do this.<\/p>\n
You might have a simple text frame out on the pasteboard with information typed into it. (On a related note – you might want to check out our free HistoryLog<\/a><\/em> plug-in – it uses this idea to provide you with an automatic document history. https:\/\/www.rorohiko.com\/wordpress\/indesign-downloads\/history-log\/<\/a>).<\/p>\n You might be using part of the document name to refer to the customer code or hold a deadline date (e.g. so you’d know that a document called RORO12_20091112.indd<\/em> is related to customer code RORO12 <\/em>and is due by 12-Nov-2009).<\/p>\n Meta-information is where the Script Label comes in handy: the Script Label is a convenient way to attach a little bit of text, any text, to a page item.<\/p>\n InDesign does not care what text you attach. Whatever you put into the script label won’t normally affect the output of your document – but it’ll keep the text with the page item.<\/p>\n Some people use the Script Label to tag page items for automated processing by a script – hence its name ‘Script Label’: it is very often used by script developers.<\/p>\n However, it is not limited to just that. Your imagination is the limit.<\/p>\n I’ve made up a sample scenario here – read it, and that might give you some new ideas. I’ve called this scenario ‘the todo-list-scenario’.<\/p>\n There’s some scripting involved, but you don’t need any scripting knowledge to make use of it – if you can follow instructions, you should be able to make this work.<\/p>\n The problem: imagine I have a spread with heaps of text frames, and all of these page items need to be inspected. Some of them need to be modified depending on what I find.<\/p>\n Suppose all these text frames contain customer comments for the Playamathing<\/em> toy, and they might or might not contain a reference to a color.<\/p>\n There’s a frame that contains the text “I really love the red Playamathing”. Another says “The yellow Playamathing with the extra knobs is my favourite”, and so on… Imagine there are hundreds of those frames, scattered all over the layout in a fairly haphazard layout.<\/p>\n My task is to read all these bits of text, and change the background of the frames to match the color mentioned, if there is one. If no color is mentioned, I am to leave the background white.<\/p>\n How do I keep track of which ones I’ve inspected and which ones I still need to do? Script Label to the rescue!<\/p>\n First of all, I select all text frames. Then I bring up the Script Label palette and type ‘TODO’ in it. Then I click somewhere in the pasteboard area.\u00a0Through that simple manipulation, I’ve now ‘marked’ all selected text frames with a script label ‘TODO’.<\/p>\n I now keep the Script Label palette open, and each time I finish one of the text frames, I simply remove the ‘TODO’ from the script label for that text frame.<\/p>\n This approach is still rather cumbersome, and we’ll improve it through a few simple scripts and keyboard shortcuts. Here’s how!<\/p>\n Open a text editor. You could use Notepad<\/em> on Windows, or TextWrangler<\/em> (http:\/\/www.barebones.com<\/a>) on Mac.<\/p>\n Don’t use the Apple-provided TextEditor<\/em> – it will try to save your script in RTF format instead of plain text, and then it won’t work.<\/p>\n Tip: if you’re really in a bind, Stickies<\/em> (the sticky-note app that comes with Mac OS X) works better than TextEditor<\/em> when it comes to creating plain text files.<\/p>\n Type the following text into a new text file:<\/p>\n This is a one-line script. There are a few small ‘gotchas’, and I’ll discuss those later, but it’ll do.<\/p>\n Save the one-line text document into a file called mark_todo.jsx<\/em><\/p>\n Make sure the file extension is .jsx<\/em>, not something else. It’s easy to accidentally create a file called mark_todo.jsx.txt<\/em> (with an extra .txt<\/em> file name extension). To compound that problem, the Windows Explorer or Mac Finder are often configured to not show the final .txt<\/em>, and hence such a file might look<\/em> OK, yet refuse to work. Be aware that what looks like a .jsx<\/em> file might not be one.<\/p>\n Now, store this mark_todo.jsx<\/em> file in the InDesign Scripts – Scripts Panels<\/em> folder. Go to your InDesign application folder, then into Scripts<\/em>, then into Scripts Panels<\/em>. Put the mark_todo.jsx<\/em> file there.<\/p>\n (A method to quickly get to the Scripts Panel<\/em> folder is to right-click or control-click the Application<\/em> folder on the Scripts Palette<\/em> in InDesign and then select Reveal in Finder<\/em> or Reveal in Explorer<\/em>).<\/p>\n Now duplicate mark_todo.jsx<\/em> file, and rename the duplicated file to unmark_todo.jsx<\/em>. Then open unmark_todo.jsx<\/em> in your text editor and eliminate the four letters of TODO, so it reads:<\/p>\n Go back to InDesign. On the Scripts Palette in InDesign, when you double-click either mark_todo.jsx <\/em>or unmark_todo.jsx<\/em>, they will look at the current selection, then take the very first item in that selection, and adjust the script label of that item to either be TODO or nothing.<\/p>\n These two scripts have some limitations, as you’ll find out. Try this: make sure no page item is selected and then double-click either one of them on the scripts palette.<\/p>\n You get a nice big fat error dialog: the script is trying to access part of ‘the selection’ and nothing is selected, so InDesign is a little bit unhappy about that.<\/p>\n Not to worry! You can safely ignore this – nothing bad has happened.\u00a0We’ll just live with that behavior for now – simply keep in mind that you must have a single item selected before running either script.<\/p>\n The next step is to assign some keyboard shortcuts to these two scripts. Go to Edit – Keyboard Shortcuts<\/em>, and create a new set if necessary – I created a set called Todo Script Set<\/em>. Go into the Product Area Scripts<\/em>, and then assign shortcuts to the two scripts – on my Mac, I’ve assigned them Ctrl+T<\/em> and Ctrl+U<\/em>. On Windows you might want to pick some other shortcuts – pick something that works for you.<\/p>\n The scripts palette should now show these shortcuts next to the scripts. Bring the Script Label<\/em> palette into view, select a page item and repeatedly hit Ctrl+T<\/em> followed by Ctrl+U <\/em>while observing the Script Label<\/em> palette.\u00a0The word TODO<\/em> should appear and disappear from the Script Label<\/em> palette each time you hit the shortcut.<\/p>\n That’s another step in the right direction – marking and unmarking individual page items just became a whole lot easier.<\/p>\n Now the next question is: how to quickly find page items that still have a ‘TODO’ script label? Sadly enough the standard ‘Find’ function in InDesign does not seem to be of much help.<\/p>\n Scripting to the rescue! Below a script that finds the next item with a ‘TODO’ script label.<\/p>\n I won’t elaborate on how this script works – if you’ve done some ExtendScript-ing before it should be fairly easy to follow. If you’re new to ExtendScript – simply make sure you copy the script verbatim.<\/p>\n Save this script to your Scripts Panel folder as next_todo.jsx<\/em>.<\/p>\n Each time you double-click this script, the currently selected item will ‘jump’ to the next item that still has a TODO<\/em> label. You can assign another shortcut key to this script – I used Ctrl+N<\/em> on my Mac.\u00a0Each time I hit Ctrl+N<\/em>, my selection jumps to the next page item with a TODO<\/em> label.<\/p>\n We’re not done yet! If you install our FrameReporter plug-in (https:\/\/www.rorohiko.com\/framereporter<\/a>) you can configure it to visually show the script labels. With FrameReporter active, and configured like this:<\/p>\n I can do Select All<\/em> on my spread, and I get to see this:<\/p>\n I can immediately see that two of the three items still haven’t been examined. Unlike most of our plug-ins,\u00a0FrameReporter<\/em><\/a> is not a freebie, but it’s still a steal at just US$29.<\/p>\n But wait, there is more! Soon, we’ll have the YeShore<\/em> plug-in available which extends the InDesign CS4 Live Preflight (https:\/\/www.rorohiko.com\/wordpress\/yeshore<\/a>). It has a number of powerful new preflight rules, one of which involves script labels.<\/p>\n If you have YeShore<\/em> installed (e.g. because you’re on our beta program – check the web page to find out more), you can configure a rule to find all unfinished page items:<\/p>\n I’ve made a preflight profile called ‘Check all done’ and added a rule that says that the script label should not be TODO<\/em>. With this profile active, it becomes very easy to see how many items I still have to handle, and to ‘hop’ to any items that are still marked as TODO<\/em>. I simply click on one of the lines in the Preflight panel and InDesign immediately selects the corresponding item.<\/p>\n I hope that these samples are useful! And if you’re interested, check out FrameReporter<\/em><\/a>, or stay tuned to hear more about YeShore<\/em><\/a>!<\/p>\n Cheers,<\/p>\n Kris<\/p>\n","protected":false},"excerpt":{"rendered":" In this blog post, I want to talk a bit about the secretive Script Label in InDesign. You might have noticed the Script Label palette, and wondered what it was used for – it’s under Windows – Automation – Script … Continue reading 2. Practical Use of the Script Label<\/h3>\n
2.1 Marking page items with a script label<\/h4>\n
![\"snap1\"](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/snap1.png\" "\\"snap1\\"")
<\/p>\n![\"snap2\"](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/snap2.png\" "\\"snap2\\"")
<\/p>\n2.2 Using Scripts<\/h4>\n
app.selection[0].label = \"TODO\";<\/pre>\n
![\"snap3\"](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/snap3.png\" "\\"snap3\\"")
<\/p>\napp.selection[0].label = \"\";<\/pre>\n
![\"snap3a\"](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/snap3a.png\" "\\"snap3a\\"")
<\/p>\n![\"blog_scriptlabel_errormessage\"](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/blog_scriptlabel_errormessage.png\" "\\"blog_scriptlabel_errormessage\\"")
<\/p>\n2.3 Using Keyboard Shortcuts<\/h4>\n
![\"blog_scriptlabel_keyboardshortcuts\"](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/blog_scriptlabel_keyboardshortcuts.png\" "\\"blog_scriptlabel_keyboardshortcuts\\"")
<\/p>\n2.4 Finding marked items<\/h4>\n
do\r\n{\r\n if (app.documents.length == 0)\r\n {\r\n break;\r\n }\r\n\r\n var document = app.activeDocument;\r\n if (! (document instanceof Document))\r\n {\r\n break;\r\n }\r\n\r\n var currentItem = null;\r\n if (app.selection.length > 0)\r\n {\r\n currentItem = app.selection[0];\r\n }\r\n\r\n var undoneItems = [];\r\n for (var idx = 0; idx < document.allPageItems.length; idx++)\r\n {\r\n var pageItem = document.allPageItems[idx];\r\n if (pageItem.label == \"TODO\")\r\n {\r\n undoneItems.push(pageItem);\r\n }\r\n }\r\n if (undoneItems.length <= 0)\r\n {\r\n break;\r\n }\r\n\r\n var nextItemIdx = 0;\r\n\r\n if (currentItem != null)\r\n {\r\n var currentItemIdx = -1;\r\n var searchItemIdx = 0;\r\n while (currentItemIdx == -1 && searchItemIdx < undoneItems.length)\r\n {\r\n if (undoneItems[searchItemIdx] == currentItem)\r\n {\r\n currentItemIdx = searchItemIdx;\r\n }\r\n searchItemIdx++;\r\n }\r\n if (currentItemIdx >= 0)\r\n {\r\n nextItemIdx = currentItemIdx + 1;\r\n if (nextItemIdx >= undoneItems.length)\r\n {\r\n nextItemIdx = 0;\r\n }\r\n }\r\n }\r\n\r\n app.select(undoneItems[nextItemIdx]);\r\n}\r\nwhile (false);<\/pre>\n2.5 Seeing Marked Items<\/h4>\n
![\"Screen](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/Screen-shot-2009-11-18-at-3.26.27-PM.png\" "\\"Screen")
<\/p>\n![\"Screen](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/Screen-shot-2009-11-18-at-3.29.23-PM.png\" "\\"Screen")
<\/p>\n2.6 InDesign CS4 Live Preflight<\/h4>\n
![\"Screen](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/Screen-shot-2009-11-18-at-3.34.43-PM.png\" "\\"Screen")
<\/p>\n![\"Screen](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2009\/11\/Screen-shot-2009-11-18-at-3.37.12-PM.png\" "\\"Screen")
3. Conclusion<\/h3>\n