Scripting Applications: Not Just Smalltalk
time to read 2 min | 267 words

James Robertson has a post about application scripting that I partly agree with.

 That's why I include a workspace in BottomFeeder - I actually use it myself for scripting and experimenting. That kind of end application scripting has led to actual product features, and is something that is well nigh impossible in Java or C#. In applications shipped in those languages, you have a dead end - if the developer didn't consider it, you're just done. Does this mean that just anyone can start coding in the Bf workspace? No, you do need to know the APIs and class names - that's a limitation. But at least you get far enought to have the limitation :)

I agree that application scripting at the client is useful; and I think that it's very likely that users / developers would want an easy way to modify the application after it has shipped. My problem is that he goes on to claims that it's nigh impossible to do so in C# or Java. No I can't say much for Java but in .Net you can most certainly do that, and it's not that much of a bother.

Here is my post about Automating Your Application and here is the original article about adding scripting capabilities to your application.

Tweet Share Share 0 comments
Tags: