Oh hey, this is the end. Well, it's about time! I need a holiday break and what better holiday than Christmas! The journey, it was long and dangerous. It started out fine and refreshing since the first half of the semester was HTML and CSS. You know, that stuff we learned from a previous class so when a assignment came along, we looked at it and did our work without mass confusion.
But, there came something from the east. A dark and foreboding storm was rising overhead and there we saw... JavaScript! It was new, strange and it wasn't exactly friendly. We accepted the challenge of learning this new technology, but it was something quite different compared to HTML and CSS. The assignments were tough, and for an online class I felt like I wasn't getting enough out of the class if I were to actually apply it in a work related environment. I'm not sure if I really did learn much, since it was more like getting the assignment done on time was the top priority than actually understanding the material.
I don't know if I'll be dealing with JavaScript as I seek further education. If I do, I'll definitely need to be in a class and actually see more of the programming done right in front of me. I definitely learned how to learn with the aid of friends, but sometimes I think I was venting out frustration along with them. I'm not sure, but I do know a glorious and bright day will arrive. All that lies in front of it is a final.
Thursday, December 11, 2008
Sunday, November 30, 2008
Events
JavaScript has been really challenging lately and events added onto that struggle. Thinking about events, I can say we all have ran into events on websites before. I think that events, if planned out in advance, can be easily accomplished in regards to simple tasks.
However, I found it rather frustrating trying to incorporate events into my website that I've been, on a step-by-step process, building together. I now see that CSS can have a huge effect on JavaScript because CSS alters the appearance of your content, whereas JavaScript relies on the shape of your content to act a certain way.
My problem was that my links based on my entire website's style versus the style of the accordion event were interfering with each other. I think I know why accordion is used mainly for navigation, because links specified for navigation could be set with the accordion style. Therefore, that would leave all the links in the content alone.
What I ended up doing was setting a style in the head of the HTML file for the pages that have links. I couldn't exactly get the accordion links to act separate from the content, so I had to pull my site in reverse and start building parts of it over. It was not a simple tasks. :|
Overall, if I had planned on using events from the beginning, I think I wouldn't have had much trouble. Events are useful no doubt, but I sometimes think that using a lot of advance markup can clash with other markup and make a mess of your site. What may have started out as a chore could have ended up as a fierce struggle between man and beast!
However, I found it rather frustrating trying to incorporate events into my website that I've been, on a step-by-step process, building together. I now see that CSS can have a huge effect on JavaScript because CSS alters the appearance of your content, whereas JavaScript relies on the shape of your content to act a certain way.
My problem was that my links based on my entire website's style versus the style of the accordion event were interfering with each other. I think I know why accordion is used mainly for navigation, because links specified for navigation could be set with the accordion style. Therefore, that would leave all the links in the content alone.
What I ended up doing was setting a style in the head of the HTML file for the pages that have links. I couldn't exactly get the accordion links to act separate from the content, so I had to pull my site in reverse and start building parts of it over. It was not a simple tasks. :|
Overall, if I had planned on using events from the beginning, I think I wouldn't have had much trouble. Events are useful no doubt, but I sometimes think that using a lot of advance markup can clash with other markup and make a mess of your site. What may have started out as a chore could have ended up as a fierce struggle between man and beast!
Tuesday, November 18, 2008
DOM
As we should all know by now, DOM stands for Document Object Model. The definition given by W3C states that "the DOM is a platform- and language-neutral interface that will allow programs and scripts to dynamically access and update the content, structure and style of documents."
The overall concept of the DOM is to create a standard for all the HTML, styles, and script that have to be animated into a web page. The vendors will then have a set way to manage and create for the Web and should make for a sort of compatibility across the Web as well.
As for my personal opinion on the DOM, I like it. I mean, it works for me and it makes sense considering it flows in that tree chart, or whatever it's called. I'm not sure what else they did or could do to manage the way all the elements of a HTML file would appear on the Web. So, either way, it works for me and that's fine.
The overall concept of the DOM is to create a standard for all the HTML, styles, and script that have to be animated into a web page. The vendors will then have a set way to manage and create for the Web and should make for a sort of compatibility across the Web as well.
As for my personal opinion on the DOM, I like it. I mean, it works for me and it makes sense considering it flows in that tree chart, or whatever it's called. I'm not sure what else they did or could do to manage the way all the elements of a HTML file would appear on the Web. So, either way, it works for me and that's fine.
Tuesday, November 4, 2008
JavaScript
My first impression of JavaScript was, and I quote, "What the..." as my mouth hung open for a minute or so.
JavaScript is still confusing to me. I'll think I've got it down, but something else will pop-up and make me scratch my head. I know I'm going to have to learn this stuff if I want to work with Web and it is the first real time I'm looking at this stuff. I'm just hoping that I'll catch on to the JavaScript know-how.
JavaScript and Java can be easily confused. If you're unaware to the concept of either, I can see why. You might think someone is just shortening JavaScript if they say "Java", but it can mean a whole world of difference if you've got the knowledge. Java is a much larger and more complicated language that creates "standalone" applications. JavaScript only works in an HTML document and is read and enacted by a web browser. A scripting language is a programming language interpreted by another program and is usually typed on a keyboard.
JavaScript was originally named "Mocha" and developed by Brendan Eich of Netscape. It was later changed to LiveScript and then finally to JavaScript. The reason for the name "JavaScript" could have been because of the added Java support for Netscape's web browser, Navigator. Now that more browsers have support for JavaScript, it is becoming more popular and accepted.
JavaScript is still confusing to me. I'll think I've got it down, but something else will pop-up and make me scratch my head. I know I'm going to have to learn this stuff if I want to work with Web and it is the first real time I'm looking at this stuff. I'm just hoping that I'll catch on to the JavaScript know-how.
JavaScript and Java can be easily confused. If you're unaware to the concept of either, I can see why. You might think someone is just shortening JavaScript if they say "Java", but it can mean a whole world of difference if you've got the knowledge. Java is a much larger and more complicated language that creates "standalone" applications. JavaScript only works in an HTML document and is read and enacted by a web browser. A scripting language is a programming language interpreted by another program and is usually typed on a keyboard.
JavaScript was originally named "Mocha" and developed by Brendan Eich of Netscape. It was later changed to LiveScript and then finally to JavaScript. The reason for the name "JavaScript" could have been because of the added Java support for Netscape's web browser, Navigator. Now that more browsers have support for JavaScript, it is becoming more popular and accepted.
Sunday, October 12, 2008
Mobile Devices
Mobile devices are a great way to check the Web when you're on the go or away from your computer. It seems that almost all mobile devices today have web capabilities. Yet, each mobile device is unique. Different screen resolution, screen dimensions, and shapes.
It could be very important for one to develop a mobile device oriented site. I guess it might depend on what site you design, like say a sales website. Either way, knowing how to develop a site for a mobile device will eventually be a must the way I see it. The future seems to hold the promise that everyone will have a personal mobile device that will perform multimedia tasks. Browsing the Web happens to be one of those tasks.
What technology excites me is the actual mobile devices that can connect to the Web, along with their other features. In a sense, they're like mini laptops. Especially ones with a full keyboard and wide screen that could easily function for the Web.
It could be very important for one to develop a mobile device oriented site. I guess it might depend on what site you design, like say a sales website. Either way, knowing how to develop a site for a mobile device will eventually be a must the way I see it. The future seems to hold the promise that everyone will have a personal mobile device that will perform multimedia tasks. Browsing the Web happens to be one of those tasks.
What technology excites me is the actual mobile devices that can connect to the Web, along with their other features. In a sense, they're like mini laptops. Especially ones with a full keyboard and wide screen that could easily function for the Web.
Sunday, October 5, 2008
Accessibility
While doing research, I came across the Web Content Accessibility Guidelines (WCAG), which happens to be published by the W3C's Web Accessibility Initiative. Not only are these guidelines about making content more accessible for disabled users, but also for all user agents, including highly limited devices.
There are three priority levels to these guidelines:
Priority 1: Web developers must satisfy these requirements, otherwise it will be impossible for one or more groups to access the Web content.
Priority 2: Web developers should satisfy these requirements, otherwise some groups will find it difficult to access the Web content.
Priority 3: Web developers may satisfy these requirements, in order to make it easier for some groups to access the Web content.
Web accessibility in general aims to address: Visual, Mobility, Auditory, Seizures, and Cognitive issues amongst users. By following the 14 guidelines of the WCAG, you should be able to make your website accessible.
I think it's important to keep your website accessible because you want all users to be able to see and read your content. If someone with a disability tries to access your website, with say a screen reader, if your website isn't accessible for them, the screen reader won't be able to communicate the content properly. It's almost as if you're keeping these users out and only allowing fully able users into your "club".
There are three priority levels to these guidelines:
Priority 1: Web developers must satisfy these requirements, otherwise it will be impossible for one or more groups to access the Web content.
Priority 2: Web developers should satisfy these requirements, otherwise some groups will find it difficult to access the Web content.
Priority 3: Web developers may satisfy these requirements, in order to make it easier for some groups to access the Web content.
Web accessibility in general aims to address: Visual, Mobility, Auditory, Seizures, and Cognitive issues amongst users. By following the 14 guidelines of the WCAG, you should be able to make your website accessible.
I think it's important to keep your website accessible because you want all users to be able to see and read your content. If someone with a disability tries to access your website, with say a screen reader, if your website isn't accessible for them, the screen reader won't be able to communicate the content properly. It's almost as if you're keeping these users out and only allowing fully able users into your "club".
Sunday, September 21, 2008
Analyzed Websites
The first website that came to mind was www.ign.com. IGN stand for "Imagine Games Network", but they don't just deal with videogames. All kinds of media is reported and reviewed at IGN and it is a great place ot find updates on movies, DVDs, games, music, anime, comics, and TV. Ironically, IGN just redesigned their website a few days ago. The entire site hasn't been updated just yet, but the home page is a perfect example of what the entire site will look like. Personally, I'm fine with the style and look of the new site, though there are some complaints. There's defintely more ad space than previously before, and the new navigation will take some getting use to. This website of course uses CSS to style its layout. It has six errors when I went to validate on the W3C Validator. The site in my opinion is still, in a way, user-friendly because the navigation is at the top and the different categories are listed. Hopefully when the whole website is finished updating, it'll look like it's intended.
The second website I visited often is www.penny-arcade.com. It's a webcomic site where the characters, Gabe and Tyco, discuss (in a way...) current issues in the media, though they tend to focus the electronic (computers, videogames, etc) side of it. It's a simple website to begin with. It's basically a blog with links to other portions of the site. There's links to the comics, forums, store, and other works and events. It doesn't look like they use tables for their layout, so it's safe to assume they use CSS. It's just the site isn't too complex since as I said, it's like a blog with links to their comics. There are about three errors for the site according to the W3C Validator. It's easy enough to navigate throughout the site and that's what I like about the site besides the humor I find in the comics. The one and only thing I don't like is that if there isn't enough text posted in the blog portion, the ads will extend the webpage and leave empty space. This isn't a very constant problem though since most of the time they have more than enough to talk about.
The last and the site I think is pretty bad is www.msn.com. Ironically, I have this site as my home page, but I hardly spend time on the site to really take advantage of it. I'll usually see what's the top stories and uses the email service. Technically, MSN is just a page of links to their articles and other media. It's easy to click on links, no doubt, but it doesn't look that appealing. It's all blue text because of every statement, phrase, and line is a link to a video or article. I don't know why, and I hope it's not meant to be, but when I view the page source.... everything is on a single line. It also seems like the website uses CSS and surprisingly, the site validates on the W3C Validator. I mean, I like it when I just chance at it when my browser first opens, but overall, I can't stay on MSN for an extended period of time.
The second website I visited often is www.penny-arcade.com. It's a webcomic site where the characters, Gabe and Tyco, discuss (in a way...) current issues in the media, though they tend to focus the electronic (computers, videogames, etc) side of it. It's a simple website to begin with. It's basically a blog with links to other portions of the site. There's links to the comics, forums, store, and other works and events. It doesn't look like they use tables for their layout, so it's safe to assume they use CSS. It's just the site isn't too complex since as I said, it's like a blog with links to their comics. There are about three errors for the site according to the W3C Validator. It's easy enough to navigate throughout the site and that's what I like about the site besides the humor I find in the comics. The one and only thing I don't like is that if there isn't enough text posted in the blog portion, the ads will extend the webpage and leave empty space. This isn't a very constant problem though since most of the time they have more than enough to talk about.
The last and the site I think is pretty bad is www.msn.com. Ironically, I have this site as my home page, but I hardly spend time on the site to really take advantage of it. I'll usually see what's the top stories and uses the email service. Technically, MSN is just a page of links to their articles and other media. It's easy to click on links, no doubt, but it doesn't look that appealing. It's all blue text because of every statement, phrase, and line is a link to a video or article. I don't know why, and I hope it's not meant to be, but when I view the page source.... everything is on a single line. It also seems like the website uses CSS and surprisingly, the site validates on the W3C Validator. I mean, I like it when I just chance at it when my browser first opens, but overall, I can't stay on MSN for an extended period of time.
Subscribe to:
Posts (Atom)
