This site gives the latest browser use statistics and some links to more specialized markets. Scroll down for their summary.
For the incredibly detailed, here is a site that keeps a copy of every browser ever made!
Several of you have commented on how differently your work looks from platform to platform and even on different browsers on the same platform. This is an unfortunate reality of Web authoring, and it only gets worse as you push the limits. The only answer is to have as many browsers as possible on your authoring computer. Fortunately, they are free for the most part.
In reality, at least one statistics place cites Internet Explorer 5 and 6 having 85% of the market (down from a high of 94%), so if your site looks and works on one of those two browsers on Windows you are in very good shape. But education and academic markets do have Netscape hanging around because of Composer, the only free graphical Web authoring tool. So you will probably want a copy of Netscape 4.x (usually 4.7somthing) and possibly the new Netscape 6 or 7.
Mac users should either go to a PC lab and test or get a copy of Virtual PC to run the Windows browsers on your authoring machine. You will often find great differences in your design on a Wintel box. Virtual PC was recently engulfed by Microsoft; I used to use it but now just go to a lab.
Sometimes you just get to where you can't find what's wrong with your Web page. Or perhaps you just want to be sure your software is writing things well. When you get to this point, its time for a trip to the validator. It's free and available online.
First, take the Webmonkey's short tutorial on validating HTML code online. This will ensure your code is free of bugs that will keep it from working on all platforms.
On the Mac, it can be a stand alone program or a plugin. In BBEdit, you can use a nice program call BBTidy, which is downloaded from a different site. Install in in the BBEdit Plugins folder.
One of the real advantages of working in a dynamic medium like the web is that you can go from planning into the actual production of the site very quickly. I describe this process as developing a site skeleton. The process is fairly simple:
Once the skeleton is finished, then your development process involves going to each page and adding elements to it. In other words, you "flesh out" the skeleton, if that's not taking the metaphor too far into the macabre.
This is a planning step that I hope you will find useful when working on future Web sites, including this week's work with the WebQuest.
Step 4: Begin to collect the content for your site. Look for text, graphics and any other useful elements that would help your quest teach.
Use the text as a starting point, but see if there are other resources on the web that express your chosen lesson more clearly.
This is also the time to start finding and bookmarking the sites your students will use to complete the WebQuest.
Step 5: Create a planning document based upon the past week's readings.
Include at least the following:
Step 6: Using the above instructions, start a site skeleton for your WebQuest. Then add the content and upload it to a directory called "webquest" in your Web folder on our course server.
Thursday, April 13, 2006 9:56 AM