3 ms·

As a developer, I've often felt that if I can't script something, embed it into my own software or service, or even redistribute it, then I haven't really done

by th0ma5 13y ago

As a developer, I've often felt that if I can't script something, embed it into my own software or service, or even redistribute it, then I haven't really done it with software. This is an unrealistic goal if I was in DTP work still, but by setting this bar, I've been amazed about how my understanding of the context of a problem has broadened my horizons. For instance I feel I now have a great grasp on Nurbs, Voxels, and 3d meshes in general from having done it all with Clojure instead of Blender. Batch processing with Imagemagick is now so second nature to me I can't stomach the idea of having to load up PS or even Gimp. I think when the process involves subtle interactive hand touches and nuances, then an interactive editor will always win out. However rudimentary, discrete "operations" are things computers should do well, and PS and Gimp fall short in my opinion. Gimp being slightly better sort of with its open scripting.

evan_ 13y ago
Photoshop got full scripting support in 2003 with Photoshop CS. Before that you had to install a free plugin and it didn't support everything but it was still pretty powerful, I don't remember exactly when that came out but I think it was first for version 6 in 2000. Photoshop has also had full recordable macro support ("Actions") since 1996. Many photographers I've worked with have developed huge suites of actions they've created that enable them to automate much of their workflow despite having no coding ability whatsoever. http://www.adobe.com/devnet/photoshop/scripting.html http://www.adobe.com/devnet/photoshop/scripting.html
- th0ma5 13y ago
  Yeah I guess I was thinking about that when I wrote this, but for instance with Python I can instantiate a batch of transformations, and integrate other libraries, other programs, and share inputs and outputs among all of them. I'd be excited if there was a CS scripting whereby I could take an AI file, apply layer effects, and then position that in a 3D transform in AE, and render an MP4 all in one script. I can do that with Linux and open source utilities, but I can't with CS. Also AI is horribly leaky in memory when dealing with advanced computational design where you have billions of points, whereas open source SVG renders take such a thing in stride.

by th0ma5 13y ago

evan_ 13y ago

Photoshop got full scripting support in 2003 with Photoshop CS. Before that you had to install a free plugin and it didn't support everything but it was still pretty powerful, I don't remember exactly when that came out but I think it was first for version 6 in 2000. Photoshop has also had full recordable macro support ("Actions") since 1996. Many photographers I've worked with have developed huge suites of actions they've created that enable them to automate much of their workflow despite having no coding ability whatsoever. http://www.adobe.com/devnet/photoshop/scripting.html http://www.adobe.com/devnet/photoshop/scripting.html

th0ma5 13y ago
Yeah I guess I was thinking about that when I wrote this, but for instance with Python I can instantiate a batch of transformations, and integrate other libraries, other programs, and share inputs and outputs among all of them. I'd be excited if there was a CS scripting whereby I could take an AI file, apply layer effects, and then position that in a 3D transform in AE, and render an MP4 all in one script. I can do that with Linux and open source utilities, but I can't with CS. Also AI is horribly leaky in memory when dealing with advanced computational design where you have billions of points, whereas open source SVG renders take such a thing in stride.