[Philip Tulett]

Hi Paul,

I am look to fill in PDF forms using Omnis, and started looking at your sample ldpdftools.

I know you originally wrote the demo for Studio 10.2, but following your instructions, I can get it run fine with Studio 11.0 and Studio 11.1, but I am failing to get it to run with Studio 11.2. I am sure its me missing a step…

Omnis have changed the way Packages are added to the main **jsworker** project (as per the README.md in the jsworker directory.

I have tried ‘npm install -save ldpdftools’ but that reports:-

npm error code E404

npm error 404 Not Found – GET https://registry.npmjs.org/ldpdftools – Not found

npm error 404

npm error 404 ‘ldpdftools@*’ is not in this registry.

npm error 404

npm error 404 Note that you can also install from a

npm error 404 tarball, folder, http url, or git url.

Clearly, its my error, but I can’t find what I am doing wrong.

Kind regards Phil

[Philip Tulett]

Hi Paul,

Actually, I can only get it to work with Studio 11.0 not Studio 11.1 or Studio 11.2.

I think it is the way I am adding the ldpdftools entry to the omnis_modules.mjs file, which is new to the later versions of Omnis.

Kind regards Phil

[Philip Tulett]

Hi Andreas,

Have you tried using the servermgmt.lbr with JS Client Serial Number ?

It does not load/run correctly.

Works fine when using the developer serial numbers.

I have just sent an email to Omnis UK Support on this.

Kind regards

Phil

[Philip Tulett]

Hi there,

In Studio 10.2 I use the following line of code to obtain the port the server is listening on:-

Calculate ip_port as $modes.$dotoolmethod(kEnvToolBrowser,160)

You can also use “$prefs.$serverport” to obtain the static port, but that is not reliable when using Dynamic Port assignment.