🚀 go-pugleaf

James--

Actually, the VBScript examples are quite a bit different from the VB examples of the same names that were in ID 2.x--most of them, for example, create their user interface using InDesign's Dialog object. The previous examples were all done as VB6 projects with VB forms. The logic of the examples has changed, and (of course) all of the terms have been updated (the examples show the change from TextContents to Contents, for example).

VBScript will be the VB language type I use to deliver example scripts for InDesign from now on. VBScript is accessible, and users need have nothing other than Notepad to write the scripts, and VBScripts run faster from the Scripts palette.

The only time I will create VB.NET/VB6 example projects is when I need to demonstrate something specific that can more easily be done there, such as some XML operations. In those cases, I'll be tempted to use VB6.<g> In any case, the VBScripts should be relatively easy to adapt to VB.NET, as the terminology of the InDesign object model is the same.

Others may develop examples in whatever language they want, of course.

By the way--I'd advise against using the prefix "id" for your variables, as it's used by InDesign's enums. Speaking of enums, one change from 2.x is that you need to specify the enum class, as well as the enum member, when you're using an enum. So what was:



Rem 2.x example 
myParagraph.Justification = idLeftAlign

should now be:

Rem CS example 
myParagraph.Justification = idJustification.idLeftAlign

Thanks,

Ole