Skip to content

Provide help for global APIs used at top-level code.#1130

Merged
lmccart merged 2 commits intoprocessing:masterfrom
toolness:issue-1121
Nov 29, 2015
Merged

Provide help for global APIs used at top-level code.#1130
lmccart merged 2 commits intoprocessing:masterfrom
toolness:issue-1121

Conversation

@toolness
Copy link
Member

This fixes #1121.

Right now the only global this PR detects and provides help for is color, as this is one that it seems like beginners often use at top-level code (I stumbled on it when first using p5, and so have others). In the future, though, maybe we could somehow get a list of the global symbols from YUIDoc or something?

For now, are there any other global symbols we should provide help for?

@lmccart
Copy link
Member

lmccart commented Nov 26, 2015

awesome! I think random() is another common one, too. yeah, eventually it'd be nice to have the full list pulled from the docs or src, but I don't think it's as high priority.

@toolness
Copy link
Member Author

Ah good idea! Just added random.

This makes me wish we could add one of those "anonymous usage reporting" types of features that lots of consumer products have, so that we could get statistics on other kinds of errors folks are making, but that'd probably be hard to do in a way that doesn't violate privacy or otherwise weird people out. Maybe it's just best to encourage teachers to keep a spreadsheet of common errors, as suggested in #971 (comment).

lmccart pushed a commit that referenced this pull request Nov 29, 2015
Provide help for global APIs used at top-level code.
@lmccart lmccart merged commit 34d88a4 into processing:master Nov 29, 2015
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.

Provide friendly error help when sketches use p5 functions outside of setup/draw

2 participants