[JS] [CS3 onwards]

Hi.
I am needing to include in my script the ability to change paragraph styles, but the target style is within a paragraph style folder.
My current code for a folderless structure is this:
if(myStory.paragraphs[ii].appliedParagraphStyle.name == "PRO - Product Heading")
myStory.paragraphs[ii].appliedParagraphStyle = "PRO - Product Heading " + myColour;
I know how to get the folder name of a style by using the parent property, but how to apply with that parent property is where I am stuck.
I had thought (and foolishly tried) myStory.paragraphs[ii].appliedParagraphStyle = "Pro:PRO - Product Heading " + myColour; thinking that "Pro:" would look for a style folder, but that didn't work.
Any help as always would be greatfully received.
Cheers
Roy

The problem here is that JS silently looks up things if it cannot apply your current command. In the case of setting a paragraph style, you can feed it a string, but that actually gets checked against the current list of paragraph styles, and it's the style itself that gets used.
This ought to work:
myGroup = app.activeDocument.paragraphStyleGroups.item("PRO");
myDirectLinkToAStyle = myGroup.paragraphStyles.item("PRO - Product Heading :+color);
.. stuff here ..
myStory.paragraphs[ii].appliedParagraphStyle = myDirectLinkToAStyle;
Untested, untried, etc. You know the drill.
(I always type a post in full before daring to click any of the horrendous Jive formatting buttons. I find it inexplicably difficult to edit code with that weird and unpredictably-behaving Code Formatting thingamajig. Before not-that-long-ago, I simply switched to HTML mode and injected my edits straight into the correct place, but -- oh sadness! -- New and Improved Jive seems to bracket each and every single character with some "function (bladiblah) (release(whatever))" crap code.
Since the Adobe programmers seem to have grown a liking to Flash, WRITE A FLASH EDITOR for the forums! Or simply buy one -- I've seen a-plenty online Flash editors with lotsa nice features. Either way, get rid of this Jive bull.)

Similar Messages

[JS] [CS3 onwards] Simplify some code

Hi.
I have been using a for loop to find a certain paragraoh by its style name for a while now, and I am wondering if I am using the best approach?
I am using:
for (x=0;x<=myStory.paragraphs.length-1;x++)
     if(myStory.paragraphs[x].appliedParagraphStyle.name == "SOS - Savings")
     code here...
but wondering if I can use somethng like:
mySavePrice = myStory.paragraphs.appliedParagraphStyle.name("SOS - Savings");
Just a thought...
Cheers
Roy

Roy,
I sometimes use this approach to processing a story. Usually, I'll have a large switch that operates on the appliedParagraphStyle.name property. But, unfortunately, this:
myStory = app.selection[0].parentStory;
myPSnames = myStory.paragraphs.everyItem().appliedParagraphStyle.name;
Doesn't work. So, instead, I use:
myStory = app.selection[0].parentStory;
myPstyles = myStory.paragraphs.everyItem().appliedParagraphStyle;
for (var j = myPstyles.length - 1; j >= 0; j--) {
     switch (myPstyles[j].name) {
          case ...
          case ...
etc.
Dave

[JS] [CS3 onwards] Scripting Styles within folders

Hi.
This is my second attempt with this thread, as I failed to add a sufficient title last time.
http://forums.adobe.com/thread/631524?tstart=0
This is the link to the original thread... I am hoping I am not making my error worse by doing this!
Cheers
Roy

The problem here is that JS silently looks up things if it cannot apply your current command. In the case of setting a paragraph style, you can feed it a string, but that actually gets checked against the current list of paragraph styles, and it's the style itself that gets used.
This ought to work:
myGroup = app.activeDocument.paragraphStyleGroups.item("PRO");
myDirectLinkToAStyle = myGroup.paragraphStyles.item("PRO - Product Heading :+color);
.. stuff here ..
myStory.paragraphs[ii].appliedParagraphStyle = myDirectLinkToAStyle;
Untested, untried, etc. You know the drill.
(I always type a post in full before daring to click any of the horrendous Jive formatting buttons. I find it inexplicably difficult to edit code with that weird and unpredictably-behaving Code Formatting thingamajig. Before not-that-long-ago, I simply switched to HTML mode and injected my edits straight into the correct place, but -- oh sadness! -- New and Improved Jive seems to bracket each and every single character with some "function (bladiblah) (release(whatever))" crap code.
Since the Adobe programmers seem to have grown a liking to Flash, WRITE A FLASH EDITOR for the forums! Or simply buy one -- I've seen a-plenty online Flash editors with lotsa nice features. Either way, get rid of this Jive bull.)

[JS][CS3] Change the content type of a text frame

Hi,
a bit basic maybe but I'm stuck on this from an hour...
I need a textFrame to become a graphic object.
The textFrame has no content.
How can I change the contentType on that object?
Thanks anticipately.

This looked like an interesting challenge, so I'm taking a shot at it. I created a new document and added three text frames (unpopulated) to the first page. I tagged them "Image", "Caption" and "credit". I then exported as a snippet, deleted the document and opened another new one. Then I placed the snippet (so far, everything has been manual -- no scripts) and indeed, the snippet placed and the frames were added to the document's structure and were properly tagged -- the three tags were automatically created by the action of placing the snippet.
So, let's duplicate this in a script. Even though I know exactly where the snippet is, I'm going ask the user to find it. That way, I eliminate the issue of getting the path to the snippet wrong:
var myDoc = app.documents.add();
var myPage = myDoc.pages[0];
var myPlacePoint = [myPage.marginPreferences.left, myPage.marginPreferences.top];
var mySnippetFile = File.openDialog("Choose the snippet");
if (mySnippetFile == null) { exit() }
var mySnippet = myPage.place(mySnippetFile, myPlacePoint);
And that worked. The snippet is on the page exactly where I wanted it. So, now we need to find the text frame that has the "image" tag. First, we must explore just what mySnippet consists of.
OK, it's an array of three stories. That's a tad weird. Why isn't it an array of three text frames? I wonder what would happen if two of the frames in the snippet were threaded -- but let's address that later after we solve the immediate issue. The point is that we know that the snippet consists of three separate text frames that aren't threaded. So:
for (var j = mySnippet.length - 1; j >= 0; j--) {
     var myTag = mySnippet[j].associatedXMLElement.markupTag.name;
     alert(myTag);
And this gives me the three tags (and reminds us that when you tag a text frame you're also tagging the story that holds it. So:
var myDoc = app.documents.add();
var myPage = myDoc.pages[0];
var myPlacePoint = [myPage.marginPreferences.left, myPage.marginPreferences.top];
var mySnippetFile = File.openDialog("Choose the snippet");
if (mySnippetFile == null) { exit() }
var mySnippet = myPage.place(mySnippetFile, myPlacePoint);
for (var j = mySnippet.length - 1; j >= 0; j--) {
     var myTag = mySnippet[j].associatedXMLElement.markupTag.name;
     if (myTag === "Image") {
          var myFrame = mySnippet[j].textContainers[0];
          myFrame.contentType = ContentType.graphicType;
          break;
And that does the job.
Thomas,
You were very close but you forgot that the text frames that make up a story are addressed as textContainers from CS3 onwards. Your code would have worked in CS2.
Dave

CS 2 run on Windows 8.1 64 bit?

My old computer running Windows XP died. I need to reinstall CS2 on my new computer running Windows 8.1 64 bit. I reinstalled the entire suite but cannot activate it. Followed Adobe instructions to uninstal it then looked for the CS2 non activation version download. Can only find CS3 onwards. Any suggestions more than welcome.

Download Acrobat 7 and CS2 products Use the new serial number provided with the download.

Creating something better than Photoshop CC ?

The basic CC concept just doesn't work for many people, including myself. Bottom line: there must be a perpetual license option for a basic photo image editing program. For many photographers, Photoshop Elements just isn't robust enough. My guess is that other companies will jump into this huge new market, but that's going to take time.
It looks like Adobe is the only company in the position to produce a solution in the short term. So let's start there.
Over at the Kelby Blog and NAPP (the "Photoshop Guys," NAPP memebers and Blog contributors) they are actually working on a product concept to present to Adobe in response to CC. It's initially being called "LightShop" and its basic premise is to be a stripped-down Photoshop CC that integrates with Lightroom. It will have minimal Type, no 3D, no video, and less special effects and other bloat -- just a clear Lightroom-like interface that is smooth and fast. Most important, it sells as a perpetual license like Lightroom, for under $200. This concept sounds interesting -- if you're into Lightroom. I'm not.
Another idea is for Adobe to offer something like a Photoshop Elements "Extended Edition." Now that they have killed the Standard Edition of Photoshop, a product like that would not encroach upon the now professional market focus of Photoshop CC. It would be relatively easy to produce because most of the code is already in Photoshop Elements for more advanced features -- it's just turned off. ACR already comes with Elements, and Bridge could be included as before. If some of the deficiencies of standard Elements could be addressed, and some of the consumer oriented bling thrown out, then it could be ideal for amateur to semi-pro photographers. Photoshop plug-ins would work as they do now. Sell a perpetual license for under $200, and I think a lot of non-CC customers would be happy. An upgrade from CS3 onwards would be great too, for maybe $100.
But exactly what features would be best for a Photoshop CC alternative product? Is 16-bit necessary if you are global-editing RAW in ACR or Lightroom? Can you really tell the difference in a print or on the Web? What about Blend Modes -- do we need that many? How about just one sharpening filter -- the upcoming version of Smart Sharpen?

You bring up a great point. Lets say when we eventually die and lets say our family or even clients want to see what we have done. Adobe with cc in a way has cut off your legacy by not having a perpetual program that can automatically open your files. Which is different from saving as older file type.
If cc had more price options i would be very temped to join it. Ither a 30-40$/month plan for say a suite as they have done for years or pick your favorite 3 programs and 1-2 minior ones like bridge or acrobat. I would also like to see a 10-15/month plan for just 1 program but that is not a special offer but long standing price. Im sure the cc price will change within the next 12 months which is for good or bad why you can only lock in a 1 year plan. It would be nice if like a phone you could lock in your plan price for 2 years. At least you would know what to expect. Adobe should look at phone subscriptions and see how we get people to pay 90/month for a phone which for many is a toy and they cant get people to pay 50/month for tools. With phones when you renew your contract gennerally every 2 years you get a massive discount on some new phones and some will actaully be free or upto 70% off. Adobe shoudl consider this. The more adobe products you have the bigger your renew discount should be. They could do it as 2 year contract or have several durations besides monthly and yearly. Have a 6 month, 18 and 24 month. Say you pay 50/month for your contract duration of 1 year, when it comes time to renew you should have a discount lets say 10-20% off which would be 40-45$ which is handy. If you upgrade to cc and have a suite you should have a biggerest discount than just 1 program say instead of 40/month like 30/month for that contract duration and if you have master collection maybe 20/month for the duration. Then with those 2 suites when its time to renew still give a discount but maybe less. Maybe a suite becomes 40/month and master 30/month but give more discount than those who just renewed. Give us what feels like incentives not punishments.
Ya having 3 almost 4 photoshops was getting a big crazy. Photoshop extended, photohop, photoshop elements and light room. I guess its good for adobe to consolidate but they could have done it with out the cloud. Just make elements and lightroom merged and bump up the price maybe 40%. I think thats fair. Similarly with photoshop and extended, merge the 2 and increase price to 1/2 way between both. Starts getting weird when you have many overlapping things. Like web design has dream weaver and muse. I would love to get that as 1 program or a package deal since they do the same thing but go about it differently. Merge them as 1 and increase price 40%. Same with indesign and incopy, merge them together and increase price 40%. This will make each program stronger and a better buy. Just good house keeping to simplify. Adobe offers so many things I honestly dont know what some of their new things like fusion do. Many have only been around 1-2 years and its becoming complicated to know about all their stuff especially when they start overlapping.
Good luck adobe. I do love you but you are breaking my heart. I want to stay but you need to make some changes to help me want to.

Middle East, Arabic, Hebrew language for Adobe Design Standard or Premium?

Where can I find those? Are there trials for Adobe Design Premium or Standard, any version from CS3 onwards in Middle East, Arabic or Hebrew language?
Either to buy or to download. If not from Adobe itself, what sites can be trusted?
I see some upgrade language kits from languagesource dot com for example but not sure about those.
Any suggestions?

Dear Jeff A eright I wish to use CS3 I am not Expert I am new in this field therefor I wanted to use CS3 trial Middle Eastern b/c I am working in Muslim country this time, If I could be able to use & understand CS3 I will buy it but I don't want to try each software alone, I want to download suite, if I would be satisfied with CS3 I will use it, if I couldn't then will buy CS2 Middle Eastern, also I had downloaded Photoshop CS3 English version it was asking for searial I wanted to use that 30 days trial but I couldn't get that as trial, you are Adobe employee & you can do some thing for me, I just want only legal Copy & you are able to provide its link & thats is not piracy you know it, about win-soft I don't like them, there is no any thing to download for me I also want to try InDesign & Photoshop CS2 Middle Eastern, but I can't download from there site, CS2 or CS3 would be better & enough for me, so kindly do something for me if you can.

Linked Image Border Problems

This just started happening, and I can't figure out how or
how to fix it. When I open up a blank HTML page, insert an image,
then add a link to the image, DW automatically inserts a solid
border around the image. The border property is blank, where it
used to default to 0. I can manually change the border to 0 and it
gets rid of the border...but this is a pain to do for every single
linked image! Does anyone know what the problem is or how to fix
it? It used to automatically default to 0. I am using the latest DW
included with CS3.

> When I open up a blank HTML page, insert an image, then
add a link to the
> image, DW
> automatically inserts a solid border around the image.
This is actually default browser behaviour which DW is
emulating with the
code it's been given.
>The border property is
> blank, where it used to default to 0. I can manually
change the border to
> 0 and
> it gets rid of the border...but this is a pain to do for
every single
> linked
> image!
Pre-CS3, DW automatically inserted the border="0" attribute
into the <img>
tag on every single linked image.
From CS3 onwards, Adobe is dropping HTML formatting
attributes and
encouraging everyone to use CSS.
>Does anyone know what the problem is or how to fix it? It
used to
> automatically default to 0. I am using the latest DW
included with CS3.
The CSS fix is much easier than the previous default to
border="0"
behaviour.
Just add "a img ( border: none; }" (without the quotes) to
your external
linked stylesheet.
Regards
John Waller

How to import a c. 2001 Premiere 6 project?

I used Premiere on the Mac until Adobe abandoned the Mac platform, and I have several projects, including a documentary, that I cut in it. I believe that version was Premiere 6, maybe 6.5?, sometime around 2001.
Now that Premiere is back on the Mac, I'd like to revive those old projects and recut them, but I see this:
Premiere Pro on Mac OS imports projects from version CS3 onwards. You need the Windows version to open projects from earlier versions and save them as a current one.
Can it really be they are they saying you need a Windows version of Premiere Pro CC to open an older Mac-generated project? Or are they saying you need a legacy, PC version of Premiere to pull an old project into the present?
If it's the former, I suppose I need to find someone with Premiere Pro CC on Windows, yes? And then that new project (imported into the prproj format) will be openable by Premiere Pro Mac?

Hi luchesse. Congratulations on inheriting the new position
and welcome to the world of RH.
You can start by looking at
this
link on Peter Grainge's site. Whilst you are there, bookmark
his home page as it is an encyclopedia RH resource.
Something else to check is that your project's source files
are on a local drive? RH and network drives aren't buddies!

Photoshop archaeology -- when was the 1TB disk size limitation removed?

I've just joined a photo lab as IT manager. They are running a mixture of Photoshoop versions and have some horrible operational hacks to get around the 1TB drive size limiation in PS 7. We're a small shop and can't afford to upgrade all of our Photoshop licenses at once, so I want to start by upgrading everyone running a version that has the 1TB limitation.
Does anyone know in which version that limtation was lifted? I have looked at release notes for CS3 onward; have not been able to find release notes for CS and CS2.
TIA for any info.
Stu

I'm not sure of the answer to your question, but I would keep one or two "legacy" systems around, for plug-ins that won't run in more modern versions. You may also want to do this to support legacy hardware.
I say this as I am planning a new hardware purchase to build such a "throwback" system - a couple of scanners and a Xaos Tools plug-in don't like the modern era.

An Open Letter To Adobe Systems from Scott Kelby about Creative Suite pricing

http://www.scottkelby.com/blog/2011/archives/22903

PECourtejoie wrote:
1)Historically, there has always been a grace period, that allowed get the newer version for free if you purchased the old one very close, or after the announcement, and before the actual disponibility of the new version of the Creative Suite. This would allow, this time, to upgrade from CS3 onwards to CS5.5, and get CS "next", bypassing, this time, the one version limit.
That's true, and it's something I was thinking about afterwards. I remember after CS5 was announced, there was a grace period of several weeks where if you bought or upgraded to the CS4 version of your suite or product, you'd be entitled to a free upgrade to CS5 when it shipped. If that was the case this time around, then I would take advantage of it and upgrade to CS5.5 during the grace period in order to get CS6.
PECourtejoie wrote:
But in fact the Creative Cloud is already cheaper if you add the point versions upgrades, subscriptions to Muse, Carousel and maybe Edge, plus the price of whatever tablet apps are released.
Compared to the Master Suite.
If one uses only, say the Video Production, and has no need for the other offerings, going the Creative Cloud way is more expensive.
While that's true, there are also many people who find the prospect of cloud software subscriptions unappealing (myself, for one). I vastly prefer paying for something once and having it from that time on. The Creative Cloud subscription seems like a good deal for those who don't have that prejudice, or those who might want to use the additional "cloud" services that the boxed/download perpetual license won't have, but that won't be enough to change the minds of many customers. The Creative Cloud will apparently be around $50 a month, so it works out to $600/year. Assuming Adobe sticks to a 24 month cycle for major versions, always with a x.5 release around the half-way point (and assuming the upgrade prices for the perpetual license stay about what they are now), then the Creative Suite "box" upgrade will still be slightly cheaper, dollar-wise. To upgrade from CS5 to 5.5 is $550, and I'm assuming 5.5 to 6 might be around that same price, and then CS5 to 6 assuming the $950 position on that upgrade guide chart). When we're going to CS7, then I assume those prices will remain about equivalent for upgrades from CS6 and 6.5.
However Adobe decides to deal with this customer backlash, there are numerous ways they can appease most of us. Sony Creative Software has the most generous upgrade policies I've encountered for their products (granted, they only really offer competing products for Premiere Pro and Audition); Adobe is looking mighty greedy next to such companies right now. This thread alone has some good suggestions,
1) Allow a grace period with CS6 so that users of CS3 and CS4 aren't left out in the cold, becase many of us will simply go elsewhere if this doesn't happen. This could either take the form of an "upgrade to CS5.5, receive CS6 free" once CS6 is officially announced, or a period of 1-2 months after CS6 ships during which upgrades from CS3 and CS4 are allowed.
2) If they stick to the "1 version back", a price reduction of a couple hundred off the suite upgrades might help soften the blow.
3) Consider a "2 version back" instead.
Or some combination of features from the above.
Truth be told, if Adobe sticks to a ~24 month release cycle for major versions from here on out, I wouldn't really be opposed to upgrading every major version. $950-$1000 every 2 years to keep the Master Collection current sounds like a pretty good deal to me. But if Adobe expects me to buy CS6 as if I'm a new customer when I own both CS and CS3, they're in for a rude awakening.

I own Adobe CS4 (student edition) and I'd like to upgrade to Creative Cloud but it seems I don't qualify for it. Why?

Hi, I would like to understand why I don't qualify for an upgrade as any other Adobe's customer from CS3 onwards.
I have with me the serial number and original disks. Any help would be much appreciated. Thanks, Paola

paomezza wrote:
Hi, I would like to understand why I don't qualify for an upgrade as any other Adobe's customer from CS3 onwards.
Adobe typically does a poor job of making the fine print obvious.
See Terms and conditions
"This offer is not available to Education, OEM, or volume licensing customers."
Other offer are currently available though
Adobe Creative Cloud for students and teachers | Adobe

Can the current "40% discount offer" be used if you are already paying for Creative Cloud?

I saw people sharing this offer through different socail networks:
https://creativecloud-specialoffer.adobe.com/special-offer/?loc=en_GB&cc=GB
Im already a paying Creative Cloud customer, and i would love to only pay 40% of what i do now for a year.
Starting a new business, i need to keep costs as low as possible, so this would be heaven sent.
So can i "Upgrade" my current subscription to this new discounted one?
I hope someone can help me out.
Best reguards!

The offer is for customers who own a perpetual license from CS3 onwards. Thus the wording "Offer available to all registered users of individual products and suites, CS3 or later."

Are older versions of adobe creative suites supported by OS X Mavericks

Is adobe creative suites CS3 supported by OS X Mavericks?

From what people have reported here, anything from CS3 onwards is supported. I run CS4 with no issues.
Pete

A positive report (so far)

I have been a long time Premiere user (version 3, yes 3, not CS3 onward) and have been generally pleased with the overall experience. I also was being a bit of a bug about the subscription idea (too many bad experiences with the likes of Auto Desk and the ilk) and I found the idea of being forced to upgrade as versions came out or face an ever increasing upgrade fee distasteful. I have Master Collection and that is not inconsequential to do. Well after cooling my jets and actually looking at the Creative Cloud offer, I upgraded (at a very reasonable cost). Being on a continual upgrade path is nice as well.
Positive Point One: Upgrade model is friendly
Additionally since the version 6 Premiere I have dearly missed hearing audio in the trim monitor. When I complained I received overwhelming silence. Adobe suggested a feature request and the community said "maybe that was useful, I've never really needed that, what do you use that for". My work flow. Timeline, fast forward looking for breaks and mark them, goto top and use shortcuts to advance to next marker, cut. Go to top, open Trim Monitor and advance through, quickly ripple and rock-n-roll through cut points (listening to audio as well as looking at picture to find the rough cuts)
IT'S BACK!!! Audio in the trim mode . Additionally now material on different tracks trim just fine. No advancing along and skipping chunks on different tracks (I lift material to higher tracks for a quick sorting method. ie. Track 1 probably not useful, Track 2: potential use, Track 3 Primary Use)
Also the new trim modes (which being a long time premiere editor, I am not that used to yet) appear to have great value.
Positive Point Two: Trimming much improved
So after complaining, I offer a Thank You to Adobe. And of course all the goodness all over the place, both Premiere and other apps make me giddy.
Kevin L

Agreed. I have been using it since CS3, coming from Avid, Velocity & FCP. It simply gets better with each new revision, but CS6 feels like they've really hit it hard. The overall user experience feels faster and more intuitive. For me, it's almost a nebulous thing, but it just feels better, for whatever that's worth.
I've currently been comparing CS6 to Smoke 2013 (doing the same project in parallel) and I keep coming back to CS6. While I would prefer nodal compositing (I come from a Nuke/Fusion bknd), the CS6 suite is much snappier. Disk caching in AE it a huge help, and Dynamic link (while in need of a few tweaks, feature-wise) is still a great feature. Granted, Smoke is in Alpha/Beta, but I'd take the Pepsi Challenge anyday with the CS6 suite over Smoke.
-mike

[JS] [CS3 onwards]

Similar Messages

Maybe you are looking for