Coleman opened this issue on Jan 10, 2006 ยท 72 posts
svdl posted Wed, 11 January 2006 at 4:45 PM
Jimdoria - you're right. Bolting on a scripting engine afterwards is a surefire recipe for major development headaches. So IF eF are going to rewrite Poser from the ground up, they'd better do it with scripting designed into the app! If not, I seriously doubt whether scriptability will ever be at a decent level. The VBA route in Office was quite complicated indeed. The first "sort of" VBA appeared with Access version 1.0. The first full VBA was in Excel 4.0. WordBasic was a rather lame and counterintuitive scripting language. Office 97 was the first version that consolidated VBA as the Office scripting language, and the first version that allowed for calling other apps from within a script. Not flawless, indeed. I ran into quite some bugs, in every Office version. But usable, for the most part, and without blatant omissions in functionality. There's a good reason Corel dropped its own scripting engine for WordPerfect and licensed VBA!
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter