Wednesday, March 14, 2012

Week 10 Reading Notes

This week I greatly enjoyed Doug Tidwell's "Introduction to XML" article - Finally, an article about programming that does not presume tons of background information! And is written in normal English! I especially enjoyed Section 4, "Defining document content," which did a good job of describing DTD, Document Type Definition.

Although Ogbuji's "A survey of XML standards" presumed too much background information, it gave me a clear description on the process by which certain coding practices become standards. And his article thoughtfully gathered different standards communities together and described their different standards-making processes one-by-one. This is a useful tool for anyone who would like to know what goes in behind the scenes.

I strongly believe that I am learning more from actually doing the labs, and not that much from the readings. When I follow Evgeny's labs step-by-step, and actually do the work, then I understand the material.

There is an old Chinese proverb on learning that goes: "To hear is to forget. To see is to remember. To do is to understand." I think these learning principles can still be applied to learning 21st century programming languages! I would like to see LIS 2600 developed such that there is very little reading, but longer and richer screencasts, with more complicated labs.

Saturday, March 3, 2012

Week 9 Reading Notes

I am very excited about some of HTML5's new features, particularly (a) semantic replacements for generic block and inline elements; and (b) the ability to script APIs. (a) will make coding more user-friendly; and (b) will help programmers plug-in more cutting edge APIs more easily.

I am surprised that the HTML5 syntax is no longer based on SGML . . . Might there be problems for browsers to read HTML5, in the light that most browsers were programmed to read older versions of HTML? I wonder whether WHATWG coordinates with browser programmers to make interoperability a living reality, and not just a fancy idea!

There is an HTML5 browser test that seems to show Google Chrome and Firefox leading the way! Yay for Chrome users =) .

Week 8 Lab

Revised Index File:


New CSS Style File:


Wednesday, February 22, 2012

Week 7 Lab

http://www.pitt.edu/~edh25/index.html

Week 8 Reading Notes

I have some thoughts regarding last week's CamTasia lecture.

First, what new librarians really need is a "best practices" guide on how to design a library website. With so many options like FrontPage, Dreamweaver, and LibGuides, librarians are faced with so many platform options that they don't know which one to use to design a website.

Second, because librarians may be employing the above platforms to design library websites, what is the value in learning HTML? Now I know that we should have at least an elementary knowledge of HTML, but what is the scope of that elementary knowledge? Are we learning too much HTML, and should we spend more time learning a website design platform, like Frontpage or Dreamweaver?

I feel that library schools must define the scope of basic website development skills more clearly, so that we are not wasting time on knowledge which we will not use. If we don't use a certain piece of knowledge, it's obsolete and we will forget it.

Third, it is very hard to read this week's readings on Cascading Style Sheets before doing the lab. We should be assigned both the reading and the lab at the same time, so we can get a firm comprehension on what CSSes are. I believe this will be more useful for future LIS 2600 students in the future.

Just my two cents!

Wednesday, February 15, 2012

Week 6 Lab


Barcode is 0088888888




Week 7 Reading Notes

After reading "Beyond HTML," I felt that it was outdated. For example, Goans, Leach and Vogel seem to emphasize the importance for librarians of learning HTML.

While I believe that all librarians should have a basic knowledge of HTML, I believe there is an "easy" solution that may help librarians. Institutions can subscribe to Springer LibGuides, to permit their librarians to create LibGuides which are similar in look, content, and feel. We at Temple employ LibGuides and are able to customize them within limits. Therefore, we don't need to know the details of setting up or navigating a CMS that much. The drawback, of course, is that Springer LibGuides costs money annually. A CMS-system customized to one's institution would cost time and effort upfront, but later, one may not need to pay for it.