DOCSLIB.ORG

Coding Standards, Block Elements, Text Elements, and Character

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Coding Standards, Block Elements, Text Elements, and Character © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION CHAPTER 2 © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE CodingOR DISTRIBUTION Standards,NOT FOR SALE OR DISTRIBUTION © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC BlockNOT FOR SALEElements, OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Text Elements, and © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Character References © Jones & BartlettCHAPTER Learning, OBJECTIVES LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION ▸ Understand HTML5 coding conventions ▸ Know when whitespace collapsing occurs and learn where they can be found. and how to combat it with the pre element. ▸ Use HTML comments appropriately. ▸ Understand phrasing elements, like q, ▸ Use the content model categories to deter- cite, dfn, abbr, and time. mine© which Jones elements & Bartlett are allowed Learning, inside a LLC ▸ Learn CSS basics.© Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION given container. ▸ Learn how and when to use character ▸ Define a block element. references. ▸ Understand blockquote elements. © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 33 © StationaryTraveller/Getty Images © Jones & Bartlett Learning, LLC© Jones & Bartlett Learning, LLC.© NOTJones FOR SALE& Bartlett OR DISTRIBUTION Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 9781284093698_CH02_Pass06.indd 33 07/11/17 9:36 PM © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 34 CHAPTER 2 Coding Standards, Block Elements, Text Elements, and Character References CHAPTER OUTLINE© Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 2.1 Introduction 2.12 q and cite Elements 2.2 HTML Coding Conventions 2.13 dfn, abbr, and time Elements 2.3 Comments 2.14 Code-Related Elements © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC 2.4 HTML Elements Should Describe Web 2.15 br and wbr Elements NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Page Content Accurately 2.16 sup, sub, s, mark, and small Elements 2.5 Content Model Categories 2.17 strong, em, b, u, and i Elements 2.6 Block Elements 2.18 span Element 2.7 blockquote Element © Jones & Bartlett Learning, LLC © Jones2.19 &Character Bartlett References Learning, LLC 2.8 Whitespace Collapsing NOT FOR SALE OR DISTRIBUTION NOT 2.20FOR WebSALE Page OR with DISTRIBUTION Character References 2.9 pre Element and Phrasing Elements 2.10 Phrasing Elements 2.21 Case Study: A Local Hydroelectric 2.11 Editing Elements Power Plant © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 2.1 Introduction © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC In the prior chapter, you were introduced to just enough about HTML elements so you could NOT FOR SALEput together OR a DISTRIBUTION rudimentary web page. In this chapter, we’llNOT introduce FOR youSALE to additional OR DISTRIBUTION HTML elements, so your web pages can be more expressive. In presenting the HTML elements, we make a point of using standard coding-style conventions, so your code will be acceptable to the web community as a whole. © Jones & Bartlett Learning,Throughout LLC this chapter and the rest© of Jones this book, & you’ll Bartlett be exposed Learning, to lots of HTML LLC elements. NOT FOR SALE OR DISTRIBUTIONIf you’re like most people, learning lots ofNOT things FOR that are SALE all in a singleOR DISTRIBUTIONcategory can be overwhelm- ing. Defining subcategories can make learning easier. For example, rather than trying to memo- rize every animal species (an impossible task because thousands of new species are discovered each year), biologists remember categories of species, such as reptiles, mammals, and crustaceans, and assign each species to a particular category. Likewise, before you get overwhelmed with ele- ment© overload, Jones we & describeBartlett the Learning, categorization LLC scheme used by the World Wide© JonesWeb Consortium & Bartlett Learning, LLC (W3C)NOT for organizingFOR SALE HTML OR elements. DISTRIBUTION A bit confusing at first, but it’ll pay offNOT later. FOR SALE OR DISTRIBUTION In this chapter, after we present coding-style conventions and the W3C’s element catego- rization scheme, we present elements that span the width of a web page (block elements) and then elements that can be embedded inside a paragraph (phrasing elements). At the end of the © Jones &chapter, Bartlett we Learning,take a break from LLC HTML elements and introduce© Jones character & Bartlett references. Learning, Character LLC NOT FOR SALEreferences OR allow DISTRIBUTION you to generate characters that are not NOTon a standard FOR SALEkeyboard. OR For DISTRIBUTION example, if you need to display the half character (½) on a web page, you can do that with a character reference. © Jones & Bartlett Learning, LLC© Jones & Bartlett Learning, LLC.© NOTJones FOR SALE& Bartlett OR DISTRIBUTION Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 9781284093698_CH02_Pass06.indd 34 07/11/17 9:36 PM © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 2.2 HTML Coding Conventions 35 © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC 2.2 HTMLNOT CodingFOR SALE Conventions OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Browsers are very lenient in terms of requiring web developers to write high-quality code. So even if a web page’s code uses improper syntax or improper style, web browsers won’t display an error message; instead, they’ll try to render the code in a reasonable manner. You might think that’s a © Jonesgood thing, & Bartlett but it’s not. Learning, If a web page usesLLC improper syntax, different browsers© Jones might & render Bartlett the web Learning, LLC NOTpage FOR differently. SALE In ORa worst-case DISTRIBUTION scenario, the web developer tests the NOTweb page FOR on a SALEbrowser ORwhere DISTRIBUTION no errors are evident, mistakenly concludes that all is well, and publishes the web page on the Web. And then a user loads the web page using a different browser, and that browser renders the page in an inappropriate manner. So as a web developer, how do you deal with this problem? You should test with multiple browsers and check the syntax using the W3C’s HTML validation service. © Jones & Bartlett Learning,As you may recall, LLC coding-style convention rules© Jones pertain to& theBartlett format of Learning, code. For example, LLC NOT FOR SALE thereOR DISTRIBUTIONare rules about when to use uppercase versusNOT lowercase, FOR SALE when to OR insert DISTRIBUTION blank lines, and when to indent. Those rules help programmers understand the code more easily, but the browsers don’t care about such things. Consequently, for all those people who create web pages on their own, there’s nothing to stop them from using horrible style. If they want to put the code for their entire web page© Joneson one line, & browsersBartlett will Learning, treat that code LLC the same as code with proper© newlinesJones & Bartlett Learning, LLC and indentations.NOT However, FOR SALE if you areOR taking DISTRIBUTION a course in web programming, your teacherNOT FORwill SALE OR DISTRIBUTION (I hope) deduct points for poor style. More importantly, if you create web pages for a company, your company will require you to follow their coding-style conventions. Companies like their programmers to follow standard coding conventions so the resulting programs are easier to maintain (program maintenance means debugging and enhancing a pro- © Jonesgram after & Bartlett it has been Learning, released initially). LLC This is particularly true ©for Jones medium- & and Bartlett large-sized Learning, LLC NOTcompanies, FOR SALE where OR programs DISTRIBUTION are debugged and enhanced by a largerNOT number FOR of SALE people. OR With DISTRIBUTION more people involved, there’s a greater need to understand other people’s code, and adhering to standard coding conventions helps with that. In this book, we attempt to use coding-style conventions that are as widely agreed upon as possible. And how does one find such conventions? It’s the same as for everything else in the © Jones & Bartlettworld—by Learning, googling LLC it. If you google “html style guide,”© Jones you will & getBartlett the coding-style Learning, conventions LLC NOT FOR SALE usedOR byDISTRIBUTION Google, the company. Because Google is ubiquitous,NOT FOR Google’s SALE style OR rules DISTRIBUTION have gained huge support from the web developer community. Consequently, this book uses coding conventions that match Google’s coding conventions. In this section, we’ll go over some of the more import- ant style rules, but for a more comprehensive description, see Appendix A, HTML5 and CSS Coding-Style ©Conventions. Jones & For Bartlett now, it’s OKLearning, to remember LLC just the following style rules:© Jones & Bartlett Learning, LLC ▸ For evNOTery container FOR SALE element, OR include DISTRIBUTION both a start tag and an end tag. So even thoughNOT it’s FOR SALE OR DISTRIBUTION legal to omit a p element’s end tag, don’t do it. ▸ Use lowercase for all tag names (e.g., meta) and attributes (e.g., name). ▸ Use lowercase for attribute values unless there’s a reason for uppercase. For a meta © Jones &author Bartlett element, Learning, use title case LLC for the author’s name because© that’s Jones how people’s & Bartlett names are Learning, LLC NOT FOR normallySALE ORspelled DISTRIBUTION (e.g., name="Dan Connolly").
Load more

Recommended publications
  • Just Another Perl Hack Neil Bowers1 Canon Research Centre Europe
    Weblint: Just Another Perl Hack Neil Bowers1 Canon Research Centre Europe Abstract Weblint is a utility for checking the syntax and style of HTML pages. It was inspired by lint [15], which performs a similar function for C and C++ programmers. Weblint does not aspire to be a strict SGML validator, but to provide helpful comments for humans. The importance of quality assurance for web sites is introduced, and one particular area, validation of HTML, is described in more detail. The bulk of the paper is devoted to weblint: what it is, how it is used, and the design and implementation of the current development version. 1. Introduction The conclusion opens with a summary of the information and opinions given in this paper. A Web sites are becoming an increasingly critical part of selection of the lessons learned over the last four years how many companies do business. For many companies is given, followed by plans for the future, and related web sites are their business. It is therefore critical that ideas. owners of web sites perform regular testing and analysis, to ensure quality of service. 2. Web Site Quality Assurance There are many different checks and analyses which The following are some of the questions you should be you can run on a site. For example, how usable is your asking yourself if you have a web presence. I have site when accessed via a modem? An incomplete list of limited the list to those points which are relevant to similar analyses are given at the start of Section 2.
    [Show full text]
  • Bbedit 13.5 User Manual
    User Manual BBEdit™ Professional Code and Text Editor for the Macintosh Bare Bones Software, Inc. ™ BBEdit 13.5 Product Design Jim Correia, Rich Siegel, Steve Kalkwarf, Patrick Woolsey Product Engineering Jim Correia, Seth Dillingham, Matt Henderson, Jon Hueras, Steve Kalkwarf, Rich Siegel, Steve Sisak Engineers Emeritus Chris Borton, Tom Emerson, Pete Gontier, Jamie McCarthy, John Norstad, Jon Pugh, Mark Romano, Eric Slosser, Rob Vaterlaus Documentation Fritz Anderson, Philip Borenstein, Stephen Chernicoff, John Gruber, Jeff Mattson, Jerry Kindall, Caroline Rose, Allan Rouselle, Rich Siegel, Vicky Wong, Patrick Woolsey Additional Engineering Polaschek Computing Icon Design Bryan Bell Factory Color Schemes Luke Andrews Additional Color Schemes Toothpaste by Cat Noon, and Xcode Dark by Andrew Carter. Used by permission. Additional Icons By icons8. Used under license Additional Artwork By Jonathan Hunt PHP keyword lists Contributed by Ted Stresen-Reuter. Previous versions by Carsten Blüm Published by: Bare Bones Software, Inc. 73 Princeton Street, Suite 206 North Chelmsford, MA 01863 USA (978) 251-0500 main (978) 251-0525 fax https://www.barebones.com/ Sales & customer service: [email protected] Technical support: [email protected] BBEdit and the BBEdit User Manual are copyright ©1992-2020 Bare Bones Software, Inc. All rights reserved. Produced/published in USA. Copyrights, Licenses & Trademarks cmark ©2014 by John MacFarlane. Used under license; part of the CommonMark project LibNcFTP Used under license from and copyright © 1996-2010 Mike Gleason & NcFTP Software Exuberant ctags ©1996-2004 Darren Hiebert (source code here) PCRE2 Library Written by Philip Hazel and Zoltán Herczeg ©1997-2018 University of Cambridge, England Info-ZIP Library ©1990-2009 Info-ZIP.
    [Show full text]
  • DFDL WG Stephen M Hanson, IBM [email protected] September 2014
    GFD-P-R.207 (OBSOLETED by GFD-P-R.240) Michael J Beckerle, Tresys Technology OGF DFDL WG Stephen M Hanson, IBM [email protected] September 2014 Data Format Description Language (DFDL) v1.0 Specification Status of This Document Grid Final Draft (GFD) Obsoletes This document obsoletes GFD-P-R.174 dated January 2011 [OBSOLETE_DFDL]. Copyright Notice Copyright © Global Grid Forum (2004-2006). Some Rights Reserved. Distribution is unlimited. Copyright © Open Grid Forum (2006-2014). Some Rights Reserved. Distribution is unlimited Abstract This document is OBSOLETE. It is superceded by GFD-P-R.240. This document provides a definition of a standard Data Format Description Language (DFDL). This language allows description of text, dense binary, and legacy data formats in a vendor- neutral declarative manner. DFDL is an extension to the XML Schema Description Language (XSDL). GFD-P-R.207 (OBSOLETED by GFD-P-R.240) September 2014 Contents Data Format Description Language (DFDL) v1.0 Specification ...................................................... 1 1. Introduction ............................................................................................................................... 9 1.1 Why is DFDL Needed? ................................................................................................... 10 1.2 What is DFDL? ................................................................................................................ 10 Simple Example ......................................................................................................
    [Show full text]
  • Sublimelinter Documentation Release 4.0.0
    SublimeLinter Documentation Release 4.0.0 The SublimeLinter Community Sep 16, 2021 User Documentation 1 Installation 3 2 Settings 5 2.1 Settings stack...............................................5 2.2 Styles (colors)..............................................5 2.3 Project settings..............................................6 2.4 Settings Expansion............................................6 3 Linter Settings 9 3.1 args....................................................9 3.2 disable..................................................9 3.3 env.................................................... 10 3.4 excludes................................................. 10 3.5 executable................................................ 10 3.6 filter_errors................................................ 10 3.7 lint_mode................................................. 11 3.8 python.................................................. 11 3.9 selector.................................................. 11 3.10 styles................................................... 12 3.11 working_dir............................................... 13 4 Customization 15 4.1 Context Menu.............................................. 15 4.2 Key bindings............................................... 15 5 Troubleshooting 17 5.1 Debug mode............................................... 17 5.2 The linter doesn’t work!......................................... 17 5.3 Debugging PATH problems....................................... 17 6 Creating a gutter theme 19 7 Creating a
    [Show full text]
  • Notetab User Manual
    NoteTab User Manual Copyright © 1995-2016, FOOKES Holding Ltd, Switzerland NoteTab® Tame Your Text with NoteTab by FOOKES Holding Ltd A leading-edge text and HTML editor. Handle a stack of huge files with ease, format text, use a spell-checker, and perform system-wide searches and multi-line global replacements. Build document templates, convert text to HTML on the fly, and take charge of your code with a bunch of handy HTML tools. Use a power-packed scripting language to create anything from a text macro to a mini-application. Winner of top industry awards since 1998. “NoteTab” and “Fookes” are registered trademarks of Fookes Holding Ltd. All other trademarks and service marks, both marked and not marked, are the property of their respective ow ners. NoteTab® Copyright © 1995-2016, FOOKES Holding Ltd, Switzerland All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the written permission of the publisher. “NoteTab” and “Fookes” are registered trademarks of Fookes Holding Ltd. All other trademarks and service marks, both marked and not marked, are the property of their respective owners. While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document.
    [Show full text]
  • Sample Chapter 3
    108_GILLAM.ch03.fm Page 61 Monday, August 19, 2002 1:58 PM 3 Architecture: Not Just a Pile of Code Charts f you’re used to working with ASCII or other similar encodings designed I for European languages, you’ll find Unicode noticeably different from those other standards. You’ll also find that when you’re dealing with Unicode text, various assumptions you may have made in the past about how you deal with text don’t hold. If you’ve worked with encodings for other languages, at least some characteristics of Unicode will be familiar to you, but even then, some pieces of Unicode will be unfamiliar. Unicode is more than just a big pile of code charts. To be sure, it includes a big pile of code charts, but Unicode goes much further. It doesn’t just take a bunch of character forms and assign numbers to them; it adds a wealth of infor- mation on what those characters mean and how they are used. Unlike virtually all other character encoding standards, Unicode isn’t de- signed for the encoding of a single language or a family of closely related lan- guages. Rather, Unicode is designed for the encoding of all written languages. The current version doesn’t give you a way to encode all written languages (and in fact, this concept is such a slippery thing to define that it probably never will), but it does provide a way to encode an extremely wide variety of lan- guages. The languages vary tremendously in how they are written, so Unicode must be flexible enough to accommodate all of them.
    [Show full text]
  • 0789747189.Pdf
    Mark Bell 800 East 96th Street, Indianapolis, Indiana 46240 Build a Website for Free Associate Publisher Copyright © 2011 by Pearson Education Greg Wiegand All rights reserved. No part of this book shall be Acquisitions Editor reproduced, stored in a retrieval system, or transmit- Laura Norman ted by any means, electronic, mechanical, photo- copying, recording, or otherwise, without written Development Editor permission from the publisher. No patent liability is Lora Baughey assumed with respect to the use of the information contained herein. Although every precaution has Managing Editor been taken in the preparation of this book, the Kristy Hart publisher and author assume no responsibility for Senior Project Editor errors or omissions. Nor is any liability assumed for Betsy Harris damages resulting from the use of the information contained herein. Copy Editor ISBN-13: 978-0-7897-4718-1 Karen A. Gill ISBN-10: 0-7897-4718-9 Indexer The Library of Congress Cataloging-in-Publication Erika Millen data is on file. Proofreader Williams Woods Publishing Services Technical Editor Christian Kenyeres Publishing Coordinator Cindy Teeters Book Designer Anne Jones Compositor Nonie Ratcliff Trademarks All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Que Publishing cannot attest to the accuracy of this infor- mation. Use of a term in this book should not be regarded as affecting the validity of any trademark or service mark. Warning and Disclaimer Every effort has been made to make this book as complete and as accurate as possible, but no warranty or fitness is implied. The information provided is on an “as is” basis.
    [Show full text]
  • Pdflib API Reference 9.0.1
    ABC PDFlib, PDFlib+PDI, PPS A library for generating PDF on the fly PDFlib 9.0.1 API Reference For use with C, C++, Cobol, COM, Java, .NET, Objective-C, Perl, PHP, Python, REALbasic/Xojo, RPG, Ruby Copyright © 1997–2013 PDFlib GmbH and Thomas Merz. All rights reserved. PDFlib users are granted permission to reproduce printed or digital copies of this manual for internal use. PDFlib GmbH Franziska-Bilek-Weg 9, 80339 München, Germany www.pdflib.com phone +49 • 89 • 452 33 84-0 fax +49 • 89 • 452 33 84-99 If you have questions check the PDFlib mailing list and archive at tech.groups.yahoo.com/group/pdflib Licensing contact: [email protected] Support for commercial PDFlib licensees: [email protected] (please include your license number) This publication and the information herein is furnished as is, is subject to change without notice, and should not be construed as a commitment by PDFlib GmbH. PDFlib GmbH assumes no responsibility or lia- bility for any errors or inaccuracies, makes no warranty of any kind (express, implied or statutory) with re- spect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for par- ticular purposes and noninfringement of third party rights. PDFlib and the PDFlib logo are registered trademarks of PDFlib GmbH. PDFlib licensees are granted the right to use the PDFlib name and logo in their product documentation. However, this is not required. Adobe, Acrobat, PostScript, and XMP are trademarks of Adobe Systems Inc. AIX, IBM, OS/390, WebSphere, iSeries, and zSeries are trademarks of International Business Machines Corporation.
    [Show full text]
  • Locale Database
    International Language Environments Guide Part No: 817–2521–11 November 2010 Copyright © 2005, 2010, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • Introduction, Internet and Web Basics, XHTML and HTML
    Introduction, Internet and Web Basics, XHTML and HTML http://localhost:8080/cocoon/projects/cscie12/slides/20070130/handout.html Introduction, Internet and Web Basics, XHTML and HTML http://localhost:8080/cocoon/projects/cscie12/slides/20070130/handout.html Table of Contents | All Slides | Link List | Examples | CSCI E-12 CSCI E-12, Fundamentals of Web Site Development Introduction, Internet and Web Basics The Course XHTML and HTML Course Syllabus | Course Schedule I. Content for the Web January 30, 2007 A. Markup (XHTML, HTML) B. Style (CSS) Harvard University C. Building a Site Division of Continuing Education D. Images and Media Extension School II. "Everything" else Course Web Site: http://cscie12.dce.harvard.edu/ A. Javascript and AJAX B. Hypertext Transfer Protocol (HTTP) Copyright 1998-2007 David P. Heitmeyer C. The Apache HTTP Server D. Keeping a site healthy Instructor email: [email protected] E. Dynamic Sites Course staff email: [email protected] The Course Staff David Heitmeyer Teaching Fellows Mike Cynn Rei Diaz Evan Elias Sonal Patel Susan Smith 1 of 39 2/7/2007 4:26 PM 2 of 39 2/7/2007 4:26 PM Introduction, Internet and Web Basics, XHTML and HTML http://localhost:8080/cocoon/projects/cscie12/slides/20070130/handout.html Introduction, Internet and Web Basics, XHTML and HTML http://localhost:8080/cocoon/projects/cscie12/slides/20070130/handout.html Texts What the Course "Is" and "Is Not" In addition to the texts, there will be online readings assigned and online references cited. Is Is Not Required texts: Freeman, Elisabeth and Eric Freeman. 2005. Head First HTML with CSS & XHTML.
    [Show full text]
  • Requirements for Web Developers and Web Commissioners in Ubiquitous
    Requirements for web developers and web commissioners in ubiquitous Web 2.0 design and development Deliverable 3.2 :: Public Keywords: web design and development, Web 2.0, accessibility, disabled web users, older web users Inclusive Future Internet Web Services Requirements for web developers and web commissioners in ubiquitous Web 2.0 design and development I2Web project (Grant no.: 257623) Table of Contents Glossary of abbreviations ........................................................................................................... 6 Executive Summary .................................................................................................................... 7 1 Introduction ...................................................................................................................... 12 1.1 Terminology ............................................................................................................. 13 2 Requirements for Web commissioners ............................................................................ 15 2.1 Introduction .............................................................................................................. 15 2.2 Previous work ........................................................................................................... 15 2.3 Method ..................................................................................................................... 17 2.3.1 Participants ..........................................................................................................
    [Show full text]
  • C++ Reading a Line of Text
    C++ Reading a Line of Text Because there are times when you do not want to skip whitespace before inputting a character, there is a function to input the next character in the stream regardless of what it is. The function is named get and is applied as shown. cin.get(character); The next character in the input stream is returned in char variable character. If the previous input was a numeric value, character contains whatever character ended the inputting of the value. There are also times when you want to skip the rest of the values on a line and go to the beginning of the next line. A function named ignore defined in file <iostream> allows you to do this. It has two parameters. The first is an int expression and the second is a character. This function skips the number of characters specified in the first parameter or all the characters up to and including the character specified in the second parameter, whichever comes first. For example, cin.ignore(80, '\n'); skips 80 characters or skips to the beginning of the next line depending on whether a newline character is encountered before 80 characters are skipped (read and discarded). As another example, consider: cin.ignore(4,’g’); cin.get(c); cout << c << endl; If the input to this program is “agdfg” then the input is ignored up to and including the ‘g’ so the next character read is ‘d’. The letter “d” is then output. If the input to this program is “abcdef” then the input is ignored for the first four characters, so the next character read is ‘e’.
    [Show full text]