A fast, easy to use, free, and community supported 2D game engine
Tim
Member
Folks,
I've put together an overview on OpenFeint integration with the Cocos2D-iPhone framework. It introduces OpenFeint and covers the process to create a leaderboard for your application. It then goes on to show the bits of code I needed to integrate with my Balloon Boy app.
You can review it here:
Feel free to provide comments as well as let me know of any particular errors or suggestions for improvement.
thx
Hi Tim
Things changed slightly with OF 2.4 (latest 2.4.3). 3 more frameworks to add and weak linking of 2, etc...
@jmak35
Looks like it's at: http://pocketworx.com/?p=80
- kalx
Just a quick follow up regarding the tutorial.
It was a breeze to integrate OpenFeint following your directions so again a big thanks for taking the time to write the article.
The only minor change I would perhaps consider is how you add Frameworks to the project.
I used to browse the folders manually and add them too, but I later found out that in the General tab of the target you can add the necessary linked libraries without having to know where they actually reside.
I would suppose this is the most standard approach and makes it a bit more intuitive, although the end result is of course the same.
Thanks again Tim ;)
Hi All,
I've followed Tim's instructions but I just can't get OpenFeint to run. I'm using:
Cocos 0.99.2
XCode 3.2.2
iPhone SDK 3.1.3
My cocos project was created using the installable Cocos project template and is very standard. When I add OpenFeint, everything seems to compile fine but I notice that none of the OpenFeint XIB files get compiled. What's more, they're all in the compile sources build phase rather than the copy bundle resources and I get warnings about not being able to compile sourcecode.xib files. I moved them into copy bundle but they still don't get compiled.
*Then* I noticed that the cocos template project has no Interface Builder compiler build options. I guess the assumption is that noone will want XIBs in a Cocos project.
If I run up the app, OpenFeint reports that it was intialized but no UI shows up and it stops my Cocos UI from working. Comment out the call to OF initialization and it works fine.
BTW, I didn't bother renaming all my class files to ".mm" because I saw someone say you only need to do this for classes that directly interact with OF. So, I put all OF interaction in a separate handler class, which seems to run OK (except for the lack of UI).
I'm going to try tracking down the XIB problem next. The other odd thing is that if I install OF in a brand new XCode project and try and build it (putting in all the right build flags) I get a massive number of compiler errors.
Any thoughts ?
Cheers, Andrew.
Success !!! The problem turned out to be because the XIB files weren't getting compiled. Long story, but when OpenFeint was dragged into the project, Xcode saw the .xib files as sourcecode.xib types, put them into compile sources and then didn't know how to compile them. Turning them all into file.xib types did the trick. So, basically my Xcode is broken when it comes to XIB files, but at least it's all working now.
Interestingly, I didn't end up renaming all my .m's to .mm's, just the ones that directly interacted with OF, and yet OF works fine. Any thoughts ?
- Andrew
I'm trying to update with the latest version of OpenFeint (2.5) a game that was build with cocos2D 0.7.
All compiles OK, but when I call launchDashboard, nothing happen.
There must be something I'm doing wrong.
I've noticed that my game is not using a main xib file to instanciate the UIWindow, could it be the reason ???
[edit]
So it's weird, if I simply change the orientation to UIInterfaceOrientationPortrait, it works!
But if I come back to UIInterfaceOrientationLandscapeRight, it doesn't show.
Note that I didn't remove the resources for landscape orientation, so righti now I'm stuck with this...
@andrewjg: I found out, through experimentation that only objective-c modules that interact with c++ modules need to have .m changed to .mm. However, I usually just rename all of my modules to .mm from with xCode since I like c++.
Thanks for the info on the file.xib too. I had that problem once too last year and it will be nice to remember this solution for myself when I get into OF.
-Mike
You must log in to post.
