Making Suggestions and Displaying Existing Suggestions
- Nov 09, 2012
- 1 Comment
This week I made some progress by connecting the "Show mentee worlds" view to the community, as in the future it will be pulling the mentee's shared worlds from the community for the mentor to pick from. The Mentor can select a world, look at the student's code and watch the animation.
I started to work on the "Make Suggestions View" and soon realized that I need to do some more thinking about how exactly to implement it before I can move forward. When a mentor makes a suggestion, we need to store the changes in the code so that we can show them to other mentors and make tutorials out of the changes when other students' worlds fit the rule. On the front end, I also need to figure out a way to show these changes to the other mentors in a meaningful way. I have thought about a few ways to do this, such as showing the original and changed code, and showing changes like revision histories, but neither of these seem to fit exactly right. Thinking about something like google docs revision history, crossing out deletions and changing the color of additions works because you can do this for each individual letter- you don't need to keep words as whole elements. In Looking Glass, procedures cannot be split up into smaller pieces, so when you change a parameter, you can't show it in the way you would normally show changing a letter in a word document.
I am also trying to decide whether mentors should be able to see their code changes highlighted in some way as they are making the suggestion. I'm afraid this might be kind of distracting, but it might also help them to make sure they can see the changes they have made and whether that is what they meant to do. This way, they can see what other mentors will see when reviewing their suggestion, which might improve the quality of the suggestions.
My new computer also arrived this week, which was pretty exciting!
Comments
caitlin said:
<p>Having just finished reading Michael's blog entry I'm wondering whether there's a way to leverage annotations in the code itself to track some of this. The nice thing about going this route is that we should be able to make some relatively straight-forward changes in the code editor to change the way that say a parameter shows up if it's been changed by a mentor. I think annotation through the ast is probably good for additions/modifications.</p> <p>For deletions, I've been wondering whether we want to use a modified version of "disable." </p> <p>This may also drive that whole push to make it so that components can choose to create different versions of themselves depending on the perspective. That way we could make it so the kid doesn't necessarily see things as marked up differently (although maybe we'd want to do some mark up, just a different kind than what we do for mentors?) Who knows. </p>
Log In or Sign Up to leave a comment.