Week 16:

This is portfolio week. Having a chance to look back over the course of the project has let me see a few things. A lot of the time through this project, it didn't feel like I was accomplishing much, but looking back I can see that I completed several important parts of the project. A lot of the time, the work I was doing was not creating new parts and content on the website, but ensuring that all the websites parts worked together, by compiling the work done by others, and tracking down bugs they caused. I think I had a unique view on the project, as I was embedded in several different peoples parts of the project, aside from just my own, which gave me a unique perspective on how various parts of the project where progressing.
While I am fairly happy with how the project turned out in the end, I still think that our group could have improved the site in various ways.

Week 15:

We finished the website this week for submission, and got everything uploaded fine. We split the documentation into several parts, and every member of the group finished and submitted their chosen parts with plenty of time, bar one. Fortunately, we all picked up the slack for the one group member who let us down with his part, and got the documentation finished in time.

I did the implementation&use of data sets, and instructions for use parts of the documentation write up.

Week 14:

Most of the work this week has been on styling the website. Most of what I've been doing is changes to the CSS. Also, as the only member of the group with easy access to the UQ network, AND a working copy of filezilla (Phillip's antivirus software flags it for some reason), I've become the main path for uploading pages to the server after people finish working on them. Because of this, I've been doing my best to ensure that people don't accidentally overwrite changes others have made, something that I realised was important after a large portion of changes to CSS I made got accidentally wiped out (it was an easy fix, since I still had the original file). The sites coming along nicely now, I think. We've switched from a solid color background to a retro-looking image background, and we have several image buttons that Angus made. I've been doing a lot of bugfixing as well, tracking down problems where people have used the wrong capitilization, or used the wrong CSS ID because of an outdated version of the CSS file.

I've also expanded the code that sends the player character information from the character select screen to the battle screen to also include the enemy character information, since the character select page chooses a random enemy now, as well as loading all the characters for the player to choose.

Week 13:

We've gotten to the point where we have data to put into the webpage, so that's pretty good. There's nothing to complex going on at this point, but Angus gave me the javascript for loading character information, so I've got that being output onto the screen (Angus wrote the javascript to assign variables to stuff on the webpage, I just had to set up the CSS ID's for each value, and put it into the  character select page). I also had to write some code so that once a selection is made, the current page is changed to the battle page, and the selected characters information is sent along with it. I sent the character information along in the URL, since this was the easiest method, and the information isn't sensitive.

Code for sending character information:

(part of a larger function, runs when the player selects a character)

{
charinfo='';
charinfo=charname + ',' + charclass + ',' + charrank

}

Function that runs when the player confirms their choice:

       function battle(charclass) {
window.location = "battle.html?"+charinfo;
}

Code for recieving character information:

var query = window.location.search;

 if (query.substring(0, 1) == '?') {
query = query.substring(1);
 }

          var data = query.split(',');
charname=unescape(data[0])
clas=data[1]
rank=data[2]

Week 12:

Still not much I can do at this point. The javascript written by angus and phillip is fairly complex at this point, so there is not much I can do to help them without requiring them to waste time explaining what they've already done. I've been working on a layout for the battle page in the meantime, creating the 'player' and 'enemy' ID's in CSS, with the following code:

#player{
background-color: #a4d1ff;
padding-bottom: 40px;
margin-left: 1.7%;
padding-left: 5px;
padding-right: 5px;
text-align: center;
float: left;
width: 39%;
border-style: solid;
        border-width: 3px;
border-color: #074680;

}

#enemy {
background-color: #fca65b;
float: right;
padding-bottom: 40px;
padding-left: 5px;
padding-right: 5px;
width: 39%;
text-align: center;
border-style: solid;
        border-width: 3px;
border-color: #074680;

}

This produces a pair of lighter-coloured blocks side by side on the battle page. At the moment I have no content to put in them, but Angus says he is getting close to being able to return character data to but in these blocks, so thats good.

Battle page appearance:

Week 11:

This week not much happened. I messed with the websites CSS a little, but made no obvious changes. Mostly right now I am waiting for the Javascript to be in a state where it creates obvious outputs on the site that I can format to match the rest of the site. Most of my time in contacts is spent discussing the rules of the game, and suggestions for things we might change. I've also spent a little bit of time looking at trove, as I am becoming a little concerned that we may not have enough different famous people on trove to make this concept work well.

Week 9:

This week I have been  working on the layout for the website pages, trying to make an appealing layout that will be easy to add content into. I have created a 'Content' class in the CSS file, which I intend to use to hold the content for each page, so that all pages content should appear the same, regardless of which team member created it.

The layout that I have currently for the site is okay, I feel, but I also feel it could be improved. In particular the footer is giving me trouble, as it always sticks to the bottom of the page, and is a set height. This could cause problems on certain computers, and it limits how small the page can be re-sized to as the footer will cover other elements if allowed to.

This week we had some of the current java script code put into the website for a demo, although the java script does not currently affect  the appearance on page, it only outputs into the console. There weren't any troubles incorporating the java script into the web page, simply copy-pasting worked fine.

Picture of the web page as of this week: