Regardless, here is my plan:

1. Learn Flixel and create a game
2. Port it to iOS [EDIT: that is, port my game to iOS, using the Flixel iOS port that is in the Canabalt source]
3. ???
4. PROFIT!!!

…all while blogging about the experience, of course. At least, that’s the idea — no promises that I’ll actually get very far! If I get really ambitious I might even write a tutorial at some point.

First experiences

Getting started with Flixel was pretty easy, thanks to the “Hello, World” tutorials available on the Flash Game Dojo wiki (which appears to be the main documentation hub for Flixel). After that I wasn’t sure where to go next, since the documentation is a bit scattered and disorganized. I did find some great info on the Github project page and wiki, which oddly is not linked to from the Flixel home page (as I said, a bit scattered). Perhaps Flash Game Dojo is where all the action is supposed to be now? I’m not really sure.

What I’m finding most helpful right now are the very simple example games, complete with source code, provided by Adam Atomic, which are a great help to see how the framework expects things to be set up. The FlxTeroids source code is instructive, as well as EZPlatformer (which has a nice tutorial with it).

Despite the disorganization, there is a lot of good information out there, including the very active forums (which I’ve not yet explored).

A question of units

One bit of info I couldn’t find was what units the FlxObject class uses for velocity and acceleration. I did a quick experiment, and it turns out that velocity is in pixels per second, and acceleration is in pixels per second per second — all very sensible, but it wasn’t explicitly stated anywhere I could find. Similarly, the angle and angularVelocity members are in degrees (not radians) and degrees per second.

What’s next?

This has been a bit of a rambling blog post (I, too, am a bit scattered!). Next I decide on what kind of game to make (something very simple) and start making it! Along the way I will share what I’ve learned.

Stay tuned…!

If an app wanted explanatory text in the Settings app, you pretty much had to make do with Titles and Group titles. Ugly.

It turns out that in iOS 4.0 and higher, Apple allowed for third-party apps to have descriptive text too. And I only found out about this last week (I noticed its use in the Ladidude app).

The longer descriptive text is called “Footer text” in Apple’s nomenclature, and can be attached to any Group. To add your own, do the following:

1. Open your Settings.bundle Root.plist in Xcode
2. Go to the group you want footer text attached to.
3. Add a new Item to the Group and edit the key to be “FooterText” (you’ll have to type “FooterText” in manually):
   
4. The set the value to whatever text you want to show up. If you need to insert linefeeds, type option-Enter.
   
5. Now you can visit your app’s settings in the Settings app. It should look something like this:
   

If your app is compatible with iPhone OS 3.x as well, not to worry: the extra FooterText key is simply ignored on pre-iOS4 devices.

I’ve created a PHP script that makes this task somewhat easier.

Requirements:
A web server that runs PHP 5 with the following extensions:

• ZIP
• either MBString or Iconv
• either BC or GMP or phpseclib

Installation/usage:

1. Download and unzip the files into a new directory on your web server.
2. Create a directory for each app you want to deploy (the directory cannot have any spaces in its name!).
3. In this directory, put:
   • the .IPA file of your app, built using Xcode’s “Build & Archive” command (no spaces in the filename)
   • the .mobileprovision file (again, no spaces in the filename)
   • a 512×512 PNG file named iTunesArtwork.png (case-sensitive)
   • a 72×72 PNG file named Icon.png (case-sensitive)

   The directory structure should look like this:
   

4. Now visit the web page that corresponds to the directory where you unzipped the files. You should see something like this:
   
   with one entry for each directory.
5. Visit the same page on an iOS device running iOS 4.0 or higher. You should be able to install the app simply by tapping on the corresponding “app” link. You shouldn’t need to install the provisioning profile separately, but if you do, it can also be installed via the web site by tapping on the “provisioning profile” link.

That’s it. I admit the code is a bit of a mess, as it was hacked together relatively quickly. I haven’t been able to get it working when there are spaces in the names of the files or directories. Perhaps someone else can fix that :)

This code uses the very useful CFPropertyList PHP library by Rodney Rehm to parse the Info.plist file that’s in the IPA, to extract all the info required by the XML manifest. That’s how the magic happens.

Download the files here.

But something odd was happening. After my appDelegate called registerForRemoteNotificationTypes:, I was not getting any response callback at all; neither application: didRegisterForRemoteNotificationsWithDeviceToken: nor application: didFailToRegisterForRemoteNotificationsWithError: was being called. That’s right, not even an error callback.

Meanwhile, the code was working fine on my iPhone. A few quick Google searches didn’t turn up anything very useful, except for one suggestion to try installing another app from the app store that used push notifications. I figured that would at least be good for a test.

I launched the App Store app, and tried to download Boxcar. I immediately got this alert:

The clue!

Aha! Of course. Because the iPod touch’s battery had died, its clock had been reset to 1969, and thus could not make an SSL connection to Apple’s servers. Setting the iPod’s clock to the correct data and time fixed the issue: push notifications were now working correctly.

I just thought I’d document this in the off chance that it might help someone else :)

It turns out that for whatever reason, if you try uploading your certificate signing request using Chrome, it will fail with an error (Chrome bug? site bug?). So: use Safari (or Firefox, apparently, based on the comments)!

That means there’s no way I could get anything approved for the app store before October ends. I suppose, in theory, I could get something ready to at least submit by then, but that means completing a whole game in a week’s time. It’s possible, but to be honest I’m not sure if I’m up to it.

All I’ve got so far are two rectangles on the screen. In theory, this will become a gameplay prototype. In practice… it’s two rectangles on the screen.

I sure hope I get better quick. Not going to give up just yet. In the meantime, I think I’ll just go and have a little lie down somewhere.

I’ve been meaning to participate in one of these game-making challenges for a while (like Ludum Dare, or Toronto Game Jam), but never have, partly because those 2- or 3-day sprints are a little too easy to procrastinate about (blink and they’re over! and I am a master procrastinator), and partly because they seem a little too intensive for me in my advancing age (I like sleep!).

This one seems like something I could actually do and yet still be a kick-in-the-pants challenge. I like that PoV references NaNoWriMo in his post :)

Since I plan to make an iOS game, fulfilling the last part of the challenge (sell a copy) is partly at the mercy of Apple’s app review process, but I’m going to give it my best shot anyway. And of course I plan to blog about it all here.

Wish me [good] luck! And let me know if you’ll be participating too.