Dis-N-Gaged

Almost exactly seven years ago, before the launch of Apple’s iPhone and the ubiquity of the App Store, Nokia launched the N-Gage. The N-Gage was a combination mobile phone and gaming device that was intended to take on Nintendo’s Game Boy Advance.

The N-Gage (mk1 pictured below) was pretty much the first gaming phone and should really be considered a failed yet bold attempt to kick-start what is now a huge multi-billion dollar business globally. The N-Gage didn’t get the kind of success Nokia really hoped for despite the many millions invested in marketing. I actually liked this phone and did happily use it as both a phone and gaming device, although admittedly the main game I played was Tony Hawk’s Pro Skater! Combining a gadget with skateboarding is a sure way to catch my eye.

Sidetalkin’

The most obvious quirk of the phone’s design was that you had to hold the thin edge of it to your head to make calls, so it looked pretty comical! (Check out http://sidetalking.com/ !) Nokia subsequently brought out the ‘N-Gage QD’ which removed the side-talking feature and added a backlight and made it a bit smaller, as well as putting the game card slot on the outside instead of inside behind the battery!

The demise of the N-Gage started back in 2005 when the N-Gage as a hardware device ceased production leaving only N-Gage as a software component on various Nokia devices. However, September last year marked the final nail in the coffin (N-Gage 2003-2009: An Obituary) of the N-Gage when it was finished off completely.

As quirky as it looked, I think the N-Gage was an interesting concept which was ahead of its time – location-based multi-player networked gaming via bluetooth or over the internet via mobile-phone networks? Back in 2003? Who would ever be able to afford the data fees that the carriers would have charged you back then?!! Nokia spent a lot of money trying to make it a success, but the timing just wasn’t right for a device with those capabilities.

Nokia are really up against the wall these days with Apple’s iOS platform and the Android platform pushing the bar in both hardware and software capabilities. Although I’m a hardcore iPhone user I used to be a very happy Nokia user, the Symbian S60 OS integrated pretty well with my Mac. Once I got an iPhone of course that all ended, but I’ve still enjoyed using my various Nokia handsets such as the N80 and N95.

Pushin’ the envelope

Nokia do seem to be trying to find their feet in this changing mobile device landscape, certainly the Nokia N8 device has some great features, especially the 12MP camera which seems to produce some pretty spectacular photography.

Innovation like Nokia’s Push project also seems to demonstrate some of the same pioneering spirit behind the N-Gage, breaking new ground by exploring the use of mobile devices as part of our physical activities – of particular interest to me are the skateboarding and snowboarding prototypes (as I said earlier, a sure way to get me interested is to combine gadgets with skateboarding!).

I’m looking forward to seeing what comes out of these initiatives (I’d like to get my hands on either the skate or snow prototypes to play around with them!). For now I’ll just end with saying farewell to the Nokia N-Gage!

More random thoughts on the iPad

I’ve already written my thoughts on the iPad, but here’s a few more thoughts about the iPad that have either been going through my mind or I’ve read about elsewhere and that I think are worth drawing attention to.

Another reason why Flash won’t be on the iPhone: Flash isn’t the only web plugin

If Apple allows Flash on the iPad (or iPhone / iPod touch) then the floodgates will be opened for other plugin such as Microsoft’s Silverlight and Java to be allowed onto the device. Possibly even opening Apple up to anti-competitive scrutiny for only allowing Flash. If Flash isn’t on the iPhone then no other plugin / runtime has any more of a right to be there either.

Mac OSX Snow Leopard an indication of OSX on iPad-like devices?

Reading this TechCrunch article about rumours of a possible larger iPad running something more like the full Mac OSX made me wonder whether the slimming down process involved in the development of Snow Leopard is a clue as to whether we’ll see OSX running on lower-powered, lower-energy processors. Perhaps we’ll even see Mac OSX running on the ARM processor architecture itself? Even if not on a different processor architecture then at least on some other efficient low-powered chip.

The controlled nature of the iPad’s OS has gotten some people worried that future versions of Mac OSX will end up being the same with no ability to install apps of your own choosing etc. It would be interesting to pose this question directly to Steve Jobs – just what is the future of Mac OSX? I guess we’ll find out at the next WWDC!

Many Flash games websites wouldn’t be playable on the iPad

Louie Mantia makes some really good points in his article “Flash Isn’t The Problem, Flash Design Is The Problem”. Many Flash based websites rely on you hovering over menus to navigate through them, and the majority of Flash games use the keyboard as the means of controlling them. Both of these methods of interaction are not applicable to the iPhone or iPad’s interface paradigms, as such even if Flash was on the iPhone or iPad you wouldn’t be able to use many of these sites or play many of the games!

~

If I think of anything else or find other interesting post I’ll add them here :)

Tip: Setting up a Minolta PagePro 9100 printer under Snow Leopard

Mac OSX 10.6 brought quite a few new but subtle features and changes, one of those subtle changes was the dropping of support for the AppleTalk protocol. Many people who upgraded to Snow Leopard (or newer versions of OSX) got caught out and suddenly found themselves with a non-functioning printer.

I was aware of this change but even so I found myself in the same position, and despite all the various articles and posts I read I couldn’t get my Konica Minolta PagePro 9100 printer working. I resorted to sharing my printer via an old iMac that was running OSX 10.4 and printing that way, it worked but would take a long time to print a single page and frequently had to be rebooted to keep it working.

After running like that for a few months I decided to try and figure out how to get the PagePro 9100 working directly again as I couldn’t handle using the same slow process any more. Amazingly I managed to find a Konica Minolta setup guide and it actually worked! So here’s the process:

Configuring a PagePro 9100 printer under Snow Leopard

I followed instructions in an old Konica Minolta support PDF document that you can download from the Konica Minolta site, unfortunately their site is rubbish and doesn’t let you link to files easily so here’s a link to download it:

http://dl.dropbox.com/u/18567/Crown-MacOS10_3-installation.pdf

Note: Before you start you’ll need to know your printers IP address, the PagePro 9100 can be set to have a fixed IP address but this wasn’t needed when printing using AppleTalk so yours may not be set up with one. You’ll need to get that changed using the printer’s controls on the top. You really need to get this sorted out before you can proceed any further. Update: See end of article for help with IP address settings on your printer !

Ok, here’s the simple setup process:

  • You need to set the printer up using the IP printing method, you’ll see a blue circular globe icon in the Add Printer dialog so click that option.
  • Use the Line Printer Daemon option under the ‘Protocol’ drop down.
  • Enter the fixed IP address of your printer into the ‘Address’ field.
  • Enter a queue name in the ‘Queue’ field (I used PagePro 9100).
  • The ‘Name’ field will probably have taken the IP address automatically but this can be changed to PagePro 9100 too.
  • Select the ‘Select Printer Software’ in the ‘Print Using’ dropdown at the bottom. You should be able to find the Konica Minolta PagePro 9100 PPD file in the list. Choose that from the list.

Set the appropriate trays / bins etc for your printer etc and then that should be you set up hopefully!

Addendum: Configuring the IP address settings on the PagePro 9100

In response to a request for help in the comments below I’ve added some instructions on how to configure the IP address settings on the PagePro 9100. Configuring the settings is a bit of a pain due to the tiny little single-line display on the printer, but hopefully these instructions will help!

You need to make sure the printer is not getting a dynamic IP address via DHCP, so you need to disable DHCP on the printer. Once that is switched off you can then set the fixed IP Address that is required in order to set it as per the instruction in this article.

To get to the settings to do this press the green ‘Online’ button on the printer controls to put the printer into Offline mode, then use the ‘Select’ / ‘Next’ / ‘Previous’ buttons to move through and select options.

You need to drill down to the following settings:

Menu -> Administration -> Communications -> Optional NIC -> Crownnet -> TCP/IP

Now that you are in the TCP/IP options you need to disable DHCP, select ‘DHCP’ from the available options (there are quite a few to choose from, just keep clicking through using the Next/Previous buttons), set this to ‘#disabled’ and then click the ‘Menu’ button once to move back up one level.

You now need to set the fixed IP address, you should be back up one level with ‘DHCP’ showing in the screen. Click next a few times and select ‘Internet Address’, you should now be able to enter all the digits of your IP address. Please note that you need to include 3 digits for all four parts of the address, so rather than just ‘192.168.0.4’ you need to enter ‘192.168.000.004’.

Make sure to use whatever IP address range your network runs on, routers use various different ranges so you need to set an IP address that is appropriate for your network’s range.

Addendum #2: Get default page size on PagePro 9100 to be A4 instead of ‘Other’

If you’re using the PagePro in the UK or at least with UK region settings in order to print to A4 paper then you may find that whenever you print that the printer always uses a default page size of ‘Other’ instead of A4. Although this actually prints to A4 correctly it always bothered me that it showed this way, so I decided to figure out what the problem was.

After a bit of looking around in the PagePro 9100 OSX EN.PPD file I found all the entries relating to A4, in PPD files the dimensions of paper sizes are configured using a dimension called points, basically there are 72 points to an inch. In the case of A4 in this PPD the dimensions used are 596 by 842, however, A4 is a metric-based page size of 297mm by 210mm so I checked out what these convert to in points.

It turns out that the PPD rounds all of the page dimensions to the nearest point, so I then edited the PagePro’s PPD file to use the accurate point dimensions for A4 which are 595.28 by 841.89 (you need to replace it in a few locations in the file). I then re-setup the printer with the updated PPD and it now uses A4 as the default page size once more! It seems that OSX 10.6 is fussier about the specific page dimensions than OSX 10.5 was, but this tweak sorts it out. I’m sure you could modify the PPD for any other paper format that you wanted to use, just google the correct point dimensions for your page size and the update it in the file.

Here’s a link to an already modified PagePro 9100 PPD file with updated A4 dimensions to save you having to tweak it yourself.

Addendum #3: OSX 10.7, 10.8, 10.9, 10.10, 10.11, 10.12

These instructions will basically work for all version of OSX since Snow Leopard, so 10.7 Lion, 10.8 Mountain Lion, 10.9 Mavericks, 10.10 Yosemite, 10.11 El Capitan definitely all work and 10.12 Sierra should be fine too as the protocols used are the same.

Tip: Use a symbolic link to force Mail.app downloads into the main Downloads folder in Mac OSX (Updated for OSX 10.8 Mountain Lion)

TIP UPDATED FOR Mac OSX 10.8 Mountain Lion! – Mac OSX 10.5 introduced a setting in Mail.app Preferences to set where email attachments are downloaded to when you open them or when images are loaded in HTML emails. If you’ve never looked in the default ‘Mail Downloads’ folder you might just get a surprise as to how much junk is actually in there as it’s not obvious that these files are building up!

It is possible to change the location for these downloads so that it is in a more obvious location, but I found that even when setting an alternative to the default ‘~/Library/Mail Downloads’ folder, such as the main ‘Downloads’ folder, that these attachments would still download in the default ‘Mail Downloads’ location. The solution to this problem was to delete the ‘Mail Downloads’ folder and create a symbolic link to my preferred ‘Downloads’ folder.

To do this you need to navigate to the ‘Mail Downloads’ folder which you’ll find in your user account folder (the folder with your name and the Home icon), then go into the ‘Library’ folder and you should see the ‘Mail Downloads’ folder. Note: Since OSX 10.7 Lion came out the ‘Library’ folder is hidden by default, to get to it you need to access the ‘Go’ menu in the Finder whilst holding down the alt key.

Next step is to delete this folder and then fire up Terminal on your system – this bit requires a bit of command line entry but it’s fairly straight forward. When you open up Terminal you should end up with a login prompt and you will be located within your user account files on the system, presuming this is the case we can get on with creating the symbolic link!

In the example below I am going to create a symbolic link to the main ‘Downloads’ folder that is used by Safari so that all downloads from either web browsing or email will end up in the same place:

ln -s ~/Downloads "library/Mail Downloads"

If all has gone well you should now find that any attachments you open from emails will now appear in your regular downloads folder instead of the hidden away Mail Downloads folder!

UPDATE: OSX 10.8 Mountain Lion changes the location of the Mail Downloads folder

In OSX 10.8 the “Mail Downloads” folder location has moved to the following location (See this MacOSXHints article for more details):

~/Library/Containers/com.apple.mail/Data/Library/

To apply the above link for OSX 10.8 you will need to use the a different command to create the symbolic link. The first step is to go to the new folder location, I’d recommend doing this via the terminal as you need to run the command from there, go to: ~/Library/Containers/com.apple.mail/Data/Library and delete the existing ‘Mail Downloads’ folder that is in there. Then use the following command to create the symbolic link in this new location:

ln -s ~/Downloads "Mail Downloads"

Once that’s done all your attachments in OSX 10.8 Mountain Lion should now end up in your Downloads folder allowing you to easily keep track of attachment files and avoid them unnecessarily clogging up your hard drive.

Thoughts on the iPad

Apple have finally unveiled their tablet device to the public so we can finally stop hearing all of the pontification that has gone on for the last few months about a device that Apple had never given any public indication even existed (the pontification only to be replaced by the rumblings and grumblings of those who got too enamoured by some of the various rumours!).

In the true spirit of “Internet Journalism” I thought I’d add my own thoughts about Apple’s newly announced iPad. Here are a few thoughts / questions about the iPad and the impact it may have.

Flash on the iPad?

It’s a question being asked by many people, and with a move to a larger screen some would say it deserves even more to be on the device. However, I wouldn’t expect it soon, if ever to be honest. Unless the Flash plugin can be made more efficient processor, memory, energy wise it won’t happen.

I don’t think this is simply arrogance on Apple’s part as some might say, I think Apple approach the usage of the iPhone OS that runs on the iPhone and the iPad with a view to making it as efficient as possible. Some people were expecting or hoping for the iPad to use the full Mac OSX but are disappointed that it’s not on there, although some see that as a limitation I think it shows that Apple isn’t willing to put even their own more fully-featured OS on the iPad as it wouldn’t run as efficiently on the device. So if they do that with their own OS why should we expect an unmodified / unoptimised version of Flash to be allowed on the device?

I do think there is more to it than just the issue of efficiency though, John Gruber makes some good points in his recent post “Apple, Adobe, and Flash“. Personally I doubt Flash will ever be on the iPad or iPhone.

Will there be a new iPad App Store “Gold Rush”?

Even though I doubt Adobe will ever get Flash on the iPad I do look forward to seeing what native apps Adobe might bring to the iPad. Photoshop Mobile is a great little app for the iPhone so a larger sized version of that could be pretty cool. Apple have set a nice precedent for full-featured apps like Keynote, Pages and Numbers at $9.99 each so there could be some financial incentive to create a good image editing app.

It may only be a 1ghz processor in the iPad but it appears to be far more powerful than the raw ghz would suggest. It would be great if the $9.99 price point can remain as it might encourage developers of iPhone apps to develop more for it, as the race to the bottom and the $0.99 / £0.59 price point has made the supposed “Gold Rush” of the App Store an impossible dream for many, many developers.

Does the iPad signify the end of Mac OSX?

Some people have concerns that Apple’s focus on the iPhone OS is an indication that Apple is heading away from the geek or power user and is instead focused solely on the domestic / consumer end user. Whilst that may be true to some degree (Apple is a consumer electronic company after all) I think that Mac OSX has a strong future and a rightful place on the more powerful hardware that the MacBook, Mac Mini, iMac and Mac Pro computers offer.

I think that iPhone OS will influence the future development of Mac OSX in regards to user interface and aesthetics. Mac OSX 10.6 Snow Leopard brought a lot of efficiency improvements, largely thanks to the optimisation required to get iPhone OS running on the limited hardware requirements of the iPhone and iPod touch (along with the dropping of PPC support!).

The iPad is the gateway drug for Mac OSX development.

The iPod and iPhone have often been seen as a ‘gateway drug’ for Apple laptops / desktop computers – people like how nicely they work and are then attracted to Mac for the same reasons. In a similar way I think the iPad will be a gateway drug for iPhone developers getting into developing apps for the full Mac OSX that runs on Apple’s laptops and desktops.

Designing apps for the iPad will bring with it some new challenges for mobile device developers – more screen space for the user interface, processor and memory improvements. Apple are touting the iPad as a third category of device in-between a smart phone and a laptop, developers will have to get used to this paradigm as well.

The iPad isn’t just a laptop with a small screen (i.e netbook) it’s a new type of device with hardware and software tailored to suit the demands of a lower speed cpu and lower memory. Netbooks generally push the limits of their smaller hardware form and tend to run Windows XP or Windows 7 which are really laptop OS’s and as such really need to be running on at least a 1.6ghz atom cpu with 2GB of memory to be usable. The iPad is built a whole different way, with a focus on using the minimum of cpu speed and memory by maximising the efficiency of the OS.

Where the iPad becomes the gateway drug is that as iPhone developers (many of whom didn’t previously develop for Mac OSX) get into developing iPad apps they will get more familiar with developing for a larger screen resolution. They’ll bring with them the knowledge and experience of developing apps within the tight constraints of the iPhone’s cpu and memory and start to enjoy the freedom and power that the iPad’s higher spec offers them. It’s only a short step to see how a developer could then take the next step up and make their apps function on the full Mac OSX laptop / desktop OS.

I look forward to seeing an increase of very efficient programmers developing apps for Mac OSX in future, having learned to code Objective-C within very tight limitations. :)

Other media coverage etc.

Adobe Flash to add DRM in the player via Flash Access 2.0

I’ve blogged a few times about Flash and how it seemed like an obvious tool for the job of a cross-platform means to provide protected streaming video, in particular for the BBC’s iPlayer in the UK. Many of the things I’d thought in those old posts have actually happened now, streaming Flash video is now used to provide access to the BBC iPlayer content on many platforms such as Mac OSX, iPhone / iPod touch, Wii, PS3 and other devices. Streaming Flash video is also used for Hulu.com in the US.

In addition to the streaming option Flash is now used to provide a cross-platform downloadable iPlayer service via Adobe AIR’s protected runtime, so it’s all come a long way really. Of course no-one really likes DRM but at least it does provide a way to make all of this content available (geographic restrictions aside) without any major restrictions – apart from not being able to download directly onto the iPhone / iPod touch I suppose!

Adobe Flash Access 2.0

Adobe has just announced a new version of a software developer kit called Flash Access 2.0 (previously known by the snappily named ‘Adobe Flash Media Rights Management Server’). One of the main features is that it will enable protection of files that can be played directly within the Flash player instead of requiring it to be wrapped within the Adobe AIR runtime. This will offer a lot more flexibility in that files can be played directly within the browser. The technology supports MPEG4 H.264 content as well as FLV files so the quality of video provided via this technology has the potential to be very good.


Example of Flash Access 2.0 workflow.

I’m not sure if this has any real impact for services like BBC’s iPlayer as they already have a downloadable option via the AIR based iPlayer. It’s an interesting situation with distribution of digital video content really, DRM was a complete failure when it came to audio but there’s no sense that content creators are about to take the same approach as the music industry. Of course the big missing piece to the digital media distribution puzzle is that none of this Flash based content can be used or distributed to Apple’s iPhone and iPod touch platform.

Time for Fairplay DRM to be broadly licenced?

I’m not holding my breath waiting to see Apple add Flash support to their devices and I understand that in many ways. However, the main benefit I’d see personally for support for Flash video on the iPhone is to be able to access more of the streaming video content that is out there as most of it is Flash based, and only the likes of Youtube have the means to offer content in multiple formats. Asides from accessing Flash format streaming video I’m not bothered about accessing any other kind of Flash content on my iPhone (I think the Javascript / HTML / CSS3 / WebKit stack is much more suited, that’s maybe something for another blog post).

Although there’s some sense in supporting Flash video on the iPhone I think what could be a solution is for Apple to make their Fairplay DRM licencing available for others to use on their own websites, media stores etc. If we’re not likely to see media become completely DRM free then what is at least needed is any easy, cross-platform, cross-device method to distribute digital video content to whatever device is desired. At the moment the whole digital video distribution system is full of restrictions, dead-ends and political manoeuvrings by big media companies.

I wonder if it’s going to take greater consumer unrest to finally force the various companies to work together for the greater good, to simply be able to play video content that you’ve paid for on any device you want? Especially if that device is an iPhone or iPod touch? At the moment it’s just “a bag of hurt“.

P.S. Don’t anyone suggest Microsoft’s Silverlight as a solution, we don’t need yet another format for video distribution!

 

iTunes 9 and other wonders…

Apple’s 09/09/09 Media event introduced some new things both expected and unexpected, many expected an iPod touch with a camera but instead there was an iPod nano with not only a camera but FM radio and a built-in pedometer! I was surprised about the FM radio as I never expected that to be added to an iPod. Here’s a few of the things Apple introduced today along with some thoughts / notes etc:

iPod shuffles – shiny rainbows

Now in multiple colours as well as a special edition stainless steel model. There were rumours that this tiny little iPod was going to be ditched but that didn’t happen. They also announced a new 2GB model along with shuffle-compatible third party headphones and controller peripherals. I’m not sure how much smaller you could make an iPod shuffle really. (iPod shuffle ?)

iPod nano – complete with camera

At first I didn’t think an iPod nano with a camera was that big a deal but after watching one of the video clips demoing the video features I found myself wanting one to carry around so that I could film things again. I’ve missed being able to film stuff since getting my iPhone 3G, however, there’s no way I’m buying yet another iPod so I’ll just have to look into getting an iPhone 3GS at christmas time instead! The nano’s video format is 640×480 pixel h.264 video and looks to be pretty good quality, it almost makes me wish Apple would just make a dedicated camera but I don’t think that will happen. (iPod nano ?)

iPod classic – memory bump

There’s nothing that different in store for the iPod classic, just a simple storage bump from 120GB to 160GB instead. I still like the classic iPod and the scroll wheel, it’s a great interface for accessing files. The iPhone / iPod touch’s touch screen is great but the scroll wheel is still very efficient I think. I wonder though how much time is left for these iPods? Probably still a fair bit, but once flash memory gets into at least 128GB sizes I think the iPod classic will be assigned to the history books. (iPod classic ?)

iPod touch – 64GB model and price drop

There was no rumoured iPod touch-with-camera announced, just a price drop on the existing model as well as a 64GB model announced. I think a new version with a camera is in the works, it just doesn’t make sense for the nano to have it and not the touch. Also the lineup is now 8GB, 32GB and 64GB, I’d expect to see it become 16GB, 32GB and 64GB when the new model is announced. That’s just my speculation though. Update: This press release from Apple about the new iPod touch updates paints a slightly different picture though, it indicates that the 32GB and 64GB iPod touches have the same internals as the iPhone 3GS, “The 32GB and 64GB models also include up to 50 percent faster performance and support for even better graphics with Open GL ES 2.0“. Interesting. (iPod touch ?)

iTunes 9

An expected announcement and one that took up the majority of the media event. iTunes 9 introduced a revamped interface (with it’s usual introduction of unusual / new interface aesthetics!) and a few other new features. One thing that’s disappeared though is the shopping cart feature, now you have to either add it to the also newly added Wish List feature or you have to use 1-Click purchasing! That’s a little bit scary.

There’s now also the option to share items on the store to either Facebook or Twitter, I was hoping for more integration with social networks, particularly last.fm but alas it’s not to be. One other thing I noticed is that iTunes now finally behaves like all other good Mac apps and will actually maximise when you click the maximise button! Previously this would toggle iTunes into it’s Mini Player mode, I’m really glad they’ve changed this.

Here’s a rundown of some of the new features of iTunes 9:

  • iTunes LP – Intended to introduce the digital equivalent of album covers complete with liner notes, lyric, videos etc. This is something that is long overdue, I look forward to checking out some of these. Another question though is how are these made? I’m pretty sure they won’t involve Flash but I’ll be keen to find out how they’re produced.
  • Home sharing – This basically allows you to easily share tracks between up-to five machines that you can authorise to play back songs. This seems really handy for households with more than one computer, drag and drop songs between shared libraries.
  • Redesigned iTunes Store – Improved navigation is one of the main tweaks, it now seems more like a web page with consistent navigation along the top of the window. You can also set an option in the preferences to use the full window when browsing the store, this basically gets rid of the list of options on the left hand side. It’s quite handy to get a bit more space when browsing the store.
  • iTunes Extras – Another long overdue feature! I’m not that impressed with the iTunes store’s video offerings, many movies are not available to rent until long after many other rental stores have had them. So these movies are only available to purchase, what’s more they’re a bit expensive too compared to picking them up in DVD format from somewhere like play.com or even at your local Tesco supermarket. Ok, rant over. iTunes Extras basically adds a bit more value by including the special features that you’d get on your regular (and cheaper!) DVD purchase. I’m a tiny little bit more likely to buy one now (I still probably won’t though).
  • Genius mixes – An interesting new feature, it finds songs that go well together and automatically makes mixes out of them. One thing to point out though is at first I couldn’t see where this feature was, you need to choose ‘Update Genius’ from the Store menu in iTunes in order to update and activate the feature.
  • Improved syncing – Undoubtedly one of the most sought after features by anyone who owns an iPhone or iPod touch and has a lot of applications on it, you can now organise the layout of all of your apps inside iTunes itself. It’s not quite how I’d proposed it but close ;)

iPhone OS 3.1

iPhone OS 3.1 for iPhone (and 3.1.1 for iPod touch) were announced too. It introduces a few new features that tie in with iTunes 9’s new features, nothing massively new but then again it is a point update. Amongst the various features shown on the iPhone OS software update page a couple of little tweaks caught my eye:

  • Remotely lock iPhone with a passcode via MobileMe
  • Warn when visiting fraudulent websites in Safari (anti-phishing)

Being able to lock an iPhone remotely enhances the already brilliant MobileMe feature of locating your iPhone via GPS and also remotely wiping a lost iPhone. Anti-phishing support in Mobile Safari is a great feature too, something all browsers need these days.

Anyway, enough writing about it all, I’m going to go and re-organise my iPhone apps :)

Post-install notes of Mac OSX 10.6 Snow Leopard

I thought I’d compile a few notes / points of interest of things I’ve noticed after installing Mac OSX 10.6 Snow Leopard on my development Mac. I’m going to keep updating this page and adding things to it as I come across them.

I use the default install of Apache & PHP and install MySQL from the installer from MySQL.com, I guess I should custom build and install these but it’s easy enough to work with the defaults anyway.

PHP under Snow Leopard

PHP under Mac OSX 10.6 Snow Leopard is version 5.3.0 and thankfully has the GD libraries enabled by default. Especially good for WordPress installs so that it can do image resizing for thumbnails etc.

I noticed I was getting an error relating to timezones on many of my sites, along the lines of:

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system’s timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function.

The solution I used to this was just to restore the previous php.ini file, this showed in the /etc directory as ‘php.ini.default-5.2-previous’. Just rename it to ‘php.ini’ (replacing any existing php.ini file if it exists, it didn’t for me). You’ll then want to edit php.ini and look for the ‘date.timezone’ setting and put in your timezone info (PHP.net timezone page) and then restart Apache. Hopefully it should be fine after that.

I also started getting a lot of warnings on some of my development sites along the lines of:

PHP Deprecated: Assigning the return value of new by reference is deprecated in…

These are warnings about old deprecated PHP4 era code, recent versions of PHP5 enable these warnings, but you can switch these off by adding an additional error reporting element to your php.ini file in the error handling section:

error_reporting = E_ALL & ~E_DEPRECATED & ~E_NOTICE

Just add the E_DEPRECATED part and then restart Apache and the warnings should be gone.

Apache

The version of Apache is 2.2.11, the latest available from Apache.org is 2.2.13 so it’s fairly up to date. If you think this is an issue then check out the release notes for 2.2.13.

MySQL

MySQL isn’t installed by default in Snow Leopard so you need to install it yourself. I simply downloaded the latest 64 bit Intel version from MySQL.com, they only show version for Mac OS 10.5 at the moment but it worked fine for me. The installer provides a startup item to make MySQL run at boot time and also a System Preference to control it, it’s worth noting that this is only 32 bit so it will make System Preferences restart itself into 32 bit mode, not a big deal though.

Booting 64 bit

There’s been a fair bit of discussion about Snow Leopard and it being 64 bit. By default Snow Leopard boots into 32 bit mode, however this doesn’t make that big a difference as 64 bit apps will run in 64 bit and access all the memory available on your system. One thing to note though is that the original unibody MacBook (which I have!) can’t startup in 64 bit mode, I’m not sure if that’s a big deal or not though really.

If you want to get into a really in depth examination of Snow Leopard’s 64 bit capabilities then check out John Siracusa of Ars Technica’s comprehensive review, beware though, it’s a lengthy read but it’s a great overview of the new technologies that are under the surface in Mac OSX 10.6.

Flash plugin out of date

The Flash plugin needs updated as the version that comes in Snow Leopard is an old version (10.0.23.1) which has some security vulnerabilities, just go to http://www.adobe.com/go/getflashplayer and download the latest version. There’s been quite a bit of coverage of this online, the gist of it is summed up in this post over on Daring Fireball. Basically the most up to date version of the Flash plugin was probably released after Snow Leopard’s final release version’s features were frozen, so basically Snow Leopard overwrites the newer version with an older version upon install.

It’s easily fixed by downloading the latest version, although I don’t know why Adobe don’t make the autoupdate feature of the Flash plugin a bit more aggressive. I can’t think of the last time I saw any prompts to update it, you can actually adjust the autoupdate settings via the Flash Player Settings Manager page on the Adobe website (which you probably never knew existed!).

Quick Look from Print progress dialog

I’m not totally sure this is a new feature to Snow Leopard, I may just have never noticed it before! If you hit space or double-click on a print job in the print progress you get a Quick Look preview of your document, even if it’s not new it’s quite a handy feature!

That’s my thoughts / experiences so far, I’ll add more to it as I come across things of interest. Anybody noticed any other new features / issues? Drop a comment if you want and I’ll maybe add it to the notes.

~~~~~

 

How to restore a MySQL database from your Time Machine backup

I’m writing this as much to remind myself as for anyone else really :) I generally run databases running on my MacBook which I use for sites in active development, I then transfer these databases over to a staging server which are then use by other people in the team and sometimes clients to input site content. Last week I imported content from the staging server and overwrote my local database thinking that the staging server was the most up to date, but as it turned out I was incorrect!

Fortunately I’m running Mac OS X’s Time Machine backup on my MacBook so I didn’t see a problem as I could just restore it from that. However, in reality it wasn’t quite as straight forward to do, so here’s what I had to do in the end to restore this database from my Time Machine backup.

Step 1: Find your local databases

Navigate to the location of your MySQL databases. For my MySQL install this is found at /usr/local/mysql but depending on how you’ve installed MySQL it might be elsewhere.

As you’ll probably see that’s not a location you can just regularly view in the Finder on Mac so you’ll need to use the ‘Go to Folder…’ option within the ‘Go’ menu in the Finder.

Once you’ve got to that location you’ll see the MySQL data folder which shows up with a red no-access symbol on it so you can’t actually navigate straight into it via the finder. Seeing as we can’t access the folder to restore a specific database we’ll just restore the whole folder from the Time Machine backup instead.

Image of MySQL's Data folder in the Finder

Step 2: Shutdown your MySQL server

It’s important that you shut down your MySQL server process before you continue. How you do this depends on how you’ve got MySQL installed. If you installed MySQL from the official installer for OS X downloaded from the MySQL website then you may have the a System Preference which you can use to stop it.

If you’ve installed MySQL another way such as self-compiled or via Mac Ports or you just want to use the Terminal then you can stop it from the Terminal instead. The following command can be used:

sudo mysqladmin shutdown

If you don’t have MySQL configured in your path in Terminal you may need to use the full path to the mysqladmin command:

sudo /usr/local/mysql/bin/mysqladmin shutdown

The path to those files may vary depending on how you’ve installed MySQL so if it doesn’t work then you’ll need to check the correct location. Note that I’ve also used ‘sudo’ in that command in case you need root privileges to stop the MySQL process. Check the MySQL documentation for your version of MySQL for further help.

Step 3: Rename your MySQL data folder via the Terminal

Image of file listing in OS X's Terminal applicationThe next step is to rename your MySQL data folder temporarily to avoid any clashes when restoring the data folder from the Time Machine backup. First you need to get into your MySQL directory:

cd /usr/local/mysql

You can then list all the files to check you’re in the right place:

ls -al

You should now see all the files including the ‘data’ directory where the databases are located. We can now use the following command to rename the data directory:

sudo mv data data-bak

Once that’s done you should see your directory happily renamed in both the Terminal and the Finder window.

Step 4: Enter Time Machine to restore your MySQL data directory

The next step is to enter Time Machine mode and restore the data directory from the backup. I’m sure you probably know how to enter Time Machine mode but make sure you enter whilst focused on the MySQL Finder window.

Image of restored files in Finder windowGo back in time a sufficient amount so that you’ll definitely be getting the version of the data that you want, highlight the data folder and click Restore. Because we renamed the data directory Time Machine will simply restore the data directory without any prompts. You should now see both the restored data directory and the renamed data-bak directory.

Step 5: Copy the database from the restored data directory

You can now copy the database from the restored data directory, this is done via the following Terminal command:

sudo cp -R data-bak/my_database_name data/my_database_name

The database is actually a directory containing other files so you need to use the ‘-R’ flag to recursively copy all of these across with the directory itself.

Step 6: Delete the restored data directory and rename the data-bak directory

Now that the database is restored and copied you can safely delete the restored data directory as it’s no longer needed at this point. Note: Be very careful using the ‘rm’ command! Bad things can happen if used incorrectly!

sudo rm -R data

You can then rename the data-bak directory back to it’s original name ‘data’, note that the ‘mv’ command doesn’t require the ‘-R’ flag:

sudo mv data-bak data

Step 7: Check file permissions / ownership

You may need to check the file permissions and ownership of the database that you have just restored to make sure that it will be accessible by MySQL when it is running. These may vary depending on your MySQL install method but they should be something like this:

drwx—— 60 _mysql wheel 2040 8 May 12:14 my_database_name

Basically the directory is owned by the user ‘_mysql’ and in the group ‘wheel’. If you need to change the owner then use the following command:

sudo chown -R _mysql data/my_database_name

Step 8: Start up MySQL

Once this has all been done, you can then start MySQL again using either the System Preference if you have it or via the Terminal command:

sudo mysqld_safe &

or with the full path:

sudo /usr/local/mysql/bin/mysqld_safe &

Step 9: There is no Step 9!

Hopefully you should now be able to access your newly restored database. As I said at the beginning, this is the method I used to restore a database myself recently, there may be other ways to do it but hopefully these steps might be of use to anyone else in the same situation.

How to make your Nokia N95 more like an iPhone

My recent switch to an iPhone after using a Nokia N95 for the last year and a half has been great, there’s a load of features on the iPhone that just make a load of sense.

I’d always been keen to try out the various apps available from the Nokia Labs website on my N95 so I thought I’d just do a quick post with links to apps that can make your N95 just a little bit more like an iPhone! These will also work on many other S60 Symbian OS Nokia phones and they are also free downloads from the Nokia Labs website!

Conversation

SMS management on the iPhone is great as it gives you a view that’s similar to that found in an instant messaging app like iChat / MSN etc. It’s great as it allows you to see the messages in the form of a conversation. The Conversation app from Nokia allows to you something pretty similar.

http://betalabs.nokia.com/betas/view/conversation

Contacts on Ovi

This app mainly provides an Instant Messenger experience but also adds some cool features like status updates and location updates. If you’ve been envious of the Brightkite app for iPhone then this is something similar.

http://betalabs.nokia.com/betas/view/contacts-ovi

Friend View

If you need a bit of a Twitter fix (ok, I know that you can get actual Twitter apps for Symbian!) or want more of a Brightkite experience then Friend View offers location and micro-blogging service.

http://betalabs.nokia.com/betas/view/nokia-friend-view

Nokia Audiobooks

The iPhone is, obviously, a great music player that will also play audiobooks with various controls. The N95 in comparison is an ok music player but isn’t up to playing audiobooks. However, Nokia Audiobooks fills that gap by allowing playback of highly efficient audiobooks by using tools like bookmarking and browsing chapters.

http://betalabs.nokia.com/betas/view/nokia-audiobooks

Set your camera to low quality and don’t record video

Ok, this last one is a joke. It’s true that in comparison to the N95 the iPhone camera is not great, it’s poor in low light and doesn’t support video recording at all. So if you want an authentic iPhone experience on your N95 change your picture settings on the N95 to their lowest and you’ll get something similar to the iPhone! (although probably still better!).