Way to call built-in Tcl interp, but not from a "tool"?

Question

question

BillS asked Mar 25, '10 BillS posted Mar 25, '10

Way to call built-in Tcl interp, but not from a "tool"?

We have a scenario where a menu contribution we're making to iTest may receive some Tcl data (specifically Tcl commands loaded from a text file). We'd like to be able to process that by calling directly to the iTest built-in Tcl interpreter.

If it were a tool plugin, or an execution monitor, or any of those kind of plugin additions it'd be straight-forward, but this is from a plugin that's simply a menu contribution and separate code.

Any thoughts on whether this is achievable? We have other options, this just struck me as one of the nicer potential choices... so before I spend any time digging further I figured I'd check at a high level if it was feasible.

Thanks,

-Bill

iTest sdk

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2010-03-26T05:44:47Z

KumarS answered Mar 26, '10 KumarS posted Mar 26, '10

It should be. TclInterpreter service should be accessible through some open platform apis. Let me dig through and find out.

3

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KumarS commented · Mar 26, 2010 at 06:01 AM

This is not part of SDK - but you can do following:

if you add a dependency to this plugin:

com.fnfr.svt.fftcl

You can call:

public ITestTclInterpreter createInterpHandle() throws InterpCreationException;

ITestTclInterpreter will allow you to evaluate tcl statements. It will the tcl shell which is set in iTest preferences.

Note that this is an internal API and will not work in next release of iTest. It will only work in 3.4. Not only that, it may stop working in a new service pack of 3.4 - but probability of that is really low. We will take a look if we can make ITclInterpreter from the SDK available for purposes other than tools.

0 ·

PaulD KumarS commented · Mar 26, 2010 at 03:28 PM

I think you might have this wrong, Kumar.

I believe you need the com.fnfr.svt.adapter.tcl plugin and then:

ITestTclInterpreter interp = InterpHandler.createInstance().createInterpHandle();

Right?

0 ·

AdamB PaulD commented · Mar 26, 2010 at 04:44 PM

Hi Bill,

There is a better way to get a tcl interpreter. If you include the package:

com.fnfr.itest.platform.tcl

You will then have access to its activator:

ActivatorTclService

If you call:

ActivatorTclService().getDefault().getTclServiceManager()

You will get an ITclServiceManager. It has methods that let you create a tcl interpreter.

Wei will be able to answer further questions about this.

One caveat, this is not in the officially supported SDK, so it may change from release to release (But given it is in the platform, it is less likely to change than the options above.) We will look to add a supported API for services like this.

-a

0 ·

question