Education - Uploading Sketches

edited December 2016 in p5.js

Hi All, I was wondering if anyone could advise me on the following. Im teaching about 150 students P5.JS next term and wondering what the best place would be for each student to upload their sketch? It can't really run it on the uni server, nor can I ask each student to get a domain. Im considering using dropbox but that isn't ideal. Any suggestions? Thanks

Answers

  • edited December 2016

    For using a public host like the ones @GoToLoop recommends, having them all use the same tag or tags as a requirement of the assignment will also make your life much easier during feedback and evaluation.

  • I'd personally recommend CodePen.

  • Answer ✓

    Github. Start them young. 8)

  • @koogs, is that also setting up GitHub Pages etc. for display, or just then interacting on the desktop through a checked out repo? Never had a class use Github for web publishing (or used it for that myself, actually) so I'm curious. All one class repo?

  • I don't even know if github hosts 'runnable' pages, was more a (slightly jokey) suggestion that they should be using source control anyway so why not use that?

    But thinking about it you'd need a paid account (edu account?) set up so individuals can't see the other accounts in the group or plagiarism would be rife.

  • Github.io might do it. I have a static page there but you can host Jekyll based pages I believe and they use JavaScript.

  • What are the advantages or disadvantages of using any of them?

    https://www.OpenProcessing.org/
    http://p5js.SketchPad.cc/
    http://codepen.io/
    Github.io

    Kf

  • edited December 2016

    OpenProcessing, SketchPad and also p5IDE: http://p5ide.HerokuApp.com/editor
    we don't need to write our own HTML template in order to load p5js libraries.

    Besides CodePen and other general JS hosts, Mozilla's Thimble proved me very useful when I needed to store other file types as well: $-) https://Thimble.Mozilla.org/en-US/

    Of course, there's always GitHub. But it's slightly more complex to setup as a webpage. :-\"

  • Perhaps the major problem with OpenProcessing and SketchPad is that plagiarism would be real easy.

  • edited December 2016

    Those are free public host sites for JS code. Although some have a paid option and may provide private hosting. For free private hosting, GitHub offers Gist btW: https://Gist.GitHub.com/ :-bd

  • There are ways to control plagiarism the first would be to require the students to upload their sketches just before the assessment deadline e.g. no more than 6 hours before and/or submit a printed version to the tutor before uploading to prove he/she created the version uploaded. Also these sites use timestamps which would identify who uploaded first.

    Sites like OP ,which allow comments enable more novel forms of assessment e.g. self assessment where students can comment on other students sketches.

  • Just visited OP for the first time in ages, its been completely revamped so I am not sure about the timestamps now.

  • Well, I guess if you have honest students then that wouldn't even be a problem, but otherwise, students generally find ways to, well, cheat.

  • edited December 2016

    Just visited OP for the first time in ages, its been completely revamped...

    That revamped version now happened very recently AFAIK. :\">
    Along w/ that, p5.js option was introduced. Otherwise I'd only have cited http://p5js.SketchPad.cc/ >-)

  • What are the advantages or disadvantages of using any of them?

    The best (maybe only) way to answer this is to just try it out yourself and see which one you like best.

  • I've recently had some struggles using the revamped OpenProcessing search. It didn't seem very reliable -- you might want to do a test on whether tags / descriptions are actually findable if that is part of your grading strategy.

    There are better ways around the plagiarism problem than avoiding public repos -- even with 150 students. For one example, generative exercises which take the student ID as the input.

  • With regard to plagiarism, I would think there would be two steps:

    Step 1: Students submit their code directly to the teacher. The teacher runs each one locally and issues grades.

    Step 2: After the grades are returned, then students can upload their code somewhere. This is more for the "cool factor" of being able to show off their code, plus deploying code is a confusing thing that's good to teach.

    If you're worried about plagiarism (and OP did not say that they were), then don't have them post their code publicly. Also consider that next year's students will have access to the public code as well.

  • And if you're worried about plagiarism, the projects should be more innovative and should not exist on the web.

  • Hi all, thanks for your feedback. Looks like using GitHub Pages is the way forward for me. Many thanks

Sign In or Register to comment.