I am getting ready to release a new version which will use the new licensing features of Tightener. That way, I can start charging some money for my work, and recuperate something to make up for time and effort.
I envision that the price will be a recurring yearly subscription of US$49/seat for desktop versions, and something like US$949/server for server licenses (InDesign Server)
]]>Thank you for your fast reply. Sounds good. Looking forward to the new release.
]]>I am still working on the licensing functionality in Tightener, which will ultimately be used to convert JSXGetURL into a commercial product. The most probable licensing model will be a yearly recurring per-workstation fee, probably around US$30. Unlimited licenses will probably also be available, based on some yearly fee of a few US$1000. All of this is still very much undecided.
I will probably release another time-bombed version until 31 Dec 2023, to bridge the gap until I am ready to release the licensed version…
]]>I’ve never seen the phenomenon, but that all does not sound surprising!
]]>~/Library/Caches/com.adobe.indesign
~/Library/Preferences/Adobe InDesign
Cheers for the reply.
Yes, it was the latest version. My application is transpiled and copied into the InDesign scripts folder on build and was working before the previous version of your library expired. So I dropped in the new version’s JSXGetURL folder into my application and got “DEMO TIMED OUT” response when I ran it.
Then I copied in sample.jsx manually and received a “getURL.addRequestHeader is not a function” error. Next I removed the offending line, and again got the “DEMO TIMED OUT” response. On a hunch to do with some sort of caching ocurring within InDesign, I moved the script and library to a new folder in the scripts directory, and et voila it works!
So, does this mean that InDesign is caching the old version of the framework? Any ideas would be much appreciated.
PS I use it your package to grab data from an API for my own private use (I dynamically build my CV from a Sheets document. Thanks for your work!
]]>Is this with the latest version? I just tried it out and as far as I can tell, it works fine. Make sure you use the latest:
This will run until the end of June. After that, I hopefully will have a licensing/payment scheme in place, based on Tightener, and for version 0.1.0 onwards, there probably will be some licensing fee for non-demo use…
]]>