Web development tools and plugins to help you debug
Turok: Dinosaur Hunter
There is a famous cheat from way back in February of 1997 from a little game (or well known game that has been lacking as of late) called Turok. This first interactive foray into the world of Turok the Dinosaur Hunter included tons of silly cheats that player could use – that is, hopefully after they had beat the game first.
One secret code, a variation of the well known “God Mode” cheat, allowed players to get infinite ammunition, invincibility, all weapons, big head mode, disco dancing dinos, level skip, and boss skip … all in one nice shiny package.
This code, called the “Ultimate Cheat”, was simply NTHGTHDGDCRTDTRK, which, like all of the other Turok cheats, was a code within itself, as the letters represent a phrase that had all the vowels removed. Can you guess what it said?
Simple – On the eighth day, God created Turok.
This “Ultimate Cheat” is similar to all of the other “God Mode” cheats out there. Tons of games today, especially First-Person Shooters or Action-Adventure games, allow the player to access “God Mode” via the cheats section or through a sequence of button presses.
Where did God Mode come from?
According to the Wikipedia entry about video game cheating, “Cheating in video games has existed for almost their entire history. The first cheat codes were put in place for play testing purposes. Play-testers had to rigorously test the mechanics of a game and introduced cheat codes to make this process easier.”
Furthermore, God Mode itself was originally meant to provide a developer, tester, or programmer the ability to play through a game as if they were God in that universe. This would allow them, much like our Native American Dino Hunter, to have all guns, invincibility, infinite ammo, level skip etc. at the tip of their fingers.
Why you ask? Well if one is truly going to ensure that they have all the bases covered as far as features, bugs, functionality and everything else that goes along with development, they need to go through their self-created universe as if they were … God.
Why can’t Web Developers have God Mode?
They certainly can! There are countless tools, plugins, and useful browser settings just waiting to be used – the problem is most people may not be aware of them! Let’s start with the subjective best choice to quickly bug fix, optimize, and test any web page or application… good ole’ Mozilla Firefox.
Firefox is best known as the first successful browser to take a large stake of the browser market from Microsoft’s Internet Explorer. For a lot of web sites, Firefox has surpassed Internet Explorer as the preferred browser of the masses. One of the nicest features of Firefox is the overwhelming abundance of plugins and add-ons. Plugins can help take an untested site above and beyond the normal level of polish that any developer could deliver in a shorter amount of time than without.
On top of that, if you find that the quick validator is not good enough, then you can use the tool drop down and simply press “Validate HTML” which will automatically send your page over to the World Wide Web Consortium (W3C.org) validator to get more in-depth error message descriptions and help.
Web Developer will help turn any clunky page into a well-oiled machine.
Along with Firebug, everyone needs the Yahoo created plugin YSlow to find out why their page loads are so slow. After all, how many times have you thought to yourself: “Why is this page so slow?” – with YSlow you can find out with the easily understandable categories (with grades) and also get great tips, ideas, and solutions for each and every problem.
Finally, you should consider getting ColorZilla, simply because it streamlines the process of finding that hex code color (and RGB!) of any element that you can mouse over in Firefox. Why wouldn’t you want this?
Firefox – Okay, What About the Other Browsers?
Apple Safari offers a fairly substantial suite of tools built-in to aid in the debugging of any page. By turning on the Develop Menu in the Advanced tab under preferences, you can have access to the error console (which shares a ton of features used in Firebug like the timeline, script debugging, and the element viewer, as well as the ability to disable images, cache, JavasScript, and CSS) making a great extra for any user that loves Safari. Plus you get to access the activity monitor, which can help you find problems with filenames, locations, or scripts.
Looking deeper, you will find a robust profiler similar to what you will find in Firebug or the Safari Develop Menu, as well as the added ability to switch into IE7 mode with IE8 – which isn’t 100% great since the browser does not exactly portray what an Internet Explorer 7 user will see. Yes to reiterate: IE8 in compatibility mode/IE7 mode it not equal to IE7. You are better off using a standalone Internet Explorer 7 to test your sites.
Who knows? Maybe Internet Explorer 9 will have a better method to test for lower IE versions. Or maybe IE9 won’t.
Once you have it up and running, you can see exactly what the problem is with your Flash file. Perhaps you left out a certain asset file, or maybe you embedding options are blocking certain features like full screen. Face it – when you build things with Flash, you need to make sure they work, or else no one will come back for a second dip!