Finally cleaned up my desk at home. Plus I borrowed my brother’s spare LCD.
Very nice having the additional screen real estate. Can’t wait to buy larger dual widescreens in the future. 30″ monitors anyone?
Finally cleaned up my desk at home. Plus I borrowed my brother’s spare LCD.
Very nice having the additional screen real estate. Can’t wait to buy larger dual widescreens in the future. 30″ monitors anyone?
After developing an intensive JavaScript website in Firefox and testing with other browsers, including IE8 in compatibility mode I discovered IE8′s compatibility mode doesn’t simulate IE7′s JS.
Hence a JS bug was bringing all of IE7′s JS processing to a halt even on the initial page load.
A first step I recommend is temporarily deactivating any JS compressors you may have enabled as pathing problems can crop up from using them and cause issues for IE7.
Beyond that I discovered the major snag resulted in this error from Visual Studio:
Expected identifier, string or number
Unfortunately that doesn’t give too much information but I was discovering it in my callback functions within my jQuery. It turns out IE7 has a particular issue with the syntax of JSON:
$(".box").animate({
height: "100%",
opacity: "1.0",
}, 600, function() {
alert("test!");
});
While the above appears to be valid there is a deceptively simple issue that IE7 chokes on. The comma on the end of the third line. While most browsers recognise the empty slot after the opacity variable of the JSON array being passed into the animate function – IE7 gets really confused and starts complaining about the next semi-colon in your code (in this case part of the callback function).
Just an interesting issue that other browsers don’t care about but IE7 is really bamboozled by
So I installed Gnome Do (0.7.99.1-0) last night and it’s pretty awesome. One of the themes enables a full-fledged dock interface when not in search mode.
Gnome Do on its own is an equivalent to QuickSilver which is an OSX search and command program. By hitting the super key and the space bar on your keyboard Do will pop up a box to type a command or search term into. It’s got an interesting plugin system that enables it to perform tasks such as:
An example of initiating a conversation would be:
To install Gnome Do with the Docky theme available you’ll need to add Gnome Do PPA Repository to your sources:
deb http://ppa.launchpad.net/do-core/ppa/ubuntu intrepid main deb-src http://ppa.launchpad.net/do-core/ppa/ubuntu intrepid main
Simple sudo edit
/etc/apt/sources.list
And append the deb lines to the end. Then open Synaptic and reload the manager. Then search for ‘Do’ and install Gnome Do.
Full example screenshot:
The only thing I dislike about the Docky theme is that it loses the listing of possible actions that Gnome Do normally provides as it autocompletes your typing. Try out the regular Do themes and then try Docky’s and you’ll see what I mean.
Otherwise it’s a pretty awesome app and much better than Cairo or Sim dock which I have tried previously.
Kudos to the Do team!
EDIT:
As David points out in the comments, Gnome Do can also (and apparently is optimised for) start its search process by object and then interact with it via its possible actions. In other words, I can type the name of a friend on my pidgin contact list, hit tab and then select to begin chatting with them. Or I could select to copy their email contact information.
Hence, any of the actions that are possible with that friend would be listed. Very cool stuff. Thanks for pointing this out David.
Personally I prefer the original approach as it relates more to English and feels like a more natural language processing flow for the user but that’s just me. I’m sure users in countries where the verb follows the object will be appreciative of the Do team’s efforts!
When you are interacting with WordPress’s Query Posts function the codex page gives great examples.
However, the one glaring omission is documentation on how to handle variables with spaces. For example you might want to query for posts with the tag “Converse”, this is easily achievable with:
# the query terms are not case sensitive, so converse==ConVERsE==Converse
query_posts('showposts=1&tag=converse');
But what if you wanted to query for a tag that contained spaces in it, like “Onitsuka Tiger”? Unfortunately none of the examples on the WordPress page currently provide an answer and giving the query_posts function spaces doesn’t result in anything. And while you might assume urlencode or rawurlencode might be the answer – they’re not.
The answer is that the spaces must be replaced with hyphens:
$manufacturer_tag=str_replace(' ', '-', $manufacturer_name);
query_posts('showposts=1&tag=' . $manufacturer_tag);
Apart from that omission the WordPress codex is still undeniably one of the greatest examples of an OSource API.
After debugging an Ajax Internet Explorer issue for about 3 hours today at work wherein what should’ve been some simple JSON data being returned by a jQuery $.post call the server instead returned the website’s main splash page.
I eventually discovered the problem was also clearing the user’s checkout basket. Upon realising that I discovered the user’s session was dematerialising on the server-side as well.
A few google’s later I found this post on the Magento forum (finally their forum is useful):
http://www.magentocommerce.com/boards/viewthread/27475/
So basically there are options in Magento’s admin backend that cause disruptions in IE for sessions and result in user’s losing their entire session.
In my case it was disrupting Ajax calls all the time. Why have the Magento developers made a buggy set of options the default for the admin panel when the bug affects the most common browser in existence?
Those options do sound great in terms of security but until they’re stable and tested they shouldn’t be made the default.