PaulSpoerry.com

SimpleTags is my prefer automatic tag generating plugin. It greatly simplifies tagging your posts and it’s just an all around well done plugin. One problem: It doesn’t work with the latest version of Wordpress… or does it?

After my initial upgrade I simply thought the author Amaury BALMER was just a little behind the curve in updating the plugin… or *gasp* maybe it wouldn’t be supported in the future. Perhaps both are true, but after a quick search in the plugin repository I discovered that there is nothing that prevents SimpleTags to work except that there is a hard coded Wordpress version check in there. This isn’t a BAD thing… maybe the later versions of WP wouldn’t work with it? Who knows… but the solution to resolving the issue is pretty straight forward and simple.

If you edit the plugin via the editor interface, find this line (near the top):

if ( strpos($wp_version, '2.7') !== false || strpos($wp_version, '2.8') !== false) {

and change it to

if ( strpos($wp_version, '2.7') !== false || strpos($wp_version, '2.8') !== false || strpos($wp_version, '2.9') !== false ) {

Save and you’re good to go!

A rather silly “trick” ( and really that’s all it is, has been making headlines over the last few days. From what I can tell it was really brought to the forefront by Ina Fried from CNET who says:

“By creating a new folder in Windows 7 and renaming it with a certain text string at the end, users are able to have a single place to do everything from changing the look of the mouse pointer to making a new hard drive partition.”

So somebody decided to call this “God Mode” because to enable this “trick” you make a folder called GodMode.{ED7BA470-8E54-465E-825C-99712043E01C} and double-click on it. What you end up with is… drum roll… the control panel; it’s just in a different view than you’d normally see.

First of all, the text ”GodMode” has nothing to do with making the trick work. You can call the folder “IFreakinRawk.{ED7BA470-8E54-465E-825C-99712043E01C}” and now you’ve discovered the magical “IFreakinRawk” feature hidden in Windows.

In reality all you have discovered is:

A documented feature of the shell. Folders can be easily made into ‘namespace junctions’. The whole thing is described on MSDN. Basically, any folder named <DisplayName>.<CLSID> will show up with just the <DisplayName> portion visible in Explorer, and navigating into the folder will take you to the namespace root defined by the <CLSID> portion of the name. This isn’t for USERS, it’s really more of a developer feature.

The second thing is that it’s really the “All Tasks” folder. This is a special shell folder which is used as the source of the “Control Panel” search results seen in the Start menu. This folder was not designed to be browsed to directly, as the normal Control Panel folder (accessible via Start -> Control Panel) contains all the same items but with a custom view designed to be easier to navigate. The “All Tasks” folder has no custom view, so you just see the standard Explorer list view and little else.

The existence of this folder and its CLSID are implementation details and should not be relied upon by anybody for any purpose.

People hate IE6; they’ve made that abundantly clear on the web. Unfortunately, plenty of people are still stuck using it for reasons such as their work not letting them upgrade. So Google is doing something about it.

Chrome Frame is a new browser plug-in developed by Google to give you a Chrome browsing experience inside of Internet Explorer. LOL… seriously: Chrome Frame turns IE into Chrome.

It’s freakin hilarious that Google seems to hates IE so much that it has spent its own time “improving it”. You could also read that as “spent it’s own time to destroy it”.  Product Manager Mike Smith and Software Engineer Alex Russell, say that they simply want to make a more seamless web experience for both web users and developers. RIGHT… whatever… if it helps kill IE6 off the web I’m all for it.

So what is this thing? It’s just a plug-in that creates a new frame inside of IE that IS the Chrome browser. The plug-in itself is only about 500K, but then it must download around 10 MB of Chrome-related data to work correctly on a machine (I assume a one time download). The look will be so seamless that a user shouldn’t realize they’re not simply browsing with their regular old version of IE… except that it’ll be hell-a-faster and standards compliant.

To target the Chrome plug-in for IE, developers simply have to insert a meta tag in their HTML code. If Chrome Frame isn’t found, the page will render just as it normally would in IE.

Chrome Frame will work with IE6, IE7, and IE8 on any Windows-based machine.

So this is obviously wicked cool, and Microsoft’s response should be just as cool as well!!!!

You can find Google Chrome Frame here. And learn more in the video below.

Ben Firshman has ported the vNES into Javascript. Seriously… in JavaScript. While that’s pretty cool itself what it really shows is the blinding fast speed at which Google Chrome can handle JavaScript. In Google Chrome you get Full speed, 60 FPS emulation. Firefox… about 10 FPS. Now you can goof off with some cool old school NES games right from your browser… as long as your browser is Chrome (COMEON GOOGLE… GET EXTENSIONS IN THERE SO I CAN SWITCH!)

http://benfirshman.com/projects/jsnes/

Geoff Chappell published an article explaining how the 4GB memory limit for 32-bit Windows (he is writing mainly about Vista) is more of a licensing preference than an architectural limit. The article outlines how Chappell unlocked his system to use all the memory that is present, but cautions that such hackery is ill-advised for several reasons, including legal ones.

“If you want [to be able to use more than 4GB in Vista] without contrivance, then pester Microsoft for an upgrade of the license data or at least for a credible, detailed reasoning of its policy for licensing your use of your computer’s memory. … [C]onsider Windows Server 2008. For the loader and kernel in Windows Vista SP1 (and, by the way, for the overwhelming majority of all executables), the corresponding executable in Windows Server 2008 is exactly the same, byte for byte. Yet Microsoft sells 32-bit Windows Server 2008 for use with as much as 64GB of memory. Does Microsoft really mean to say that when it re-badges these same executables as Windows Vista SP1, they suddenly acquire an architectural limit of 4GB? Or is it that a driver for Windows Server 2008 is safe for using with memory above 4GB as long as you don’t let it interact with the identical executables from Windows Vista SP1?”

Read the full article here.