Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tips for Students commented at beginning of code. #563

Open
truthgoddess opened this issue May 31, 2019 · 2 comments · May be fixed by #566
Open

Tips for Students commented at beginning of code. #563

truthgoddess opened this issue May 31, 2019 · 2 comments · May be fixed by #566

Comments

@truthgoddess
Copy link
Contributor

See: https://woofjs.com/create.html#starting-text-test

While working on #448, ran into an issue in which some very cool tricks and shortcuts weren't easily or well placed as buttons in the tools menu.

A solution is that we can put information as a comment in the code editor window as shown above.

I will include reasons that CTRL-D is better placed here in a comment for #448, but I think for this issue, we can think about if this is good, what can be included, and then work on making it happen.

Pros to this:

Students will see comments in the code, and start wondering about it, why it exists, what to do with it, and what a comment is.

Students will eventually read and try out the shortcuts and commands themselves. Some of them are quite fun, and it will engage student's curiosity.

Links provided at the bottom encourage students to use resources that they need to understand Javascript. They can also reinforce that WoofJS is javascript. Currently, Piskel seems a very easy to work with and popular choice in my classes. The students who I point to that find it easy to use and makes Woof even more fun.

@madduccino @stevekrouse What do you both think?

@stevekrouse
Copy link
Owner

stevekrouse commented Jun 3, 2019 via email

@truthgoddess
Copy link
Contributor Author

I think that the tools menu is the best place. Maybe I should have tried that earlier. Will make the look now, add the pull request for a few items, and then ask for suggestions about additional items before merging.

@truthgoddess truthgoddess linked a pull request Jun 5, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants