From their FAQ: "Pnuts runs with on-the-fly bytecode compiler by default." A Dalvik-aware Pnuts might work, but I suspect otherwise it'll try executing ordinary Java bytecodes on Dalvik and run into issues.

I think most Java scripting languages went this route (Jython, Groovy, JRuby, etc.), which may limit one's options in the near term. That's one of the reasons I went with Beanshell, figuring its execute-off-an-AST approach might well hold up on Android.

"Good luck with the book."

Likewise!

Good luck with the book.

My hope is that it's more of a "seal of approval" vs. the Apple-style "it only runs if *we* say it runs". Prospective buyers/downloaders can look for the seal of approval and make their decision based upon whether it's there or not.

One limitation of scripting is that you can't register a script in AndroidManifest.xml. And you can't script layout XML files, resources, or anything else that gets packaged in the APK. So, you always need some Java code as the entry points into your application (e.g., your activity) and probably some other files as well. You can't create an Android application that is 100% scripted, at least with the current frameworks at our disposal.

While I will probably add a chapter on scripting to an Android book (possibly the Advanced Android one I have on the drawing board), I am a little hesitant to make it the foundation of all the examples, particularly in the current book.

And thanks for the feedback on the article and book!

You could incorporate this into your book to easily test out examples on the emulator.

Your book is very well done.