Mobile Detection and Redirection – Updated

A user of my Mobile Detection and Redirection script examples dropped by to comment and let me know that the scripts are working – but the mobile sites are not being indexed by google.  This is due to the fact that I neglected to include the Googlebot-Mobile User Agent in the function that detects mobile users and redirects them appropriately.  A quick change to the code and we’re all fixed up… thanks to John!


Here’s the updated downloadable code with examples.

[download id=”1″]


Puppet Module List Shows Funny Graphic Characters with PuTTY

Puppet is a configuration management tool that enables you to configure and maintain software and configurations across a wide variety of machines – rather than doing things manually.  Puppet enables you to package software and configurations into something called modules.  You can create these modules by hand or download some freely available modules from the repository available at

This post is just a quick note on how to fix a minor, annoying problem encountered when using puppet from the command line over a PuTTY session. The problem can be reproduced using the following command which lists the modules you’ve got installed in your puppet module repository.

[root@puppetmaster ~]# puppet module list
âââ camptocamp-tomcat (v0.0.1)
âââ puppet-wordpress (v0.0.2)
âââ puppetlabs-motd (v1.0.1)
âââ puppetlabs-pe_accounts (v1.0.2)
âââ puppetlabs-pe_compliance (v0.0.6)
âââ puppetlabs-pe_mcollective (v0.0.43)
âââ puppetlabs-stdlib (v2.3.1)

Notice the occurance of âââ . These characters are supposed to be translated by PuTTY into sweet looking line graphics. However, the default translation setting for your PuTTY Terminal session is set to Western European.

If we change this setting to UTF-8, we’ll see the characters get translated properly into the line graphics intended by puppet.

Hope this helps!

Tagged , , ,

Create a Simple Document Viewer with ExtJS

A document or report viewer is simply a tool that can be used to provide quick, indexed access to various PDF report files, image files or even word documents. You can easily index your documents as you author them but some versions of PDF tools don’t permit this. Another option would be to create a Microsoft Powerpoint slideshow – but this doesn’t give you the left-hand navigation tree capabilities of an indexed Adobe PDF (for example.)

I wanted to create a tool that could be used to provide visual access to many individual documents while presenting an easy-to-navigation tree structure based on the groupings or categories of these documents.

This article will provide the tools and examples necessary to enable you to create a simple, light-weight, portable (zip and go), cross-browser, web-based (serverless) document viewer. The intent is to have an archive that you can mail or carry on a thumb drive and distribute freely to customers, prospects or colleagues to enable quick and easy viewing and access to a collection of PDF or other files.

As I always do… let’s cut to the chase… looking for the downloads or source code?
[download id=”12″]

Before we start, I’ll also point you to the working demo / example.

A west region with a treeview control and a center panel with details that change as you select items from the treeview. This type of interface is ubiquitous and yet creating something like this to simply view documents may seem very difficult for folks that haven’t worked with javascript. The document viewer application was created to provide a mechanism for viewing collections of sample reports.  A design goal for this application was for it to be completely standalone – not requiring any additional software or web server to view the documents.

At the heart of this system is a perl script – This is a perl script that was written to create a javascript object notation assignment (JSON) used to populate a treeview control for the purpose of displaying example pdf reports with previews. In order to use this package to create your own custom file or report viewer, you must create a comma separated value (CSV) file with the following values.


Column 1 – Report file specifies the name of the PDF report file that will be downloadable from within the viewer.

Column 2 – Preview file specifies the name of the preview or thumbnail image that will be presented in the details pane of the viewer application.

Column 3 – Group specifies the treeview group where this report will be grouped.  You should sort your csv file so that groups are stored together.

Column 4 – Title specifies the title of the report and will be displayed in the details pane of when the user clicks on the report in the treeview.

Column 5 – Description specifies the details of what the report will show.


reportfile_number_one.pdf,preview_of_report_file_one.png,Group One, Example of a Report File One,This report shows some serious stuff.
reportfile_number_two.pdf,preview_of_report_file_two.png,Group One, Example of a Report File Two,This report shows some more serious stuff.
reportfile_number_three.pdf,preview_of_report_file_three.png,Group Two, Example of a Report File Three,This report shows some more serious stuff.
reportfile_number_four.pdf,preview_of_report_file_four.png,Group Two, Example of a Report File Four,This report shows some more serious stuff.
reportfile_number_five.pdf,preview_of_report_file_five.png,Group Two, Example of a Report File Five,This report shows some more serious stuff.
reportfile_number_six.pdf,preview_of_report_file_six.png,Group Three, Example of a Report File Six,This report shows some more serious stuff.
reportfile_number_seven.pdf,preview_of_report_file_seven.png,Group Three, Example of a Report File Seven,This report shows some more serious stuff.

You may include the column headers in your file – however, ensure that you use the --skipheader flag when executing the script.

Perl.  The script is written in perl so you will need an environment were you can execute perl scripts.  A subrequirement is that I’m using some libraries that you may not have installed in your perl environment.

Checkout if you get some errors about missing libraries.

Here’s an overview of the process to create your own custom document viewer.

  1. Download the [download id=”12″] package.  This will contain everything you need to

create and customize your own self contained document viewer.  Self contained

means that you don’t even need to host these documents and the viewer on a web

server… you can simply open the index.html file from a browser.

  1. Review the directory tree for the example package.
|-- css     Style Sheets
|-- extjs    Javascript Library for the treeview and panel components
|-- images    Various supporting image files (like icons, etc.)
|-- js    Javascript source files
|-- reports    Report directory - this is where you'll place the reports, pdfs and preview thumbnail files that will be displayed in the viewer.
|-- scripts    Scripts used to create and customize your viewer
  1. Since you’ll be creating your own document or report viewer, you’ll probably want to delete the contents of the reports directory.
  1. Create the report files that you’ll be displaying in the document viewer.  Report files can be PDF, PowerPoint (ppt) or Word Document (doc) files.  Typically, the report file examples are multi-page pdf files.  Once you have the report files, copy them into the reports directory in the base of the example package.
  1. Create a screenshot, or preview image that will be displayed in the preview section of the details panel when viewing the report.  zScreen is a great, free utility that lets you capture portions of your screen and save them to files.  I prefer ‘png’ format because of smaller size.  You’ll need to create one preview image for each report you plan to display in the document viewer.  Copy or place these preview image files into the reports directory along side the actual pdf or ppt report files.
  1. Now you’ll need to create a comma-separated file that contains the names of your report files, the groups they’ll be displayed in, the document titles and a description of each.  As previously mentioned the format for this file is REPORTFILE, PREVIEW, GROUP, TITLE, and DESCRIPTION.  You can find an example in the scripts directory in a file called example.csv.
  2. Create the documents.js file.  This is the file which contains the Javascript Notation (JSON) which is used to populate the treeview control as seen in this image.  The package contains a script named and can be found in the scripts directory of the example package.  This script should be run from the main directory of the archive and must be provided several command line options in order to execute properly.  The following is an example execution of the script:

scripts/ --csvfile scripts/example.csv --outputfile js/documents.js

This was executed from the base directory of the example archive file.  The –csvfile argument tells where to file the csv file that you created in step 5.  The –outputfile argument tells where to write the json.

It is important to note that the script assumes that you have not modified the directory layout and that you are storing your reports and previews or thumbnails in the “reports” directory.  You may run the script with “—help” to obtain additional information and options.

$ scripts/ --help

Usage: scripts/ --csvfile <filename> [--outputfile <filename.js>]
[--outputfile <outputfilename>] controls the output javascript filename - defaults to stdout
[--reportdir <reportdirectory>] specifies the directory where the pdf files may be stored
[--thumbdir <thumbnailedirectory>] specifies the directory where the thumbnail or preview image files may be stored
[--htmltitle <htmltitle>] specifies the title to be used in the report viewer html file
[[--overwrite] | [--nooverwrite]] - controls whether the output file will be overwritten

The following is an example of the resultant documents.js file that is created.

var json=[{"iconCls":"group","text":"Group One","children":[{"content":"reports/reportfile_number_one.pdf","description":"This report shows some serious stuff.","size":"16.23 KB","published":"01-29-2012","iconCls":"pdf","preview":"reports/preview_of_report_file_one.png","text":"Example of a Report File One","id":"1","leaf":"true"},{"content":"reports/reportfile_number_two.pdf","description":"This report shows some more serious stuff.","size":"16.23 KB","published":"01-29-2012","iconCls":"pdf","preview":"reports/preview_of_report_file_two.png","text":"Example of a Report File Two","id":"2","leaf":"true"}],"id":0.0960750988024337},{"iconCls":"group","text":"Group Three","children":[{"content":"reports/reportfile_number_six.pdf","description":"This report shows some more serious stuff.","size":"16.23 KB","published":"01-29-2012","iconCls":"pdf","preview":"reports/preview_of_report_file_six.png","text":"Example of a Report File Six","id":"6","leaf":"true"},{"content":"reports/reportfile_number_seven.pdf","description":"This report shows some more serious stuff.","size":"16.23 KB","published":"01-29-2012","iconCls":"pdf","preview":"reports/preview_of_report_file_seven.png","text":"Example of a Report File Seven","id":"7","leaf":"true"}],"id":0.119647523478733},{"iconCls":"group","text":"Group Two","children":[{"content":"reports/reportfile_number_three.pdf","description":"This report shows some more serious stuff.","size":"16.23 KB","published":"01-29-2012","iconCls":"pdf","preview":"reports/preview_of_report_file_three.png","text":"Example of a Report File Three","id":"3","leaf":"true"},{"content":"reports/reportfile_number_four.pdf","description":"This report shows some more serious stuff.","size":"16.23 KB","published":"01-29-2012","iconCls":"pdf","preview":"reports/preview_of_report_file_four.png","text":"Example of a Report File Four","id":"4","leaf":"true"},{"content":"reports/reportfile_number_five.pdf","description":"This report shows some more serious stuff.","size":"16.23 KB","published":"01-29-2012","iconCls":"pdf","preview":"reports/preview_of_report_file_five.png","text":"Example of a Report File Five","id":"5","leaf":"true"}],"id":0.423250772097287}]

var htmltitle='Example Report Viewer;'

Notice that the script determines the proper filetype and assigns the appropriate icon class – pdf for pdfs, ppt for ppts, etc.  Also note that the script determines the file size and date created.  These attributes are displayed in the details panel when viewing the documents.

Again… here’s the goods:
[download id=”12″]

Twitter Updates for 2012-01-23

  • Raising a (rather early) toast in honor of the passing of an amazing and inspirational man. (@ Devil's Alley) #

Testing a bug in the Graceful Sidebar Plugin

Debbie dropped by to let me know of a bug in the Graceful Sidebar Plugin. This post is testing out some fixes for the bug.

Test Post – Testing WPGeocode

[wpgc_ip] – IP Address of the reader
[wpgc_city] – City of the reader
[wpgc_state_name] – State name of the reader
[wpgc_state_code] – Two letter State code of the reader
[wpgc_country_name] – Country name of the reader
[wpgc_country_code] – Two letter Country code of the reader
[wpgc_latitude] – Latitude of the reader
[wpgc_longitude] – Latitude of the reader

[wpgc_is_nearby] – Uses the value you specify in the Nearby Range setting from the administrative panel

Graceful Sidebar Version 1.0.13 Released!

Support for the popular qTranslate plugin has been implemented inside the Graceful Sidebar Plugin. qTranslate enables bloggers to internationalize their content directly in the wordpress administrative console. qTranslate has a support forum that appears to be active with some good suggestions for using the plugin on your site. Cheers to Ozden for the suggestion to support this helpful plugin!

Tagged , ,