Skip to content

Tips for Students commented at beginning of code. #563

Open
@truthgoddess

Description

@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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions