Re: Running IDL .pro script from another app, using the IDL API [message #55915 is a reply to message #55914] |
Thu, 13 September 2007 13:34   |
codepod
Messages: 19 Registered: March 2006
|
Junior Member |
|
|
On Sep 13, 12:56 pm, David Fanning <da...@dfanning.com> wrote:
> Jim Brown writes:
>> Our R&D group uses IDL and has written .pro scripts for use in
>> testing. Our test engineers use a Microsoft Windows desktop app
>> (developed in-house) but have to get out of the app, start IDL, and
>> then run a script. This happens several times during a test. What I'd
>> like to do is to have our testing app call an IDL API and run the
>> script "in the background" while the test engineer did something else.
>> However, I don't know if this can even be done. Most of the
>> documentation that I've been reading addresses calling an external
>> program from within IDL.
>
> There is a reason for this, but it won't do much good
> to go into it. But keep in mind, IDL was never designed
> for this purpose. :-)
>
>> - I want to do the opposite.
>
> You want to know about "Callable IDL". You can read all
> about it in the External Development Guide, found among
> the other Programmer's Guides in your on-line IDL help.
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
What you'll want to use is the IDL Connector objects, which were build
for this exact scenario. They are part of IDL 6.4 (no extra license
required). Built off the IDL Export Bridge technology, these are basic
COM and Java objects that provide simple access to IDL (Execute
String, Set/Get variables). This is much easier that Callable IDL,
which is difficult to use. So if you can access COM or Java from your
application, you could use this technology.
-CP
|
|
|