I keep distracting myself...

I've found that when I'm working on things that occasionally I'll focus on things that aren't terribly important rather than getting something working. For instance, I've been working on Alpha 3 and making some good progress - got the entire create new game system reworked and it's acting well. Now I need to start looking at changing the game logic and display to work with the Easy, Medium, and Nightmare modes. And what I did I most recently find myself doing? Taking a snapshot and working on the background for the main game screen.
I mean, the background does need to be completed, but honestly - it can wait until I'm closer to being completed with the game play. It's hard, though, because I know that it needs to be done, it's something I can work on in my mental background, and I'm playing with the colors and layout anyway due to the Easy and Medium play. Still, though - like reading quickly - I sometimes have to remind myself to re-focus on what's important.

The clunky main game
interface screen

It's a little harder with independent projects because I'm not tracking it as closely as I would a project at work. The background IS ugly as compared to the rest of the app now because it's all clunky (as shown to the right). I did ask if the interface seemed non-intuitive and such and got back (from one person) that it seemed fine. I'm hoping that if I can make it a little prettier, use some better images, etc., that I can make it clearer what's being used for what. I need to just make sure that it's not becoming a "high priority" item for me, but rather staying in the background. I know that I'll get it done before I put out Alpha 3 and I'm actually making faster progress than I expected. Still have a couple of changes to make to the data flow to support the additional checks for letters - which ones are right and which ones are in the right position. Sort of brings in some skills I haven't done with Xcode and objective-C, so it'll be a good learning experience. I just hope that I can get it sorted out quickly and back to doing what doesn't matter.
What kinds of things do you do when you're developing to keep yourself focused on the major tasks and not get sidetracked by the "cool" things you still have to do?

Alpha 3 Update

It's been over a month since I sent out Alpha 2 and the main comment back from testers was: this game is really hard! I've decided I need to focus for Alpha 3 on adding in game difficulty. It's something I wasn't really planning on doing quite yet (it was going to be after this next release), but I think that in order to get the most feedback and to make the game approachable I need to get difficulty levels sorted out.
There are two main changes I need to make to get it working. The first is that I need to redesign the "create new game" functionality. It's kind of clunky right now design-wise, so I'm going to delve into that and get it cleaned up and segmented a little better than it is. The second is that I need to change the main game screen UI to support the easier levels.
The current UI looks like the image on the right. It's obviously very basic (and not terribly helpful), but the idea is that you find out how many letters from your word are in the computer's word. For TOMBS, none of those letters are in the computer's word. FIRED and GLYPH both share one letter, but that letter may or may not be in the right place. (In case you're wondering, the "Debug" button in the corner will show you the word in case you get stuck - but just in the Alpha games.)
I'm envisioning 4 different levels of game play. The first - Easy - will show you which letters are correct and in the right place and also which letters are correct but not in the correct position. Medium will display which letters are correct, just not whether they're in the right position. Hard will be the standard game - you only see how many letters in your word are correct, but not which ones. And Nightmare (because I do love me some Quake and Doom) will only let you know when you place the right letter in the right position (but won't show which letter). Yeah - nightmare indeed.
This is going to require quite a bit of redesign to the UITableViewCell to display this additional information. Plus, the whole background for the game board is very bland and uninteresting right now - just white with controls on it. I think it makes sense to beautify it a bit so it's not so jarringly different from the rest of the screens. So Alpha 3 will be a significant release. I just hope that I can get it working in relatively short order. I guess I better get cracking on it...

Alpha 1 Released!

I went home over lunch (the spousal unit is "not well") and decided to take another stab at the installation. I cleaned everything, rebuilt, and sent it back to her email address. When I unzipped everything and dragged it onto her iTunes it seemed MUCH happier - my icon showed up in her Apps list, which was nice. When I click "Sync" it all installed happily and life was looking much brighter. When I ran it on her iPhone and it actually WORKED, that was great (and it connected to the website to get the word list), life was FAN-FREAKING-TASTIC!
I've packaged everything up and sent it out to my alpha testers who will hopefully be able to install it and test it. And I hope they'll be able to read the help screen. In the interest of just getting the alpha out the door I opted to punt on the scrolling help image. It's a placeholder anyway and I couldn't see continuing to hold up the alpha to make it work when it wasn't going to be in the final project anyway. The existing solution is less-than-optimal, but it's also temporary.
In the meantime, my game is now out in the wild. A momentous day for Otto Von. W00t indeed.

Alpha 1 Updates

Well, it was a busy weekend for the Empire Lyric Players, which meant it was a busy weekend for me (because I'm president of the group). Rehearsal Friday til 10:something-way-too-late, Saturday off (I played a TON of Dragon Age: Origins - definitely needed the break to stave off the pending mental collapse), then move-in on Sunday, which went much faster than I expected. We arrived at noon to help unload and they were finishing getting everything off the trailer into the theatre. WOW. I don't think move-in has ever gone that smoothly or had as many participants (practically the entire cast was there). Then errands on Memorial Day and first rehearsal in the theatre. Hard to believe our show goes up in 2 more days!
But wait - wasn't this a post about Alpha 1 Updates? Why yes, you're right - it is! Thanks for the reminder. So where IS Alpha 1? The short answer is "coming soon". The longer answer is a bit more complicated. I was having any number of problems getting my app debugged. It was working fine in the simulator, but as soon as I installed it on my iPhone it would crash on launch. No warning - just "no longer running". I couldn't attach a debug process, the console log (thank you Xcode Organizer!) showed nothing untoward, NSLog messages showed nothing... I was at a complete loss. I restored my phone to just 3.1.3 and then re-synched with iTunes. Still no love. Then, magically, it started working.
For anyone who's been a developer for any period of time, the "magically disappearing bug" is a frightening thing. Why did it go away? When will it resurface (because without fail it will)? I still can't find anything wrong, though, so it's hard to say it wasn't not some kind of configuration problem, but I'm not happy. I thought I would try to install it on Susie's phone as well to see if it surfaced there (I turned mine into a development device so I could see what was happening, but it didn't help). When trying to install on Susie's phone I got the strangest error:
The application "OttoJotts" was not installed on the iPhone "Susie's iPhone" because an unknown error occurred (0xE8008001).
Whiskey Tango Foxtrot? Why would iTunes not know what the error is? Oh, au contraire, mon frere, but iTunes DOES know what it is. What error 0xE8008001 is telling you is that you have an unsigned application that iTunes won't let you install on an iPhone. In other words, iTunes thinks the application is not a valid App Store or Ad Hoc distribution. Of course the question now is why doesn't iTunes think it's a valid ad hoc distribution? As to that, I'm uncertain at present. I need to dig into why it doesn't seem to think that I'm building an application with the right provisioning certificates. The error I was getting before from her iTunes was that there weren't any valid provisioning profiles for the application, which seemed odd as it was the exact one I was including in the build settings. She's running her iTunes on Windows and I'm on Mac, so that's always a joy, but still I've done it previously without too much trouble. Definitely more digging necessary, but here's the kicker - this is HELL WEEK.
What is Hell Week? In performance parlance, it's the week before a show opens. Every night is a rehearsal and generally you're still working a regular 9-5 (-ish) schedule that week, so you're up at the butt-crack of dawn to get to work, work a full day, then go to the theatre and spend another 5-6 hours at rehearsal. Then back home to bed all to do it again the next day. Good thing the show opens on Thursday. We have a JDBC movie night on Friday and I might end up crashed on the field at Invesco/Mile High. :)
Over the next couple of days I need to figure out what's up with the provisioning profiles and see why this isn't working as I thought. Maybe in a couple of days I'll actually have the Alpha done and out to testers. When I do, I'll make sure to let everyone know via this blog.

Understanding at last?

So, I was looking at the iPhone Developer Center trying to figure out from the tech notes why symbolicatecrash, which I was reading would be working just fine, was not working just fine. What I believe it is now, though, is that my SDK version is 3.1.2 and my iPhone OS version is 3.1.3. *sigh* Just shows to go you that as a developer you should always stay up-to-date on the latest SDKs when they're released. Now I need to see if there's a way for me to download the old 3.1.3 SDK. Why, you ask? Because of the iPhone SDK 3.2.
The new SDK requires Snow Leopard which I haven't installed yet (I just ordered it). In the interim, I'm just kind of shooting in the dark with what's happening. Given what I've been reading, it seems like that's the issue, which would be nice. If so, it would at least mean that I'm not a complete idiot. :) The worst part is that even if I do get it to symbolicate, I need to find out why it's failing.
Overall it's been a pretty frustrating experience, but at least it looks like things are turning around and this does seem like the most likely answer to the problems I've been experiencing. And it's also not been abundantly clear from the blogs I've been reading what this issue is.
So, there we go. At least for now. *sigh*
Update: I found a link to the old 3.1.3 SDK which I'm downloading now while I wait for Snow Leopard to arrive. I'll at least be able to do iPad development once I get Snow Leopard, but it's not been a big item on my to-do list, so I've delayed. Apparently one version too long. Wish me luck!

Alpha 1 Troubles Continue

I've been trying a variety of different methods to characterize what's happening with my application, but, to date, they've been unsuccessful. I was looking at some crash logs from my phone, but I've been unsuccessful in getting symbolic information for the crash logs. I've been looking online for a solution, but no luck. What I know is that it's not crashing in my code directly - rather, it's buried pretty deep in some core Apple code (which is never terribly helpful). I've been trying to undo the changes I had done to see if that resolves the problem, but, again, no love. I did add some logging to my app and it all seems very happy - my code loads fully and THEN I have a crash.
This is probably the most difficult kind of issue to resolve. First, you don't have anything but the crash logs. Using symbolicatecrash is not an ideal solution to resolving problems. I may need to turn my phone into a dev device and see if I can debug from there. I actually still have several avenues of attack, but they're more alleys than avenues or boulevards. :)
Will keep you updated.

Alpha 1 of New Game Delays (sigh)

Well, the first alpha of the new game is just about complete. Most things have gone as well as I'd hoped, although one section of the game was causing a few more fits and starts than it should have had I just bothered to think about it. I chalk it up to my progressing illness which resulted in being practically incapacitated yesterday and unable to breathe. I have asthma and am not unfamiliar with breathing problems, but this was closing in on how I felt when I was hospitalized with pneumonia and some exotic secondary infection modern medical science was unable to identify (gotta love those). Regardless, I resolved the issue moved on with life.
I then got to the final two things I needed to do before I could begin looking at an Alpha - a basic help screen and, you know, actually getting it ON a device. :) I got a basic help screen image typed up and figured I'd just add a UIImageView object with that as the image to a UIScrollView and voila - it'd all just work. But, no. Nothing on the iPhone seems truly simple and this was no exception. I began working through my primary reference book but it was silent on scrolling. Crap. So I began surfing the web hoping to find something - a few ideas, but nothing that actually did what I expected it to do. As of this morning, no change - help is still not scrolling. *sigh* I may need to create a completely separate application to test the theory and then make sure I've dotted all of the i's and crossed the t's in my app to enable everything.
The second part, which I decided to do after punting on the help, was to get it installing on the device. I had already done that with a previous version and figured this wouldn't be a problem. I built it, installed it, sync'd my iPhone, ran it - and it crashed. CRAP! Oh, wait! Glimmer of hope - I was referencing a local file (I was developing sans network at one point and changed the code). Change the code, reinstall, sync iPhone, run app - crash. Whiskey Tango Foxtrot? This was working fine in the simulator... and still does. Okay... Wait - there's some kind of crash log available. Quick search on the web and I find what I need - where it is and what it looks like. And it looks like a symbolic dump of a Windows app with the same level of detail (i.e., none). Wait - what's this "symbolicatecrash" script? It enables you to turn your crash logs into something with actual symbols? Cool. I'll at least know where the crash is. Except that it didn't work. I poked around a little today and think I might have an idea why it's not working as expected, but again - it's delaying Alpha 1. I did try adding some additional checks this morning quickly to see if I could get around what I thought the bug was, but it did nothing. Great...
So, Alpha 1 is practically in the bag. Unfortunately, there are still 2 bugs holding up release to the wild. Okay, it's more of a caged environment, but still. Hoping it will be done in the short term. I would hate to have ANOTHER application for the iPhone that gets stuck in "Alpha Hell".

Prototyping new game

So I've taken a bit of a hiatus from Daimyo, but just briefly. I'm working on the prototype to a new game that I'll reveal when it's done. I'm going back to Objective-C for iPhone work and, honestly, it's been a bit of time since I worked on anything about it. Good thing is that things are coming back a little faster than I thought it might. I need to get back to some of my reference books, though, because I want to do something that's not really "standard" now (of course). Overall, though, it's coming along nicely as a prototype. I didn't actually think I'd be able to knock this out as quickly as it's been going.
Also had fun checking out an interview with Natalia and Keith at Imangi studios. Ready Set DC did a profile on them and it was quite nice to read about some folks I've been following on Twitter because, well, they're awesome but also the kind of people I could see hanging out with on a Friday. :) The link to the article is here.
So, things are progressing well with the prototype and Daimyo is after that. I think that the weekend may see the completion of the proto, which gives me a week or so to actually knock out the product and get it in people's hands. Then it's off to make the pay version (the proto is of the lite version) and then, maybe, get it up on the App Store.
So, there ya go.