Showing posts with label beginner. Show all posts
Showing posts with label beginner. Show all posts

Saturday, September 29, 2012

Wizard's Magic Ball 2.0 - Delivered!

If you've got my Wizard's Magic Ball app, then you may have noticed an update today.

That update is a neat, new customization feature.  It allows you to write and record your own answers for the Wizard's Magic Ball.  If you're unhappy with what you've recorded, you can always restore the default voices (though, you have to save again if you want the default to stay on).

Also, if you look at the screenshot to the left, you'll probably notice the difference in color between the "yes" and "no" answers. This is to indicate which group the answers are in for rigging.  If you rig for "no," you'll get an answer for the orange group, and if you rig for "yes," you'll get an answer from the green group.

Go try it!

Also, look for a couple of very special updates tomorrow....

*Sneak*

(Oh, side note: this is not yet released on Android.  That will happen sometime soon...)

Sunday, March 4, 2012

Wizard's Magic Ball - Delivered!

UPDATE:  My app is in the App Store as well.

It has taken long enough, but I finally got an app delivered.

(click the image to go to Android market)

It turns out that even the smallest of apps is a ton of work.  Even this one, which was made with the use of the wonderful Corona SDK.

If you're interested in developing for iOS or Android and don't have the time, energy, or money to get up to speed with both Objective-C and Java, I highly recommend Corona.  Best of all, it's free to try out, so what are you waiting for?

That being said, I learned quite a bit in getting this little app to market:

1) Windows may not care about file name capitalization, but every other OS does, so if you're developing on Windows, do yourself a favor and pick a simple strategy for naming files (like keeping them all lowercase) and stick to it.  I spent several hours trying to figure out why my app wouldn't work on my tablet, only to trace it down to a reference to "LevelEditor" when the file name was "levelEditor."

2) Multiple X-Code installs will likely cause a headache when attempting to deploy to your iOS device.  This site was instrumental in getting my system setup to deploy Corona apps:
http://pushkararora.com/how-to/how-to-uninstall-xcode-completely/

3) For current Corona users, you need the following: X-Code 4.2 (4.3 is currently not working with Corona because of some of Apple's changes), and the current Application Loader.  Application Loader can be found on iTunesConnect, a site you will probably never have heard of, if you haven't done any iOS development before.  Also, it's almost impossible to find (go to Manage Applications, then look at the bottom under Application Loader).  The easiest way to get up to speed is to uninstall all X-Code installs, restart your system, install X-Code 4.2, restart your system, install the latest Application Loader, restart your system, and proceed from there.

4) Apple must use stagecoaches to deliver your app to the reviewers.  Also, their process for signing apps must have been borrowed from the Dead Sea scrolls.  For reference, it took me about an hour to get my app on the Android and Amazon market places.  It also cost me $25 (that was for the Android market, Amazon costs $99 a year, but they're waving the first year).  To get it on the Apple Store took me an entire day and $99.  Also, it's still not out yet.  I have to wait at least a week for them to accept my contract so that I can sell apps and at least a week for them to review my app (as of right now, the app has still not been picked up for review).  Be forewarned.  If you have any sort of deadline, get your Apple accounts squared away before starting on your app.

5) Corona is awesome, but there are some things to be aware of, most notably: test on as many devices as you can because the resolution will be an issue.  Corona comes with some neat scaling features, but while that works well for scaling big images to the right size, it doesn't help out so much with positioning of game elements.  I wrote a utility class for take the device's resolution and using that to scale all my elements and positions to the right places.  NOTE: Corona auto-scales assets if they won't fit in texture memory.  That means that, with my code, I had to make a special case to deal with assets that might run afoul of the texture memory limits on some devices (basically, anything over 1024x1024).

6) Make sure that you make a vector version of some of your screens and your app icon because you'll need a set of screens and icons in a myriad of sizes for each market place.

7) Asus Transformers often have a power button issue that comes from the outer button not lining up with the physical one inside.  I'm still trying to get mine fixed, but be forewarned if you're thinking about picking one up for running your apps.

8) Getting an app onto the market places where people can buy it and play it is an awesome feeling.  I recommend everyone try it out.

Wednesday, July 27, 2011

How to get Ruby on Rails running on a PC with zero prior knowledge!

I know next to nothing about Ruby or Rails, so of course, I'm beginning by following tutorials on the internet. A couple months ago, I went to http://www.ruby-lang.org/en/ and did the super intro tutorial at http://tryruby.org/. If I don't get too distracted with attempting to get Android and Rails talking, I think I'll go through the other tutorials referenced on the ruby-lang site. More on that if I return to them.

Beginning here:

Notes:
  1. There's now a selection in the installer for Td/Tk which has something to do with GUI building in Ruby... more on that later if it becomes important. (spoiler: it doesn't)
  2. I'm running Vista, so when I start the gem server, I get confirmation dialogues by the dozen. Good times.
  3. I just installed Ruby for the first time, so I've only got these gems installed: minitest, rake, rdoc, rubygems.
  4. If you follow the instructions to a T, you'll see the following dialogue noting that sqlite3-ruby has changed names.

  1. Though, it no longer tells you to add the .dll to your bin folder, I figured it couldn't hurt, so I added the latest dll to my C:\Ruby192\bin folder. I got the latest by going to the download page and selecting the only one I saw.
  2. I installed rails per the instructions, and I got this sweet error(it says generating docs, so hopefully, this isn't important... :/ ):
















  1. At this point, I would like to note that Rails (or I guess I should say Ruby) scares me. I've just typed a few commands, and some super complex stuff has been taken care of for me (or at least that's what I'm guessing based on what I've read and what I'm seeing happen). This is awesome, exactly what I've always wanted, but it makes me nervous. Didn't someone say something about being careful what you wish for?

And that's it.  Gertig's instructions totally worked.  Now, it's time to follow his tutorial to link Ruby on Rails and Android.

(Note: I've almost got Android and Rails talking, but I left my cable at work, so I can't test the last change, meaning my post on it will go up tomorrow when I'm sure it works.)