CS 242 Spring 2012 : Assignment 2.1

This page last changed on Mar 05, 2012 by cemeyer2.

Assignment 2.1 – Adding Structure and Style to Your Portfolio


Code Complete Chapters 3 and 4

The reading is due before lecture on Monday, March 12th


Regular Expressions

The tutorial is due before lecture on Monday, March 12th

Final Project Proposal

First, take a read through the Final Project Details page for information about what the final project is like. By Monday, March 12th 2012 at 4PM CST we expect you to email your moderator your initial project plan as a PDF document.

For the last 4 weeks of the semester, each of you will complete your own final project. The project can cover any domain using any language, toolkit, or framework, but you cannot have your final project for this course be part of a project or assignment for another course you are currently taking. Before you can begin your final project, you must first write up a plan and submit it to your section leader for approval. The plan must contain:

  • Summary of application including functionality, language used, libraries needed, platforms targeted, etc
  • Why you chose this application (i.e. to learn something, to solve a problem…)
  • Who will use this application when it is completed
  • List of features

Expect your plan to be at least a full page in length. Your TA or moderator might ask you to revise your plan after submitting it if he thinks that you are trying to do to much or too little. Lastly, please submit your proposals in PDF format to eliminate chances of any problems when trying to read them. Once your moderator approves your plan, you will have to formalize the proposal for the following week. Details on what is expected in the formal proposal will be posted with the next assignment.

Studio Assignment

This assignment is due at before the start of your discussion section on March 15th and 16th in SVN in a folder named Assignment2.1.

Last week, we turned our two input XML files into one nicer output XML file. This week, you will be employing 2 new technologies to give your portfolio some graphical structure and style. Namely, this week you will be using XSL and CSS to transform your output from last week into something that looks pleasant this week. The XSL will transform your XML into an HTML file with structure that can be displayed in a web browser. You will then use CSS to add some style to the transformed HTML output to give style to your portfolio. Continuing from last week, feel free to develop and test your code anywhere you wish, but you must deploy your final code to the cPanel server for ease of grading.

Getting Started

Before you begin on this part of the assignment, we encourage you to work through the following tutorials to familiarize yourself with XSLT and CSS:

Functional Requirements

There are a few things that you need to include on your output this week. Namely, you should in some way include all of the information that was part of the requirements for the output from last week.

  • The title of each of your projects
  • The date for each project
  • The version for each project
  • The summary for each project (the most recent commit message for that assignment)
  • A listing of each file in the project with
    • Its size
    • The doctype of the file: is one of code, test, image, documentation, resource, etc (feel free to add as many doctypes as you wish).
    • The path is the path to your files in SVN.
    • The file itself loaded in an iframe only on demand
    • Each version of each file in the project
      • The number is the revision number for that commit
      • The author is the netid of the committer
      • the info is the commit message for that revision
      • The date is the date of that commit

Using XSLT

We realize that you can use a variety of methods to apply your XSL document to transform the XML you generated last week, but we prefer that you use PHP where possible. This allows a nice clean output that will work nicely with next week’s code. Assuming you made a DOMDocument object last week to generate your output, transforming it with your XSL is relatively simple:

Using CSS

Once you have some HTML output, you need to style it with CSS. You can include the link to your stylesheet as part of the XSL template document you write to do the transform. Anything not in XSL tags is just echoed out as HTML output after it has been transformed. So you can use CSS includes, JavaScript, etc just as normal. We understand that not everyone out there has extensive CSS knowledge or design skills, so we are just looking for you to do something that looks “nice”. As long as you put a good effort into adding some color and style into your portfolio, you will get full credit for this part of the assignment.


Criteria Weight Comment
Basic preparation 3  
Cleverness 3  
Code submission 6 submitted on time and to the correct location
Decomposition 6  
Documentation 3  
Naming 3  
Overall design 6  
Participation 6 How you critique others code.
Presentation 6 How you critique your code.
Requirements – XSLT 15  
Requirements – CSS 9  
Document generated by Confluence on Mar 29, 2012 02:55

  1. No comments yet.

  1. No trackbacks yet.