Skip to content

final project exploration #1: learn Github, play with a Racket library

Notifications You must be signed in to change notification settings

oplS17projects/FP1

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 

Repository files navigation

Final Project Assignment 1: Exploration (FP1)

DUE Sunday, March 12, 2017

#Part 1: Get github If you don't have a github account, go get one. https://github.com/ This whole assignment will be done and submitted via github, and you're already here!

#Part 2: Try a Library In this exercise, you will play with at least one library provided by the Racket developers. You will have the opportunity to explore another library later.

Please choose libraries that you think you might be interested in using in your final project.

Start off at the Racket home page, http://racket-lang.org/, and then click on the Documentation link, taking you here: http://docs.racket-lang.org/.

There are lots of libraries. Play with one.

Your job is to explore one library and write up your results. Load the library and write some code to drive it around. For example, maybe you are interested in retrieving data from the web. If we look at the net/url library, we will find functions for creating URLs, issuing HTTP GET commands, and displaying the results. Here is a little bit of code for driving around a few of the functions in this library:

#lang racket

(require net/url)

(define myurl (string->url "http://www.cs.uml.edu/"))
(define myport (get-pure-port myurl))
(display-pure-port myport)

Notice that (require net/url) is all you need to put in your buffer in order to load the library and start using it. This above is a trivial example; to complete this for the purposes of this assignment (if you go down the path of pulling HTTP requests), you should use the parsing libraries to parse the HTML, JSON, or XML that is returned.

The following libraries are not allowed for project explorations:

  • games/cards
  • racket/gui
  • racket/draw

You can still use these in your project, but you must explore different libraries for this assignment.

#Part 3: Write your Report Write your report right in this file. Instructions are below. Delete the instructions when you are done. Also delete all my explanation (this stuff), as I've already read it.

You are allowed to change/delete anything in this file to make it into your report. It will be public, FYI.

This file is formatted with the markdown language, so take a glance at how that works.

This file IS your report for the assignment, including code and your story.

Code is super easy in markdown, which you can easily do inline (require net/url) or do in whole blocks:

#lang racket

(require net/url)

(define myurl (string->url "http://www.cs.uml.edu/"))
(define myport (get-pure-port myurl))
(display-pure-port myport)

My Library: (library name here)

My name: put your real name here

Write what you did! Remember that this report must include:

  • a narrative of what you did
  • highlights of code that you wrote, with explanation
  • output from your code demonstrating what it produced
  • at least one diagram or figure showing your work

The narrative itself should be no longer than 350 words.

You need at least one image (output, diagrams). Images must be uploaded to your repository, and then displayed with markdown in this file; like this:

test image

You must provide credit to the source for any borrowed images.

Code should be delivered in two ways:

  1. Full files should be added to your version of this repository.
  2. Key excerpts of your code should be copied into this .md file, formatted to look like code, and explained.

Ask questions publicly in the email group.

How to Prepare and Submit this assignment

  1. To start, fork this repository.
  2. (This assignment is just one README.md file, so you can edit it right in github)
  3. Modify the README.md file and commit changes to complete your report.
  4. Add your racket file to the repository.
  5. Ensure your changes (report in md file, and added rkt file) are committed to your forked repository.
  6. Create a pull request on the original repository to turn in the assignment.

Project Schedule

This is the first part of a larger project. The final project schedule is here.

About

final project exploration #1: learn Github, play with a Racket library

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published