Comments (9)
This one is specifically about the "unknown" parsing error, where a whole can't be parsed. We need to give more instructive feedback about the error, and try to figure out what they were trying to type and offer targeted recommendations.
from gidget.
For now, I have currently gone through the text.js file to redo the speech to make it more consistent for both the control and experimental conditions.
Any suggestions on how we can give feedback about what they typed in? Currently, only some of the function calls in text.js have variables pushed to them.
from gidget.
The feedback should really depend on the tokens they have typed in. At the very least, we should be giving them some detail about the commands that Gidget knows and examples of how to type them. Even better would be feedback that's tailored to what they typed (for example, if there were typos, checking for off by one character typos and seeing if they match any of the commands or objects in the world, then recommending commands). If nothing matches, we could show a list of the commands that Gidget knows, like a help listing for a unix command.
from gidget.
Got it. I think this will be a valuable feature of the language as it serves dual purposes - to highlight an error, and also to act as a teaching opportunity.
I haven't worked with this kind of text parsing/processing before, so I am certain that I won't have anything usable implemented by tomorrow's target pilot launch date.
from gidget.
Let's talk about it in our meeting tomorrow.
from gidget.
This is a reminder that we should talk about this during magic desk time.
from gidget.
The feature idea:
- Add a cheat sheet below the code area that contains all of the commands that Gidget knows
- The commands that Gidget knows are determined by which level the player is on. Add some code to level specs that detail which commands are not available and use it to hide syntax on cheat sheet.
- When Gidget encounters some sort of parsing error, rather than offering suggestions in the dialog, he highlights elements of the cheat sheet to explain why he was confused.
- The user always has control over showing and hiding the cheat sheet
- The cheat sheet goes away after the parsing error is passed, unless the user was the one who opened it.
from gidget.
Added a cheatsheet, a control for toggling it, and code that highlights specific parts of it when particular parsing errors are encountered.
Work remaining for Mike:
- Go through each level and call world.addHiddenCommand() for each command Gidget shouldn't show in the cheat sheet.
- Add all missing commands to cheat sheet, being careful to name them 'cheat-' since the UI code hides them based on the names passed into world.addHiddenCommand().
from gidget.
- All current commands are included except for 'name.'
- All levels updated to hide unknown commands for that stage
- Changed some wording to make Gidget gender neutral.
from gidget.
Related Issues (20)
- Non-Gidget actors' response to errors in their code HOT 3
- Safari (Windows) styling is misaligned HOT 1
- Create platform-specific stylesheets HOT 2
- Graphics are not sharp in certain browsers due to auto-resizing HOT 1
- need blender.sad.png HOT 1
- Crediting sources
- initialize.js should explicitly check for unsupported browsers in redirect HOT 3
- Step buttons don't execute gCode in Firefox (Mac & Windows) HOT 5
- Safari (Windows) not loading completely HOT 8
- Update 'unsupported.html' to reflect our decision not to support Mac Chrome HOT 1
- Should Linux browsers be supported? HOT 3
- Code buttons misaligned in Linux Firefox
- Go through all text for consistency before MTurk launch HOT 1
- Go through all images for consistency before MTurk launch
- Disable debug menu and other shortcut keys before release HOT 1
- Wording of "quit" dialogue buttons may be too suggestive HOT 1
- Browser access via whitelist instead of blacklist HOT 1
- Modify scenes.js so it supports different positioning of a sprite HOT 1
- After receipt of MTurk code, container is still visible underneath the "quit/disabled" message. HOT 1
- Button doesn't close window after press in MTurk Code "at least one level" box HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gidget.