It’s been a long, hard slog! Nearly three years ago, I set out to build a technology stack to address the gaps in Adobe’s automation tooling for the Creative Cloud ecosystem.
It seemed like a crazy endeavor for one person, but persistence (and a lot of blood, sweat, and tears) paid off.
I’ve finally reached the ‘minimum viable product’ stage, where I can use and present some of the tools I’ve been working on. There’s still much more to do, but the first tools are now available for use.
I’ve started converting Rorohiko’s automation tools to this new technology stack (currently TextExporter, JSXGetURL, SmokeWordStacks, SizeLabels)
The project, originally called Tightener, has stabilized over the last 6-8 months, and I’m now focusing on building tools for automating Adobe Creative Cloud apps (InDesign, Illustrator, Photoshop, etc.).
This subset of the project is called Creative Developer Tools, with two main components: CRDT_ES (for ExtendScript/CEP) and CRDT_UXP (for UXPScript/UXP).
Another key component built on top of Tightener and CRDT is PluginInstaller.
PluginInstaller aims to be a unified packager and installer for various types of software, including ExtendScript, CEP panels and soon UXPScript, and UXP panels.
It also uses a central registry to track users, machines, activations, and usage without storing personal data. The registry uses SHA-256 hashes, keeping the actual data secure on users’ computers.
Future features
Stuff I have in mind, which might or might be realized:
- Porting the Rorohiko scripts, extensions and plugins to use PluginInstaller
- PluginInstaller support for C++ plugins and hybrids
- PluginInstaller support for UXPScript
- PluginInstaller support for UXP Plugins
- CRDT module with a look-similar feature for ScriptUI that can be used with both ExtendScript and UXPScript
- CRDT module for user-interface development, to replace CEP and UXP for creating user interfaces
- PluginInstaller search feature in various catalogs/enhancement store
- Jupyter Notebook for ExtendScript
- Python for automating Adobe Creative Cloud
Currently Available
Here’s a look at the currently implemented elements of the technology stack, from outer to inner components.
PluginInstaller
-
Generic Platform: Initially designed for the Adobe ecosystem but adaptable to other environments (e.g. Python ecosystem).
-
Unified Package Format (.tpkg):
- Text-based format with metadata in the first 1KB, ensuring easy identification.
- Capable of packaging and installing ExtendScript and CEP solutions. UXP soon.
-
Comprehensive Tool Replacement:
- JSXBIN and ZXPSignCmd Replacement: Manages self-signed certificate generation and .zxp file creation.
- ExtensionManager Replacement: Installs .tpkg files directly from URLs or after download.
-
Advanced Features:
- Facilitates monetization and purchases, with a proof-of-concept integration with PayPal used in our Rorohiko products.
- Payment processor agnostic. Developers can slot in their own payment processor if desired.
- Handles activations and selective feature enablement for monetization.
- Supports demo/trial versions and tracks anonymized usage data, providing insights into tool installations and usage frequency.
- It’s now easy to experiment with different payment models: donationware, nagware, short subscriptions, long subscriptions…
- Unified install experience for the end-user
- Open for use by other developers
- Pricing is still up in the air, but my intention is to make it totally free for small developers (1- or 2-man bands) with a revenue below a certain level.
Creative Developer Tools
-
CRDT_ES:
- #include-able library for ExtendScript/CEP
- Provides useful functions and acts as a JSXBIN replacement.
- Enables code-signing for ExtendScript.
-
CRDT_UXP:
- require()-able library for UXP/UXPScript
- Offers functions that extend beyond the security sandbox.
- Provides missing features such as environment access, binary file read/write capabilities, and encryption.
-
JSXGetURL:
- Enhances ExtendScript with CURL features, effectively integrating Tightener capabilities.
Tightener Registry-Enabled Version
- Dependencies:
- In addition to Tightener Base also needs OpenSSL, curl, and zlib, to allow communication with the registry.
- Advanced Features:
- Unique Identifiers: Generates unique machine, user, and order GUIDs.
- Central Registry: Uses a registry that stores only hashed data, ensuring no identifiable information or passwords are kept.
- Distributed Data Storage: Relies on remote nodes (i.e. the user’s computer) for data storage needs.
- Capability Tracking: Supports activating and managing floating licenses and activations.
- Persistent Data Handling: Manages persistent local usage data for demo modes, trial versions, etc.
- License Management: Handles floating licenses, allowing large accounts to allocate seats dynamically without requiring PluginInstaller for each end-user.
- Availability:
- Offered in various formats: as a command-line tool, or compiled and statically linked into various apps, as a DLL, or as a plugin for different environments.
Tightener Base Version
- Core Features:
- Pure C++ Code: Built entirely in C++ with no dependencies beyond the C++11 standard library.
- Embedded Glue Language (TQL): Used for bridging; can also provide a scripting DOM into applications, akin to ExtendScript.
- Messaging Protocol: Facilitates inter-app communication using a star topology, similar to Adobe Bridge’s protocol.
- Optional Networking: Through gateway apps, multiple computers can be connected into a mesh of stars, enabling cross-network messaging.
- Availability:
- Offered in various formats: as a command-line tool, or compiled and statically linked into various apps, as a DLL, or as a plugin for different environments.