• State Suggested Answer
  • Replies 23 replies
  • Answers 3 answers
  • Subscribers 356 subscribers
  • Views 19485 views
  • Users 0 members are here
Options
Related

SDK and documentation for Trados 2007

Jesus Mañogil

Hi all,


I'd like to automate some tasks using the old Trados version, I mean 2007.

I've seen there are plenty of documentation from 2009 on, but I don't find anything related to the previous version and its SDK. Anybody with the same problem?


Thanks in advance.
Rate translation
×
Suggest better translation
×
  • 0 in reply to Evzen Polenka

    Unknown said:
    Regarding PowerShell - have YOU personally tried to write some simple T2007 automation in VBScript and compare it with TS201x effort needed for the same automation using PowerShell?

    ......

    So I strongly suggest everybody to get realistic and get out of their offices and talk to real common users...

    Hi Evzen,

    I get your point, it's unfortunate you can't see it from our persepective as the current solution is lot more successful than the old COM approach ever was.  However, maybe as Patrik suggested it may be that adding a simple way to call the sort of things you understand might be useful for some users.  I don't think we need to get out more though as I can assure you I know of more development work carried out by our users since we provided this capability than we ever had before.

    On your question to me... well I'm not clever enough to develop anything and don't know anything about the COM stuff, but when the powershell toolkit came out I did have a go and even showed quite a few people how to get started.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Hi Paul,

    please have another go with CURRENT Studio version (i.e. 2014/2015) installed on CURRENT operating system with CURRENT standard updates and the Powershell Toolkit and you will see what I'm talking about (and as I said, it's not about changing the Studio paths in the PS modules... it's about some weird .NET version vs. PowerShell version hell).
    And also try to do MORE than the very few simple operations included in the toolkit!

    You guys still don't get what I'm talking about - there is a HUGE difference between DEVELOPER and (POWER)USER with scripting ability...
    This forum's community is NOT powerusers, these people are developers.

    As long as the API stays accessible ONLY via .NET hell, there WON'T be any "simple way" to do things... because the re is no SIMPLE way to use .NET hell.
    Unless some developer(!) puts a HUGE effort into creating something what will 'mimic' the ease of use of the former COM API.
    Which is highly unlikely to happen... because developers don't see the need (THEY do speak .NET, so why would they do it, right?) and powerusers don't have the knowledge.
    So us, scripters like me (or maybe Jesus who started this thread) will be still out of the game.

    There is absolutely no NEED to abandon COM (as we see on Microsoft Office).
  • 0 in reply to Evzen Polenka
    Hi all.

    I believe you all are partially right. In my personal case I've used several programming languages and being open-minded people is the best option...at least to keep mentally sane.

    Thanks again.