Quantcast
Channel: Adobe Community : Popular Discussions - InDesign Server Developers
Viewing all articles
Browse latest Browse all 20709

Basic question

$
0
0
Hi all,

I'm new to this and would appreciate some input from you guys.

I'd be very interested in your opinion on (broadly speaking) the most basic way for an application to interact with (UI free) plug-in code. According to the SDK documentation, the way to go about it seems to be:

http://img104.imagevenue.com/img.php?image=74804_Slide4_122_492lo.jpg

...where "Script manager" is a plug-in with a SOAP interface (named RunScript) dependent on the syntax defined in the WSDL file that comes with the SDK. "SOAP client" corresponds to the "Test client" command line application also supplied with the SDK. Necessary tasks would include:

1) exposing the "WT" plug-in functionality to the Scripting DOM,
2) reworking the "Test client" to fit the application,
3) writing the script(s), and
4) figuring out how to make them return a meaningful response to the application. The SOAP syntax includes a response field, but the scripts don't know that.

A simpler (undocumented?) approach would seem to be:

http://img164.imagevenue.com/img.php?image=74808_Slide5_122_567lo.jpg

...where "WT manager" is a modified "Script manager" (without the scripting support) using a customized SOAP syntax. It would be extremely convenient to be able to access "WT" classes directly. Unfortunately, I haven't been able to find appropriate sample code and/or documentation.

Any thoughts? Can scripting be avoided, or are my concerns (re: response mechanism) groundless?

Many thanks in advance!

-Mark

Viewing all articles
Browse latest Browse all 20709

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>