Posts tagged "extendscript"

Drawing: Assumptions, Mistakes, and Solutions

My most recent blog post on drawing paths in Illustrator, InDesign, and Photoshop (here) was an interesting exercise for me. In the process of writing the drawing routines, I made several mistakes, found that things I assumed to be true were, in fact, false.

I’ve solved the various problems and have created a workaround or two. I thought it might be useful for other CS Extension developers if I documented the problems and solutions. This way, you can learn from my mistakes. I make lots of mistakes, so it would be nice if we could get some use out of them.

In this article, I’ll show solutions for some of the problems I left unresolved in the previous post. For the most part, they weren’t critical to the point of the post, but it’s nice to tie up the loose ends. I’ve posted an updated version of the project here (this contains all of the code changes discussed in this post):

drawing

Update: This project is now available via Import>Adobe Creative Suite Extension Builder>Remote Creative Suite SDK examples.

My Point of View

First, let me admit to a bias: In my opinion, everything an application can do should be scriptable. Everything. I think InDesign has the best scripting support of the three applications, because its coverage is the most complete. This isn’t to say that it’s perfect, just that it’s a lot closer to my ideal. This means that I tend to approach the other applications with an InDesign bias.

Next, I’m coming to CS Extensions from the world of ExtendScript. My instinct is to develop and debug using the ExtendScript Toolkit (ESTK), then port to ActionScript. I think that this approach is probably shared by quite a few CS Extension developers.

Continue reading…