How to use Studio APIs from good old JScript / VBScript / etc.?

Hi,

sorry if this is a weird question, but I'm NOT a developer, I'm a batch scripting guy...

The old Trados 2007 SDK documentation was perfectly comprehensive and I used it for creating some nice automation scripts, e.g. in JScript

var wb = new ActiveXObject("TW4Win.Application");
wb.TranslationMemory.Open (tm, tmuserid);
wb.TranslationMemory.AnalyseFiles (jobfile);
wb.TranslationMemory.Close();
wb.Quit();

Now, how do I do such trivial thing with Studio 2014 API?

(yes, I know that jobfiles are not supported, that's not what I'm talking about... I'm talking about knowing clearly from the SDK documentation the name of the object to create, the methods and their parameters to use...)

All this Visual Studio stuff looks totally Chinese to me... classes, namespaces... OMG, where is the KISS principle gone? Or am I missing something?

I do NOT want to create EXEs... I NEED to create "open source" scripts, which any localization engineer in the company can simply modify according their needs and run immediately, without compiling anything and similar stuff...

Oh, and no PowerShell either...

  • Hi Evzen,

    What you are asking for is not available.

    Your example is using COM underneath and Trados does not have a COM interface. (although it has been requested before to SDL)

    You could check out the powershell toolkit if you have a professional license, but you already stated "and no Powershell" (which I don't understand)

    https://github.com/sdl/Sdl-studio-powershell-toolkit

    Powershell is becoming the standard scripting/shell environment on Windows. VBScript and JScript are now legacy so I recommend switching.

  • Anonymous
    Offline Anonymous

    That's quite old one trick.
    Forget about it and You'd better learn the same functionality using SDL APIs from the very beginning.
    And most importantly, If you know how to use it let me know the trick you've learnt, I am a seeker just like you.
    (By the way, Though I know some(and more) Chineses, the VS stuffs are far more complicated than that. Just for your reference.)

  • Hi there!

    "I find your lack of faith disturbing". *ahem*

    It should very well be possible - provided that at least you or one of your fellow engineers (the more the merrier) get your head around .Net Framework. Then you can create your own COM/ActiveX, which you should then be able to access via script.
    Not going into whether it is a wise thing to do - I think we can find a lot of pros & cons on this.

    Still take a look here, this might get you started:
    http://stackoverflow.com/questions/3360160/how-do-i-create-an-activex-com-in-c

    BTW: The "TW4Win.Application" object was not open source either so this is about as open source as you can get.

    Hope this helps.