On Fri, Sep 27, 2013 at 1:03 PM, Anirvan <[email protected]> wrote: > Hello Kris, > > Appreciate your response. > > Even I have an inkling that trying to write some plugin might just end up > being something *big*. However, what we need to establish is whether a > particular user was able to follow our tutorial and do some basic > application changes as part of our chapter exercises. > > So yes, we are trying to determine whether a user was able to correctly make > *physical* code changes as part of a chapter's exercises. > > Consider it like, suppose you were preparing a tutorial on Javascript, and > you wanted your tutorial to be interactive, you can have many ways to test > whether the user is able to follow the instructions on her own. But that's > not possible to do with Android through a web-based platform. At least not > that I know of. So is their any way I could tell the user — go do this and > this, and after that run your code. Now if it runs properly, we should be > able to receive some signal through the build process, which indicates that > the user did the right thing. And then, we let the user know whether she was > successful with the last set of assignments.
What even is "the right thing?" Do they have to have the class named the correct thing, do they have to have some sort of functional behavior? Do they have to place the button on the screen in the right way? Ultimately, there are going to be an infinite number of ways to do the right thing, each valued slightly differently. Static analysis at the source level is extremely hard in Eclipse because it's a huge API that you have to tie yourself to pretty intimately. Whenever I parse Java source I actually use a compiler toolkit, because Eclipse's mechanisms are so hard to work with. In any case, I think you have bigger problems, since doing this for JavaScript seems equally complicated. The way to start is to look at changes to the AST of the code. This is pretty possible to do within Eclipse, supposing you're willing to put in a lot of work. However, nobody on this list can really help: this is more about designing Android programs. Instead, I'd point you at a list targeted towards Eclipse hackers. Kris -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
