Mozilla to skip Fx3.7 and go straight to 4.0

May 11th, 2010

Mozilla’s Director of Firefox Mike Beltzner, yesterday announced that Mozilla is to” jump” Fx3.7 and head straight for 4.0.

The main reason for this is because, Fx3.7 consisted primarily of “Out of Process Plugins” which as most of you know has been implemented in Fx3.6.4. This has pushed developers to bypass the 3.7 release and focus on pushing out Firefox 4.0, hopefully by November.

A couple of things that jump out to me are that there will be no more modal dialogs and software updates will switch to background tasks. This is to help improve the user experience as they are two of the main pause points in a using Firefox.

The background process updates I can understand, Chrome has shown that this is by far the best way to push out updates and bug fixes to users and ensure that everybody is running the same version across the board. The removal of modal dialog however Im not too sure about.

There are also the expected updates, the new chrome (browser layout, not Google browser) redesign, which has removed many of the less used parts of the interface as found during a Test Pilot back in March and from developer feedback.

Firefox 4.0 UI concept - May 2010

Firefox 4.0 UI concept - May 2010

Something Im really excited about are the developer tools. In particular the console. Beltzner described it as a Quake style console, pulled from the top of the browser, as an advanced view source. With the ability to edit css/dom elements, and make other tweaks on the fly. They will continue to support Firebug and will also add a couple of other api’s to allow us to access rendering times and memory usage from within our apps with should help a lot with development and optimisation.

If you using Firefox or a modern web browser that supports fully open HTML video, you can watch Mike Beltzner presentation.
It is almost an hour long but I do recommend watching or at least listening, to what Mozilla believe is the future of Firefox and the direction they are going.

For more on this story, head over to Mike Beltzner blog post, view the slides and watch the presentation.

01100001011011100110010001110010011011110110100101100100

May 2nd, 2010

For a while now, I’ve been wanting to learn how to build and develop mobile applications on Android, I made a start using Appcelerators Titanium, but not long after during a press conference, a certain fruit seller announce his phone was banning apps developed using 3rd party tools. While this didn’t affect me directly, as I have no interest in the iPhone or developing for it, this news meant that the future of Titanium has been thrown into doubt and I don’t want to learn and start developing with a product that may not be around in a years time.

With this in mind, this last week or so I have been dipping my toes into the wonderful world of native Android development.I have gone for the setup advised in the SDK documentation, Eclipse with the ADT plugin. Quickly passing over the Hello World app, as a developer its a task  I must complete before doing anything else, I started on my first application. I decided that for my first attempt I would stick to something I know and rebuild a web based tool I help develop for a well known Manchester server hosting company.

Its been a long time since I last did anything in Java so was a little rusty, but after a few lunchtimes and couple of late nights I have managed to cobble together something that resembles and could just about pass for an Android Application.

So what is it you ask, this wonderful app you have been building up (wont shut up about if you follow me on twitter)? Well I can now tell you, its a speedtest. Not for how fast your mobile connects to the internet, I’ll leave that to the guys at speedtest.net, but to test the speed your website can deliver files to your visitors, now I cant provide you with a link to download and install it as its not really finished and as its not an officially sanctioned app, but I can show a couple of screen-shots from the current alpha version.

ukfast speedtest android appukfast speedtest androif app running testukfast speedtest android app result

This is probably as far as this application goes, unless the boss asks me to continue with it, as although its quite basic and there isn’t all that much to it, it has served its purpose and helped me to figure out how an application should work, its activity life-cycle and how to correctly put one together.

The next step is to think of that award winning, must have,  how did we live without it  idea that will make me millionaire… any suggestions?

Missing TortoiseSVN Shell Icon overlays

April 10th, 2010

This has been bugging me for weeks and today I finally found and resolved the problem so thought I should share in case anyone else has this problem too.

I couldn’t remember when I first noticed they were missing but when ever I checked a working folder on my laptop the tortoise svn icon overlays were missing. When I edited a file the red cross would appear as expected, but the green tick to say a file was up to date or the question mark for non-versioned files were missing, meaning I didn’t know if a file was up to date with the repo head or an ignored/non-versioned file.

This morning I came across a post on stack overflow that suggested modifying the registry to over-right the usual Microsoft default setting cock-up. In Windows, for memory reasons Im guessing, they have limited the number of allowed Shell Icon overlays  to 11. Now at first this seems like a logical way to stop memory abuse in Explorer. But for some stupid reason (most likely so their overlays come first), they are actioned in alphabetical order, so any overlays in position 12+ are ignored. With M being in the middle of the alphabet this results in the majority of these slots being allocated by Microsoft Products. In this case Tortoise SVN (obviously starting with a T) was being pushed out of the allowed slots.

I found this out by doing a search in the registry for ‘ShellIconOverlayIdentifiers’  (NOTE: only open regedit if your comfortable using it, we don’t need to change anything just taking a peek so you should be ok). This reviled that most of the Shell Icon slots were being taken up by something called Microsoft Groove. Not having a clue what this is I turned to a popular search engine to find out.

Microsoft Groove is the name for their multi-user document collaboration tool, which makes sense that it would need some icon overlays as it is essentially the same thing as Tortoise SVN. I don’t do any online document collaboration so re-searched for how to remove it. The Microsoft knowledge base article advised to remove the feature from Office via the add/remove programs control panel but when I looked I couldn’t find anything that mentioned Groove but after a further search or two I found that it has now been renamed to Microsoft SharePoint Workspace, which was listed in my version of Office. I disabled the feature and restarted my laptop and I now have my overlay icons back.

™

Verify your domain via DNS

April 1st, 2010

Google have announce another way to verify you own a domain in their webmaster tools, via a DNS TXT record.
This solves a problem I have had many times in that it verifies the whole domain.

Until now, you had to verify you owned every sub-domain on a domain before you could use webmaster tools for it, while for most sites this is fine, you verify the www. version, sometimes there are a couple more that need to be done.
for example on my site, I use the non-www domain, also there is a dev. and a api. that also need their own verification meta tag/html file. If I want to use webmaster tools on another sub-domain I have to verify again… this becomes a tiresome process.

Enter the new DNS verification. You now add a TXT record to your dns and it automatically covers any sub-domains you add.
That’s it… done! There is of course the usual dns propagation you have to worry about so it may not be a quick as adding a meta tag, but it defiantly saves time in the long run.

You can find out more by visiting the Google Web master tools or popping over to the Webmaster Central blog.

Enable broken image placeholders in Firefox

March 11th, 2010

Something that has always bugged me about Firefox is that if it encounters a broken image it doesn’t display an image place-holder. Instead it displays the alt attribute as in-line text. This can cause problems if your primary development browser is Firefox, as you may not notice broken images on a page.

For a while there has been an option in the config to display image place-holders while a page loads but not for broken images as on IE (yes I’m praising an IE feature!).

Image placeholders on load is set to ON by default, your can change this if you want by going to about:config and searching for ‘image’. The option your looking for is:

browser.display.show_image_placeholders

Just double click to change the value.

As I said before, this doesn’t affect broken images after the page has loaded, and after several searches it looks like the option just isn’t available to Fx users as a general setting. There is however a solution…

Firefox allows users to specify custom CSS to be applied to websites on a global basis, e.g if you want your default link colour on unvisited links to be black instead of the default blue.

You do this by making changes to your global content css file. You can find it at the following location (OS Specific – I’m on windows 7) ‘%appdata%\Mozilla\Firefox\Profiles\\chrome’ (if your on a domain you will need to edit it in your roaming folder), look for a file called ‘UserContent-example.css’ and rename it to ‘UserContent.css’, this will then be loaded by Firefox when it fires up.

Add the following CSS to the file and restart Firefox..
/* Enable image placeholders */
@-moz-document url-prefix(http), url-prefix(file) {
img:-moz-broken{
-moz-force-broken-image-icon:1;
width:24px;
height:24px;
}
}

Thats it… when you next come accross a broken/missing image, you will get a box the size you have defined in its place with the alt inside it.

Return to the Homepage Read Gavin Taylors Blog View Gavin Taylors Portfolio About Gavin Taylor Contact Gavin Taylor