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

Non clickable tools tips #566

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

truthgoddess
Copy link
Contributor

@truthgoddess truthgoddess commented Jun 5, 2019

@madduccino @stevekrouse

Put non-clickable tools, tips, and tricks in a menu which I have called Coding Tricks (but which is a placeholder in case we all have better ideas.)

I moved the comments from the more blocks menu into this menu, since the more blocks menu is more focused on functions, and I believe we should in the future provide better tutorials on coding topics like functions, so the focused more blocks is a great place for that if we want to fill it out.

Added leftover commands that we wanted from #564.

Tried to choose a color type that wasn't represented yet in Woof since this menu doesn't have a corresponding menu in Scratch. I'd argue for a version of pink to add a color that attracts pink lovers, since the pink isn't represented anywhere, is clear, and can help brighten the experience for users. It is also a cultural color sometimes used in a disparaging way, and by associating it with WoofJS we help bring the color into a space that can be appreciated by everyone.

That being said, I think the most important thing is choosing a color that isn't represented yet, and in the long term, I'm hoping our efforts make Woof more fun and immediately exciting, and I think a little splash of pink can be very exciting.

Closes #563.

I expect that there will be changes to many aspects of this, and am happy to make them.

@truthgoddess
Copy link
Contributor Author

@nicolekelner Love your thoughts here too if you want.

@stevekrouse
Copy link
Owner

[This is an automated integration to preview this pull request's changes to the website.]

https://cdn.rawgit.com/stevekrouse/WoofJS/51f384e08c86d1a7265b535fb33133c21948b950/index.html

@truthgoddess
Copy link
Contributor Author

I notice that I wrote backslash when I should have written forward slash, so I'll fix that before a merge is done, but I anticipate feedback, so I'll also fix it after the feedback.

@truthgoddess
Copy link
Contributor Author

truthgoddess commented Jun 5, 2019

Also notice that the horizontal lines are the color of the block in my branch. I think that would be better for all of our docs, rather than the grey. So, if anyone agrees or disagrees with that, I'm happy to adjust as necessary. Again, my thought is:
if (WoofJS == more fun) {students = excited about WoofJS}

@truthgoddess
Copy link
Contributor Author

@stevekrouse @madduccino Bump! :)

Since camp is starting this week, and I feel that we are pretty organized, I'm probably going to have time to get back to curriculum and Woof. I'd love to your thoughts on this. Color wrong? Placement wrong? No color on bars? Not a good place for it? Anything at all helps. I don't like leaving things open. I'd love to move this forward step by step.

Cheers.

@madduccino
Copy link
Collaborator

I think it's great to have this information available! I'm not sure if it should be its own block, though. I'd vote for having a Coding Tricks option in the Tools menu and have a modal pop up when you click it.

@truthgoddess
Copy link
Contributor Author

Cool, I'll try that and update this!

@stevekrouse
Copy link
Owner

Agreed with @madduccino. I might call it "More Tools". I worry that "Coding Tricks" might feel a bit too cute or childish.

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 this pull request may close these issues.

Tips for Students commented at beginning of code.
3 participants