Adobe Illustrator CS6 has been available since late April 2012, so more and more users were starting to wonder when Scriptographer for CS6 will finally be released.

Aware that it is time for an official answer, I am finally taking time to formulate one. It was far from easy, but a decision has been made: I am not able to spend more time on making CS6 a reality, and instead will focus my time on creating a very decent alternative and escape route with Paper.js, a JavaScript library for the open web and the HTML5 canvas element that Jonathan Puckey and I have launched in 2011 and are very actively developing since.

The idea for Paper.js grew out of a research and teaching project at ECAL that we have been conducting during 2008 - 2011, in which we used Scriptographer to teach programming to visually thinking students in blocks of one-week workshops. In parallel to these workshops, as part of the research project we continuously improved, streamlined and simplified Scriptographer's API, added new functionality based on observations from the classes and wrote many tutorials and materials to facilitate the teaching. All this material has partly lead to Paper.js' success, since it allowed us to provide great documentation from day one.

Based on these experiences, we are now in the process of planning an online coding environment using Paper.js that sports a subset of the features that the Illustrator interface is offering, which was so beneficial when teaching programming since it allowed the inspection of the visual elements that the code produces.

I am currently using an early version of this environment for teaching at UCLA in Los Angeles, and results are so encouraging that we believe in a couple of months we will not be looking back anymore, and will be able to offer a decent replacement to the environment you came to love working with, with plenty of options to import and export graphics.

Since CS3, I have been regularly reaching out to Adobe, proposing to join forces in some way, as I thought they should be interested in our efforts. Unfortunately, they did not seem to be, or did not have the resources to spare. And with their own scripting environments based on automatic wrapping of native API still not receiving the love and attention to detail it deserves (their API is unstructured and hard to use), I just don't think that Adobe sees the necessity to invest energy there at this time. Personally I believe that is a mistake, and I have been trying to tell them so on multiple occasions. But given the quite fundamental changes that many of their applications have been undergoing in the past revisions, it is understandable that there were many more pressing issues.

For example, during the last decade, Illustrator for Mac went from OS 9 to OS X Carbon (yes, early versions of Scriptographer still run on Classic Mac OS!), from CodeWarrior to XCode, and now finally from 32 bit Carbon to 64 bit Cocoa. In CS5, the coordinate system was vertically flipped.

All these changes meant that with each new version, there was an increasing amount of time and effort to be spent to get Scriptographer functioning again. And unfortunately, the changes required to make Illustrator CS6 work on 64 bit Cocoa lead to the complete removal of ADM (Adobe Dialog Manager), the API that Scriptographer's whole user interface is built with. Even worse, there is no new API to replace it, developers are encouraged to either build UI in Flash, or use another cross-platform framework of their choice, and figure out how to integrate it in Illustrator, which is far from trivial.

So a large amount of time would have to be spent to port Scriptographer to CS6, work that will neither be pretty nor fun. Many people have suggested launching a Kickstarter campaign to raise the funds to facilitate such a transition. I considered doing so for a while, but then realised that with all other projects and commitments, I simply do not have the time to spare to do so, even with sufficient funds, as employing a programmer and coordinating it all would still be a huge effort.

But with all the source code open-sourced and available over at GitHub, anyone with the energy and time at hands to do so should feel free to take on the project and make it live on. I would be more than happy and willing to outline the changes required for CS6 which I have pretty much mapped out in my head already, and assist the process.

Developing Scriptographer has often been painful and more hard labor than anticipated, due to its ever changing host. While working on Paper.js with Jonathan, I came to realise again how much fun programming can and should be.

While it is hard to abandon one of my darlings, the benefits from doing so simply overweight the downsides, and it is with an unburdened heart that I look forward to the new endeavours.

Many thanks to all of you who supported this platform over the years! We hope we are not losing you as users. Why don't you move along with us to the new platform that is shaping with Paper.js!

To those who now feel betrayed or see the base for their work in danger: There is nothing wrong with using CS5 for the time being, which is what we will have to do as well, since many of our own works depend on it to function.

I apologize for the bad news, and hope you can all appreciate this decision.

PS: I have removed the donation button from this website now. If anybody has recently donated money in the hope of fueling the transition to CS6, please get in touch and I will send you a refund.

You don't have to apologize, it is I think a good thing to turn the page. I am personally very grateful for what you guys have done for the graphic design community and I can't wait to see what's next for Paper.js! That remains too bad for Adobe but I am not surprised. Maybe the future of tools is open source and independant (actually I am convinced of it)

This looks very exciting.
Given the name of Paper.js, it seems ironic that it is all web based :-)
Is there any chance of actually getting the outut to paper.
My use of Sg has been to work in Illustrator of course, with print output.
Any way that eps/pdf such could be created for import?
Yes I will be staying with CS5 for as long as possible to keep Sg alive but another route would be welcome!

Hi Gareth, yes the irony of the name is intentional. It's there to remind us where it comes from: print :)

SVG export is in the making and works pretty well already in recent nightly builds of paper.js. The new environment will offer simple ways to import and export graphics using that.

It is sad to hear that Scriptographer will officially be discontinued but all in all not surprising. When I was working in SF the product owners of Illustrator CS3 were meeting with agencies to see designers work flows. After sharing some of the work I was doing in Processing, NodeBox, and Scriptographer I suggested something simple like Apple's Automator built into the environment. All of this fell on deaf ears, instead they were much more excited to talk about Kuler.

PaperJS is nice and after spending some with it i've created a library, it's in the early stages but with it you can do some rudimentary 3D, pseudo-keyframed animations, additional color support, and more. Also, I've created a framework/template which structures paperJS scripts similar to processing, openframeworks, et. al.

for anyone whose interested you can read more on my blog http://goo.gl/IEOkL

Ken

I'm very sorry ... but thanks very much for the great job done and offer for free!!!
Max

:-(

Paper.js looks very promising, and I hope to be able to incorporate it in future designs I create in illustrator and after effects (I combine the two alot for work). The svg and pdf export feature will be key for me.

I have just discovered these great scripts for the first time today, and I was wondering if it is possible to use the scripts individually within Illustrator CS6? I am not really aware of the scripting side of things for adobe products, and I can understand if all the scriptographer scripts are tied to the plugin and won't work when loaded through file>scripts. I am just looking for any way I can utilize them in my vector work. Thanks!

--> Actually just tried to load individual scripts and it looks like it will not work without the scriptographer plugin. It was worth a shot.

Thanks for everything!

I look forward to figuring out how the heck I'm going to incorporate Paper.js. You should charge a fee to join the support group.

What a shame that there won't be a CS6 version but I totally understand your reasons. Thanks for all the work you put into this project in the past!!

Very sad news. I've enjoyed watching it grow over the years and have spent many creative hours using it. Good luck with Paper.js