Program 5: Python

Here is your final coding assignment, due December 4th by end of day.

Goal:

You will be implementing a query interface for a database of World Series results using Python. Your code should read the search data from a form, retrieve the data from a mysql database and output the results of the search into an html formatted table. (Hint: You can use Python's CGI library for the form handling.)

We have provided the html source of a simple search form and the SQL code for creating the table in MySQL. The database table is structured as follows:
    Year (Primary Key)
    Winning Team
    Winning Manager
    League of Winning Team
    Games
    Losing Team
    Losing Manager

Resources:

• HTML form
• SQL script to load database into MySQL

Grading:

• 10% Good turnin
• form handling
• database connection
• correct output
   

Deliverables:

• Python source file(s)
• Readme with any references

Program 4: PHP

Here is your fourth coding assignment, due November 13 by end of day.

Goal:
You will be implementing form handling for the form you have been working on using PHP. The functionality we are looking for is similar to the 'review order' part of an online shopping checkout, allowing the user to check the information entered, and go back and edit as necessary. The form should work as follows:

• On clicking submit, load a summary page that displays the information that has been entered into the form. Use CSS to style this page appropriately; it does not have to match the form styling exactly, but the styling should give an impression of continuity from the previous page.
• The summary page should include an edit button (or link).
• On clicking 'edit', reload the original form *but* with the previously entered information retained in the form field. Clicking the 'submit' button again should bring you back to the summary page with the updated information.

Grading:

• 10% Good turnin
• 20% accurately collect data
• 30% summary page, w/ basic styling
• 10% edit option on summary page
• 30% defaults sets on edit

Deliverables:

• HTML and CSS files
• PHP source files

Program 3: Javascript

Here is your third coding assignment, due on October 23, by the end of the day.


Goal:
You will be adding several Javascript functions to the form you have been working on in the last two assignments. You may also choose to use JQuery where appropriate. Add the following functions to the form fields below:

• Temporary Category Field: Mouse over dialogue that says "See instructions at http://www.ncsu.edu/human_resources/hrim/TempEECat.php"
• Address Field: Use the Google Maps API to implement a autocomplete function for the address field
• Email Address Field: Validate that the entry is a correctly formatted email address
• Date Fields: Implement a Javascript/JQuery date picker for the two date fields

Constraints:
While working towards this goal, please:

• Do not significantly modify your content or styling
• You may improve your markup, especially as needed to meet the requirements for the Javascript you are implementing
• You may use Javascript or JQuery code you find online, but you must list your sources in your written report

Testing:
Test your page on various browsers ("crossbrowser testing") using Browserling, Browsera, BrowserStack or SauceLabs — or any equivalent tool. These tools make it easy to see how a page is rendered in different browsers without actually running those browsers. Test at least half of the following browsers:

• Firefox for Windows
• Firefox for OS X
• Chrome for Windows
• Chrome for OS X
• Chrome for Android
• Internet Explorer for Windows
• Safari for OS X
• Safari for iOS

Grading:
Marks will be assigned as follows:

• 10% Good turnin
• 15% Good style, including avoiding excessive mixing of js into html and css
• 25% Do cross browser testing and validation, report same 
• 50% Correct implementation, including:
• 10% category field
• 15% address autocomplete
• 10% email format validation
• 15% date pickers

Deliverables:
Using wolfware classic assignment "js_assignment", submit:

• one CSS file
• one matching HTML file
• your Javascript/JQuery source files
• a text file of at most 1-2 pages documenting your test results and any references/code sources you used.

Program 2: css due Oct 2

Here is your second coding assignment! It's due on Friday, Oct 2, by the end of the day.

Goal:

You will be adding style to the form you created for your first assignment. Your goal is to use CSS to recreate the layout of the original form. The layout does not have to match 100%, but should be a fairly close representation.

Constraints:

While working toward this goal, please:

• Do not significantly modify your content.
• You may improve your markup, especially to identify the elements you which to manipulate.
• Turn in exactly one CSS file, and one HTML file.
• As before, do not place any CSS styling or attributes in your html, beyond the link to your CSS file.
• Do not use any javascript.

Validation:

Validate your page using the W3C CSS Validation Service. Address as many of the resulting warnings and errors as you can.

Test your page on various browsers ("crossbrowser testing") using Browserling, Browsera, BrowserStack or SauceLabs — or any equivalent tool. These tools make it easy to see how a page is rendered in different browsers without actually running those browsers. Test at least half of the following browsers:

• Firefox for Windows
• Firefox for OS X
• Chrome for Windows
• Chrome for OS X
• Chrome for Android
• Internet Explorer for Windows
• Safari for OS X
• Safari for iOS

Grading:

Your goals for a good grade are to:

• 10% Good turnin
• 15% Good separation between semantic markup (html) and appearance (css) 
• 25% Avoid deprecated html and css
• 25% Do cross browser testing and validation, report same 
• 25% Good approximation of the appearance original form

Deliverables:

Using wolfware classic assignment "css_assignment", submit:

• one CSS file
• one matching html file
• a text file of at most 1-2 pages documenting how you corrected and improved your CSS and HTML.

Program 1: html, due Friday September 11

Hey folks,

Below is your first coding assignment! It's due by end of day Friday, September 11.

***

Goal:

• Create a form for employment authorization in HTML5 alone.

Constraints:

• Don't use any CSS, or any tags that control appearance (we'll do this later).
• Your page should be contained in one html file.
• Your content should be suitable for use in a classroom context.

Content:

• Create a online version of the employee section of this form. You need only include the fields on the first page that appear before the red dotted line. Add a submit button to the bottom of the form.
• Your page should use the CSC logo found here. Make sure you download the jpg and include the file in your submission.

Validation:

• Validate your page using the W3C Nu Markup Validation Service validator.w3.org/nu/. Address as many of the resulting warnings and errors as you can.
• Test your page on various browsers ("crossbrowser testing") using Browserling, Browsera, BrowserStack or SauceLabs — or any equivalent tool. These make it easy to see how a page is rendered in different browsers without actually running those browsers. Test at least half of the following browsers:
• Firefox for Windows
• Firefox for OS X
• Chrome for Windows
• Chrome for OS X
• Chrome for Android
• Internet Explorer for Windows
• Safari for OS X
• Safari for iOS

Deliverables:

• Using wolfware classic assignment "html_assignment", submit the following as a single zip file:
• Your version of the homepage HTML5 source.
• A text file of 1-2 pages documenting the results of your validation including any remaining errors and warnings, and your summary of the results of crossbrowser testing.
• (Optional) post your impressions of the crossbrowser testing tool you used to our forum for participation credit.

Grading:

• 10% proper turn in
• 10% proper content
• 20% using html5 only 
• 20% avoiding CSS and styling 
• 20% good validation
• 20% good cross browser testing

Announcement: SAS teams — post your preferences for design partners

SAS teams,

Please post your preferences for design partners, if any, in text files at our wolfware locker. Be sure to include:

• The members of your team 
• For each team that you wish to express a preference for:
• The members of their team 
• Your preference for them, from 1 (definitely not) to 5 (definitely yes)

Please do this even if you've already sent an email describing your preferences.

SAS teams have an extra week (until Monday 10th) to submit project plans.

Professor Watson

Assignment: project proposals due November 3

Folks,

Your project proposals are due Monday November 3, by the end of the day.

Submit them as text or doc files at the matching wolfware locker.

Professor Watson

Assignment: use CSS give your manifesto some emotion!

Here is your second coding assignment! It's due in a week and a half, on Monday, Sept 29, by the end of the day.

Goal:

You will be adding style to the marked up manifesto you turned in for your first programming assignment. Your goal is to use CSS to improve the appeal and understandability of that manifesto. In particular, strive to express the emotion expressed in your content.

Constraints:

While working toward this goal, please:

• Do not significantly modify your content.
• You may improve your markup, especially to identify the elements you which to manipulate.
• Turn in exactly one CSS file, and one HTML file.
• As before, do not place any CSS styling or attributes in your html, beyond the link to your CSS file.
• Do not use any javascript, unless you wish to request extra credit.

Validation:

Validate your page using the W3C CSS Validation Service. Address as many of the resulting warnings and errors as you can.

Test your page on various browsers ("crossbrowser testing") using Browserling, Browsera, BrowserStack or SauceLabs. These tools make it easy to see how a page is rendered in different browsers without actually running those browsers. Test at least half of the following browsers:

• Firefox for Windows
• Firefox for OS X
• Chrome for Windows
• Chrome for OS X
• Chrome for Android
• Internet Explorer for Windows
• Safari for OS X
• Safari for iOS

Grading:

Your goals for a good grade are to:

• 10% Good turnin
• 10% Good separation between semantic markup (html) and appearance (css) 
• 25% Avoid deprecated html and css
• 25% Do cross browser testing and validation, report same 
• 25% Improve the appearance and understandability of your content 
• 5% Express the emotion of your content 
• 10% (extra) Enter our CSS contest, in which we publish your homework on the web so that can your classmates can vote on the best manifesto. Winners will receive an additional 10% extra credit.

Deliverables:

Using wolfware classic assignment "prog2", submit:

• one CSS file
• one matching html file
• a text file of at most 1-2 pages documenting how you corrected and improved your CSS and HTML. At the top, please indicate whether you would like to enter your page in the contest.
• (Optional) post your impressions of the appearance of your homepage with provided CSS file to our forum for extra credit.

Assignment: html markup of an online manifesto

Hey folks,

Below is your first coding assignment! It's due by end of day Monday, September 15.

***

Goal:

• Create a page describing an online manifesto in HTML5 alone.

Constraints:

• Don't use any CSS, or any tags that control appearance (we'll do this later).
• Your page should be contained in one html file.
• Your content should be suitable for use in a classroom context.

Content:

• We suggest that you use the Cluetrain Manifesto (wikipedia), but you are free to use any classroom appropriate manifesto you like.
• Many manifestos are too long for this assignment. Feel free to edit or summarize as you like to make this manageable, but ensure you fill at least one desktop screen.

Validation:

• Validate your page using the W3C Nu Markup Validation Service validator.w3.org/nu/. Address as many of the resulting warnings and errors as you can.
• Test your page on various browsers ("crossbrowser testing") using Browserling, Browsera, BrowserStack or SauceLabs — or any equivalent tool. These make it easy to see how a page is rendered in different browsers without actually running those browsers. Test at least half of the following browsers:
• Firefox for Windows
• Firefox for OS X
• Chrome for Windows
• Chrome for OS X
• Chrome for Android
• Internet Explorer for Windows
• Safari for OS X
• Safari for iOS

Deliverables:

• Using wolfware classic assignment "prog 1", submit the following as a single zip file by end of day Monday September 15:
• Your version of the homepage HTML5 source.
• A text file of 1-2 pages documenting the results of your validation including any remaining errors and warnings, and your summary of the results of crossbrowser testing.
• (Optional) post your impressions of the crossbrowser testing tool you used to our forum for extra credit.

Grading:

• 10% proper turn in
• 10% proper content
• 20% using html5 only 
• 20% avoiding CSS and styling 
• 20% good validation
• 20% good cross browser testing

Assignment: an example web app

Hey folks,

During and after your first html assignment, you should be working on finding and posting an example web app. Details here!

The assignment is due by end of day September 3.

The assignment asks you to turn in using our Google Community.

Prof. Watson

Reactions: for Wednesday, and in general

Folks,

For Wednesday, please view several of the historical videos in our list, and react to at least two of them online at our class forum, before class. Use the hashtag #html. You can find details on good reactions at our class site.

In general, we will not be reminding you each week about reactions, so please monitor the class calendar and if you see shorts or a viewing list for a topic please go ahead and view and react to these before class. You need only post one reaction per day we spend on a topic. If instead of shorts we lecture in class on a topic, please react after lecture. You aren't required to react to today's lecture.

Professor Watson

Assignment (updated): give us your online IDs

(updated: added subject line)

Hey folks,

Assuming you consent on the previous assignment, we need to collect your IDs for those tools. In particular, we need you to create a Google profile so that we can add you to our online community, and we need your GitHub ID so we can give you access to your public project repo.

Please use this form to give us your IDs by end of day Monday, August 25.

Professor Watson

Assignment (updated): your consent for use of online tools

(updated: with due date)

Hi folks,

Your first assignment! An easy one. Please complete this by end of day Monday 25th.

Please view this online consent form, and indicate whether or not you consent to use of online tools. Please email us as well if you choose not to consent.

Remember that your grades will only be returned to you through WolfWare classic, no other forum or tool.

Professor Watson

Assignment: those review and quiz questions mentioned Wednesday

Folks,

Those review and quiz questions I mentioned Wednesday are ready. You can find them on the notes page under the javascript and jquery topics.

Recall that review questions are marked only for participation (any answer is acceptable). Please feel free to collaborate with fellow students on these questions.

Quiz questions are graded, but because of the limited time remaining, we will drop the lowest of your two scores on these new questions. In sum then, you need only answer two of the four quiz questions from this semester for full quiz marks.

Announcement: Grading rubric for css assignment

Here it is! 

Your goals for a good grade are to: 

• turn in the assignment components as and where needed. Ju Hee can help with this, but not with remaining points. 

• do cross browser testing and validation, report same 

• maintain a good separation between semantic markup (html) and appearance (css)

• meaningfully improve the appearance and understandability of your content (wide range here) 

• avoid any deprecated css or html 

from Web Class @ NCSU http://ift.tt/1dnEX4c
via IFTTT

Assignment: indicate your project preferences

Hi folks,

As we discussed in class today, your projects descriptions are out! You can view them on our course's project page.

We will place you in teams and match you to your projects by class Wednesday. To help us match you with projects and team members you would like, as well as ensure that teams are well balanced and a good match with project needs, please fill out this project matching form by end of day Tuesday.

Professor Watson

Announcement: we've updated the assignment to posting to clarify logisitics

Have a look at the new version to clarify things.

Assignment 2: add some style with CSS! (updated)

(updated: logistical correction)

Here is your second coding assignment!

Mechanics:

This assignment has two parts. The first is due in one week, by end of day Wednesday, March 26. The second is due a week later, by end of day Wednesday, April 4.

As you know, with your consent we are performing an experiment with this assignment, so its mechanics are a bit unusual. You will be adding style to two html files: your own page, and someone else's page. You will be adding style two times to each file:

• In one part of the assignment: you will create CSS from scratch for your own page, while with the other page, you create CSS with the help of starting CSS output from our experimental tool. 
• In the other part: you will swap the pairing, meaning you will create CSS starting from our tool's output for your own page, while you will create CSS from scratch for the other page.

The order in which you perform these parts is being varied for experimental reasons.

My student (Juhee Bae) will shortly send each of you an email describing your randomly selected order, and a link to the experimental CSS output you need. On March 27, you will receive a link to the experimental output you need for the second part of the assignment.

Goal:

Use CSS file to improve the appeal and understandability of html content.

Constraints:

When working with experimental CSS output:

• Work with the improved html files that we provide you. (We sometimes improved semantic markup to enable better experimental CSS output.)
• Do not significantly modify your html content.
• Do not share the experimental CSS output with others. 
• The output includes five different CSS style sheets. Choose one to work with, and improve it to reach your goals.

In any case:

• Ensure your content is suitable for a classroom
• Turn in exactly two CSS files for each part of the assignment, one for each html file.
• As before, do not place any CSS styling or attributes in your html – remember, you won't be turning it in.

Validation:

Validate your page using the W3C CSS Validation Service. Address as many of the resulting warnings and errors as you can.

Test your page on various browsers ("crossbrowser testing") using Browserling, Browsera, BrowserStack or SauceLabs. These tools make it easy to see how a page is rendered in different browsers without actually running those browsers. Test at least half of the following browsers:

• Firefox for Windows
• Firefox for OS X
• Chrome for Windows
• Chrome for OS X
• Chrome for Android
• Internet Explorer for Windows
• Safari for OS X
• Safari for iOS

Deliverables:

Using wolfware classic assignment "css", for each part of the assignment, submit:

• two CSS files
• two matching html files
• a text file of 1-2 pages documenting why you modified any CSS you received
• (Optional) post your impressions of the appearance of your homepage with provided CSS file to our forum for extra credit.

Announcement: extension -- assignment 1 is now due Wednesday February 5

Due to last week's snow day, our first assignment is now due Wednesday February 5.

Assignment (due February 3): Create a home page in html5

Hey folks,

Below is your first coding assignment! It's due by end of day Monday, February 3.

***

Goal:

• Create a short home page for yourself in HTML5 alone.

Constraints:

• Don't use any CSS, or any tags that control appearance (we'll do this later).
• Your page should be contained in one html file.
• Your content should be suitable for use in a classroom context.

Validation:

• Validate your page using the W3C Nu Markup Validation Service validator.w3.org/nu/. Address as many of the resulting warnings and errors as you can.
• Test your page on various browsers ("crossbrowser testing") using Browserling, Browsera, BrowserStack or SauceLabs. These tools make it easy to see how a page is rendered in different browsers without actually running those browsers. Test at least half of the following browsers:
• Firefox for Windows
• Firefox for OS X
• Chrome for Windows
• Chrome for OS X
• Chrome for Android
• Internet Explorer for Windows
• Safari for OS X
• Safari for iOS

Deliverables:

• Using wolfware classic assignment "html", submit the following as a single zip file by end of day Monday February 3:
• Your version of the homepage HTML5 source.
• A text file of 1-2 pages documenting the results of your validation including any remaining errors and warnings, and your summary of the results of crossbrowser testing.
• (Optional) post your impressions of the crossbrowser testing tool you used to our forum for extra credit.