Unleashing Creativity with Custom Adobe Illustrator Plugins: A Developer's Journey
For decades, Mapsoft has worked with Adobe Illustrator. In this discussion, we outline the technologies we use and explain how we decide on the technologies to employ in our Illustrator plugin development projects.
Choices of Technologies for Adobe Illustrator plugin development
When developing plugins or scripts for Adobe Illustrator, the choice between C++ and ExtendScript depends on various factors such as the complexity of the task, performance requirements, and integration level with Illustrator. Here’s a table outlining key differences and considerations:
| Aspect | C++ | ExtendScript |
|---|---|---|
| Complexity | Suitable for complex, high-performance tasks. Involves in-depth knowledge of C++ and the Illustrator SDK. | Best for simpler tasks and automations. Easier to learn and use, especially for those familiar with JavaScript. |
| Performance | Higher performance, especially for intensive tasks like rendering or processing large files. | Adequate for less demanding tasks. Slower in execution compared to C++. |
| Integration Level | Deep integration with Illustrator, access to lower-level APIs. Can create custom UI elements and tools. | Limited to the capabilities of the scripting interface. Cannot create custom UI elements. |
| Development Environment | Requires a setup with an IDE like Visual Studio or Xcode, and the Illustrator SDK. | ExtendScript Toolkit or similar text editors are sufficient. No complex setup required. |
| Cross-Platform | Requires handling platform-specific code for Windows and macOS. | Scripts are generally cross-platform with no extra effort. |
| Distribution | Compiled plugins need to be distributed and installed. May require managing different versions for compatibility. | Scripts can be easily distributed and run by users without installation. |
| Update Compatibility | Sensitive to Illustrator updates. Plugins may need updates to remain compatible. | Generally more resilient to Illustrator updates. |
| UI Capabilities | Can create complex, custom UI elements. | Limited to basic dialog boxes and predefined UI elements. |
| Access to Illustrator Features | Full access to Illustrator’s features and capabilities through the SDK. | Access is limited to what is exposed through the scripting interface. |
| Learning Curve | Steeper learning curve, especially for developers not familiar with C++. | Easier for those familiar with JavaScript or similar languages. |
| Development Time | Longer development time due to complexity and compilation. | Quicker to develop and test scripts. |
| Community and Support | Smaller community, more complex issues may arise requiring in-depth knowledge. | Larger community, easier to find solutions and examples online. |
Table Summary
In summary, choose C++ for complex, performance-critical plugins that deeply integrate with Illustrator, requiring a comprehensive understanding of Illustrator’s SDK and C++. ExtendScript is better suited for simpler tasks, automation, and when ease of development and distribution are priorities. The choice ultimately depends on the specific requirements and constraints of the project you are undertaking.
User Interface Considerations
Comparing user interface elements, particularly when considering CEP (Common Extensibility Platform) used in both ExtendScript and C++ environments against wxWidgets, which is specific to C++, provides insight into the flexibility and suitability of these tools for different UI needs in Adobe Illustrator. Here’s a comparative table:
| UI ASPECT | CEP (COMMON EXTENSIBILITY PLATFORM) | WXWIDGETS (C++) |
|---|---|---|
| Environment Compatibility | Compatible with both ExtendScript and C++ environments. Offers a versatile approach for UI development across different languages. | Limited to C++ environment only. Suitable for developers specifically working within C++ framework. |
| UI Design Flexibility | High flexibility. Supports HTML5, CSS, and JavaScript for UI, enabling modern and dynamic interfaces. | Traditional UI elements with a native look and feel. More suited to conventional desktop applications. |
| Complexity of UI | Can create sophisticated and interactive UIs, leveraging web technologies. Ideal for complex, feature-rich plugins. | Well-suited for standard UI components but may be limited in creating highly interactive or custom UIs. |
| Cross-Platform Consistency | UIs are generally consistent across platforms due to the web-based nature of CEP. | Requires careful design to ensure cross-platform consistency due to differences in native widgets. |
| Ease of Use | Relatively easy to use for developers familiar with web technologies. | Familiar to C++ developers, but requires understanding of native UI development concepts. |
| Performance | Good for UI but can be less performant for complex computations compared to native C++ UIs. | Generally offers better performance for UI rendering and responsiveness in a native environment. |
| Integration with Illustrator | Seamless integration with Illustrator, especially for extensions using ExtendScript. | Direct integration with Illustrator’s functionalities, offering deeper control within a C++ plugin. |
| Learning Curve | Easier for developers with web development background. More intuitive for designing modern UIs. | Steeper for those without C++ or native UI development experience. |
| Customizability | High degree of customizability due to the use of HTML/CSS. | Customizable within the constraints of native widgets and the C++ language. |
| Distribution and Updating | Web-based UI elements can be updated without changing the core plugin, offering easier maintenance. | UI updates require recompiling and redistributing the plugin. |
| Accessibility | Web technologies offer tools and standards for accessibility, but implementation requires attention. | Accessibility features depend on the native platform standards and wxWidgets’ support. |
In Conclusion
CEP offers a more flexible and modern approach to UI development in Adobe Illustrator plugins, especially beneficial for developers comfortable with web technologies. It works across both ExtendScript and C++ environments, providing versatility. In contrast, wxWidgets caters specifically to C++ developers, offering a more traditional, native UI approach that may be more performant but less flexible in terms of design and cross-platform consistency.
In the future we expect that Adobe will introduce UXP to Illustrator developers as has already happened with InDesign and Photoshop and will soon be a consideration for Illustrator plugin development. To what level UXP will be able to provide the same level of speed and flexibility as has existed in the C++ plug-in interface is debatable.
Case Study
See this Case Study of integration of SMART whiteboards and Adobe Illustrator on a previous development integrating Adobe Illustrator and SMART whiteboards. This was developed primarily using the C++ interface for Adobe Illustrator Plugin Development which was essential for the required speed and interoperability of the SMART developer tools.
See our Illustrator software development link on the main website.
Author: Michael Peters
