https://www.blogger.com/comment.g?blogID=3799366651359702810&postID=420224074924324973&page=1
https://www.blogger.com/comment.g?blogID=7821109072135779287&postID=2584970093813856530&page=1
Thursday, October 23, 2008
Wednesday, October 22, 2008
Muddiest Point Week 8
I'm not sure I understand how to upload the html files for my webpage onto the FTP server at Pitt. Are there instructions for this somewhere on Pitt's webpage?
I am going to look and see if there are any, and if so I'll post a link to the information.
So far I have found this document: http://technology.pitt.edu/Documentation/html_inst.pdf
I am going to look and see if there are any, and if so I'll post a link to the information.
So far I have found this document: http://technology.pitt.edu/Documentation/html_inst.pdf
Monday, October 20, 2008
Week 9 Required Readings
All of the readings for XML left me confused. I felt like there was some simple part I was missing or was not explained. In the resources for the IBM reading on XML there was a link for a Intro to XML tutorial. I found doing this tutorial which is free, but you have to register with IBM, helped me understand just what the creation of XML was for.
A user can create specific tags with in a document to denote for example if it is a title or a postal code. This makes finding these elements of a document easier.
A tag is anything between brackets - < >
An element is a type of a tag. If you break down the tag, it could include <blue>, <red>, <green>, etc.
An attribute - is a name value pair. I can't think of a good example of this.
It enable records to be read faster by different pieces of software. It also makes the web easier to search. If you are looking for postal codes it will somehow know to only search for fields labeled postal code.
The document must follow a specific set of rules that would be set down in a DTD (document type definition).
XML is more strict than HTML. You need to make sure all of your elements are ended, in the right order, and they are case sensitive, otherwise you will get an error message.
Introduction to XML: http://burks.bton.ac.uk/burks/internet/web/xmlintro.htm
This gives some background on XML, but I didn't understand what they meant. I needed some physical examples. Which is why I liked the tutorial I did above, even though it too ended up over my head.
A survey of Standards: http://www.ibm.com/developerworks/xml/library/x-stand1.html
This gives a list of standards for XML that have been made over time by various authorities on the internet. I found the links in this document to be rather helpful.
Introduction to XML Schema: http://www.w3schools.com/Schema/schema_intro.asp
This is like the HTML tutorials from last week. It gives examples of what the XML documents would look like and examples of how to code them.
Extending Your Markup: An XML Tutorial
This is another explanation of the elements that make up XML.
A user can create specific tags with in a document to denote for example if it is a title or a postal code. This makes finding these elements of a document easier.
A tag is anything between brackets - < >
An element is a type of a tag. If you break down the tag
An attribute - is a name value pair. I can't think of a good example of this.
It enable records to be read faster by different pieces of software. It also makes the web easier to search. If you are looking for postal codes it will somehow know to only search for fields labeled postal code.
The document must follow a specific set of rules that would be set down in a DTD (document type definition).
XML is more strict than HTML. You need to make sure all of your elements are ended, in the right order, and they are case sensitive, otherwise you will get an error message.
Introduction to XML: http://burks.bton.ac.uk/burks/internet/web/xmlintro.htm
This gives some background on XML, but I didn't understand what they meant. I needed some physical examples. Which is why I liked the tutorial I did above, even though it too ended up over my head.
A survey of Standards: http://www.ibm.com/developerworks/xml/library/x-stand1.html
This gives a list of standards for XML that have been made over time by various authorities on the internet. I found the links in this document to be rather helpful.
Introduction to XML Schema: http://www.w3schools.com/Schema/schema_intro.asp
This is like the HTML tutorials from last week. It gives examples of what the XML documents would look like and examples of how to code them.
Extending Your Markup: An XML Tutorial
This is another explanation of the elements that make up XML.
Thursday, October 9, 2008
Week 7 Muddiest Point
When I am in Downtown Pittsburgh, my IPod sometimes picks up a "Free Wi-FI" connection that I do not believe is the free two hours a day WiFi. When I looked it up online, I found out some of these may be up to nefarious things, and that when you are connected to most public wi-fi spots your computer may be at risk. Is their anyway to protect your computer and information? Also how can you tell the difference between a legit WiFi connection and one that is up to no good?
Wednesday, October 8, 2008
Assignment 5 - Koha
Here is my link to assignment 5. My topic of interest was books for a Consumer Health Library.
http://pitt4.kohawc.liblime.com/cgi-bin/koha/bookshelves/shelves.pl?viewshelf=8
http://pitt4.kohawc.liblime.com/cgi-bin/koha/bookshelves/shelves.pl?viewshelf=8
Week 8 Required Readings
http://www.w3schools.com/HTML/ - W3 HTML Tutorial
This is a tutorial teaching the elements of html. It introduces them slowly, one by one. Each building on the other. The first and last time I used html was in 1997. I had just stolen bits of code from other source codes on websites. This gives a clear example of what each piece of html is and does.
The article points out that upper vs. lower case letters are unimportant, but the WC3 thinks that lower case letters should be used, just in case they ever change their minds.
A lot of the commands in HTML are pretty straight forward, italics is represented by an "i", subscript is "sub" and so forth. I liked that "try it" editors were available to mess with the code in a hands on fashion.
HTML Cheatsheet - http://www.webmonkey.com/reference/HTML_Cheatsheet/
This document provided a list of easy to use HTML codes.
3.) Learning CSS: http://www.w3schools.com/css/css_intro.asp
CSS stands for Cascading Style Sheet, this coding was developed to take care of the problem with using font formats in html. Apparently this was expensive for web designers to use.
Using a style sheet seems to make the coding of colors and backgrounds easier. Instead of having to redo that code in every web page, these are files where they can be inserted, and will show the font how they want it to be displayed. This page is a good example of how this works.
It works like the HTML tutorial by giving specific examples to each element of a web page.
Beyond HTML
This articles looks at an academic library that let their librarians run free with Front Page to create web pages about their part of the library. I initially thought this would lead to creativity in each department. Everyone would have their own unique online voice. However, they were given little to no training. This lead to every page being different, which made it difficult for students to use the webpages to locate information. The new CMS uses CSS coding. This innovation led to a more uniform approach to the librarians web pages. It also made it easier for the students to navigate.
The way they went about implimenting it, I thought was practicle. It is hard to switch everyone over to a new system at once, so doing it piecemeal made sense. Also, they were training people how to use it, which was a step ahead of the old Front Page system.
This is a tutorial teaching the elements of html. It introduces them slowly, one by one. Each building on the other. The first and last time I used html was in 1997. I had just stolen bits of code from other source codes on websites. This gives a clear example of what each piece of html is and does.
The article points out that upper vs. lower case letters are unimportant, but the WC3 thinks that lower case letters should be used, just in case they ever change their minds.
A lot of the commands in HTML are pretty straight forward, italics is represented by an "i", subscript is "sub" and so forth. I liked that "try it" editors were available to mess with the code in a hands on fashion.
HTML Cheatsheet - http://www.webmonkey.com/reference/HTML_Cheatsheet/
This document provided a list of easy to use HTML codes.
3.) Learning CSS: http://www.w3schools.com/css/css_intro.asp
CSS stands for Cascading Style Sheet, this coding was developed to take care of the problem with using font formats in html. Apparently this was expensive for web designers to use.
Using a style sheet seems to make the coding of colors and backgrounds easier. Instead of having to redo that code in every web page, these are files where they can be inserted, and will show the font how they want it to be displayed. This page is a good example of how this works.
It works like the HTML tutorial by giving specific examples to each element of a web page.
Beyond HTML
This articles looks at an academic library that let their librarians run free with Front Page to create web pages about their part of the library. I initially thought this would lead to creativity in each department. Everyone would have their own unique online voice. However, they were given little to no training. This lead to every page being different, which made it difficult for students to use the webpages to locate information. The new CMS uses CSS coding. This innovation led to a more uniform approach to the librarians web pages. It also made it easier for the students to navigate.
The way they went about implimenting it, I thought was practicle. It is hard to switch everyone over to a new system at once, so doing it piecemeal made sense. Also, they were training people how to use it, which was a step ahead of the old Front Page system.
Sunday, October 5, 2008
Assignment 4 Jing Project
In my screen cast I teach people how to use the Drug Identification Wizard. My flickr screen shots show how to install the HON Code Toolbar.
Links to Flickr
1. http://www.flickr.com/photos/27567778@N08/2916271653/in/set-72157607582455477/
2. http://www.flickr.com/photos/27567778@N08/2917166484/in/set-72157607582455477/
3. http://www.flickr.com/photos/27567778@N08/2917178296/in/set-72157607582455477/
4. http://www.flickr.com/photos/27567778@N08/2916387559/in/set-72157607582455477/
5. http://www.flickr.com/photos/27567778@N08/2917221320/in/set-72157607582455477/
Link to Jing Project
http://screencast.com/t/B3sJ9KOVF
Links to Flickr
1. http://www.flickr.com/photos/27567778@N08/2916271653/in/set-72157607582455477/
2. http://www.flickr.com/photos/27567778@N08/2917166484/in/set-72157607582455477/
3. http://www.flickr.com/photos/27567778@N08/2917178296/in/set-72157607582455477/
4. http://www.flickr.com/photos/27567778@N08/2916387559/in/set-72157607582455477/
5. http://www.flickr.com/photos/27567778@N08/2917221320/in/set-72157607582455477/
Link to Jing Project
http://screencast.com/t/B3sJ9KOVF
Subscribe to:
Posts (Atom)
