I was just about to ask the same question. I hope it's supported soon. Scriptographer is great.

Yes, please... Scriptographer is a force for good, it would be great to have it continue onto CS6.

it would be great to have scriptographer on cs6 , now that it's native 64 bit it will be superb.

btw , amazing job .

Ty in advance

Oh, that would be fantastic.
Hoping for the best.

I agree—it would be amazing to be able to use an updated (64-bit) version of Scriptographer in Illustrator CS6. It's a remarkable tool as-is… I can only imagine how powerful it would be with 16-20 extra GB of RAM behind it. :-)

Unfortunately, porting Scriptographer to CS6 is far from trivial.

In the process of converting Illustrator to 64bit, Adobe had to abandon Carbon in favor of Cocoa. And as part of that transition, they decided to deprecate ADM (Adobe Dialog Manager), the SDK that all Illustrator UI was previously written in, and which was exposed to plugins in the past. ADM is based on Carbon, so converting the aging SDK to Cocoa would have been a lot of work, and probably wouldn't have much sense to them.

Unfortunately, Scriptographer's own UI classes are all based on ADM, and its own UI is built using these. So to port Scriptographer to CS6 means to invest a substantial amount of time in replacing all of this functionality with something new.

To make matters more complicated, Adobe has decided to not expose a new UI framework and instead give the plugin developers the freedom to choose their own framework (which will never look the way Illustrator CS6 does, or CS7,8,9 will). The only officially supported option is to write all UI in SWF and map it to plugins. This is not a viable option for Scriptographer.

I have looked into other ways of porting the UI to a new framework that then could be ported back to older versions, and with Scriptographer internally based on Java, I found a good candidate in SWT. It exists on Windows and Mac, and comes in flavors of both Cocoa and Carbon. I even started investigating how to embed it on older versions, and found some viable options.

BUT:

All this is huge amount of work, requiring a huge amount of time (I think about two months of full time work), time that I do not currently have. And since it would be unpaid work, I am also not in the financial situation to devote a lot of my time to this task.

So sadly, for now I cannot specify any date for this new version to become a reality.

But perhaps there are people willing to help out with the required work? You would have to be familiar with JavaScript and SWT, or willing to learn and experiment. If interested, please get in touch: sg (a) scriptographer.org.

I am sure that Inkscape community will be happy to work with you.
I don't really understand why a cool idea such Scriptographer was developped for a proprietary Adobe software. What happened shows exactly why designers need open source software to make they own tools and to keep on experimenting.
I can imagine that a fork of Scriptographer for Inkscape means a lot of work, but all this energy will allow to be independant. This way, you will save the work necessary each time Adobe chose to change its API.
Actually I am sure that you already know that. I am sad for Scriptographer, but I stay confident: Scriptographer will have a huge influence for the next generation of (open source) tools for graphic designers.

Advice:
Since this is an plug that alot of people love and uses, why not try it on kickstarter? This way we(the users) gets the needed plugin and you(the developer) gets paid. Just a thought.

It's a good idea, but it won't solve the issues of time. What I need as badly perhaps is people who could take on a part of the workload.

Like Raphael said, why don't you ask the Inkscape community to help you ?
Tell me if I'm wrong, but i've always seen Scriptographer as an open source minded project. So why don't you leave the business mercenary Adobe products who apparently don't mind if you're dying or not despite all the licences you help them to sell by increasing their cool attitude.
Since a long time I don't understand why you're so Adobe addict and don't move to open source tools, seems so logical.
Now it's high time i think.