chradja
-
Posts
7 -
Joined
-
Last visited
Everything posted by chradja
-
I'm currently do a lot professional scripting with Adobe IndDesign and I think you covered here most of the needs. Of course access to a stable kind of ID (or name) of the different block is essential. But pretty much part of the scripting (on my side) is not only generate full pages, but also piece of them. Very important also is the ability of the scripting interface to manage or guess all possibles overflows...
- 655 replies
-
- 1
-
-
- automation
- scripting
- (and 3 more)
-
WASM is a completly different engine than javascript. Although it is capable of executing javascript code in a sandbox.
-
..
-
Nice to have this confirm ! And looking forward to welcome you in the world of industrial publishing ! I'm so happy to have (soon I hope) an alternative to Indesign Server ...
-
Python is fine but JavaScript better as part of the API could be integrated in a browser, and why not as they start from scratch having in that browser visualisation and basic graphic tools available as well
-
Regarding the scripting language, Javascript sounds to me the more modern approach: Take a look here on how to embed a very performant engine (the one used by Nodejs) : https://v8.dev
- 655 replies
-
- 1
-
-
- automation
- scripting
- (and 3 more)
-
Definitively, I would consider the publisher application for enterprise deployments as soon as it as a strong API (allowing developments not only of scripting, but also of plugins), and a server version then. InDesign has won the war against Xpress because of that (One strong API for plugins, one strong API for scripting and a server version). Because nowadays a lot of solution provides semiautomatic publishing which generates pages (often catalogs) that are then finished and polished by creatives without worrying about correct content and focusing only on the look.