Saturday, 8 May 2010

Reflection on the errors and Troubleshooting

During the process of creating the website: http://studentnet.kingston.ac.uk/k0833787/
I came across few technological problems. Firstly, I struggled to resize the window of the web size to fit the screen nicely but eventually I used the CSS code and typed:
body onLoad= “window.resize To (655,450)” in order to have the best size of the site. Because I am typing this on my blog I cannot insert < > before and after "body" otherwise I'll get an error but those symbols < > have to be typed too.

When the website was finished and I tried to upload it onto the student server and somehow following all the steps from the module guide I lost the connection with the images and I had to locate the source for all of them. Instead of the longer option of clicking and directing the source for each picture I opened the code panel and removed the word “website” which appeared in front of the names of my images. That way I saved a lot f time and eventually I had my site back to normal. To prevent further errors I backed-up my work on a second USB stick so I could try and upload the site to the server again.

In order not to plagiarize I had to reference all images that were downloaded and used on my site. Because I hadn’t saved the links previously I had to find the best way of finding the sources of those images. I located the image, right-clicked on it and selected the “get info” option. On there I could see where the image came from and I just re-typed the website name and saved for later referencing. I was very glad that I knew about this option, otherwise I would not remembered all the websites I visited and in the end I would have used images that are not referenced. To back myself up I also put links of all the sites I used to help me to create my website. That includes the visual images as well as the audio. That way I am giving a visible credit to these websites (www.flashkit.com, www.net-a-porter.com, www.look.co.uk) and will not get in trouble for plagiarizing my work.

No comments: