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

Scale back capstone lab #22

Open
vilmibm opened this issue Apr 21, 2015 · 2 comments
Open

Scale back capstone lab #22

vilmibm opened this issue Apr 21, 2015 · 2 comments

Comments

@vilmibm
Copy link

vilmibm commented Apr 21, 2015

The capstone lab currently introduce a lot of useful concepts and is mostly well organized but unfortunately many of these concepts are not introduced by the ClojureBridge curriculum. My students were caught off guard by:

  • ref
  • absence of ! idiom for noting state-changing functions (this is a thing the curriculum hints at)
  • for
  • doseq
  • dotimes
  • dosync
  • namespaces
  • Dereferencing (@)
  • Where to find images (snowflake, blue background)
  • No explanation of q/smooth or changes in q/frame-rate
  • Hard to tell what changed between each code sample
  • The concept of refactoring
@yokolet
Copy link
Member

yokolet commented Apr 21, 2015

Thanks for filing this!

For record, ClojureBridge/curriculum#115 , is a related issue. But, this issue makes clear how we should incorporate quil into curriculum.

@yokolet
Copy link
Member

yokolet commented Sep 2, 2015

Hi @nathanielksmith , I finally updated main curriculum and snowflakes app.

  • Deleted from snowflakes app
    ref, for, dosync, deref
  • Added topics in main curriculum
    doseq, dotimes
  • Where to find images
    There's a link in step 1-4, "put two images there"
    Do you think this helps? If you have other ideas, let me know.
  • q/smooth, q/frame-rate
    The explanation about q/smooth was added in step 2-2
    all q/frame-rates were deleted from snowflakes app. I changed the last swing part and now all examples work fine with the default frame-rate value
  • Changes between each code samples
    I added comments what lines were changed or added in the code. It is markdown, so line number won't be added to the code 😦 I hope this got better, but again, let me know if you have other ideas.

Given that, remaining topics are namespace and concept of refactoring. I'll think about how to do these.

Anyway, take a look. I appreciate your feedback.

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

No branches or pull requests

2 participants