Article View: adobe.scripting.indesign
Article #15063Re: VB.Net and InDesign CS different then InDesign 2.0
From: James_Mahood
Date: Mon, 15 Dec 2003 21:49
Date: Mon, 15 Dec 2003 21:49
5 lines
1436 bytes
1436 bytes
Actually I am only dissatisfied with Adobe, Microsoft is fine. When Microsoft creates an SDK (Software Developers Kit) interface it stays the same so they maintain backwards compatibility. It is nice when old programs work on new operating systems. They also put notes in the help files for the older interfaces directing developers to use the new calls. You are right, scripting for anything is notorious for not maintaining backwards compatibility. I think it is the vary nature of scripting that when the program changes, old scripts won't work. The issue here is the SDK for InDesign to use it with a Visual Basic program, not a script, that didn't maintain backwards compatibility. Adobe could have maintained backwards compatibility by providing two interfaces to InDesign CS.
Technical Details
Message-ID:
<2ccec5cf.8@webx.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!fu-berlin.de!newsfeed01.sul.t-online.de!t-online.de!webxReferences:
<2ccec5cf.-1@webx.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f939a,28e19235f1e28fa8 X-Google-Attributes: gidf939a,public X-Google-ArrivalTime: 2003-12-15 14:08:11 PST From: James_Mahood@adobeforums.com Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!fu-berlin.de!newsfeed01.sul.t-online.de!t-online.de!webx Newsgroups: adobe.scripting.indesign Subject: Re: VB.Net and InDesign CS different then InDesign 2.0 Message-ID: <2ccec5cf.8@webx.la2eafNXanI> Date: Mon, 15 Dec 2003 13:49:45 -0800 References: <2ccec5cf.-1@webx.la2eafNXanI> Lines: 14 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit