While version 2.1 of JsxBlind library has just been released, I'd like to focus on a technical issue you may have encountered. If the script to be obfuscated contains eval(…) or app.doScript(…) blocks, there is a good chance that abysmal errors arise. Here is the solution to this enigma…
Tag : JSXBIN
JsxBlind | The Case of “Nested” Variable Names
February 06, 2019 | JsxBlind | en
JsxBlind 2.0 Meets IdExtenso
October 31, 2018 | JsxBlind | en
Faster, cleaner, smarter, JsxBlind 2.001 is out! As a library, it now belongs to IdExtenso's toolbox, which I think is top-notch news for serious ExtendScript developers. Also available here is the “standalone version” (named JsxBlindRun) that should work fine from InDesign CS4-CC or ESTK…
JsxBlind 1.008: Important Bug Fix [OBSOLETE]
April 21, 2018 | JsxBlind | en
JsxBlind v.1.008 is now available and fixes a serious issue you may have encountered using the previous version. Thanks to my colleagues Davide Barranca and Justin Putney it has been found that JsxBlind's output could be corrupted when originating from a process that relies on a persistent engine…
JsxBlind's New Version for ExtendScript Developers [OBSOLETE]
January 22, 2017 | JsxBlind | en
JsxBlind 1.007 is available today—still for free—and now delivered in two formats: a standalone script (JsxBlindRun.jsx) that offers a quick and easy way to scramble a JSXBIN file straight from InDesign (as previously), and a “includable library” (JsxBlindLib.jsxinc) that provides advanced options to developers who need to plug JsxBlind features in an automated workflow (ESTK extension, panel development process, or any custom framework.)
JsxBlind | The First JSXBIN Obfuscator for ExtendScript
December 21, 2015 | JsxBlind | en
As Christmas is approaching I wish to share with the scripting community a very unexpected utility, which for legal reasons I can hardly tell anything detailed! Paradoxically, as you shall see, JsxBlind aims to protect script authors from being despoiled…
YALT 2 | Your Scripting Localization Engine
July 24, 2010 | YALT | en | fr
In August 2009, we introduced YALT —“Yet Another Localization Technique”— as an alternate way to manage multilingual strings and automatic localization in our InDesign scripts. I use it in my everyday projects and I definitely abandoned the native ExtendScript L10N feature, which I believe is too restrictive and not so clever. YALT is a lightweight, quickly includable and easy-to-use tool. Month after month I improved the snippet with the result that it now has nothing to do with the original version! Maybe it's time to share YALT 2.1 with you. . .
Binary JavaScript Embedment (CS4/CS5)
April 13, 2010 | Tips | en
The jsxbin format (“Binary JavaScript”) is a boon for developers because it enables them to distribute a script without exposing its precious code. The ExtendScript ToolKit (ESTK) offers an Export to Binary feature which instantly converts a human-readable js(x) file into jsxbin. InDesign can then interpret this file as if it were a pure JavaScript. The only (boring!) problem is that the encoded script is not allowed to load a persistent session through the #targetengine directive. Here is a secret trick to bypass this limitation with a single encrypted file.
Can InDesign Script Rewrite Itself?
November 06, 2009 | Tips | en | fr
As illustrated by the YALT technique, it's easy —and powerful!— to let a script read its own bytes while it is running. We could even go further and get a script to update itself to achieve some advanced functionalities.