mock up

Mock up

Early mockup, testing Colours from Kuler (Adobe)
#1A1F2B #30395C #4A6491 #85A5CC #D0E4F2



PLEASE ADD TO POOL (I cant edit your posts m8 ^^)




ANTI its up too you! Different styles will help us more - CHRIS

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Mock up

Hi guys I have a question. Can I change the style or I should follow the same that Craig have done?

A consideration of Copy Right issues

A consideration of Copy Right issues in relation to Cloud Fish.

Images -
Fonts used -



Images
Any images we might use will be Creative Commons based.
http://creativecommons.org/licenses
This means in short that as long as we abide by the authors request (this maybe just to reference them somehow in the content) we can use the content created by them, tweek and even use the images for commercial use.

Fonts
A font will come with its own set of licensing rules. With the onset of HTML5, custom embedded fonts leaves developers open to copyright infringement in reference to the fonts they use.
A font by legal definition is regarded to be the same as software and hence taken very seriously. That is why we will be using free font websites.
http://www.fontsquirrel.com is a site that provides free commercial and non-commercial fonts with no strings attached.


"Look & feel"
A relatively new consideration, thanks to major lawsuit cases such as Apple suing Microsoft over the "look and feel" of Windows new operating system. This also transfers over to web pages.

We can safely sat that Cloud Fish is unique and isn't copying layout/colour schemes of other websites.

mockup

session_start();

I have managed to manage secure access to the cloudfish site once logged in by using php sessions which redirect to the loggin page once a session has finished. I have done this by giving the session a value to that of the $_post['user_name'] and then checking for it at the top of every page.

Once the session has been ended on logout users are automatically redirected to the splash page.

Logout script:

unset($_SESSION['user_name']));
session_destroy();

Secure file upload checklist

Whilst researching the file upload script that will be used to add avatar photographs to the contact book I found this piece which I'm sure will prove useful. This is a checklist of different measures to help prevent unwanted files being sent to the server maliciously or by accident.

http://hungred.com/useful-information/secure-file-upload-check-list-php/

Important information for transferring info to db

Whilst researching the login section of the splash page and checking credentials against those in the database I found important information about mysql_real_escape_string function that protects information when it is transferred to the database. This is particularly important for data such as usernames and passwords.

Details:

http://us.php.net/mysql_real_escape_string

Database and Website maps (Group Pool)

Website Maps

Initial idea

 

Deadlines & Brief

Overview
You are to specify, build and evaluate a small/medium sized application to run across the internet. The actual site you build is entirely your choice, so long as it is able to address the criteria appropriately, and guidance and feedback regarding your proposed ideas will be given during workshop sessions between weeks 3 and 7.

Element 2S: Specification of the proposed system worth 25% due week 7: Your specification should be sufficiently detailed to enable a prospective user or purchaser to select the application and for another programmer to be able implement the application. Include the following elements:

Concept and context - 20%
Site layout and design - 20%
Backend design - 40%
Advanced issues - 20%

The following elements are likely to form a significant part of a complete specification:

• A strong concept. 
• Evidence of research both technical and contextual. 
• Evidence of consideration of alternative solutions. 
• Evidence of consideration of feasibility. 
• A complete site map. 
• Two example input page mockups, two example output page mockups. 
• Data specification (usually ER and EA diagrams). 
• Specification of dynamic pages (inputs, purpose, validation). 
• Consideration of development language and tools. 
• Consideration of broad security issues. 
• Consideration of copyright issues. 

Element 2A: Demonstration of the finished application worth 50% due week 14:

A functional prototype of your application is to be published live on an Internet server.

If any parts of the system are password protected you must clearly give the necessary password details in a file passwords.txt submitted via the Online File Submission. Keep a backup copy of your work (which works on Localhost).

Demonstration of application:

• You are required to demonstrate your completed application in week 14. 
• A schedule of demonstration times will be posted under Submission Details below. 
• The demonstration is an integral part of the assessment process. 
• Failure to demonstrate your application will result in a maximum mark of 49% 
• The purpose of the demonstration is to: 
• provide confirmation that the application is your own work 
• allow you to respond to comments or questions about your work from the assessor 
• explain any points about your work not otherwise covered 

You will be required to explain your work both in terms of a user's perspective and from a technical perspective.