🚀 go-pugleaf

I agree with you that VB is better choice for scripting InDesign as .NET.
What I don't understand is the politic of developers of InDesign waisting so much time to build SDK which nobody want to use because it is not realy friendly for programmers - it takes much to much time to lern how to make a plug-in and finding the right way to find objects and properties. Even if the API is beeing better and better it still takes 10 times more time to develop a plug-in doing the same a script can do. Would it not be better to make InDesign FULL scriptable with all the widgets, menus and other stuff? Even now CS support Script-Dialogs but there is still something missing on it - some controls are not aviable like a simple ListBox! (why?).
Well, the only one advantage of API is, it works platform independ - quite OK for small plug-ins but when you try a bigger projekt using Databases it will not be platform independed because the access to DB via ODBC is not the same on PC or Mac. Another stuff is the way Adobe is dealing with programmers - I work with API and scripting of InDesign since early alpha version of InDesign 1.0 - each new version has many changes to ObjectModel of InDesign which causes additional work - I think it is not OK, even Microsoft has find the way to make changes to ObjectModel but keeping the old references still supported - the way each programable application should work. And today the computers are so fast - it is not realy a problem VB is much slower then C++. So why again cannot it be done the easiest and fastes way? - think about waisted money of companies which are working on solutions with InDesign because of API and scripting differences.

BTW - it is possible to access the text of the TextFrame like this:
TextFrame.Contents="dummy text"
myVariable=TextFrame.Contents

regards

Jarema