Feed on
Posts
Comments

(In no particular order)

Stopped support and development of their toolbar for Firefox
Maybe it’s the cynic in me, but I have to believe that this was done to get more people to switch to Chrome. I mean why else would they do this? The only public mention of this by Google says that Firefox now has most of the toolbar’s functionality built-in to the browser. Well sure, if you take the time to install a bunch of add-ons and create new bookmarks.
Removed the plus (+) as a search modifier
It used to be that when you required a word or phrase in a search term, you could just slap a + in front of it (e.g. don’t be +evil). In what looks like a move related to pushing Google+, Google has removed this functionality and now requires you to place quotes around any words or terms you require (e.g. don’t be “evil”). Google says that this is an improvement but I disagree.
Changed the look and functionality of Google reader
I don’t really care about the social features of Google Reader changing (I never used them), and Google shifting them to be more integrated with Google+, but I don’t like the new look. I’m sure I’ll get used to it in time, but what’s the deal with this new weird spacing they’re introducing? Did everyone at Google get giant new monitors to work with? Continue Reading »

Based on feedback (and the long time between updates), I’m releasing an updated version of the PHP pagination class.

Changes

  • No more SQL errors if using the class on a query with no results (although I fail to see the point of using it on an empty query anyway, but the bug is fixed)
  • When selecting ‘ALL’ only one page is displayed, and if you are using the display_items_per_page drop-down menu, ‘ALL’ is now selected as well.
  • If a page less than page one, or greater than the total number of pages is requested, no results are displayed and the appropriate prevous/next links are disabled
  • The items per page array that populates the display_items_per_page drop-down menu is now an option that can be configured when instantiating the class. Previously this was hard-coded to the class.
  • The $high option has been removed from the class (it was never used).

Note that if you receive a PHP notice about undefined indexes that you should turn down your error reporting. This notice may be displayed when loading the page for the first time when no $_GET variables are present. The class accounts for this, however PHP throws a notice about it.

Examples

I’ve also added license info at the head of the class (CC Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0)).

Download

Version 1.4 of the Before/After plugin has been released with a new feature – keyboard navigation. Now you can use your left and right arrow keys to move the image divider. By default this option has been disabled. There are actually two new option parameters, enableKeyboard and keypressAmount. The first, enableKeyboard, can be set to true or false to enable keyboard navigation and the second, keypressAmount, is the number of pixels you want the divider to move each time the arrow is pressed. The main reason for setting enableKeybaord to false was for those running multiple instances of the plugin on a page. If the default was true, than a press of the arrow key would move the divider on all instances.

Visit the Before/After plugin page to download the latest version and try out the demos.

Sometimes you may not be able to pre-load the images you’re using with the before/after plugin. In that situation you may want to give your visitors some indication that the images are loading so that they’re not left scratching their heads wondering if there’s a problem. Fortunately with a little jQuery and CSS you can add a loading indicator to the before/after plugin.

The jQuery

After the jQuery code to instantiate the plugin, add (assuming a container with the id of “conjainer”):

$('#container').prepend('<p id="loader">Loading...</p>');
$('#container > div:eq(2) > img').load(function() {
	$('#loader').remove();
});

The CSS

Then add some styling. Here we’re adding an animated loading gif:

#container {
	border:2px solid #666;
}
#loader {
	background: #e9e9e9 url(ajax-loader.gif) no-repeat 50% 50%;
	margin:0;
	padding:0;
	width:100%;
	height:100%;
}

And that’s it! Note that this is just a basic example and it only tests for one of the two images being loaded, however it’s basic to extend this concept further and even provide more feedback to the user.

At first I thought my eyes were beginning to go when I ran some Google searches today. It seemed as if Google’s links were brighter than they used to be. Knowing how Google likes to run tests in the wild, I decided to fire up another browser, stay logged out, and ran the same search. Low and behold I was right. Google was testing brighter links. See a blown up, unedited version for yourself:

On the left is the normal Google links color and on the right is the version being tested. As you can see, the purple and green link colors are slightly different and more bright. Personally I didn’t like looking at an entire page of links this color but who knows what Google will decide to do.

« Newer Posts - Older Posts »