The InDesign CC 2014 SDK will be available on the InDesign Family SDK Access Program from June 20.
If you are new to InDesign development, the best place to get started is ‘Getting Started with InDesign Development’, which is a guide included in the SDK.
As for this latest release, the following are the most significant changes in the SDK.
The InDesign update you received in August 2013 (InDesign 9.1) included the enabling of HTML5 extensions.
As you may already know, starting in the middle of 2014 Adobe will begin removing Flash-based extension support in Creative Cloud products, starting with Photoshop CC.
If you have any hybrid or regular Flash extensions for InDesign you need to begin migrating them to HTML5 as soon as possible.
As you may have noticed, the InDesign CC SDK is available by request from http://www.adobe.com/devnet/indesign.html.
In this latest release we’ve added new samples to the SDK whilst some more basic features of plug-in development have also changed. We’ll talk about the new samples in future blog posts, but find below the more fundamental changes you need to know about if you are creating plug-ins for InDesign CC.
The Adobe Express View Engine (EVE) is the recommended method of laying out UI widgets in InDesign dialogs. The main benefit of using EVE is that widget geometry is calculated for you, so that when you add or remove widgets to a dialog all of the other widgets are shifted automatically without you having to recalculate sizes etc.
Perhaps you’ve come to native plug-in development from a more script-based background, or perhaps you have some existing script code you want to reuse in a new plug-in project. Whatever your background, it’s really handy to be able to run a script from a native plug-in, and it’s also surprisingly easy.
The code below works out of the box so you can copy and paste as much as you please.
InterfacePtr<IScriptRunner> scriptRunner(scriptEngine, UseDefaultIID());
scriptRunner->RunScript("alert('hello, world!');", params);