Does anyone know how the change to Adobe's creative cloud is going to affect the use of scripts and will their upgrades cause linked scripts to suddenly break their paths with actions?
Every time I do an upgrade I need to re-link the scripts in my scripts folder to the new scripts folder of the newer version. I'm thinking now that the smarter thing to have done is just make a scripts folder in the root of my HD. (Mac) and then no matter what user or version should always be able to trace to path back to it.
Anyway, if the program is going to be cloud based now and accessible from anywhere as long as you have your login where are the scripts being kept? Are they cloud based too?
I haven't gone that rout yet but know to continue getting the best from the programs, change is inevitable.
Limey
Scripting and the Adobe's creative cloud
-
xbytor
Scripting and the Adobe's creative cloud
The installation folder for PS will be "Photoshop CC". I do not know if they will change this in the future. They may not know.
The location of the Scripts folder will not change until they change the installation folder.
I install my scripts under the /Developer/xtools folder on the Mac and under /Program Files/Adobe/xtools on the PC. I rarely install anything under the PS Scripts folder.
The program is "cloud based" in a loose sense. The will automagically do updates and let you do uploads and other things as a part of your workflow but you still have to have a locally installed copy of PS to do any work. This is unrelated to the PS-like image editor they had up on photoshop.com awhile back.
Scripts will not be in the cloud AFAIK. Synching settings may be possible but not scripts, again AFAIK.
The location of the Scripts folder will not change until they change the installation folder.
I install my scripts under the /Developer/xtools folder on the Mac and under /Program Files/Adobe/xtools on the PC. I rarely install anything under the PS Scripts folder.
The program is "cloud based" in a loose sense. The will automagically do updates and let you do uploads and other things as a part of your workflow but you still have to have a locally installed copy of PS to do any work. This is unrelated to the PS-like image editor they had up on photoshop.com awhile back.
Scripts will not be in the cloud AFAIK. Synching settings may be possible but not scripts, again AFAIK.
-
Limey
Scripting and the Adobe's creative cloud
Thanks Xbytor! I need to move all my scripts and re-link. I have CS6 waiting to install but have been putting it off due to the re-linking issue, having the scripts in the CS 5 scripts folder. Live and learn!
-
pedromarques
Scripting and the Adobe's creative cloud
I have solved this problem a avoided to re-link scripts on upgrades like this:
When I link to scripts, they are stored not on the scripts folder of the software but I am using the user account ID Public folder to store an daily updated copy of my central scripts (windows7) - C:\Users\Public\FolderScripts
This gives the chance to install any script as non-administrator user rights, and I have succeed to work around the obligation of installing new scripts as an user administrator.
That also gave me the chance to automatically centralized the update version of a old script, using a central mirror folder with the scripts.
So, every thing is updated and continue working on newer versions (at least the linking from a script to another script or even to a file, image on the network)
When I link to scripts, they are stored not on the scripts folder of the software but I am using the user account ID Public folder to store an daily updated copy of my central scripts (windows7) - C:\Users\Public\FolderScripts
This gives the chance to install any script as non-administrator user rights, and I have succeed to work around the obligation of installing new scripts as an user administrator.
That also gave me the chance to automatically centralized the update version of a old script, using a central mirror folder with the scripts.
So, every thing is updated and continue working on newer versions (at least the linking from a script to another script or even to a file, image on the network)