BrowserCheck 2
Download 28.04 Kb.
|
- Navigate this page:
- Ill provide some brief instructions on modification to get you started...
- Version History: 3.2
- For future versions
- Resource List
| BrowserCheck 3.2
Author: Shannon Meisenheimer, meisenheimer@ucmo.edu Files included:
The BrowserCheck package utilizes a combination of Java, Javascript, html and a tiny bit of VBscript to run some checks on the visitor's browser. We have been using it so our users can determine if their browser configuration is compatible with our Blackboard platform, but it can be used to test for client system compatibility with any web-based service or application. You will, at a minimum, need to modify portions of the Javascript files to meet what you deem "end-user compatibility" for your application. The index.html file may need some modification in terms of visual layout/design. I have provided a skeletal layout to get you started. You may need to add to or modify the .html structure and add some CSS to fit your institution's brand or design. All the files included need to reside in the same directory on a web server. The check.js file has all the script needed for reporting/checking:
The plugins.js file has all the script needed for reporting/checking for the presence of:
The PlatformCheck.class file detects the version and vendor of the Java Plugin. No modification needed here unless you want to change how this information is displayed to the user. You will need to decompile the class file. If you want the PlatformCheck.java file just let me know. This currently just shows the user the vendor and version of their Java plugin. It seemed easier to just report the version and have the user match it against a minimum requirement. It is possible to detect Java version through Javascript, but I am unsure how reliable it is. I’m currently using Javascript detection of Java on another project and may implement it if it proves consistent in performance. Keep in mind the plugin check is looking for browser plugins, not applications installed on the client system. Often the browser plugins are installed with the applications, but not always. I didn't design this part as a pass/fail check, as we don't require plugins be installed, nor require a minimum version. This just reports if the plugin is installed and attempts to determine the version if possible. Adobe has not yet created a Reader plugin for Firefox on Mac OSX, so it reports no plugin installed, even though Adobe Reader may be installed. I was going to add an alert warning the user of this if they are using FF on OSX, but I don't really like alert boxes. This is checking most common browsers and versions. I didn't bother checking for anything below Netscape 6.0, mostly because the agent strings are very vague and hard to identify. Netscape can probably be forgotten, but I’m reluctant to remove the legacy entries. I've included comments where I thought appropriate to help make modifications and for ease of understanding. You will need some knowledge of html and Javascript to modify the package to your needs, but it isn't too bad. I used Javascript over Java for the vast majority of it so it is easier and more convenient to make changes by others. I'll provide some brief instructions on modification to get you started... To change what constitutes a pass/fail/warning on browser and OS, modify the checkBrowser() function in check.js. For example the first case statement (Line 324), is executed for Internet Explorer. It first evaluates the OS and OS version and then passes through cases for each version of IE. You will see I have IE 10 (ieMax) passing the check and IE 8 (ieMin) and above failing for Windows 8 64-bit. The default condition is set to fail in the .html file and is also the default condition of the case statement (this would be any IE version lower than 8.0). With Bb now supporting stable release channels for Firefox and Chrome, you will need to be more diligent in updating what versions of these 2 browsers are supported. At the time of writing this, FF 23.0 and Chrome 29.0 were the stable channel versions (9.1 SP13 was tested on FF 20.0 and Chrome 26.0). I have set the logic to throw a warning on anything higher than the current stable release. As new browser versions are released in the stable channels, change the max variable for each browser (lines 15-26). As new versions of browsers and operating systems are released they may need to be added. Some of them are forward compatible and others aren't. It just depends on how the User Agent strings are constructed for a given browser/operating system pair. This would require potential changes to not only the checkBrowser() function, but also the switch statements that precede the checkBrowser() function. The other functions in check.js shouldn't need to be modified. The plugin piece is little more complicated to modify. The scripts used here are defined specifically for each plugin. You will need a broader understanding of Javascript to make changes to this file. Version History:
For future versions:
Resource List: I do not claim all the work done here is my own. The majority of the javascript (or at least the logic) used is available on the web, granted, I had to piece it all together...
Shannon -- meisenheimer@ucmo.edu Directory: bbcswebdav -> institution institution -> Running Cadence Sittin' on a mountain top, beating my drum institution -> Course number: mth 0105 meeting times: 5: 30-7: 50 mw section number institution -> Advanced Java Fall 2015 Syllabus Course Number: csys 2413 Business and Information Call Number: 14602 Technology Division Instructor institution -> Space policy institute elliott school of international affairs george washington university institution -> Sautomotive marketing and management course goals and objectives – semester transition 2010 am 1320 Role and Function of the American Automobile Dealership 3 credits Download 28.04 Kb. Share with your friends:
|