Posts Tagged ‘air’

  • Get a Google Nexus One working on Windows 7 for Android Development

    Today our Google Nexus One developer handset arrived at work. We bought it to do some prototype work with the Flash CS 5.5 pre-release (AIR 2.6) to allow for a much quicker development work flow. Due to the obvious Adobe NDA I can’t talk about the 5.5 feature set, but what I can say is what a complete and utter ball-ache it was to get the phone working on Windows 7, and how I finally got around it, in the hope that one day this may save some other poor sod from wasting hours like I did.

    The problem

    Plug your Nexus One into a Windows 7 PC and it won’t work. The device drivers install and then fail. So you can’t mount it and USB debugging doesn’t do anything (obviously).

    The issue

    The USB drivers aren’t Windows 7 compatible!

    The solution

    1) You need to download the Android SDK for Windows and install it. I used the r08 release as it was the most current at the time of writing. It’s available from http://developer.android.com/sdk/

    2) Once installed run the SDK Manager and let it do all the Updates that it requires. When finished click on Available packages on the left and then expand the Third party Add-ons entry on the right. Below this you’ll see Google Inc. add-ones. Expand that and lo and behold is the Google Usb Driver package (at the time of writing it’s revision 4). Tick it and click Install Selected. When complete you should see it on the Installed packages list:

    3) Now go into the Computer Management app. In Windows 7 you can right-click your Computer icon on your Desktop and pick “Manage”. You need administrator level permissions to do this. Pick Device Manager on the left and you should see your Nexus One listed under “Other devices” on the right,with a little yellow alert sign over the icon:

    4) Right-click the Nexus One entry and pick Install Driver. It will ask if you wish to Search for the driver or Browse for it. Naturally you need to browse for it. Point it at the google-usb_driver folder that is now inside your Android SDK folder. The location of this will vary from PC to PC, ┬ábut I’m hoping you know where you unzipped it all :)

    The driver will now install. I did this with the phone connected and it didn’t seem to complain at all.

    At the end of the process you should see this:

    Click Close and the Device Manager will refresh. Voila! We can haz Nexuses:

    From this point on you mount the phone and access it like a normal USB stick. It will make your life in Flash a whole lot easier now too! No more crappy slow emulators :)

    The small tests I’ve run on the phone so far look promising. Speed is still a bit of an issue, but I believe we can get around that with some clever optimisation and planning. There’s a good beginners guide written by Terry Paton on the Mochi web site.

  • Access LiveDocs locally with Doc v3.0.1

    Although the code-insight features of FlashDevelop help a lot, you can’t beat a good AS3 reference – and I use Adobe LiveDocs almost exclusively for this. Although I have a Firefox search plugin that gives me quick access to it, I have still always wanted a decent local copy that offered the same benefits my browser does, but faster.

    Thanks to the magic of Twitter (cheers @kode80) today I found such a beast in the shape of an AIR app called Doc?

    Doc? allows you to view, search and bookmark all your favourite ASDocs. But the biggest feature for me is that on-line docs can be downloaded and stored locally too. This means that the docs for things like Away3D, Flint, Papervision, Adobe CoreLib, TweenMax or anything else that has ASDoc documentation can be added to your local books collection.

    Adding a remote ASDoc

    Adding new books couldn’t be more simple. Just start-up Doc?, click the settings icon in the top-right and select “”Add Remote ASDoc”. You’ll be asked for some details. Here they are for the Stardust Particles system:

    Note: when adding URLs be sure to specify a directory, and don’t have the index.html on the end.

    Doc? will then download and index the files, storing them locally.

    Be advised that on large sets of documentation this can take a while. Indexing the AS3 Language Reference took nearly 10 minutes, and that’s on an Intel Quad Core Q9950 @ 2.83GHz with 8GB RAM. Doc? stores the indexes in a local SQLite database.

    Once downloaded and indexed the docs are available from the Books menu, ready for easy and fast local searching!

    Here you can see I searched for “Radius” specifically in the Stardust book, and am viewing the CollisionRadius page. You can search across all books, highlight results in the text, include title and/or content in the search and even bookmark sections you know you return to often.

    The tree view display has icons depending on the style of result – the green “C” circle icon means it’s a Class, but it also shows packages, methods, constants, interface and others.

    AS3 Language Reference

    One of the first things I recommend you do is download the ActionScript3 Language Reference zip from the Adobe web site (5.8MB). Unzip it somewhere and use the “Add Local Book” Settings option to add it. It will still need to be indexed (and this takes a long time), but it’s better to grab the zip as it can often have more up to date docs vs. those installed with CS4.

    I’m quite sure that this app will save me a lot of time vs. digging through browser bookmarks.

    Visit the Doc? web site

    All I’d like to see now is this built into FlashDevelop, so F1 searched within Doc? :)