2) PageItems.itemByName(): With the new layers panel comes a name property for PageItems. In previous versions PageItems.itemByName() would return the page item with the specified label in CS5, it will return the page item with the specified name (which can be set in the Layers Panel). There is no longer a quick-and-easy way to get page items by their label using the 7.0 scripting DOM.

Does this affect only JS scripts, or all scripting? I do Applescripting and we have A LOT of workflow that depends on item labels. Will this change for Applescripting?

Chris

Chris,

I expect that AppleScript users can still take advantage of whose clauses to get at the label (provided they can master the syntax).

In JavaScript, the news is worse than I feared because you can't even use versioning to get around this. All scripts that use item("label") to get at stuff will have to be rewritten.

Dave

Dave,

Aren't you ignoring items on the pasteboard there?

--

Shane Stanley <sstanley@myriad-com.com.au>

Harbs,

I think I must be wrong about this because to my immense surprise your code works -- my surprise is caused by the certainty that that's just what I tried when I concluded it didn't work. I just did this:

1. I created a new document in CS5.

2. I dragged out a text frame and labeled it "Fred".

3. I duped that twice.

4. I ran this script:

var myDoc = app.documents[0];
var myTFs = myDoc.textFrames.item("Fred");
alert(myTFs == null);
app.scriptPreferences.version = "6.0"
var myTFs = myDoc.textFrames.item("Fred").getElements();
app.scriptPreferences.version = "7.0"
alert(myTFs.length);

There's a caveat here. The end result is an array and not a collection. But presumably the getElements() part is optional. Let me try another experiment. Aha! No it's not optional. This might well explain my confusion. This works:

var myDoc = app.documents[0];
app.scriptPreferences.version = "6.0"
var myTFs = myDoc.textFrames.item("Fred");
alert(myTFs.toSource());
app.scriptPreferences.version = "7.0";

But this doesn't:

var myDoc = app.documents[0];
app.scriptPreferences.version = "6.0"
var myTFs = myDoc.textFrames.item("Fred");
app.scriptPreferences.version = "7.0";
alert(myTFs.toSource());

So, if you create an object reference while working within the CS4 versioning engine it won't work when you move back into the CS5 engine. So, by converting to an array--by using getElements()--which is a core feature, you can pass objects effectively from one engine to the other.

So, if you were converting your collection to an array anyway, then this makes converting the script a whole lot easier than I had feared. On the other hand, if you were using the reference as a collection, then you need to stay within the CS4 versioning engine for it to work. I wonder if you can move in and out of versions ... Yes!

var myDoc = app.documents[0];
app.scriptPreferences.version = "6.0"
var myTFs = myDoc.textFrames.item("Fred");
app.scriptPreferences.version = "7.0";
// some code so that something happens while we're in this engine
for (var j = 0; myDoc.textFrames.length > j; j++) {
     myDoc.textFrames[j].fillColor = myDoc.swatches[-1];
}
app.scriptPreferences.version = "6.0"
alert(myTFs.toSource());
app.scriptPreferences.version = "7.0";

Well, this isn't as bad as I feared, but I can see me having to add a lot of versioning statements to scripts I convert from CS4 to CS5

Thanks for pointing me in the right direction Harbs.

Dave

I am not a great scripting hero but i just have one question.

I have a Indesign file wich has a bunch of pages.

On each page there is a textframe wich is labelled "textcode".

When i run the script, Indesign exports each page to a pdf giving the name what's in the labelled textframe.

Update: Sorry guys, wasn't reading good. So the problem is solved!

No. I don't think so.

One of the pain area for XML works in ID.

sudar1983_14 <forums@adobe.com>

07/03/10 02:41 PM

Please respond to

clearspace-721659546-639966-2-2945664@mail.forums.adobe.com

To

Pankaj Chaturvedi <pankaj.c@thomsondigital.com>

cc

Subject

Re: With CS5, some things have changed Re: With CS5, some things have changed

Footnote will allow the xml tags in CS5?

Arivu..

Hey Dave,

you forgot to handle placed XML Elements in your findPage function and made a mistake about the Cell case.

With a selected Cell your switch statement selected the parentTextFrame and breaked the switch. After the break it would run into line

          theObj = theObj.parent;

The parent of pageItem gives you the Spread in InDesign CS5. I've found it wondering why my xml additon does not worked.

I hope i've not introduced new Bugs

function findPage(theObj) {
     if (theObj.hasOwnProperty("baseline")) {
          theObj = theObj.parentTextFrames[0];
     }
     while (theObj != null) {
          if (theObj.hasOwnProperty ("parentPage")) return  theObj.parentPage;
          var whatIsIt = theObj.constructor;
          switch (whatIsIt) {
               case Page : return theObj;
               case Character : theObj = theObj.parentTextFrames[0]; break;
               case Footnote :; // drop through
               case Cell : theObj = theObj.insertionPoints[0].parentTextFrames[0]; break;
               case Note : theObj = theObj.storyOffset.parentTextFrames[0]; break;
               case XMLElement :  if (theObj.insertionPoints[0] != null) { theObj =  theObj.insertionPoints[0].parentTextFrames[0]; break; }
               case Application : return null;
               default: theObj = theObj.parent;
          }
          if (theObj == null) return null;
     }
     return theObj
} // end findPage
 
 
 
 

regards,

gregor

UPDATE: made an addition to the Note case  ...

I think it's worth noting doc.pages[x]textFrames.item("Label") still works. It's only if you try to get the item from the document object where it doesn't work anymore.

I am using a javascript to export a pdf with settings. The script works fine in CS3 and CS4, but not CS5. I get an error from the following line of code for PDF preferences. I am exporting the PDF with OPI. What is the new syntax in CS5 for this setting?

contentToEmbed = PDFContentToEmbed.linkAll;

That didn't work. There has to be some javascript command to do this. It is still available in the PDF settings.

The error is PDFContentToEmbed is undefined. I don't know of any numeric value. This command tells InDesign to create OPI in the PDF for linked images.

I figured it out. I found the answer in Jongwares ID CS5 scripting help files. That command has been substituted with the omitBitmap, OmitEPS to look more like the PDF Export setting.

This is dealt with earlier in this same thread.

Peter

I cant my progress bar working in CS5, it works if i dont trigger it from the menu.

Does anyone have a working script like this?

Here is the script that i made that adds a menu and when you fire the submenu a progress bar should start working in a window, but nothing is happening except when i add an alert, then it fires.

#targetengine "session"
 
// Create menu item
var test_menu = app.menus.item('$ID/Main').submenus.add('Test menu');
 
// Create sub menu action
var test_sub_menu = app.scriptMenuActions.add('Run progressbar');
 
// Set on invoke action
test_sub_menu.eventListeners.add('onInvoke', function() {
     // Create a simple window
     var win = new Window(
          "window { \
               progressbar: Progressbar { size: [400, 10] } \
          }"
     );
 
     // Center and show the window
     win.center();
     win.show();
     
     // Set max value for the progressbar
     win.progressbar.maxvalue = 5;
     
     // Make a simple loop from 0 to 4
     for(var i = 0; i < 5; i++) {
          // This should happen every second
          win.progressbar.value = i;
          
          // Sleep for a second
          $.sleep(1000);
     }
     
     // Remove the test menus actions
     app.scriptMenuActions.item('Run progressbar').remove();
     
     // Remove the test menu
     app.menus.item('$ID/Main').submenus.item('Test menu').remove();
});
 
// Add the sub menu action
test_menu.menuItems.add(test_sub_menu);

I know this is an ancient post but just wondering if you got an answer on how to talk to boxs that have labels in CS5 I am just returning to the workforce and the last scripts I worked on were CS2 and my new company uses CS5. I'll repost my question below if you have any insights that would be great since we seem to have been in the same boat!

I wrote an Applescript at home on my laptop where I only have Adobe CS2 and want to use the same thing at work to show my boss what is possible with Applescript and it is failing at work cause we have Adobe CS5. Specifically placing a picture in InDesign.

This works in CS2 where I am talking to a named picture box

set picToPlace to "ARTWORK:Close Ups:05-02-04:CUA2222.tif" as alias

tell application "Adobe InDesign CS2"

activate

tell document 1

place picToPlace on rectangle "photo1"

fit rectangle "photo1" given proportionally

end tell

end tell

But at work when it gets to the {place picToPlace on rectangle "photo1"} line it stops and says something about "cannot get alias" (and gives the whole path to the file I am trying to place.)

Have they changed the wording for placing a pic in a rectangle? in CS5?