Journal 1

Since I have freelanced for several companies already I can say that I have and already do utilize the majority of the Web Development Processes mentioned in Article 1...Thank Goodness!
This article, none the less, was still great insight on how a design firm would undergo the design process. The main thing that I have taken from this article is the testing section. Although I do test the site and make sure that the images are optimized it loads fast I do admit that I am not one for making sure that all of the links work and I'm terribly bad at testing the sites in other browsers. I view them in Safari and FireFox because those are the 2 browsers I use, but other than that, bad me!

How I plan on implementing these techniques in my site is this: this class gives me the perfect opportunity to professionally go through the site, learn how to bill it properly, keep track of the hours that it took me to complete the graphics as well as the interface and possibly programming (since I am enrolled in a JS class as well).
I am also going to clean the pages up, keep the code on separate pages (.html on one pg, .css on another page and .js on its own as well. and last but not least I am going to learn more and utilize DIV tags. DIV tags are relatively new to me and since they are an important part of .js I am very interested in learning and utilizing these elements.

Journal 2

According to Article 2, the bad web design checklist, my website unfortunately qualifies for the WebPagesThatSuck.com website. While going through the checklist I definitely checked a few of the boxes off, which I didn't even know qualified my site as bad design. Sooo... Back to the drawing board, must get rid of these bad habits for the final project :)

Some of my bad habits include the overuse of graphics AND I am also shocked an appalled that using graphics for text is a bad idea. First, I tend to use more graphics when a client doesn't give me sufficient content for their pages and second I use graphical links rather than text links for my main navigation because I like to add effects to the text?? Not sure how to overcome this obstacle? Another bad habit I have is using black. I don't use black on every site I build, but I have used it quite a bit, especially on my portfolio website. I realize this is a bad idea, but black is my favorite non-color. Sorry! can't budge on that one... :)

as you can see I have a lot of bad habits to break throughout this semester, but that's why i took this course :) How I intend to fix this for the final... make sure load times aren't long, going to check the site in other browsers this time and last but not least... I am also going to prove to you that black can be done :)

Journal 3

the main 3 types of multimedia: Flash, RealOne and Quicktime

My favorite type of media is Flash. I like using Flash because you can add buttons to it that allows you to control the volume, scrub the video/ sound and provide interactivity to the user

I have never used RealOne before. I am assuming it would embed and play the same was as a quicktime movie. However, since it requires dedicated servers I am unsure of why I would want to use it?

Currently I have attached a quicktime movie to my journal page. It was quick and easy to attach. There is no interactivity, but it was a very quick way to embed a video within a page. I see no real reason to use it frequently considering the user has no control over the stopping, pausing or volume of the site which could get kind of annoying, especially if you have it set to looping.

Journal 4- Client Side Vs. Server Side Scripts

the advantages of client side scripting

they impose no load on the server since they do not directly interact with the server. Client scripts are usually visible to the clients and embedded within an html document attached via an external file. I think there are a few more advantages to server side scripting so therefore I can only think of the very same things that the book has mentioned.

The disadvantages of client side scripting

the clients user agent must support the scripting language.
You cannot write to the server and you cannot create a secure page without using the server, so all .js documents would be unsecure and you cannot prevent the user from seeing the code.

The advantages of Server Side scripting

Server side scripting does not require the user to download plug-ins, nor will you have to worry if the user's computer is configured to use it(such as .js) since server side scripting does not influence the client and even outputting to the client is optional. Server side code is executed before the .html is sent to the browser so your code is hidden and the client doesn't even need to know that there is a script running.
Scripts such as PHP have acccess to the servers file system and can therefore add security to your pages such as a shopping cart payment.

The disadvantages of Server Side scripting

server side scripting imposes more of a load on the server and access to the servers file system should be limited since the servers files would be of a more secure nature.

Triggering scripts

in order to trigger a script from an .html document using JS you would use the id element within the html page and use the document.getelementbyID within the javascript
in order to trigger a script using a server side language such as PHP I believe you would use either the $GET or $POST method?

hiding scripts from older browsers

you may want to view source to view this considering I don't know how to show code even though I've looked up things on the internet

here is my JS clock

Journal 5

Selectors- Selectors are the naming of a class or ID. Selectors match specific elements within an html and css document... and Javascript document even. They enable the user agent to identify what elements go with what style.

Classes- Identify tags in a document for use by their methods. Classes can be applied across several tags in a document.

ID's- Assigns a unique identifier to a tag. Scripts can access and manipulate tags based on their ID attribute. uses the # sign to access Identifiers that make it accessible by JS

Names- uhhhh don't recall seeing this anywhere in the book so I am going to take a shot in the dark and say that it is the actual naming convention for a selector such as .h1 or :visited.

Document Hierarchy, Inheritance and pseudo-classes

In CSS it is definitely important to understand document hierarchy and even more so when you incorporate JS into the mix. So far I am not quite sure the reason someone would use the round-about method of accessing a div (for example) via its hierarchical structure rather than just using a div class or identifier which seems to get directly to the point.

The one thing, though, that learning the DOM has done for me was drive home the style inheritance and the types of styles that take precedence over others. For example styling a simple paragraph tag versus styling a p.border tag. The styles of the p.border tag would prevail based on the rules of specificity.

From what I understand of pseudo-classes it looks as though pseudo-classes are a bit more specific in the styling sense. Pseudo-classes start with a : before the class and can be used to style :hover :visited links as well as designate language tags and more specific style elements.

Journal 6

Journal 7

Journal 8

Journal 9

Journal 10

Journal 11

Journal 12

Journal 13

Journal 14

Journal 15

Journal 16