D4DME – Support

As mentioned previously, the key part to this unit is that we understand the website code as a team as opposed to each of us having our own specialism within the work. Chace had expressed multiple times that he wasn’t very comfortable with PHP and that he didn’t really understand it. For this reason, I offered to meet up with him and go through all of the PHP that we had so far and explain how it all worked.

I also went through the code by myself and made sure that everything was commented in detail so that everything makes sense.

Advertisements

D4DME – Team Update

After several more meetings with my team, we decided that it was time for one of the others to work on the PHP. We decided that Kyle would be in charge of coding the ‘log in’ and ‘session’ which included a message function to be displayed across multiple pages.

This gave me a break from PHP and allowed me to update the group wiki. Meanwhile, Chace kept working on the CSS for the website.

D4DME – Trial and Error

After having a discussion over Chace’s mock-up for the webpage, I created a page on our wiki to document our discussions (Here). The page consists of screenshots accompanied by an ongoing conversation that we had over Facebook. Whilst the Wiki is good to document our planning and teamwork, it doesn’t provide us with a real-time chatting option that we need to keep in touch when we’re not talking face-to-face. Facebook probably isn’t the best choice and isn’t very professional, though everyone is using it and it makes it easy to keep in touch outside of uni.

D4DME – The Wiki

To make it easier for us to keep our group work clearly distinguishable from our blog work, I suggested that we create a DocuWiki page on one of our servers. I was happy to set it up on mine, as I have 24/7 hours access to the servers (one of the many perks of living on campus).

13

Screenshot of Our DokuWiki

In hindsight, I realised that having a full Media Wiki was more than what w actually needed it for, so I decided to remove it from my server space and replace it with a much simpler version.

We decided as a team that the DocuWiki will be used to host any information that we think of during our weekly team meetings (such as the one we had today) so that we can look back over our planning and have a constant record of what we need to do to progress our project.

Our DocuWiki can be found Here

D4DME – Meet the Team (Part Two)

Today was our first group meeting as a team. One of the things that we decided to cover was further changes to our ‘Meet the Team’ page. Chace and Kyle suggested a few things that we could add to make the pages look a bit more efficient (aside from content).

Untitled

Screenshot

We asked Rob if he could take a couple of photos of us working together as a group to go in our ‘Group Photos’ section.

Untitled1

Screenshot

On our ‘About Us’ page I created some similar buttons to the navigation that linked externally to our individual blogs.

Untitled2

Screenshot

All that is left to do is add our individual bios to the ‘About Us’ page and possibly some more group photos. Aside from that, our ‘Meet the Team’ page is mostly finished.

D4DME – Meet the Team (Part One)

Today I was introduced to my team mates, Mongkol (Chace) and Kyle. The first task that we have been given in our new groups is to create a ‘Meet the Team’ page.  Chace decided to start work on the design of the page(s) with HTML/CSS. The page initially looked like this:

Untitled

Screenshot

To get used to the collaborative side of this project, I asked Chase to send me his project files so that I could have a look at his code and make some additions. We identified that it would be a good idea to comment our coding so that we don’t get confused by each other’s work. I suggested that we preface each comment with an initial so that we know who has said what, e.g. /* V: verity made this comment */, <!– V: verity has made this comment –>

Chace had initially created three separate stylesheets for the three pages (Home, About, Contact). To make the coding process easier for everyone in the group, I decided to refine this down to one stylesheet that applied to all of the pages. Whilst it was a nice idea to have different coloured headers on each page, it would make it more time consuming to make changes to all three of the stylesheets, so I suggested that we compile them into one. After this I made a few changes to the HTML to make editing easier in the long run.
One of these was to move the navigation to a separate file and link it in using PHP at the top of each page.

Untitled1

Screenshot

This means that we can make a change to one of the links without having to change it on each individual page.
Aside from this, I had a look at Chace’s CSS and made some additions such as pseudo animations (by using generated code from http://matthewlein.com/ceaser/) and using the drop shadow effects that Chace had made on the main divs.

To save us some time in the long run, I added a few extra lines of CSS to make the website dynamic and scaleable with the browser. This made it so that the content of the page would adapt to fit the size of the window and wouldn’t cut anything out from view when scaled.

The final result of my additions ended up looking like this:

1

Screenshot

2

Screenshot

We agreed that it would be a good idea to wait until Wednesday, when we could all meet up, to add content to the page.

Alphabet Photography (Part Three)

Having completed the Alphabet Photograph task, I am aware of certain things that might have turned out better if they had been conducted differently. The first of these is that Tina and I used different cameras to take our photographs which resulted in different sized photographs at different resolutions. Whilst this is not a major problem in terms of appearance, it was certainly time consuming when it came to re-sizing the files to suite the others. (There was also an issue with portrait/landscape photos, though only a minute amount were landscape so it wasn’t too much of an issue to re-size them).

Although I think that the theme of our alphabet was interesting, it might have been easier to find nicer letters if we hadn’t limited ourselves to purely household items. Regardless of this, I still think that we compiled a good set of letters.

On the whole, however, I think that Tina and I did a good job with this task and that the majority of our letters are very clear as to what they are.