Unknown said:

SDL have made a great wall (again) 

Are you saying that SDL have built a wall to prevent users from implementing the apps they want with Studio 2019?

All the apps created by SDL themselves have been updated to Studio 2019. No wall.

Any apps that have not been updated yet were created by third party developers - very often free of charge to the user - this is also not a wall, just work in progress. If you are wanting a specific app to be updated for 2019 then contact its creator and ask them to update it. This isn't within SDL's responsibility.

Or have I misunderstood your reference to a great wall?

All the best,

Alison

Unknown said:

Or have I misunderstood your reference to a great wall?

Hi Alison Field 

 is referring to the fact we require apps to be upgraded at all and don't provide a framework that means they work in any version.  I think we all wish this would be the case but it's a very simplisitic view based on no knowledge of our internal needs.  In time we'll iron out these problems and continue to improve the delivery of apps as we migrate from one version to another... until then I hope users and developers will be patient with us and enjoy the platform we have made available in the first place.

I love the wording you use "simplisitic".
I clearly remember when MS Word changed their format from .doc to .docx.
That was a Real upgrade (not this kind of version 2017 to version 2019)
But, I have not changed anything, not even a line, word or space of my old AddIn (PlugIn) codes of it.
Even though MS gave me lots, lots of documents to read and adopt,
they kept their past perfectly, until today I can use the stone aged AddIn (PlugIn).

That is the real meaning of "simplistic"

regards

Unknown said:

But, I have not changed anything, not even a line, word or space of my old AddIn (PlugIn) codes of it.
Even though MS gave me lots, lots of documents to read and adopt,
they kept their past perfectly, until today I can use the stone aged AddIn (PlugIn).

I believe that one of the reasons (if not the only one) is that MS Office API uses COM interface, not .Net like Studio.

This is what I criticized from the first moment I got familiar with Studio API and asked SDL to expose the API via COM again, as it used to be back in Trados 2007 (where automation could be done was SOOOO EASILY).
It should be basically just a few lines of code... but for some weird reasons SDL keeps quiet and doesn't say anything to it.

And here we go with the consequences...

Hi Evzen Polenka hi Paul 

Ah, I understand now... I was half asleep...

I apologise Hoon Kim

All the best

Ali

Hi Evzen Polenka hi Paul 

Ah, I understand now... I was half asleep...

I apologise Hoon Kim

All the best

Ali