Introduction to the Internet and Web Page Design

Total Page:16

File Type:pdf, Size:1020Kb

Introduction to the Internet and Web Page Design INTRODUCTION TO THE INTERNET AND WEB PAGE DESIGN A Project Presented to the Faculty of the Communication Department at Southern Utah University In Partial Fulfillment of the Requirements for the Degree Master of Arts in Professional Communication By Lance Douglas Jackson Dr. Jon Smith, Project Supervisor April 2009 APPROVAL PAGE The undersigned, appointed by the dean of the College of Humanities and Social Science at Southern Utah University, have examined the project en- titled: INTRODUCTION TO THE INTERNET AND WEB PAGE DESIGN Submitted by Lance Douglas Jackson, A candidate for the degree of Master of Art in Professional Communication, and hereby certify that, in their opinion, it is worthy of acceptance. _________________________________________ Professor Jon Smith _________________________________________ Professor Arthur Challis ________________________________________ Professor Lionel Grady ________________________________________ Mr. Mark Walton ________________________________________ Professor Suzanne Larson Graduate Director DIGITIZATION PERMISSION FORM I, Lance D. Jackson, give permission to the Southern Utah University Library to digitize and archive my capstone project entitled Introduction to the Internet and Web Page De- sign, submitted for the Master of Arts degree in Professional Communication. ______________________________ _______________________ Lance D. Jackson Date ACKNOWLEDGEMENTS I wish to acknowledge the following individuals for their help, Support and encouragement in the completion of this project and the requirements of the Master’s Degree: Dr. Jon Smith, chair of my committee for his guidance support and encourage- ment and for inspiring me to think out of the box. Because of his guidance, I have begun to aspire to greater heights than I had previously though possible. Committee members Dr. Arthur Challis and Lionel Grady for their friendship and support. Dr. Suzanne Larson, Graduate Director, for always believing in me and being sup- portive and for her guidance and advice. I acknowledge the help and support of the graduate faculty of the SUU Commu- nication Department. Dr. L. Paul Husselbee has been an great inspiration to strive for the best technically correct workmanship. His courses have been demanding, yet fair and have helped me to see the importance of being thorough in research design and execution. I especially acknowledge and thank Mr. Mark Walton, Director of Web Services at Southern Utah University and member of my committee and my wife, Deborah K. Jackson. Mr. Walton has provided much in the way of content editing and suggestions. His expertise and suggestions have not only been appreciated but have also improved the quality and usefulness of the project. Debbie has been supportive from the begin- ning, without her support, this project would not have been possible. ii TABLE OF CONTENTS TITLE PAGE . i ACKNOWLEDGEMENTS. ii LIST OF FIGURES . iv LIST OF TABLES. ix EXPLANATION OF TERMINOLOGY/ABBREVIATIONS . x ABSTRACT . xi COPYRIGHT STATEMENT . xii Chapter 1. THE INTERNET AND THE WORLD-WIDE WEB . 1 2. PLANNING FOR WEB DESIGN. 15 3. TECHNICAL CONSIDERATIONS . 35 4. IMAGE EDITING AND PREPARATION . 51 5. BACKGROUNDS, TEXTURES AND ICONS . 71 6. ANIMATION WITH PHOTOSHOP. 87 7. HTML, XHTML AND STYLE SHEETS . 105 8. WEB DESIGN WITH PHOTOSHOP . 137 9. ADOBE DREAMWEAVER . 157 REFERENCES . 14, 33, 49, 69, 85, 104, 135,155, 174 VITA. 176 APPENDIX . 178 iii LIST OF FIGURES Chapter 1 1.1 Simple Network . 2 1.2 Peer-to-Peer Network . 3 1.3 Client Server Network . 4 1.4 Internet Access to a Network . 5 1.5 Monitor Pixels . 11 Chapter 2 2.1 Kress & Van Leeuewen Model . 20 2.2 Open/Cluttered designs . 21 2.3 Icon/Index/Symbol . 22 2.4 Layout Models . 25 2.5 Rough Drawing . 27 2.6 Flow Chart . 28 Chapter 3 3.1 Web Server . 36 3.2 Web Server ISP . 36 3.3 SUU Computer Network . 37 3.4 F: Drive Content . 38 3.5 My Computer Icon . 39 3.6 Content of My Computer . 39 3.7 Content of F: Drive . 39 3.8 Creating a New Folder . 39 3.9 Renaming a Folder . 40 3.10 public_html Folder . 40 3.11 Example of Files Names . 41 3.12 HTML Sample . 41 3.13 Web Folder Example . 42 Chapter 4 4.1 Minimal JPEG Compression . 53 4.2 Medium JPEG Compression . 53 4.3 Large JPEG Compression . 53 4.4 GIF Image Example . 54 4.5 Animated GIF Example . 54 4.6 Solid Background GIF Images . 54 4.7 After Touch-up Photo . 58 4.8 Before Touch-up Photo . 58 4.9 JPEG Options Menu . 59 4.10 Image Size Menu . 59 iv List of Figures Continued 4.11 Crop Tool . 60 4.12 Crop on Photo . 60 4.13 Cropped Image . 61 4.14 Color Picker Menu . 61 4.15 Setting Point of Origin for Clone Stamp . 62 4.16 Using the Clone Stamp Tool . 62 4.17 Histogram Pallet . 63 4.18 Levels Menu . 63 4.19 Unsharp Mask Filter . 64 4.20 Save for Web and Devices Menu . 64 4.21 Optimizing for Web Example . 66 4.22 Optimizing for Web Example 2 . 66 4.23 Save Optimized As menu . 67 Chapter 5 5.1 High Resolution Monitor . ..
Recommended publications
  • On the Incoherencies in Web Browser Access Control Policies
    On the Incoherencies in Web Browser Access Control Policies Kapil Singh∗, Alexander Moshchuk†, Helen J. Wang† and Wenke Lee∗ ∗Georgia Institute of Technology, Atlanta, GA Email: {ksingh, wenke}@cc.gatech.edu †Microsoft Research, Redmond, WA Email: {alexmos, helenw}@microsoft.com Abstract—Web browsers’ access control policies have evolved Inconsistent principal labeling. Today’s browsers do piecemeal in an ad-hoc fashion with the introduction of new not have the same principal definition for all browser re- browser features. This has resulted in numerous incoherencies. sources (which include the Document Object Model (DOM), In this paper, we analyze three major access control flaws in today’s browsers: (1) principal labeling is different for different network, cookies, other persistent state, and display). For resources, raising problems when resources interplay, (2) run- example, for the DOM (memory) resource, a principal is time changes to principal identities are handled inconsistently, labeled by the origin defined in the same origin policy and (3) browsers mismanage resources belonging to the user (SOP) in the form of <protocol, domain, port> [4]; but principal. We show that such mishandling of principals leads for the cookie resource, a principal is labeled by <domain, to many access control incoherencies, presenting hurdles for > web developers to construct secure web applications. path . Different principal definitions for two resources are A unique contribution of this paper is to identify the com- benign as long as the two resources do not interplay with patibility cost of removing these unsafe browser features. To do each other. However, when they do, incoherencies arise. For this, we have built WebAnalyzer, a crawler-based framework example, when cookies became accessible through DOM’s for measuring real-world usage of browser features, and used “document” object, DOM’s access control policy, namely the it to study the top 100,000 popular web sites ranked by Alexa.
    [Show full text]
  • Cross-Domain Embedding for Vaadin Applications
    Cross-Domain Embedding for Vaadin Applications Janne Lautamäki and Tommi Mikkonen Department of Software Systems, Tampere University of Technology, Korkeakoulunkatu 1, FI-33720 Tampere, Finland {janne.lautamaki,tommi.mikkonen}@tut.fi Abstract. Although the design goals of the browser were originally not at running applications or at displaying a number of small widgets on a single web page, today many web pages considerably benefit from being able to host small embedded applications as components. While the web is full such applications, they cannot be easily reused because of the same origin policy restrictions that were introduced to protect web content from potentially malicious use. In this paper, we describe a generic design for cross domain embedding of web applications in a fashion that enables loading of applications from different domains as well as communication between the client and server. As the proof- of-concept implementation environment, we use web development framework Vaadin, a Google Web Toolkit based system that uses Java for application development. Keywords: Vaadin, JSONP, cross-domain applications. 1 Introduction Web applications – systems that resemble desktop applications in their behavior but are run inside the browser – are becoming increasingly common. The current trend is that web pages have dynamic components side by side with the traditional web content, such as static text and images. These dynamic components can be small widgets that for instance display current weather information or stock exchange data, or even full-fledged web applications that offer a service related to the theme of the web page where they are located [1]. Creating dynamic web pages is much more complex than building plain old web pages.
    [Show full text]
  • Chapter 1 Web Basics and Overview
    Chapter 1 Web Basics and Overview The Web is an Internet-based distributed information system. Anyone with a computer connected to the Internet can easily retrieve information by giving a Web address or by simply clicking a mouse button. The Web is a great way to disseminate information and making it available 24/7. Information can also be collected from Web users and customers through online forms. Maintainers and administrators can control and update Web content from anywhere on the Web. All these make the Web a powerful tool for mass communication, e-business and e-commerce. Compared with TV, radio, news papers, and magazines, putting the word out on the Web is relatively simple and inexpensive. But a website is much more than such one-way communication media. It can be a virtual o±ce or store that is always open and supported by workers from anywhere. Web service companies o®er free Web space and tools to generate simple personal or even business Web pages. But, well-designed and professionally implemented websites are much more involved. Even then, expertly produced websites are still much more cost-e®ective than other means of mass communication. For business and commerce, the cost of a website is negligible when compared to building and operating a brick-and-mortar o±ce or store. Once in-place, a website is a store that never closes and that is very attractive. People take great pains in building an o±ce or store to project the right image and to serve the needs 7 8 CHAPTER 1.
    [Show full text]
  • Web Pages Are Stored on Web Server and Can Be Viewed Using a Web Browser
    WWEEBB PPAAGGEESS http://www.tutorialspoint.com/internet_technologies/web_pages.htm Copyright © tutorialspoint.com Web Page web page is a document available on world wide web. Web Pages are stored on web server and can be viewed using a web browser. A web page can cotain huge information including text, graphics, audio, video and hyper links. These hyper links are the link to other web pages. Collection of linked web pages on a web server is known as website. There is unique Uniform Resource Locator URL is associated with each web page. Static Web page Static web pages are also known as flat or stationary web page. They are loaded on the client’s browser as exactly they are stored on the web server. Such web pages contain only static information. User can only read the information but can’t do any modification or interact with the information. Static web pages are created using only HTML. Static web pages are only used when the information is no more required to be modified. Dynamic Web page Dynamic web page shows different information at different point of time. It is possible to change a portaion of a web page without loading the entire web page. It has been made possible using Ajax technology. Server-side dynamic web page It is created by using server-side scripting. There are server-side scripting parameters that determine how to assemble a new web page which also include setting up of more client-side processing. Client-side dynamic web page It is processed using client side scripting such as JavaScript.
    [Show full text]
  • Web Design and Development AAS Requirements
    WEB DESIGN AND DEVELOPMENT Program Overview people changing careers or who wish to take individual The Web Design and Development Program is designed courses to stay current in their existing jobs. to train students to design and develop web sites. Students For more information, visit: will develop a comprehensive understanding of core www.mchenry.edu/webdevelopment design principles and key development strategies. This will include developing sites for deployment on mobile The primary purpose of an Associate in Applied Science devices and standard computers and the development degree is to prepare students for employment. The of static websites and database-driven websites. The AAS degree is not designed specifically for transfer; program will train individuals to become web designers however, there are opportunities to apply some and web developers. Students will learn design theory coursework or the whole degree to a bachelor’s degree as well as gain experience in programming for browsers program. For more information, see an academic and servers. The training is geared toward students with advisor and the department chair. no experience, but will be an excellent opportunity for Requirements for the Associate in Applied Science (AAS) in Web Design and Development Curriculum: OCC 425 Minimum Courses Credit Hours Written Communication 3 (3) ENG 151 Composition I or (3) ENG 152 Composition II Oral Communication 3 (3) SPE 151 Intro to Speech Arts 3 Please see page 65 for AAS Degree course options Humanities Social Science Behavioral Science
    [Show full text]
  • Cloud Computing Synopsis and Recommendations
    Special Publication 800-146 Cloud Computing Synopsis and Recommendations Recommendations of the National Institute of Standards and Technology Lee Badger Tim Grance Robert Patt-Corner Jeff Voas NIST Special Publication 800-146 Cloud Computing Synopsis and Recommendations Recommendations of the National Institute of Standards and Technology Lee Badger Tim Grance Robert Patt-Corner Jeff Voas C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 May 2012 U.S. Department of Commerce John Bryson, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director CLOUD COMPUTING SYNOPSIS AND RECOMMENDATIONS Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-146 Natl. Inst. Stand. Technol. Spec. Publ.
    [Show full text]
  • Creating a Dynamic Web Presence
    CREATING A DYNAMIC WHAT’S INSIDE Key Concepts ......................................1 WEB PRESENCE Static vs. Dynamic Websites ..........1 The need for a dynamic web presence has increased dramatically Features of a Dynamic Site ............2 as consumers on the Internet become more knowledgeable Dynamic Techniques ......................2 and more demanding in having their needs filled. With internet Getting Started ....................................2 technologies continuing to evolve rapidly, small businesses 1. Research and Planning .............2 2. Branding and Web can easily create more interactive sites to engage their Development ..............................4 target audiences. Nuts & Bolts .......................................4 1. Select and Register a Domain Name .........................4 Key Concepts 2. Review Hosting Requirements ...5 Static vs. Dynamic Websites 3. Generate Content ......................6 4. Incorporate Interactive Tools.....6 How do they differ? A dynamic website includes elements that allow 5. Address Security, Privacy interaction with visitors, builds relationships through dialogue, and and Legal Issues ........................9 personalizes the whole web experience. Contrast this with a static, or 6. Get Indexed ..............................10 “read only,” site where there really is no way to know who your visitors are unless they contact you. Whether you are designing a site for the 7. Market Your Website ................10 first time or redesigning a current site, the goal of achieving a dynamic
    [Show full text]
  • Web Development Frameworks Ruby on Rails VS Google Web Toolkit
    Bachelor thesis Web Development Frameworks Ruby on Rails VS Google Web Toolkit Author: Carlos Gallardo Adrián Extremera Supervisor: Welf Löwe Semester: Spring 2011 Course code: 2DV00E SE-391 82 Kalmar / SE-351 95 Växjö Tel +46 (0)772-28 80 00 [email protected] Lnu.se/dfm Abstract Web programming is getting more and more important every day and as a consequence, many new tools are created in order to help developers design and construct applications quicker, easier and better structured. Apart from different IDEs and Technologies, nowadays Web Frameworks are gaining popularity amongst users since they offer a large range of methods, classes, etc. that allow programmers to create and maintain solid Web systems. This research focuses on two different Web Frameworks: Ruby on Rails and Google Web Toolkit and within this document we will examine some of the most important differences between them during a Web development. Keywords web frameworks, Ruby, Rails, Model-View-Controller, web programming, Java, Google Web Toolkit, web development, code lines i List of Figures Figure 2.1. mraible - History of Web Frameworks....................................................4 Figure 2.2. Java BluePrints - MVC Pattern..............................................................6 Figure 2.3. Libros Web - MVC Architecture.............................................................7 Figure 2.4. Ruby on Rails - Logo.............................................................................8 Figure 2.5. Windaroo Consulting Inc - Ruby on Rails Structure.............................10
    [Show full text]
  • Fiz: a Component Framework for Web Applications
    Fiz: A Component Framework for Web Applications John K. Ousterhout Department of Computer Science Stanford University Abstract Fiz is a framework for developing interactive Web applications. Its overall goal is to raise the level of programming for Web applications, first by providing a set of high-level reusable components that simplify the task of creating interactive Web applications, and second by providing a framework that encourages other people to create addi- tional components. Components in Fiz cover both the front-end of Web applications (managing a browser-based user interface) and the back end (managing the application's data). Fiz makes it possible to create components that encapsulate complex behaviors such as Ajax-based updates, hiding many of the Web's complexities from applica- tion developers. Because of its focus on components, Fiz does not use mechanisms such as templates and model- view-controller in the same way as other frameworks. ger and more useful structures. We will release Fiz in 1 Introduction open-source form and hope to build a user community Although the World-Wide Web was initially conceived that creates an ever-increasing set of interesting com- as a vehicle for delivering and viewing documents, its ponents, which will make it dramatically easier to cre- focus has gradually shifted from documents to applica- ate applications that advance the state-of-the-art in Web tions. Facilities such as Javascript, the Document Ob- interactivity. ject Model (DOM), and Ajax have made it possible to offer sophisticated interactive applications over the The rest of this paper is organized as follows.
    [Show full text]
  • How Web Browsers Work HTTP: “Definition: HTTP
    How web browsers work http://www.webdevelopersnotes.com/basics/how_do_web_browser_work.php HTTP: HTTP 1.0 document from 1990 http://www.w3.org/Protocols/HTTP/1.0/spec.html “Definition: HTTP - the Hypertext Transfer Protocol - provides a standard for Web browsers and servers to communicate. The definition of HTTP is a technical specification of a network protocol that software must implement. HTTP is an application layer network protocol built on top of TCP. HTTP clients (such as Web browsers) and servers communicate via HTTP request and response messages. The three main HTTP message types are GET, POST, and HEAD. HTTP utilizes TCP port 80 by default, though other ports such as 8080 can alternatively be used……. “ http://compnetworking.about.com/od/networkprotocols/g/bldef_http.htm HTTPS The secure hypertext transfer protocol (HTTPS) is a communications protocol designed to transfer encrypted information between computers over the World Wide Web. HTTPS is http using a Secure Socket Layer (SSL). A secure socket layer is an encryption protocol invoked on a Web server that uses HTTPS. Most implementations of the HTTPS protocol involve online purchasing or the exchange of private information. Accessing a secure server often requires some sort of registration, login, or purchase. The successful use of the HTTPS protocol requires a secure server to handle the request. http://msdn.microsoft.com/en-us/library/aa767735(v=vs.85).aspx HTML HyperText Markup Language is used for describing web documents (web pages) so that they can be correctly displayed. A markup language is a set of markup tags HTML documents are described by HTML tags Each HTML tag describes different document content http://www.w3schools.com/html/html_intro.asp Static Web Page A web page that uses only HTML does not change its appearance or its data and is therefore always a static webpage URI and URL In computing, a uniform resource identifier (URI) is a string of characters used to identify a name of a resource.
    [Show full text]
  • Cloud Computing and Mobile Application Development
    Cloud Computing And Mobile Application Development Personal and hippopotamic Simone often derange some triploidy concertedly or empanels unceremoniously. By-past and waist-deep Georgy readjusts her neurectomy asperses individually or deactivated knee-deep, is Dennis shaping? Bacillary and undealt Pace cutinized her springtide confusing while Saw trammel some polemic insignificantly. What occurs automatically reduces additional challenges Also has the cost as much in mobile application, it means network connection to services depending on a golden software development lets you with mobile application. Advantages and Disadvantages of Cloud Computing. Blueberry considers response to cloud development environment with common, place on servers and collaboration, and get losses when you need to learn how could be. Build a Firebase Android Application by Coursera Project Network. Mobile computing uses the concept in cloud computing. Compatible available whether a music of mobile and standalone devices Changes in Approaching Cloud Software Development Cloud computing has shifted. What these Cloud-Native since It Hype or The Future these Software. We scope the sun cloud based application development company across USA India. Mobile cloud computing refers to execute same technology used to deploy. Mobile App Development merges the alternate-developing Cloud Computing Applications trends with the omnipresent smartphone One member the most. How mobile computing will continually evolving research issues and testing, in regards to the cloud application and cloud computing development is. Cloud Computing Services Cloud-Based Solutions for Future-Ready Businesses With cash-to-cash support from Rishabh Software inventory can realize flexible. That the application developer is programming such powerful device without. Learn Mobile Cloud Computing With Android online with courses like Build a Persistent Storage App in.
    [Show full text]
  • The Role of Responsive Design in Web Development
    Webology, Volume 14, Number 2, December, 2017 Home Table of Contents Titles & Subject Index Authors Index The Role of Responsive Design in Web Development Fernando Almeida Centre for Innovation, Technology and Entrepreneurship, INESC TEC, Porto, Portugal. E-mail: [email protected] José Monteiro Higher Polytechnic Institute of Gaya, ISPGaya, V.N.Gaia, Portugal. E-mail: [email protected] Received October 12, 2017; Accepted December 25, 2017 Abstract Responsive design allows software developers to build a Web page that can dynamically adapt to the size of the devices. This development philosophy enables the rendering of Web pages in a fast and optimized way, ensuring a good user experience on mobile devices, tablet and desktop. In the scope of this study, we intend to explore the main advantages and limitations associated with responsive Web design. We adopted a quantitative approach based on a questionnaire filled by 181 professionals in the industry that allowed us to identify the reasons that lead software developers to the adoption of the responsive design and also address the limitations felt by them. The results obtained indicate that offering a good user experience and increasing accessibility stands out as being the most important advantages. On the other hand, the main limitations include the compatibility with older Web browsers, the higher loading time and the difficulties in optimizing user experience. Finally, it was found that the perception of the advantages and limitations of responsive design is distinct for professionals with more professional experience in the field and for freelancer developers. Keywords Web development; Responsive design; Web designing; User experience 48 http://www.webology.org/2017/v14n2/a157.pdf Introduction The advent of the Web turned possible the appearance of new form of transmission ideas and contents in online environments.
    [Show full text]