Getting into the office I’ve had some frustration with my apple wireless keyboard, so frustrating infact I’ve decided to get the blog on the go, and hope at least one person finds it, and gets a quicker resolution!
If you’re having pairing issues at all (in my case, the computer just seemed to forget the keyboard) then try the following:
1) Fully power down the keyboard, either dump the batteries out or press and hold the power button for 3 seconds.
2) Bring up the Bluetooth Setup Assistant on OSX (remove if already paired)
3) Press and HOLD the power button, the keyboard should appear in the list of devices
4) Attempt Pair, when you get the number code to enter you can release the power button.
5) Type away.
Here at MIQ we’re a fond user of the Atlassian suite of products JIRA/Fisheye/Crucible and my new favourite Bamboo. Bamboo is a CI system akin to Jenkins (with a commercial twist) and integrates beautifully with all the other products we’re so heavily coming to rely on now. We’ve been using Bamboo a number of years, but it’s only in the last few weeks I’ve really discovered it’s flexibility and value.
With a very tight project deadline, it was essential for the team of 3 to be able to push, run unit tests, and deploy somewhere useful for testing / acceptance as automatically as possible. With a few bash scripts and pom.xml magic , we’ve now got the project building (using Maven 3), running unit tests (using Jasmine) and deploying (Onto S3) and content pushed into PressRun all within ~20 seconds of a GIT Commit happening. It’s fantastic! IT’s meant someone who has little knowledge of the deployment stage (i.e a contractor) is able to push new code somewhere for testing on a real environment not a fabricated test harness.
As a company we’re now starting to use Bamboo a lot more, the IOS team love automatically pushing builds to HockeyKit! However, I’m keen to make sure every project moving forward is using Bamboo to build and deploy at least into a test environment, but still have that goal of having the Product Owner hit the go button in JIRA to deploy to production!
Dart – Structured web apps
- web5 conferenence in France?
-Next talk on AMD
DART – Chris Buckett
Language, tool Eco system, complex web apps in teams….
Single thread, optional typing, convert to JS or run in Vm
syntax like JS
Single page web apps
dart is just an option….
flexible with structure
Compile time tools
generated JS maps nicely onto original DART code.
classes are also interfaces
Dart:io http/ file access
Closing note Its a Tech Preview.
So I recently picked up a Nokia Lumia 710, from Vodafone for the very reasonable sum of £150 to replace my now dated (but loved) HTC Desire. I’ve been living with theLumia for over a week now, and so it’s only fair to the world I share my experiences moving forward. I know feel pretty comfortable with what it can do (and certainly what it can’t) so I’ll get round to putting together mini reviews of certain bits, when I get a chance.
Been featured in Novembers edition of Pivot for the PressRun product on webOS. It’s a real shame that development was pulled because of lack of custom font support on webOS. The application still exists in the market, but doesn’t load any issues.
With HP’s quite frankly crazy decision to drop the TouchPad, it doesn’t look great for webOS, infact I’m confident it will be the end.
HP are obviously looking to take the value of webOS and license it out to other hardware manufacturers that may be able to do a better job, HTC for example have transformed themselves on the back of their hardware, and Google’s Android. Could they do the same with webOS? No way. Android’s gained mass market appeal because of it’s adoption by multiple hardware vendors, and it’s availability on such a wide variety of handsets. webOS will never get that. Open Sourcing is an option, but it won’t go anywhere. Whilst the community has the best will in the world, and could probably maintain, develop, and evolve webOS and it’s excellent Enyo framework, it can’t build hardware.
I like webOS, however most people who like webOS will agree it hasn’t kept up with the pace of change of other OS’s. When it first came out, it had genuine potential as a contender for IOS, and Android. The latter still applies (Honeycomb is horrible). It needs investment, and I don’t think HP will give it that investment, I’m actually surprised they’ve come out with a commitment to continue it, and I’ll be happy to eat my words on the matter.
Ironically written on my TouchPad.
Here’s a quick summary of last night’s webOSConnect event….
- Enyo’s the platform to target if you’re coming into the game (SDK 3.0 beta released as of yesterday
- Still No viable route to get Enyo working on the Pre2 / Pixie so if you’re targetting those stick with Mojo
- No Mention of Ares, feel from other developers they don’t like it (and even Palm Developers using a text editor over Eclipse)
- Lack of hardware for developers to test apps before launch, looking to setup localised ‘Labs’ for testing.
- Admission currently developer support is flakey, looking to improve.
Overall the event for me delivered, the venue wasn’t great in terms of being able to move around and talk to people. The mood however was very positive, both from the more experienced developers with Apps in the market and new developers (who were clearly identified by their iPhones). The message was simple, HP are in this for the long run, and we’ll look at how Apple / Google have done things, and deliver a better developer experience.
webOS is an amazing operating system, and one that I’m happy to evangelise to the most hardened of Apple fans. It nicely crosses the engineers approach to Android to the designers approach to iPhone and combines a beautiful multitasking operating system, with in the case of my Pre2 a lovely piece of hardware.
Sony’s Product Blog has announced that it’s current flagship phone the X10, is to indeed be upgraded to Gingerbread (2.3.3) from it’s current archaic Eclair. Whilst it may seem good news to some, the reality is less pleasing. The update will only apply to operator unbranded units, and won’t reach the majority of users who’ve had their handsets corrupted by their network operator [Good time to debrand?].
Sony have upset their loyal handset fans a lot with their Android offering, being slow to take the X10 from 1.6 upto 2.1 (at the time 2.2 was out) and then offering no upgrade path to Froyo. Who this announcement is really targeted as is beyond me. Advanced android users will surely be running some custom rom flavour already, so won’t see the X10 getting a SE branded Froyo experience as anything worth switching for. Normal users, will most likely never see this update thanks to the little incentives for operators to try and keep their customer base using older handsets. After all, it does effectively extend the handsets lifetime nicely, given it’s still fairly well specced within the current range of handsets (pending dual core making an impact).
Still, I’m fully behind Sony on this. Even if it’s an unexpected bi-product of trying to get Gingerbread playing nicely on the new handsets. Now, come on Samsung announce Honeycomb for the Tab and I’ll be muchos impressed.
Android 2.3 recently announced the addition of support for NFC hardware. 2.3.3 has just taken this further and added
- A comprehensive NFC reader/writer API that lets apps read and write to almost any standard NFC tag in use today.
- Advanced Intent dispatching that gives apps more control over how/when they are launched when an NFC tag comes into range.
- Some limited support for peer-to-peer connection with other NFC devices.
I think it’s going to be huge,but only if hardware manufacturers start including it. I often think about NFC with QR Codes, a technology that despite being around for the last decade has only just started to take off, at least in the UK. This in part is down to the software to read these becoming much more normal, Android has the ‘Barcode Reader’ application for example. I’ve only seen a few used on UK Adversiting, Waitrose TV Ad being one and that’s normally gone before I’ve got the reader fired up!
Anyway I digress, the real question is why I think it’s going to be huge. NFC essentially drives a new way of linking an Android hadnset with the real world, be it for good or evil (Advertising is evil, context aware advertising is very evil). The ability to both consume (read like QR) or write means that the technology is bi-directional, and allows you to export data from handset back to a tag.
Finally, Google have launched the Android market on the web via http://market.android.com/ .
It’s been a proper age coming, and the last few months have seen preparations role out to support it, with new assets required for loading to store. I think it’s impact will be pretty huge in increasing the discoverability and driving application downloads with it’s one click approach to getting apps on the phone. It’s still not quite the iTunes experience, but hey how many people chose to use iTunes as opposed to be lumped with it?
It does finally however open up proper social platform integration, the ability to tweet and link to apps directly, and share amongst other users.
Tagged with: Android
Posted in Android