Archive for May, 2012

The new Adobe Exchange

Dear Valued Adobe Developer,

I wanted to make you aware of an exciting new program which Adobe will be releasing this Summer. Adobe is creating a brand new Adobe Exchange, which will enable developers, trainers, and community experts to promote, distribute, monetize and track their CS6 solutions. These products will be made visible to potential CS6 customers within the ‘Adobe Exchange’ panel in most CS6 applications. The initial CS6 products which will support the Exchange panel are:

  • Dreamweaver
  • Fireworks
  • Flash Professional
  • Illustrator
  • InCopy
  • InDesign
  • Photoshop
  • Premiere
  • Prelude

This program is appropriate for developers who are seeking effective and efficient ways to market and distribute free, paid, and trial items as well as deliver updates of those items to Creative Suite users. We are actively seeking launch partners for this program and are taking applications now for partners who would like to be added into our beta program.  Launch partners that commit to providing distributable CS6 content in the next 8 to 10 weeks will receive valuable benefits as charter members of the new Adobe Exchange.  If you are interested in becoming a launch partner and getting in on this exciting opportunity early or hearing more about the program here’s how to get started:

Complete the brief Adobe Exchange (codename: Agora) Prerelease Program sign up form:

tinyurl.com/exchangeprerelease

We plan to hold a Connect session to give you more information on Adobe Exchange. If you are interested in joining a Connect session to learn more about the program, please ensure you have signed up for the prerelease, (join here) to receive an invitation.

Ken Toole | Director, Partner and Enterprise Solutions

Adobe Drive 4 Now Available – Provides Digital Asset Management integration with CS6

It’s been a busy month for Adobe’s Solutions Enablement Team, (also known as SET). In addition to releasing Extension Manager CS6 and an update, Configurator 3, CS Extension Builder 2, various components for the Creative Cloud and much more besides, there is another great product a lot of people are unaware of; Adobe Drive.

Now at version 4, it enables the seamless integration of a digital asset management (DAM) system with Adobe Creative Suite® 6 applications. Once connected to a DAM server, you can access remote assets through your operating system file browser, through Adobe Bridge, or from the menus of CS products that integrate with Drive: Adobe Photoshop®, Illustrator®, InDesign®, and InCopy®. A lot of users and developers I talk to are not aware Adobe even has this, so I wanted to share. This is a really great release of Drive.

Check it out and download it here:

http://www.adobe.com/products/adobedrive.html

CS Extension Builder 2 GM – now available via TPP and AEDP, Adobe Store and Trial Mid June

I wanted to let you that the CS Extension Builder 2 final GM release is now available to download from the Technology Partner Program (TPP) and Adobe Enterprise Developer Program (AEDP). If you are not a member of either of these developer programs you will also be able to try/buy CS Extension Builder 2 from the Adobe Store in mid June.

I would also like to take this opportunity to thank all of the CS Extension Builder 2 Prerelease Program users. Their input created several new features and a higher quality release. We hope you enjoy it!

Learn more here:
http://www.adobe.com/products/cs-extension-builder/features.html

Jonathan Ferman | Product Manager

About the CSXS Infrastructure 3.0.1 Updates

Recently we posted updates for various CS6 applications called CSXS Infrastructure updates via the Adobe Application Manager. Unfortunately, there was no text describing what the update was for or indeed what CSXS was. Whilst we work to add in the descriptive text to the update, I wanted to provide some brief information for those that were curious as to what the update was about.

CSXS is the platform that delivers extensibility within Creative Suite products. This update to the CSXS Infrastructure, resolves an issue where certain characters contained in a users Adobe ID caused a login failure.

It’s only a very small update but an important one, so please apply the update if you are a CS6 user, now that you know what it’s for.

Jonathan Ferman | Product Manager

Configurator 3 is live on labs.adobe.com

Configurator 3 is now live on Adobe Labs. Configurator lets you create custom panels for Photoshop and InDesign and now supports CS6 amongst many other new features. I can think of two key uses for Configurator, the first is for custom panels with just what you want to have at your fingertips, the second and ideal for developers is creating tutorials for Photoshop and InDesign. As Configurator supports video and Web content it’s an ideal way to teach users about your Photoshop or InDesign solutions, leveraging existing content. The user gets to learn right within the product and you can build these panels in minutes.

Configurator 3 Highlights

Configurator 3 provides lots of new features and a number of improvements that focus on distribution, product compatibility, panel customization, and usability. Key features include:

  • Compatible with Photoshop CS5/5.1 and CS6, and InDesign CS5/CS5.5 and CS6; supports new features and automatic conversion of existing panels.
  • Distribute and share panels with other Creative Suite 6 users via the Adobe Exchange. Look for more information and a new Exchange panel to be available on Adobe Labs in the coming weeks.

You can find out about all the new features and download the software on Adobe Labs. Adobe Exchange is going to provide a tremendous opportunity for users and developers alike and we will be providing more information about it soon.

Please spread the word about the Configurator 3 release with other users and try it out at: http://labs.adobe.com/technologies/configurator/

Jonathan Ferman | Product Manager

Potential Impact of Mountain Lion’s Gatekeeper on Adobe’s Third Party Developers

 

In Mountain Lion (Mac OS 10.8), Apple are introducing Gatekeeper, a mechanism by which they can provide a degree of protection to users against running potentially harmful code.

I’d like to give some thoughts on how this might impact third party developers delivering extensions and/or native plug-ins into Adobe Creative Suite product installations.

First a brief introduction to Gatekeeper (a better introduction can be found on the Apple site)…

Gatekeeper provides three potential levels of protection:

  1. Applications can be installed with total freedom.
  2. Applications can only be installed if they are signed with an Apple Developer ID or if they come from the Apple MacOS App Store. This is the default option.
  3. Applications can only be installed if they come from the Apple MacOS App Store.

How, as a third party developer, can you ensure your plug-in installation is not limited by Gatekeeper? The safest answer at this point is to adopt Apple’s best practices, yes, that means getting an Apple Developer ID and signing your plug-in. This way, you run less risk that your users will no longer be able to use your product (and users can guarantee this bundle of joy really did come from you – this is a good thing).

If for some reason you prefer not to take this route and you want to continue to deliver your plug-ins unsigned the alternative answer really depends on how you deploy your extension. I’ll consider adding the plug-in manually, adding it through an installer, and adding it through a utility application (such as Adobe Extension Manager).

If the plug-in is  manually added to the appropriate folder on disk, Gatekeeper should not get involved (this stands to reason, in essence if it was a malicious operation, your disk is compromised anyway).

If you depend on an installer, this installer will need to conform to the Gatekeeper security model. This means you need to either:

  • Sign your installer with an Apple Developer ID certificate (though you will need to educate the user if they have the strictest setting enabled).
  • Educate your users on how to reduce the restrictions introduced by Gatekeeper (temporarily, of course).
  • Arrange to have your installer distributed through the Apple App Store (at some point in the future if this scenario is supported by Apple).

If you depend on a utility application (such as Adobe Extension Manager) to handle the installation, you should not be affected; our experience is Gatekeeper does not intercept this condition.

Once installed, we have not experienced any restrictions on the execution of applications with third party plug-ins. That does not mean that Apple will not add them at some future point.

Clearly, this is based on some quick tests we’ve run. We would be very keen to hear if your experience/understanding differs.

Finally, we are expecting further changes in this area, especially as the OS vendors continue to move towards “sand-boxed” application contexts.

These are our rough first thoughts in an area that will likely continue to evolve (as the OS vendors continue their march towards sand-boxed applications), feedback welcome.