CSC 101/IMM 120, Fall 2009

Assignment due: Friday, Dec. 4

Keep working on your portfolio. Bring questions to class on Friday. Be prepared to review what exactly needs to be in the portfolio.

Processing version of project 4 is due. Be prepared for a final code critique. The final report for this project should be part of your portfolio.

Assignment due: Tuesday, Dec. 1

Keep working on your final project and your portfolio. A version of your portfolio should be collected into a single folder that you bring to class via a USB drive, by emailing yourself a compressed file, or by whatever other means you can, such as organizing your work in a folder on the wiki.

Project 4 final demos are Friday, December 4, final reports should be included in your portfolio to be submitted during the final exam period.

The take home final will be distributed on December 4.

Assignment due: Tuesday, Nov. 24

Usability review of your Scratch prototype

Be prepared to show your portofolio web structure, even if you don't have everything connected, have the basic structure there.

Assignment due: Friday, Nov. 20

Be prepared to do a usability review of your Scratch prototype on Nov. 24

Your quiz was a take home quiz. Be prepared to continue to to flesh it out, adding all of your projects to your WebSites<Name> folder. See the quiz for details.

Assignment due: Tuesday, Nov. 17

Study for the HTML quiz. Read HTML tags, Fix a buggy tag, Go from an absolute to a relative address, Go from a relative address to an absolute address.

Develop a Scratch prototype for your final (4th) project.

Journal Assignment: What is the difference between absolute and relative addressing and why is this important? Is this just an HTML thing, or something inherently computery? Add to the wiki page.

Assignment due: Friday, Nov. 13

Project 3: Be prepared to demonstrate your 3rd project. You will need to partner with some one and each write a code critique your partner's project. You should also write a final report for your own project.

Project 4: You should have pitched a 4th project to Dr. Wolz on 11/10. Write a formal proposal for the project. This may be an extension of the 3rd project or a whole new project. This project should have interactivity in it via the mouse or keyboard. It should also load at least two kinds of files: images, sound, fonts, or text. Once again you will be asked to prototype your project in Scratch.

Portfolio As A Web Structure: Your project work to date has been posted on the wiki. To learn to create a website, and get some familiarity with a scripting language like HTML, you will submit a portfolio of your work as a web site. It is time to start getting your work organized for that. Go back through the assignments and identifyt the following:

Obviously this exercise gives you a good idea of what you are missing, and what you need to finish up before the semester ends.

Journal Assignment: Processing is considered a programming language. HTML is not. HTML is considered a scripting language. And there is some controversy as to whether Scratch is a bona fide programming language. But there is no controversy that it is not a scripting language. Enter into a discussion on the wiki regarding these statements.

 

Assignment due: Tuesday, Nov. 10

Work on the Processing version of your project which is due Nov. 13. EMAIL DR. WOLZ if you get stuck!

Based on the examples presented in class today, write a SHORT (tiny, tiny) project that incorporates mouse movement and keyboard input.

What makes an animation interactive? We studied examples of keyboard and mouse interaction. How do these contribute to engaging the user and making a story "interactive." Don't just voice your own opinions, go out onto the internet (yes, wikipedia) and research this. At a minimum, add (a) a link to a good article/animation/video on interactivity, (b) post your tiny (tiny) example of mouse/keyboard input, on the wiki page.

Clarification on project 3: It should NOT be interactive, but it may be.If you run into problems with collision detection, please wait until Tuesday when I will give you a little example of how to deal with it. Project 4 will REQUIRE you to include some interactivity. You may extend project 3, or start a new one.

Assignment due: Friday, Nov. 6

Your Scratch prototype of Project 3 is due on Friday for usability review.

Journaling assignment: Add to the discussion by posting a comment: Contrast Images and Typography: Explain how images and typography are the same and different both in terms of the way data is stored, and in the way images and type are displayed and manipulated on the screen.

Assignment due: Tuesday, Nov. 2

Create a very uncomplicated sketch using color. Experiment with either (1) HSB, (2) RGB, or HEXIDECIMAL. Post your solution on the wiki.

Develop your formal proposal for Project 3 and post it on your page on the wiki as you did with the others.

Study the tutorial on color at the Processing website. Using google, find a definition for additive and subtractive color.

Journaling assignment: A while ago, I realized that the collaboratives were not working. In order to make sure you are exposed to the important ideas, I will start to post two questions per week for the rest of the semester. Add to the discussion by posting a comment.

1) Explain the difference between additive and subtractive color. Why do we use additive color for digital graphics?

2) Explain how the hexidecimal representation of color works for both RGB and HSB color.

Assignment due: Friday, October 30

Review the "sound" examples listed in the class notes for 10/23:

Be prepared to explain how these examples and the way sound works falls within the DAHLIA model.

Time to pitch your next project. Be prepared on Friday to develop a proposal for your third project. This time you will "prototype it" in Scratch and then implement it in Processing as well. So pick carefully. You may start a fresh idea or extend your current project. Your project should mix two media: vector graphics (2D function calls), images, typography or sound. You are also welcome to dabble in 3D or explore one of the other libraries (e.g. video). Your project is not required to be interactive (e.g. use keyboard or mouse input).

Find the "color" tutorial on the Processing site and study it. We will review "color" on 10/30.

Assignment due: Tuesday, October 27

Study all of the typography examples by Tuesday when we will review them.

Take a look at the "Minim" reference page. You might also want to look at some of the example tutorials for minim.... can you find it? If not email Dr. Wolz

Your report for your first processing project is due today. Adapt the report template as appropriate. VERY IMPORTANT. Export your project so that it is an Applet folder rather than a Processing project. Upload this folder to the wiki as a "zip."

Assignment due: Friday, October 23

Study for the QUIZ. OMG there is a quiz on processing. Check out the list of things to frantically study

Processing project reports are due Oct. 27.

Complete the in code assignments for typography examples 1 - 4.

Assignment due: Tuesday, October 20

1) Final version due for code critique.

2) Five percent of your final grade is dependent upon a class resource page you put on the wiki on some topic relevant to the course. For example, Miles has already produced a tutorial on importing 3D images. Another one that is needed is how to write HTML on the Window/Vista platform using notepad. Please enter a suggestion for a useful resource you can create on the wiki page.

3) QUIZ (!!!!) on Processing. What do you think you need to know? We will build a list together in class on 10/20 for the Quiz on 10/23.

Assignment due: Friday, October 16

Usability reviews will take place 10/16. If you are struggling with your processing project please contact Dr. Wolz by email by 10/14. Office hours thursday afternoon, 10/15.

Please start the HTML tutorials. We will return to them on 10/16.

A good site for this is: http://www.htmlcodetutorial.com/
Please do the tutorials for basic HTML, CSS and Forms.

If you're just beginning, start learning HTML here.

Please also look at: CSS Forms

To practice (not required yet, but if you work better that way), you can write HTML in a text editor like textEdit on the Mac or notepad on the PC. Open your saved file with a browswer such as Firefox or Safari.

 

Assignment due: Friday, October 9

Work on your Processing project. Post your proposal on page linked from http://tcnjcsc101imm120.pbworks.com/ProcessingProjectRecord. Please place your project in YOUR project folder. Not sure how this works? Please get help from a classmate.

Assignment due: Tuesday, October 6

Looking at the wiki page on Scratch basics, be prepared to write a very small Scratch program on Tuesday that includes motion, control, events, broadcasting and yes, even variables.

Write a formal proposal for your first Processing project.

Assignment due: Friday, October 2

There will be an inclass, online quiz on Scratch on Tuesday, October 6. You will be asked to write a very simple program. To prepare, as a group, you are asked to list the concepts you think are essential to programming Scratch on the wiki. We will review this on 10/2.

We have been looking at loops and arrays in Processing. The zip file ImageAnimationPart1F09 takes you through some steps to do animation with images rather than with vector graphics. (We've been doing the latter). Work through the examples, starting with YellowFlower00 through 03, then go on to Barney and Mario. Your assignment is to change the images in Mario to your own images. You may draw them on line, scan paper drawings, or "rip' the images from the web. Post your work as a zip on the wiki.

Assignment due: Tuesday, September 29

Change the ClassyBox program to display a different drawing - a simple figure of SOMETHING other than a rectangle. (A face, a car, an alien space ship.) Hint: you should modify the Box class, not the main program to do this. THEN modify the main program to put up 100 of instances of your figure.

Assignment due: Friday, September 25

Continue work on your collaboratives (note that due dates have become flexible....)

Do the following Processing Tutorials:

http://processing.org/learning/2darray/

http://processing.org/learning/trig/

This week's theme is "learn what you don't know." The processing.org site has nice basic examples. Work through all of the examples for the following. On the wiki page for Processing concepts, please note any that you don't understand. This is not an exercise in how hard you work, but rather which examples make sense and which need some sort of human-to-human interaction.

Using the code you have studied this week, including "form" and "data", create a sketch of anything you want. Absolutely anything. Post it on the wiki.

Assignment due: Tuesday, September 22

Continue work on your collaboratives (note that due dates have become flexible....)

Do the second and third Processing Tutorials:

http://processing.org/learning/drawing/

http://processing.org/learning/color/

Go through the sample programs in the Animation Folder and do the exercise. you do not need to submit it, just do it!

Using the code we studied in class as a guide, create a sketch that explores either animation or leaving a trail. Concentrate on the code mechanics of variables and functions rather than the artistic complexity of your creation. If you particularly liked the static drawing you did last week, feel free to incorporate it into your sketch. To do this assignment please study each of the samples from this class and play with them until you understand what all the components do. Place your code as a zip file in your projects folder on the wiki, and link to it from the "Animation Examples" page.

Assignment due: Friday, September 18

Complete your code review for Scratch if necessary as well as your final report.

Continue work on your collaboratives (note that due dates have become flexible....)

Do the first Processing Tutorial: http://processing.org/learning/gettingstarted/

Read the "Environment" page as well: Open the Processing environment, on the Help pulldown menu select "Environment.

Write one very (very) small processing program from a blank page OR take one of the example programs and modify it in some small way. When you save your project, it will save as a "folder." Please compress the folder as a "zip" and upload the zip file to your projects folder on the wiki, and link it on the "first processing sampler" page.

Assignment due: Tuesday, September 15

Scratch project ready for code critique by peers. Have a "finished" version of your project ready.

Go to the Processing website and read about Processing. Download it if you like. Play around a litte.

Work on the Wiki collaborations 1 and 2 as needed.

Assignment due: Friday, September 11

Wiki Collaboration 1 FINAL version due.

Scratch project ready for usability review by peers. Not a fully working version! (see Dr. Wolz's office hours commencing Wed. 9/9.

Assignment due: Tuesday, September 8 (NO CLASS, tuesday is monday).

Please post a bare bones version of your Scratch project for review. This is in liu of holding class on Sept. 4.

Assignment due: Friday, September 4

Wiki Collaboration 1 DRAFT is due. Posted by the group on the wiki.

Scratch project proposal due posted on your Scratch page on the wiki.

Assignment due: Tuesday, September 1

Pick a block that doesn't seem to have an obvious action to you. Good candidates are "broadcast", "set instrument", "say". Write a small Scratch program that illustrates how a particular Scratch block works, but unlike the help page, that gives the barest of examples, REALLY use the block in something meaningful. Dr. Wolz has posted an example that starts with the "say" block.

Share it on the Scratch site and also link to it on the Wiki from your Scratch page. (See the class activities for August 28th.)

Get two of your friends and Dr. Wolz to comment on your programs on the Scratch site. Nag them if necessary.

Assignment due:    Friday, August 28

Write a very small, very uncomplicated program in Scratch and "share" it on the Scratch website.

Identify a project on the Scratch site that you found interesting. Download it, study the code and on the wiki page "Scratch Remixes" comment in three short paragraphs on (a) why you found it interesting, (b) what parts of the Scratch code you understand - explain how it works, (c) what part of the Scratch code you do not understand.