Programming Challenges for Mac Developers
Carlos Camacho writes "iDevGames, a Macintosh Game Developer's Site has started issuing small programming challenges to Mac developers. The first challenge just wrapped up and the result is two nifty apps. The source code for both apps, and all apps entered into the programming challenges, will be released as open source. The next challenge has added an extra day, so developers have 72 hours. The focus is on creating an application to demonstrate 'A* pathfinding.'"
Is 48-hours too short? Would 72 hours be better? Or is 48-hours about right? Please vote. If you don't mind, I would like to announce the next challenge. (At some point, I will take everyone's suggestions for other Challenges.)
OK, here is the challenge:
* You may use ObjectiveC, C, C++, or Java only
* Create an application to demonstrate how A* Pathfinding works.
* You don't need to use fancy sprites. Simple circles, or stick figures is of course fine.
* Your world can be 2D, 2.5D, or 3D.
Outside of the main objective, there are many extras you can put into your app to set it apart from others. I won't mention them because it is great to see people discover them on their own. The goal is this challenge is that we will be able to show newbies how A* works, and give them code to learn from.
Kinda sounds like they are wanting to get other people to do their work.
First Contest: Develop a Cocoa program that will calculate the distance between two spots on the globe. (given latitude and longitude. ) There were only two submissions. Second Contest: Develop a graphical representation of the A* algorithm using Java, C, or Objective-C. (This one will be 72 hours.) No prizes, only bragging rights... for a site that noone even goes to. Yipee! Have fun.
Perhaps they are hoping to get a variety of examples so newbies can see more than one implementation? Also, perhaps they want to give their readers something "fun" to do... I can see how some people would enjoy having a little mini-challenge every now and then, and they will enter the contest; and other people are too busy or would rather spend their free time in other ways, and so they won't enter the contest... And that's fine.
zach
People need to think about their headlines before they submit them. I thought this was about the difficulties Mac programmers face in today's world.
Too bad their site doesn't display the body text in Safari. If they're a Mac site, they just *might* want to fix that one.
Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
Just in case you didn't already know, the general consensus is that Aaron Hillegass's "Cocoa Programming for Mac OSX" is the best Cocoa book out there.
/ Ap plicationKit/ObjC_classic/index.html#//apple_ref/d oc/uid/20001093
/ Fo undation/ObjC_classic/index.html#//apple_ref/doc/u id/20001091
Just as important as the the Cocoa book, is bookmarking the Apple Developer Documentation in Safari
file:///Developer/Documentation/Cocoa/Reference
file:///Developer/Documentation/Cocoa/Reference
I wasted money on a couple other books before I found that one.
If you're still having trouble learning, just ask someone for the source code to a finished app that isn't too big and study it. (If you're really desperate, I've got some code you can study).
- - - - -
Caffeine is not a substitute for sleep
prefixing every software package name with an i
Another good thing to do is to get your hands on a Cocoa class browser. Here's one:
- br owser/
http://homepage2.nifty.com/hoshi-takanori/cocoa
Seems like a pretty obvious concept, so I'd be surprised if there aren't others. In any case, it can be handy.
Get working on porting OpenOffice.org to Aqua! The current ETA is 2005
It'd save me *so* much time having to run around ensuring people don't have illegal copies of MS Office on their macs.
At least with my PC users:
a) The OpenOffice.org interface isn't glaringly different
b) They can't just copy the MS office folder between machines.
-Yarn - Rio Karma: Excellent
There's a class browser built-in to Xcode. Select "Show Class Browser" from the Project menu, or press cmd-shift-c.
irb(main):001:0>
Aaron Hillegass's most excellent Cocoa introduction Cocoa Programming for Mac OS X
When you're done with that one, skip on over and check out my defacto Cocoa bible, Cocoa Programming. Just a fantastic book, application design reference and compilation of knowlege from many years of working with these frameworks.
O'Reilly's Cocoa in a Nutshell, the API listing you've been yearning for.
Always remember to include Apple's own Cocoa developer pages.
That's probably right, but once you've finished it and digested it, so to speak, which probably won't take more than a couple of weeks, the next must-have is Anguish, Buck, and Yacktman: Cocoa Programming. Very in-depth reference guide with some excellent explanations of why Cocoa features work the way they do. Hillegass and Cheeseman are always saying "just do it this way, trust me," which is pretty unsatisfying when you're trying to figure out how to make your own apps do things that you want. That said, Cheeseman's book is the best all-around reference (though it's set up as one massive, continuous project) on Cocoa application "design" (showing you how to package your app, set up resource files, localization, etc.). Anyway, my $0.02 as an owner, reader, and user of all three books.
Shop as usual. And avoid panic buying.
That's rather like calling Slashdot lazy for trying to get their readers to write news articles for them. It completely misses the point of the site.
iDG is a community of Mac game developers. Some of them are hobbyists. Some of them are professionals. The developers there encourage each other, help each other out, compete against each other on small challenges like this one, or larger ones like the uDevGame contest which attracted $27,000 in donated prizes to encourage Mac game developers.
The 48- and 72-hour challenges are an experiment introduced very recently. Developers at the site wanted a fun, low-key alternative to the intense 3-month contest we run every year. The contest may also allow the site to collect smaller, less intimidating code examples than the ones generated by the 3-month contest.
The editor/founder of iDevGames works very hard to run the site and serve the developer community. Lazy is the last word you'd use to describe him. Nor has he any use for an A* algorithm.
Stop throwing rocks at things you don't understand.
"And there be unix which have made themselves unix for the kingdom of heaven's sake." - Matt. 19:12
FRIEND: Behind on your homework? Brilliant!
ME: No, not brilliant. Hey, I've got an idea.
FRIEND: Brilliant!! ME: Hear the idea first! OK, so I've got an assignment due on A* pathfinding. Sooo, I'm gonna hold a programming competition and have everyone submit A* pathfinding programs to ME!
FRIEND: Get unsuspecting programmers to write your homework for you??