Copy link to clipboard
Copied
Vulcan.js is a file always included in documentation for CEP panels.
In simple terms, what is Vulcan.js for and what do people usually do with it?
I know a standard answer is, it helps talk to CC apps, and by the looks of the test panel CEP extension, it helps your extension talk to Creative Cloud.app, something called "CCXProcess.app" and Core Sync.app and finally CCLibrary.app.
Okay, so .. what can one do with these things using Vulcan, and what are they useful for?
Carlos' metaphor is pretty accurate. In general Vulcan allows you to do things like:
Copy link to clipboard
Copied
don't quote me, if I remember correctly
Vulcan is to CEP as BridgeTalk is to JSX
to send messages between extensions? apps?
Copy link to clipboard
Copied
Carlos' metaphor is pretty accurate. In general Vulcan allows you to do things like:
I've personally not seen anything from Vulcan about CCXProcess but I'd be curious to see how it could interact with Core Sync or the CCLibrary.
Copy link to clipboard
Copied
Hi, @Inventsable I remember that you pointed out that there is no equivalent in the UXP world, which would make interoperability difficult or impossible. Pinging @kerrishotts is there an ETA for a similar Technology/Tool?
Copy link to clipboard
Copied
Late reply but there are a variety of ways for interoperability in modern dev, including WebSockets which are supported in UXP. Vulcan wouldn't be needed to communicate between apps each containing a UXP plugin which communicate via some given port over a socket, though doing things like programmatically launching a given app (say you want a plugin in Illustrator to trigger After Effects or Photoshop to launch if not already open) might not be possible unless you can run shell or terminal commands.