1

files.length

Which returned undefined. So if there is no length property present, an easy way to count the number of keys or properties of an object in ES5-compliant javascript environments like Node.js is to use the Object prototype directly:

1

Object.keys(files).length

A little more typing, but it is fast, efficient, and most importantly: already built-in.

I was able to arrive at this solution by combining the one-line comment with the comment block in a way that takes advantage of the rules the different types of comments have to follow.

The One-Line Comment

One-line comment rules dictate that everything after the comment characters must be ignored for the rest of that line. They look like this:

1
2
3
4
5

// My code below
$someVar = array("foo", "bar", "blah");
echo "<code>";
print_r($someVar);
echo "</code>";

The Block Comment

Block comment rules dictate that once the beginning characters are started, everything up until the ending characters is ignored. They look like this:

1
2
3
4
5
6

/* My code below
$someVar = array("foo", "bar", "blah");
echo "<code>";
print_r($someVar);
echo "</code>";
*/

Combining The Two: The Best of Both Worlds

Using both those comment style rules, we can combine the two comment styles in a way that will allow us to comment and un-comment a block of code with by adding or deleting a single character. The trick is to make both the beginning and ending lines both single-line AND block style comments, like so:

1
2
3
4
5
6

//* My code below
$someVar = array("foo", "bar", "blah");
echo "<code>";
print_r($someVar);
echo "</code>";
// */

In the above example, you notice that the code will still run – it’s not commented out because the first line is following the rules of the single-line comment – ignoring the block comment declaration on the same line. By removing the first backslash at the beginning of the block, we can comment out the entire code block by enabling the block comment style instead of the single-line style. The last single-comment line is ignored because the block comment rules ignore everything up until the end block comment declaration at the end of the line:

1
2
3
4
5
6

/* My code below
$someVar = array("foo", "bar", "blah");
echo "<code>";
print_r($someVar);
echo "</code>";
// */

So a single character – a backslash at the very beginning of the block declaration can now comment or un-comment the entire block by switching the comment rules back and forth between single-line and block style. The code examples provided are in PHP, but this trick will work with any language that supports both single-line and block style comments.

The dashboard is the place for the most important things to be.  it should be the single place you can view to and get an overview of all the most important things about your website regarding your visitors without having to drill deeper or go through multiple pages or sub-sections.  But the default dashboard Analytics starts you off with is all wrong, and is almost never the information I really want to see.  Let’s see how we can fix this.

The Default Dashboard

Google Analytics Default Dashboard Setup

The first thing to note here is the repetitive information.  The “Visitors Overview” widget is the first thing you want to get rid of.  The exact same information is displayed larger above – no use in repeating the same information twice in the same screen area.  To the right of that is the “Map Overlay” widget.  While this information may be neat to see, it’s not really the real information you need day to day.  That one’s leaving our dashboard too.  So that leaves the two bottom widgets – “Traffic Sources Overview” and “Content Overview”.  These both can stay, but perhaps can be arranged a bit differently.

The Information You Need

For most webmasters, there are essentially two important questions: “How are visitors getting to my website?” and “What are visitors doing on my website?“.  The widgets we select for our dashboard must help us quickly answer those every day questions without having to drill any deeper or take any more of our time.  We also need only the information that isn’t already present on the dashboard that we can’t edit.

A More Useful Dashboard

Google Analytics Customized Dashboard

With a customized dashboard, we can now have the information we really need on a daily basis that help us answer our every day questions:

How are visitors getting to my website?
I can clearly see here that the dominant source is Google searches, followed by direct type-ins and the typo domain that redirects to the real site.  I can also see the top search keywords that visitors used to reach my website, which is very useful for measuring SEO effectiveness.

Another dashboard widget I like to have to help answer this question is the “Referring Sites” widget.  This tells me the actual websites referring visitors to me through links.  This is especially helpful if the site gets mentioned in a blog post or article so you can know about it quickly.

If you run any Google Adwords campaigns, there is also an Adwords section and a dashboard widget for campaign clickthroughs and conversions that may be helpful.

What are visitors doing on my website?
This question may take a bit more analysis to answer because there are many parts to this.  The “Content Overview” widget helps us spot the most popular pages and areas of the website, which helps us solve most of this question.

Taking the analysis further, you may want to setup conversion goals and add a dashboard widget to display the number of daily goal conversions.  You can also add widgets for the entrance and exit pages, among many other things.

Conclusion

Most of the time for most of my websites, I have only the widgets above shown on the customized dashboard image above.  The great thing about Google Analytics is that it can be customized with any widgets you want to display.  So although the default widgets are not particularly useful on a day to day basis, they can easily be replaced with widgets containing information that is useful.

One more final thing about Google Anlytics is that the date range can be customized as well.  In the screenshots above, stats for the whole month are displayed.  If you have a larger website, you may want to customize the date range to a week or even a single day to get a better understanding of what’s going on most recently.  The drawback of course, as anyone that uses Google Analytics knows, is that the stats aren’t live or real-time.  There is a 24-hour delay because all the stats are compiled and processed at the end of each day.  I’m not going to complain about it because the product is free, but just remember that if you do choose to view a single day, you will have to select the previous day instead of the current one.

One way to fix many of the issues with IE7 is to dynamically reverse the default z-index stacking order of the elements on your page. This will ensure the elements higher in your HTML source will also have a higher z-index order on your page, solving most of the IE stacking issues. If you’re using jQuery (the best Javascript library there is), here’s the quick fix:

1
2
3
4
5
6
7

$(function() {
	var zIndexNumber = 1000;
	$('div').each(function() {
		$(this).css('zIndex', zIndexNumber);
		zIndexNumber -= 10;
	});
});

This code will start with a z-index of 1000, and decrement the z-index for each DIV element of the page by 10, giving the first DIV a z-index of 1000, the second, 990, the third 980, and so on. Notice that the selector will find all DIV elements with the code “$(‘div’)”, using the same syntax as CSS selectors. If your HTML code has different requirements, feel free to change the code or the selector to suit your needs by following jQuery’s documentation on selectors.

Update for MooTools (04/14/2009):

A generous commenter has posted the code for fixing z-index issues with MooTools 1.2:

1
2
3
4
5
6
7

if(Browser.Engine.trident){
	var zIndexNumber = 1000;
	$$('div').each(function(el,i){
		el.setStyle('z-index',zIndexNumber);
		zIndexNumber -= 10;
	});
};