Tuesday, March 7, 2017

Understanding Graphic File Formats for the Web

Hello Students,
In this exercise you will practice using the "save for web & devices" feature in Photoshop, a media industry standard when creating compressed images.

Take notes during todays lecture and save them.

File Format Exercise
  1. Right-click on the two images below, save them to your computer and open them in Photoshop
  2. Go to File / Save for Web & Devices
  3. Photoshop has 12 presets, save 1 example of each. Use proper self descriptive file names from low quality to high quality
  4. Compare the results
  5. Repeat step 3 using the VW Bus illustration
  6. Write a short paragraph about your results and answer these questions. Which image has the best quality? Which has the best file size? Which has the best balance of file size and quality and why?
  7. Create a new HTML file, you may use bootstrap or you may create your own CSS for the document.  Create a single HTML page that contains your notes and your assessment of the file formats that you wrote from step 6. Embed the 12 images that you created from low to high quality below your notes and written assessment.



Alias vs Anti-Alias Pixels Explained:
In Photoshop and other bitmap/pixel based programs, Anti-Aliasing is used to give objects a smooth appearance when viewed on screen, it averages the pixel colors to create a smooth transition.

Aliasing is when graphics lack that smoothing, and we can see jagged edges to the object, or "Jaggies".



Contiguous vs Non-Contiguous:
It is important to understand the difference between contiguous and non-contiguous imagery, because different image compression formats are best used for certain types of images.

Contiguous images have subtle color changes from one pixel to another, such as photograph's, paintings, hand drawn sketches or any graphics with a lot of gradients. The JPEG compression codec is best for these kinds of images, that is why most digital camera's save images in the .JPG format.

Non-Contiguous Images have large areas of flat color, shapes and lines. These can be photo's that have been converted to 8-bits, or graphics drawn without anti-aliasing.



Graphic File Formats Explained:
There are a lot of great ways to get confused while using computers - and one of the best is figuring out graphics file formats. As with so many areas of computing, standards for graphic files are great because there are so many to choose from.

They're all different and incompatible, of course, but many programs can load and/or save a wide selection of file formats. By and large, you can tell what kind of file you've got by looking at the suffix - the letters, usually three, after the dot in the filename, otherwise known as the file extension.

Better graphics software actually looks at the file data to determine what kind of file it's dealing with, but Windows software is shamefully deficient in this regard; rename happyface.psd to happyface.jpg and it's likely that the file will become unreadable on any computer.

Below is a list of all (or almost all) graphic file formats... The ones we will use the most are JPG, GIF, PSD, AI and PNG....

ADI - AutoCAD's Device-Independent Binary Plotter Format, a vector format generated by AutoCAD.

AI - Adobe Illustrator's metafile format, which is actually a flavour of Encapsulated Postscript.

AWD - Microsoft Fax At Work format, a black-and-white (one bitplane) format for storing fax images.

BMP - This is the Microsoft Windows bitmap format, also used in OS/2. It's a fairly compact (compression is optional, but usually turned on) format for images up to 24 bit. BMP is the native bitmap format for the Windows environment.

CALS - Computer Aided Acquisition and Logistics Support Raster Format; a longwinded, seldom-seen military-spec two colour document storage format. Used in Pentagon archives, and that sort of thing.

CAM - Casio Camera, the native file format of Casio's QV-series digital cameras.

CGM - Computer Graphics Metafile, an American National Standards Institute/International Standards Organization metafile format for images of pretty much any kind.

CLP - This is the format you get when you save a file from the Windows 3.x Clipboard. It is very, very large, and very very, inefficient - and, what's more, you can only view a CLP file if you're in the same resolution as the person who made it, and are using the same number of colours. CLP is an image format that should never be allowed to touch a disk. Do not use it.

CT - The most popular of the Scitex image formats, Scitex Continuous Tone images are very large and intended for use with Scitex's professional film-printing units, which produce high-grade output for publication.

CUT - The orphaned 256 colour format used by the old Doctor Halo paint program.

DIB - This is an orphaned Windows image format. It stands for Device Independent Bitmap and was part of Microsoft's Great Plan for Windows 95; the DIB code in Win 95 is designed to simplify the creation of display drivers for new video cards by doing most of the grunt work in the operating system instead of in the driver. DIB never really took off.

DLG - Digital Line Graph, a vector format for storing geographical data.

EPS - Encapsulated Postscript is a flavour of Postscript (see below) which can be included in other documents - if your software supports it.

FPX - The FlashPix format, codeveloped by Hewlett-Packard, Kodak, Microsoft and LivePicture Corporation and now an open format administered by the Digital Imaging Group. Kodak uses it in all of their digital cameras from the DC200 onwards. Flashpix's chief claim to fame is that it stores images in multiple resolutions, so a huge, high resolution image can be quickly displayed in miniature on-screen and changes made rapidly to the displayed data only, saving the CPU-grinding full processing for whenever you actually view or output the high resolution version. Of course, this only works if your image editing program supports it, and is not useful for small images. FlashPix images can also be used for Web graphics, because the server only has to send the data being viewed (which seems to the browser like an ordinary JFIF), but since FlashPix doesn't support progressive display like JFIF or GIF or PNG, it hasn't achieved much popularity. FlashPix also has no zero-loss compression option - it either uses no compression at all, and makes a vast file, or uses medium-loss JPEG-type encoding. This makes it a clumsy format for professional use, since lossy compression is a no-no for image editing.

GIF - Graphics Interchange Format (the acronym's officially pronounced "JIF", by decree of the format's creator) is a very efficient, and still quite popular picture format. There are two "flavours" of GIF, the old 87 and the newer 89a. 89a adds several extra features like transparency (so background graphics can "show through" the GIF in places) and animation. GIF animations are a very - some would say excessively - popular form of Web multimedia, because they're small and display on all current graphical browsers without needing a special plug-in or taking up much CPU time.

Unfortunately, GIF pictures can only have 256 colours, or 256 shades of grey. 256 greys is photo quality so GIF is fine for any monochrome image, and 256 colour looks OK for many pictures, but it's no use for professional imaging.

GIF images can also be interlaced, so that you can see a low resolution version of the picture before downloading very much of it. GIF interlacing has four passes, which show one out of every eight lines, then another eighth of the image, then another quarter, then the remaining half. GIF is a data-stream type format, like JFIF, so you can view partially downloaded images whether or not they're interlaced - without interlacing, a 25% downloaded picture gives you the first 25% of the lines, starting at the top.

HRF - Hitachi Raster Format, an obscure, proprietary, one bitplane format used for storing scanner data.

IFF - This is Electronic Arts' Interchange File Format, and is the image format used by Amiga and Atari ST personal computers. There are multiple IFF formats, but by far the most popular are the image and sound file ones. A file with the .IFF suffix may, therefore, be a sound, not a picture - and it might be any one of a number of other types of data. IFF images may also, uncommonly, have the suffix .ILBM, for InterLeaved BitMap, or just .LBM on DOS-based systems.

IFF pictures are not at all efficient, spacewise, but they're fast to display, which was important for poor little Amigas with a 0.7 million instruction per second (MIPS) processor. With current PCs steaming along at hundreds and hundreds of MIPS, this no longer matters at all.

IFF is peculiar in that it has two odd variants - HAM and HAM8. HAM stands for Hold And Modify, and is a technique the original Amiga designers came up with for getting 4096 colours from hardware which, traditionally, can only display 32 at once. HAM8 is the updated version, which displays 262,144 colours on 256 colour hardware. No non-Amiga computer can display HAM images exactly as they're meant to be seen, but some conversion programs can display them as 256 or higher colour images. If your display program isn't smart enough to do this, it'll assume it's loading an ordinary 32 or 256 colour image and give you a distinctive multicoloured porridge on screen. There are some very strange IFF variants which use whole different palettes on every line; pray you never meet one.

All IFF images can be compressed or uncompressed; just about all are compressed. The compression, like the whole format, is built for speed, not efficiency, and so doesn't reduce the size much.

IMG - This is the format used by the old GEM Paint program; it only works in 256 shades of grey.

IMG - See "PIC".

IMJ - A proprietary variant of the JFIF format created by Pegasus Image Corporation.

JBG - Also suffixed JBIG, this is the Joint Bilevel Image Group's data compression and transmission format.
JBG is a way of sending one-bitplane document images so that a low resolution version arrives first, then extra data to "fill in" more and more detail. Not an image format as such - a JBG "file" is just a JBG data stream dumped to disk.

JFIF - The JPEG (Joint Photographic Experts Group) File Interchange Format, commonly called JPEG and with the filename suffix .JPG, can be the most efficient image storage method of all - at a price. First to the name. Everybody might call these images JPEG, but that just describes the type of compression used for the data; it doesn't describe how the compressed data is sorted and stored. Calling JFIF "JPEG" is like calling a Ford Falcon "internal combustion".

The idea of JPEG is that as it compresses the data it throws some of it away - technically, this is called "lossy compression". You can configure how lossy you want your JFIFs to be (well, you can if you're using even a slightly well written JFIF saver); 100% quality gives you almost exactly the same result as the original picture but also gives you a gigantic, uncompressible file. 10% quality takes up much less space but looks dodgy. You have to strike a balance.

JFIF can store up to 24 bit colour, so it's suitable for professional use, and it can do interlaced display like GIF (called "progressive" JFIF), which along with its small file sizes makes it the standard format for Web graphics. Like GIF, JFIF is a data-stream format - you can view images before you've got all of the data. Also like GIF, JFIF supports interlacing.

The JFIF format also supports CMYK (process colour - Cyan, Magenta, Yellow and blacK in a subtractive colour model, as against the additive Red, Green and Blue more commonly used) images, which makes it suitable for use in publishing applications. CMYK this support was added in a later version of the standard, though. This means that quite a few JFIF display applications, including Web browsers, do peculiar things when fed CMYK images. There's no reason to use CMYK JFIFs unless you're sending the image to a CMYK output device, which a monitor definitely isn't. Usually, CMYK ones get through because someone's converted a CMYK image of some other format, like TIFF, without changing the colour model.

JPG - See JFIF and SPF.

LBM - See IFF.

MacPaint (3k) - Usually suffixed .MAC, this is the format used by the ancient original black and white Macintosh paint program. Two colours only, 576x720 resolution only, thankfully rare.

MNG - The proposed Multiple Network Graphics (pronounced "ming") format is a multi-image extension of the existing PNG format - or it will be, if it ever makes it out of the design stage.

MSP - Microsoft Paint was the early PC answer to MacPaint, and its format is just as boring. Two colours only.

PCC - see PCX.

PCD - Kodak's PhotoCD was going to set the world alight, with happy snappers having their film scanned and the high-resolution images written to CD, to access via PC or special PhotoCD players. Amazingly, it turned out that nobody was very interested in viewing their photos on their TV, and PhotoCD flopped miserably in the consumer market. It survives as a somewhat popular professional image storage format; a genuine PhotoCD has a particular directory structure containing the images, stored in five resolutions. An ordinary PCD file can be read by any application that can read the format, but unless it's on a CD with the right structure, a PhotoCD player won't recognise it.

The PhotoCD storage process is proprietary to Kodak, who no longer sell the software to make full multi-resolution images.

PCX - The ZSoft Paint format, occasionally suffixed .PCC, is ancient but still fairly widely used, simply because everybody understands it. There are three common versions, 0, 2 and 5; 0 is the original two colour one (small but not useful), 2 only does 16 colours and is hence also of little interest to owners of rather old video cards, and 5 does 24 bit. All are large for what they do, but fast to load on elderly computers. PCX is the IBM equivalent of Amiga IFF. The size listed is for v5, at full 24 bit; v2 scored 216k and v0 48.1k.

PIC - A few proprietary (one company makes software that supports them, and nobody else does) image formats use this suffix. They are not interchangeable. Some programmers need a good slapping. PIC is most likely to be the 256 colour format of the old PC Paint program, but it might also be a Micrografx Draw! vector file, a Lotus vector file, a Pegasus Imaging Corporation image file or an image file for General Parametrics' Video Show Film Recorder.

PICT - Pict is the all-in-one Apple Quickdraw metaformat. It can include bitmapped or vector images, and can use different compression schemes.

PNG - The Portable Network Graphics format, pronounced "ping", was created as a free replacement for GIF, whose LZW compression is owned by Unisys and which can't be included in commercial software without paying license fees to the owners. It handles 1 to 48 bit images, and is a lossless, well-compressed format like GIF. It still isn't very popular, though.

PS - Adobe Systems' Postscript isn't an image format, per se - it's a page description language, originally conceived so computers could send very accurate page descriptions to the then-new high resolution laser printers. You can save black and white or even colour pictures as Postscript, but you'll end up with a very large file. Postscript is not a very efficient format, but its advantage is it's all plain text - you can modify a Postscript file with any text editor, if you know what you're doing.

PSD - Adobe Photoshop's native format, which stores all of its layer and selection and miscellaneous other image data.

RAS - This is SUN Raster format, the default image format for monster SUN workstations. Only lighhtly compressed and so a rather large format, but it supports up to 36 bit images.

RAW - This may be a Photoshop RAW file, which is a PSD file with no identifying header. Or it may be a minimally formatted image data dump - see PIC.

RGB - See "PIC".

RIX - The orphaned bitmap format of the old DOS ColoRIX paint program.

RLE - This is an antique CompuServe or Windows Run Length Encoded compressed image format, which only support 256 x 192 black and white images.

RTF - Microsoft's Rich Text Format, which is normally used as a well-understood cross-platform word processing document format, but which can store pictures as well as text. As image storage formats go, though, this one's as bloated as Postscript.

SPF - SPIFF, Still Picture Interchange File Format, the "official" International Standards Organisation Joint Photographic Experts Group (ISO JPEG) image format defined in the recent Part 3 extensions to the JPEG standard. SPIFF offers more features than the current JPEG standard and is backwards compatible (a JFIF decoder can understand most SPIFF images), but has not yet achieved much popularity. SPIFF files may also be suffixed .JPG.

TGA - The real name for this format is just plain "TGA" or "Truevision File Format", but a lot of people call it "Targa", after the Truevision video card that first used it. There's a lot of this name confusion in image file formats. It supports 1 to 32 bit images and professional features like an alpha (mask) channel, gamma settings and a built-in thumbnail image.

TIF - TIFF (to give the full acronym) stands for Tag Image File Format; many people say Tagged for the first word, which is technically incorrect but minimally important. TIFF was a large, unwieldy, 24 bit format until version 6 came out, which supported compression and made it less painful. Mind you, the fact that its compression was somewhat broken and might or might not be compatible with different programs on different computers somewhat reduced the bonus, and the further fact that the compression is LZW and thus owned and licensed out by Unisys (see GIF) is another pain. TIFF is, nonetheless, a very popular professional graphics format.

WMF - This is Windows Metafile format, which is an intermediate vector format for Windows programs to use when interchanging data and, generally speaking, should never be seen anywhere else.

WPG - This is the WordPerfect metafile format, used by WordPerfect software on various platforms. It supports bitmapped, vector and Encapsulated Postscript data.

Tuesday, February 28, 2017

Web Site Evaluation Assignment

Hello Students,
This new assignment is an exercise in evaluating a current website and proposing a redesign with lists of enhancements or features that should be included.

Web Site Evaluation Assignment:
Create a document that evaluates the current web site in regards to functionality and content, and propose a redesign with focus on enhanced functionality and content. Make sure you address or try to answer all the questions in the list below. Cite examples and details of sites you like and propose a redesign. Compile all your date into a small webpage/site and upload to our server when complete.

Part 1: Review the website at http://www.rop.santacruz.k12.ca.us

  • Answer the questions in the detailed "review questions" list below
  • Compile your data in a properly formatted HTML/CSS site titled ROP Web Site Evaluation by (Insert your name here). 
  • Format the webpage with CSS for easy reading and formatting (you may use/edit a previously created page).
  • Provide screen shots or other details to illustrate your data as needed.
Part 2: Cite examples
  • Search online for other websites, preferably education related that you think show good functionality and visual interest.
  • Provide links/screenshots with details for the features of the site that you like listed somehow
  • Provide at least 3 examples of websites with features you like and list the elements that you feel work the best and will translate to the ROP web page
Part 3: Redesign/Mockup
  • Create a redesigned front page and cite details and how the page functions
  • You can create a pen/pencil sketch for the redesign or you could use photoshop to make a digital mockup 
  • List details that your front page will feature (drop down menu's, image carousel's, slideshows, videos, etc)

Review Questions: Accessibility
  1. Is content structurally separate from navigational elements?
  2. Is the website optimized for mobile? Does it resize or shift elements around to accommodate different screen sizes and resolutions?
  3. How compliant is the website with W3C coding standards? Valid HTML/CSS?
  4. Are ‘alt’ tags in place on all significant images?
  5. Are text-based alternatives in place to convey essential information if this is featured within images or multimedia files?
Navigation
  1. Are links labeled with anchor text that provides a clear indication of where they lead without over using exact match anchor text?
  2. Depth – what is the maximum number of clicks it takes to reach a page within the depths of the site?
  3. Does any part of your site use Flash? 
  4. Responsive to click feedback – Is a response given immediately (0.1 seconds) after a click is made on a hyperlink?
  5. Do clickable items stylistically indicate that they are clickable?
  6. How intuitive is it to navigate? Are signs obvious or obscured?
  7. Is it readable? Consider typeface, font size, color contrast.
  8. Is there a clear statement of PURPOSE of the site? The purpose must be clear within a few seconds.
  9. Do you have a clear call to action on each page?
  10. Is a logical site map available?, If not, is a keyword-based search feature available? Note: Large (multi-thousands of pages) sites should have a search form.
Design
  1. Is the site’s design aesthetically appealing?
  2. Are the colors used harmoniously and logically related?
  3. Are the color choices visually accessible? (For example high enough in contrast to assist the colorblind and visually impaired in reading the site appropriately)
  4. Is the design audience appropriate?- The standard text size should be readable for visitors who don’t know how to adjust their browsers.
  5. Are the fonts easy to read on various screen resolutions?
Content
  1. Is the website copy succinct but informative?
  2. Does the copywriting style suit the website’s purpose and ‘speak’ to its target audience?
  3. Are bodies of text broken into easy to read chunks?
  4. Can text be resized through the browser or do CSS settings restrict size alteration?
  5. Is the contrast between text and its background color sufficient to make reading easy on the eyes?
  6. Is text broken into small, readable chunks and highlighted using headings, sub-headings, and emphasize features where appropriate to assist in skimming?
  7. Within articles, are there links to more detailed explanations of subjects, or definitions of jargon terms?
  8. Do you have an “about page” that identifies the author of the content, credits to source for content that was not written by the site owner himself?
  9. Do you have testimonials and publish them on the site?
  10. Do you update the content regularly and don’t live by the phrase “set it and forget it”?
Security
  1. Any obvious security flaws?
  2. How resilient are forms to special characters?
  3. Are private directories password protected via .htaccess?
  4. Are public non-document directories (cgi-bin, images, etc) indexable or are blank index.html pages or appropriate permission settings in place to block access?
  5. Is customer data stored online? If so, is this database appropriately safeguarded against external access?
Other Technical Considerations
  1. Does the site load quickly – even (especially) for mobile users?
  2. Are all links (internal and external) valid and active?
  3. Are scripts free from errors?
  4. Is the website free from server side errors?

Other Marketing Considerations

  1. Is the website properly optimized for search engines (essential text emphasized, title tags relevant, title text presented in H1, outbound links reliable and contextually related, etc.)
  2. Does the index page entice a visitor deeper into the site or shopping cart?
  3. Does the website contain elements designed to encourage future or viral visitation (i.e. a contest, newsletter, tell-a-friend feature, and forum with a subscription option, downloadable toolbar, RSS feed or similar)?
  4. Site Map available?
  5. Is every page accessible at least via a single plain HTML Link (no JavaScript or Flash Link)?
  6. Does every page have at least some text in the content? (How much text remains on the page if you remove all Images, Videos, Flash, Java Applets and JavaScript Code? Anything? Does the remainder still state the page’s purpose?)
  7. Is every individual page only accessible via a single URL or are several URLs available (and worse, used) to access the same page? Consider duplicate content issue and utilize canonical URLs.
Legal Stuff/Re-Assurance/Legitimization
  1. Did you include a Contact Us page with real address, phone number (toll-free for businesses) and contact form or email available, basically a clear and easy to use feedback/contact mechanism?
  2. DMCA Notice up? Terms of Use page available where you specify what you do and why and what visitors have to agree on if they want to use your site? This is to protect yourself from complaints or worse regarding things that you cannot control properly, such as links to third-party websites or ads from automated systems such as Google AdSense, etc.
  3. Privacy Policy up (especially if you collect data, email, names, and web analytics tracking cookies)?
When your document is complete, upload to our server for review by our client!
This project is due on Monday...

Have fun!
- Mr.W

Tuesday, February 21, 2017

Advancing Your Web Skills: Layout and Responsive Design

Hello Students,
Our newest assignment is to create a progression of small web pages that demonstrate layout, responsiveness and then utilize W3C CSS to enhance the responsiveness of your page, and finally complete a single page utilizing all the W3C CSS tools to make a page with layout that is responsive, meaning it can be viewed on many different screen sizes

Assignment:
Work with the class, or read and work independently and develop 4 single pages, demonstrating layout, responsiveness, responsiveness with layout, and finally a full W3C CSS page:

1: Layout with HTML and CSS: W3Schools - HTML Layout

This page utilizes HTML and CSS to layout elements using the Header, Nav, Aside,  Section and Footer classes

2: Responsiveness with HTML and CSS: W3Schools - Responsive Design

This sample site uses simple block classes to "stack" elements when the screen is resized

3: Responsive Page Enhanced With W3C.CSS: W3C.CSS

Building off the previous page the block classes are replaced with the w3-container, w3-row-padding and w3-third classes for enhanced responsiveness

4: Full W3C.CSS Layout and Responsive Page: W3C.CSS Sample

This page utilizes many of the W3C.CSS features such as Header, navbar, drop down, card and container W3C.CSS features.

When these pages are complete upload them to your server space for testing or turn in via USB drive.


- Mr.W

Thursday, February 16, 2017

Getting Closer to Validation: Metadata and Character Encoding

Character Encoding for Web Pages: HTTP file headers

Validation Assignment:



Details About Character Encoding and Validation:

Hypertext Transfer Protocol (HTTP) is the language used by a Web server and a Web browser to communicate with each other.

Every time a Web server serves a page to the browser, it adds an invisible "HTTP response header" to the file. This file header (not to be confused with the <head> section of a document) is metadata, which means it contains information about the file that it is serving to the browser. Many servers include character encoding (the character set used in the document) in this header. In other words, the server tells the browser how the document is encoded. (But, what the server says about the encoding may not be how the documents it serves are actually encoded; this is determined by your text editor when it saves a file.)

Most servers will say the files it serves are either ISO-8859-1 (Western European Latin characters) or the newer Unicode standard, UTF-8. In documents written in English there is little difference between these two standards; most noticeable differences will be in special punctuation. But if you wish to have your Web page display more than Western European languages (perhaps a page that mixes English with Chinese, for example), you cannot use ISO-8859-1; UTF-8 would be the way to go. At any rate, UTF-8 is the current standard for Web pages.

Browsers (also called "user agents") use an "HTTP request header" when requesting a file from the server. In this request header the browser identifies itself with a "user agent string." By keeping track of these user agent strings, Web traffic analysis software can create logs showing information on what percentage of users come to a site with Firefox, Safari, or Internet Explorer, for example.
Thecharacterencodingmeta tag

Many servers, but not all, indicate the character encoding in the HTTP response header. But whether or not your pages are on a server that indicates the encoding, you should do so in the document itself, by adding the appropriate character encoding meta tag to the head section. Assuming the document was encoded in UTF-8, and is using HTML 5, you simply need to add this to the <head> section:

<meta charset="utf-8">

Because this tag tells the browser how to interpret the characters used in the document, it should be the first tag in the<head> section.

The HTML validator needs to know which character set the document is encoded in so it can properly evaluate it. So if your pages are on a server that does not indicate the encoding, it is necessary to add the character encoding meta tag to your HTML or the validator may not be able to properly evaluate the page. Additionally, if your pages are not being served by a Web server (they are being viewed locally, or perhaps they are to be burned onto a CD) the browser will need the character encoding meta tag in your HTML to properly display the page.

In the case where the server indicates the encoding, and you also indicate the encoding with the character encoding meta tag, there is no problem if your tag and the file header from the server indicate the same encoding. But if the server says the encoding is, for example, ISO-8859-1, and your meta tag says UTF-8, the validator will give you a "character encoding mismatch" error. In such a situation the validator assumes the server's encoding is the one to use. In other words, in the event of a conflict between your tag and the server, the server overrides your character encoding meta tag.

How to see a server’s character encoding setting:

To see what your server says about the pages it is serving, you need a way to see its invisible file response header. A tool such as Rex Swain's HTTP Viewer will allow you to see this, including the character encoding, if any is indicated. Go there and enter a URL for a server that you wish to check then look at the "Receiving header."

If you see something like:
Content-Type:·text/html;·charset=UTF-8
then you know the server says the documents it is serving are encoded as UTF-8.

If you see something like:
Content-Type:·text/html;·charset=iso-8859-1
then you know the server says the documents it is serving are encoded as ISO-8859-1.

If you see something like:
Content-Type:·text/html
then your server is not indicating the character encoding.

Remember that if your server does not indicate the character encoding, it is even more important that your pages contain the character encoding meta tag. This will give the browser the information it needs to properly render your page (otherwise it will have to guess at the encoding, and it may guess wrong), and it will give the HTML validator the information it needs to properly evaluate your page.
Keepeverythingin synch

To make sure the browser renders your page as you intend (so that special characters such as curly quotes, apostrophes, accented characters, dashes, etc. display properly), and to enable the HTML validator to work, it is important that the server’s character encoding setting, your page’s character encoding meta tag, and the actual character encoding of the document all match.

It is recommneded that Web pages use the UTF-8 encoding. To ensure that your pages are actually encoded as UTF-8, your text editor must be configured to save your pages as UTF-8

Setting Komodo Preferences for UTF-8 / No BOM:

Launch Komodo and go to File/Preferences/Internationalization.
Uncheck the top option box to find the UTF-8 option in the pulldown menu
Change this second language-specific default encoding option to UTF-8.
Leave Signature BOM unchecked.

Monday, February 6, 2017

CSS Mini Page + Writing Assignment

Hello Students,
Read the details of this project thoroughly before beginning, it consists of 2 parts. Part 1 is a writing assignment that must be created as a simple HTML page and includes organization of your notes taken in-class during lectures. The second assignment is to create a CSS script to enhance the look of the HTML page. Due on Friday

Part 1:
Writing Assignment - A Summary of our studies in ROP Web Design including all class notes

  1. Create a new blank HTML file
  2. Format the HTML file with the proper HTML tags and Doctype declaration
  3. Write a title for your page. Format it with the h1 tag
  4. Write a subtitle for your page that includes your name and grade and what city you where born in. Format it with the h2 tag
  5. In your own words write a paragraph that summarizes your experience with computers and programming before this class began. Format it with the paragraph tag
  6. In your own words, write a second paragraph that summarizes what you have learned so far in this ROP Web Design class.Format it with the paragraph tag
  7. Add your notes from the previous lecture "how the internet works" and "the history of the internet" and todays lecture as well "CSS".
  8. Save your document in a new project folder called "mini css site" and make sure it is called "index.html"
Part2:
CSS Assignment - Format Your Content
  1. Create a new blank CSS file
  2. Create a set of CSS Rules to format your h1, h2 and p tags
  3. Use CSS to modify the color of your text, the font and the text size
  4. Use CSS to modify your p tag to indent your text and create a colored background for the paragraph
  5. Explore CSS properties to enhance your page, use CSS creatively!
  6. Save your CSS document in the same folder as your HTML file
  7. Create a link in the head of your HTML document to link to your CSS file
When your project is complete, turn it in via USB drive for uploading to our server. Test, debug, fix and re-pload as needed.

Have fun!

Resources:


Thursday, January 26, 2017

Basic HTML Assignment: Mini Website

Hello Students!
Your Basic HTML Assignment is to create a simple 4 page website that is about anything you like, favorite band, food, movie, actor or actress, etc. You will create a menu for navigation on a home page, and 3 other pages. These can be About, Contact and Sites of Interest. You could also have page titles, pictures or examples of your subject matter. Each page should have a menu for navigation plus content such as text or pictures. Each page should have an image or photo and text, links, lists etc. A full page is not necessary, the focus here is creating navigation, links and using color and embedding images.


Subject Matter: You can make your website about anything you like. You can make it about yourself, a favorite band, tv show, movie, food, car, place etc. The idea is to introduce me, the reader, to your interests. If you already have an idea for your site ask me and we can think about how to structure your website.

For help: Google it or ask your neighbor before asking your instructor. Below are notes about the tags we discussed in class as well as extra's. Or check out the barebones HTML guide on the link list on the side of this blog.

REQUIREMENTS:
• You must code this project in HTML from scratch.
• You must insert the proper HTML tags, Use appropriate headings to structure each of  your pages.
• Each page must contain a simple menu at the top for navigation, and a signature at the bottom to end the page such as your name, a quote or something else unique.
• Must have a total of  4 pages, more is allowed for extra credit. Page titles can be "Home, About, Contact, Favorite Websites, etc.."
• Include 1 image or photo on each page.
• Include at least 2 lists (ordered or unordered)
• Include at least 3 links to external websites (for instance the class blog etc...).
• You must include your email address either on your contact page or in your menu.
• Each page must have a background image or color
• Your home page must be titled "index.html" and be organized in a folder with all other html files and images.
• Make sure all pages have the .htm or .html extension and all images or photos are formatted for web correctly (jpg, gif, png) and reside in the same folder as the html files.


HTML NOTES:

Tags are used to format your text, text can be a link, a list, a paragraph, big, small, red, blue etc. In html tags are made like this:
<></>

You must always begin and end your tag, tags effect everything in between them. If you forget to end a tag it will effect everything after it. So to make some text look bold I would write my HTML like this:

Here is some <strong>bold</strong> text

And it would be rendered like this:

Here is some bold text


Remember that your document must be formatted, it has an html tag, plus a head and a body. Most of the content your site goes in the body. It basically looks like this:
<html>
      <head>
      </head>
             <body>
             </body>
</html>

You can also make the title of your document show up in the window. The title tag is:
<title>this is my website isn't it cool</title>

Other tags change the way text looks, like bold or italic. Try some of these others:
<i></i> makes text italic
<tt></tt> makes text teletype
<h1></h1> makes text into a header, 1 is the largest, 6 is the smallest
<hr></hr> puts a horizontal line on your page
<center></center> makes text align center
<blockquote></blockquote> makes the text indented

You can also format large pieces of text like a paragraph with the p tag:
<p></p>

If you want that paragraph oriented, you can add the align command:
align="center"
align="right"
align="left"

So if you want a paragraph that is left oriented, then your tag looks like this:
<p align="left"></p>

To make text into a link you can use the a tag. To link to a local document you can
write your html like this:
<a href="aboutme.html">About Me"</a>

If your link goes to an external site then you must include the entire URL like this:
<a href="http://www.myblogwebsite.com">My Blog"</a>

You can set the color of several different things in HTML. In the <body> tag, the bgcolortextlinkvlink, and alink attributes define the colors for the page background, text, unvisited links, visited links, and active links (i.e. the moment the link is being clicked on).

To change text color for part of a page, use the <font> container tag with a color attribute.

Color attribute values take one of the following forms:
"#RRGGBB", where RRGG, and BB are the red, green, and blue components of the color, in hex, ranging from 00 to FF.

One of sixteen "widely understood color names": aquablackbluefuchsiagraygreenlimemaroonnavyolivepurpleredsilvertealwhite (white), or yellow (yellow)

Hex code color chart from w3schools.com

HTML COLOR AND BACKGROUND TAGS
Adding color to your html files is easy. You can also use images for backgrounds as well.

Adding a background color is easy, add the bgcolor tag to your body tag. Pick a color from the chart above and type in the 6 digit hexadecimal code.
<body bgcolor="669933">

Adding a background image is easy too. Use the background tag to repeat an image across your background.
<body background="yourfilenamehere.jpg">

Check out these tags below to add color to text. Remember just wrap these tags around the text you want to modify.
<font size="3" color="red">This is some text!</font>
<font size="2" color="blue">This is some text!</font>
<font face="verdana" color="green">This is some text!</font>

Embedding images is easy too, but I will let you figure that one out on your own!  ;-)

Check out this website called HTML MADE EASY:


- Mr.Wilson



Ok have fun!

Monday, January 23, 2017

The Internet and Using Search Engines

Todays Agenda:
  • Lecture: The Internet
  • Search Engine Exercise


Search Engine Exercise:
Search engines allow you to search a database of web sites and files. Google and Bing allow you to search a directory of sites that have been registered by the site owners, for example yahoo. a Meta-search engine searchers other search engines, for example ixquick.

A good searching strategy is the key to finding the information you need:

Searching Tips:
  • Become familiar with more than one search engine, understand that different engines compile data differently. For example, google's boolean search technique is based upon popularity, but not always relevance
  • Be as specific as possible in your search terms. Use unique words or phrases
  • Use a niche site for your search, for instance amazon, or wikipedia
  • Use boolean operators in a meaningful manner (and, or, not)
  • Pay attention to publishing dates, file sources. Not everything on the internet is true
  • Don't give up easily, adjust your search terms. Experiment to find your results
  • BE A NINJA. Try using the Advanced Google Search
  • BE A SUPER NINJA. Try writing Advanced Google Search terms as code right in the browser!

Search Engine Ninja Exercise:
Research the questions below using a search engine or engines. Use advanced search techniques or specific sites to discover your answers. Compile the answers to all 10 questions and email them to me at sethwilson@sccs.santacruz.k12.ca.us

1. What does CSS and HTML stand for?
2. Who invented the worlds first Digital Camera?
3. What is the highest recorded temperature for Death Valley?
4. What is the HTML Tag that defines Emphasized Text?
5. How many Gigabytes in a Petabyte?
6. Who sent the worlds first Email?
7. What is the EFF and what do they do?
8. Who is Tycho Brahe and what part of his body was replaced with silver?
9. Who invented the font "Helvetica" and what is the meaning of its name?
10. What do the letters in HTTP and FTP stand for?

Compile your answers and email them to me. Make sure you include your name and title of this exercise in the subject of your email.