Courses‎ > ‎Software Development 1‎ > ‎Dyrland-Weaver‎ > ‎


All smaller assignments (those posted here) should be uploaded as submodules to the workshop repository in the appropriate assignment directory.

Make sure to put your submodule in the folder of your period and include your name and the name of your partner(s) (if applicable) in the repo name.

Last Class Today!

At the end of each class, 1 student will be chosen at random to post the day's notes online.
Notes will be posted in the document for each class in the notes-and-code repository on github (
Title the note [DAY] [DATE] [TOPIC/AIM] by [AUTHOR]
For example:   Wednesday, 9/14 Variable Types by JonAlf Dyrland-Weaver
Also include at the end of the note a link to an interesting piece of tech/science news.

Work 17: Moo

posted Dec 12, 2017, 10:17 AM by JonAlf Dyrland-Weaver

You mission:
Create a more palatable version of the Find-a-Cow game, using shades of your (team’s) favorite color instead of audio to let the user know how close they are to the target.
  • Use the HTML and JS files provided in the notes-n-code repo.
  • You should avoid editing the HTML file.
  • You should avoid deleting anything from the JS file.
  • Darkest shade <-> quietest “cow”
  • Lightest shade <-> on target
  • Develop using shades of grey. Once that works, you make choose your favorite color...
Upload to the workshop under 17_wow.

Work 16: DOMinate your HTML

posted Dec 8, 2017, 9:49 AM by JonAlf Dyrland-Weaver   [ updated Dec 11, 2017, 10:17 AM ]

With your table buddy do the following:
  • Grab copy of intro.html from the notes-and-code section of github.
  • Write a javascript file that will do the following:
    • When the button is pushed, add an element to the list
    • When the mouse goes over an item in the list, change the heading at the top to contain the text of the item
    • When the mouse is no longer over an item in the list, change the heading back to "Hello World!"
    • When an item on the list is clicked, remove it from the DOM
  • Add the following to your previous work:
    • Add a second list to the html page, do not add elements to it.
    • Create a second button.
    • When the second button is pressed, the new list should have an item added that contains the next fibonacci number.
    • For the mathematically inclined, you could add more lists that generate other numeric sequences if you like.
Submit your html and javascript files in the workshop under 16_jsdom

Work 15: Won't you take me to ... function town!

posted Dec 6, 2017, 6:11 AM by JonAlf Dyrland-Weaver

With your table buddy:
  1. Grab a copy of open_me.html from the 15_js folder in the workshop.
  2. Create a file called funky_town.js
    • open_me.html loads a script file by this name.
    • You will write javascript functions in this file, which you can test by opening open_me.html in a browser and going to the developer console.
    • What functions you ask? Let me tell you
      1. fibonacci(n)
        • Should return the nth fibbonaci number
      2. gcd(a, b)
        • Find the greatest common divisor of a and b.
        • You may want to consult some old code from intro or AP
      3. randomStudent()
        • Should return a randomly selected name from a list.
        • You may want to create helper functions or external list variables here, do whatever you think is needed.
Submit this in the 15_js section of the workshop

Work 14: Planet of the APIs

posted Nov 10, 2017, 6:49 AM by JonAlf Dyrland-Weaver

  • Research a REST API of your choice.
    • Make sure you can obtain a key (if required) without paying $
  • Create an entry for your api here
    •  Make a copy of the file "411 on API_NAME_HERE" in the same folder.
    • Modify your copy of the 411 file to provide information on your chosen API
  • Do not select an API that has already been written about.
  • Incorporate your new API into work 13

Work 13: Take a restful journey to the stars

posted Nov 9, 2017, 10:19 AM by JonAlf Dyrland-Weaver

  • Procure an API key from NASA Open APIs.
  • Write a simple Flask app,
    • whose sole route  renders a template, which  displays images procured via API call,  along with a bit of explanation of the image content.
    • (You need only 2 files to accomplish this.)
Store your work in the workshop under 13_rest, as lastF

Work 12: Help, I've been framed!

posted Nov 6, 2017, 10:14 AM by JonAlf Dyrland-Weaver

With your table buddy, look up either the bootstrap or foundation front-end framework (you will be assigned a framework in class).
  1. Research the framework.
  2. Create a single html page that demonstrates the key features of your framework. It should not be too complicated, you don't need to showcase every feature in the framework. 
  3. Upload your example (and any necessary framework files) to the workshop under 12_frmwk. Title your directory framework _teamName_lastaF-lastbF (i.e.) bs_team-awesome-dyrlandweaverJ-brownmykolykT

Work 12: Advanced Stuylin'

posted Nov 2, 2017, 8:50 AM by JonAlf Dyrland-Weaver

  1. Look at 4 different people's CSS work from the past 2 days. Learn from them, what worked? What didn't? What was jaw-droppingly gorgeous?
  2. Find 3 cool new CSS things/tricks/voodoo
    • Post your 3 cool things to forum.
  3. Write a new html/css combo that demos your 3 cool CSS things from above, as well as any other css you'd like to use. Make it purrrty!
    • When working on style, it's useful to have filler text, that's why you see the classic "lorem ipsum" latin text. Feel free to use lorem ipsum if you like, but you can find many lorem ipsum variants. Or perhaps you'd like to try out:
    • Also, if you want nice colors, check out:
  4. Add your html/css combo to the existing css directory in the workshop

Work 11: Stuylin'

posted Oct 31, 2017, 8:06 AM by JonAlf Dyrland-Weaver   [ updated Nov 1, 2017, 10:13 AM ]

In the workshop, under 11_css, you will find a sample html file, called style_me.html. Your mission is to create 2 different css files that can be applied to the sample html. 
  • The only modification you should make to the html file is to include a link to one of the style sheets in the <head> section.
  • Provide css styles for at least 5 different elements.
  • Use at least 5 different css properties.
Submit the html file and both css files in the css folder of the workshop.

  • provide styles for the div tag, as well as the class and id names found in the second file: style_me_classy.html

File under 11_css in the workshop, with your local submodule name in this format: lastF

Work 11: Are you Devo?

posted Oct 18, 2017, 10:03 AM by JonAlf Dyrland-Weaver

Your team of four has been contracted to design and implement a wiki. Your team advertises proficiency with Flask, Python, and SQLite.

Your “software solution,” to use the parlance of our times, will incorporate a few distinct components, so it is imperative that your team develop a design before taking any further steps.
  • A list of program components with role of each specified.
  • Explanation of how each component relates to the others.
    • Component map visualizing relationships between components.
  • Database Schema
  • Site map for front end
    • Represent each page you envision for your site.
    • Show linkages conveying user pathways for traversing site.
  • A breakdown of the different tasks required to complete this project
    • Include assignments of each task to each group member
  • Amalgamate these components into a single PDF

Work 10: Selecting Success

posted Oct 17, 2017, 10:05 AM by JonAlf Dyrland-Weaver

With your duo, write a Python script named that will access the database built in your last assignment to
  • Look up each student’s grades
  • Compute each student’s average
  • Display each student’s name, id, and average
  • Create a table of IDs and associated averages, named "peeps_avg" (thank team Sparkly Spectacular Sushi)
  • Facilitate updating a student's average
  • Facilitate adding rows to the courses table
To test the last 2 features, you should add lines to the end of courses.csv to reflect a new term's worth of course enrollment for your peeps (students).
File under 10_db in the workshop, with your local submodule name in this format: lastaF-lastbF

1-10 of 20