Tips for Students commented at beginning of code.

[truthgoddess]

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]

I think this would over-prioritize those tips. We want them to be discoverable but they aren't the highest priority. One idea is finding a place for them in the docs menu. Another idea is putting them in the Tools menu as tips (not buttons). Another idea is having a button/keyboard shortcut in the tools menu which pull up the "tips menu" which can be a popup or new tab. I think it's a wonderful idea to link to Piskel in the docs menu under image sprites.

…

On Fri, May 31, 2019, 4:14 PM Kate Norton ***@***.***> wrote: See: https://woofjs.com/create.html#starting-text-test While working on #448 <#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 <#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 <https://github.com/madduccino> @stevekrouse <https://github.com/stevekrouse> What do you both think? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#563?email_source=notifications&email_token=AARO2KZV7MUSDJZOGCAN333PYEQCTA5CNFSM4HR2UOW2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GW6SC5A>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARO2K43P2GDM3KY647XAULPYEQCTANCNFSM4HR2UOWQ> .

[truthgoddess]

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.