http://www.packtpub.com/cocos2d-x-by-example/book

Where to start... "Cocos2d-x by Example Beginners Guide" is a good great book! Turns out one of my Appsomniacs partners has bought this book and also enjoyed its knowledge (votes+=2). Even have cut my teeth and shipped on iOS, Android and Windows 8. The Windows 8 was such a hack job I could never get it cleaned up to do a push request (I think, I should just try, at least put it in my branch. Please nag at me if I don't... It may be a bridge too many not subtle changes. Anyway, I digress, the rest of this about this great book that might help a lot of people on their Cocos2d-x journeys.

=====

1) The first thing that popped out at me when I cracked the spine on this book was the large quantity of and the technical diversity of the contributors. I was impressed with their bio/resumes and the book certainly was better for it.

2) Hang on tight. The gas pedal is binary. The book gets you up and running rather quickly. Almost too quick in some respects, but later chapters make up for that hand holding fast start in ten fold. I was worried at first a lot of bits were glossed over. Do not worry about this stuff. Great details will be given in droves, and when not a good entry point to references often sufficed.

3) I actually appreciated the section (within chapter 2) that was a primer on as well as described why the C++ was arranged the way it was (e.g., what conventions were from the Objective C world and reminders of things you need to remember to do when in C++ (i.e., proper memory management because ARC is not available.)) My favorite quote so far "... relax, and let the framework work for you."

4) The learn by example part struck me as well done. It could always cover more. I was wanton for more after 6 games. Maybe combining this and the ideas found in the iPhone Cookbook you could get even more mileage. Frankly, after you tackle this books examples. I did one a weekend (~4 hours in 1-2 sessions usually) you will be pretty well versed. The games are varied enough and the topics within cover a lot of ground. I will always want more!

5) Chapter 10 is gold for anyone coming from iOS and wanting to break into Android and really use the greatness of what Cocos2d-x brings to the table (IMO anyway.) You are presented a nice 'uncluttered' step by step walk through (albeit the compile sections was 20 steps, but they were important 'no fluff' steps! I am pleased they linked their sources on this one too. Our team put this stuff together by piecing together Android NDK posts and trial and error last year (of course we never thought to share because we never thought we did it right to begin with... it compiled... and ran, so we shipped it anyway...) I think the chapter here would have saved us much time and pain. Luckily you now have this resource to leverage. My only wish was that a little more time was spent on the tricks you have to go through to get as clean as code as possible (not special casing every piece of logic with pre-compiler directives, etc. for each platform.) Maybe a little treatise on design patterns would have been helpful here too. But I guess all of that is really beyond the scope of the book (i.e., a lifetime could be spent learning how to write well designed cross platform C++ code. If anyone knows of a good book let me know!

6) I want to mention the index. It was a basic run of the mill index. Don't get me wrong it was a good and proper index. But I can not help but note this book chapters were laid out similarly to the iPhone book "Creating Games with Cocos2d for iPhone 2", which had a brilliant index (I bet someone hated it... those darn trolls convinced them not to do it this way!) In the iPhone book most chapters covered an entire game by example much as this book did too. The iPhone version's index had a breakdown of a game chapter by game name as a sub index of concepts within it. I absolutely loved that and I dearly missed it in this one. The index is fine as it is, but having tasted the other books additional index by chapter concepts I found myself longing for it as this new book was also a perfect candidate for that format as well. But it is no reason to not get this book if the subject interests you. File this under 'I have to find something to complain about in a review' comments.

=====

I do think beginning, but versed, C++ developers could pick this up and succeed if they try. If you have Objective C down C++ is not really that hard to grok also (and the parts you don't use won't likely come into play as nearly as often as you might think.) Advanced users probably won't get a lot out of it, but if you are street learned on Cocos2d like I have been (and still am learning in many respects) it wouldn't hurt to have gone over this material once.

http://www.packtpub.com/cocos2d-x-by-example/book 

Thank for sticking out my wall of text this far. I am pretty sure there is an achievement for having made it this far. ;) 

I was reminded the other day of "where to start" with an idea regarding game design and conceptualizing out your game. I was remembering a great bit of information on the topic that was instrumental to me at the time I was getting my feet off the ground...

Ian Schreiber, besides being a pretty nice guy in general, shared some pretty deep thoughts and analysis on game design in a very grand 'global' experiment a while ago in which I only partially participated in. I always regretted having to choose the path I did that took me away from it at the time, but revisiting the material has been invaluable over the years.

http://gamedesignconcepts.wordpress.com/

I really like this book co-authored by Ian Schreiber and Brenda Brathwaite (soon after Garner, now Romero):

http://www.amazon.com/Challenges-Game-Designers-Brenda-Brathwaite/dp/158450580X 

It all takes a step back from the computer a bit (and that is a good thing sometimes!), but I haven't found a single thing that didn't translate in some fashion. And the techniques on troubleshooting and verifying mechanic, although laborious, I have found worth it.

There are certainly a lot out there. But these two sources have a common voice by Ian and I like his attitude (and Brathwaite has pretty epic contributions to the industry as well and deserves more than a foot note here, but this about Ian.) Someone who manages a production schedule might go insane, but you end with a quality product given the emphasis on testing and evaluation.

Here is your entry point that is as good as any of the best entry points I have stumbled across in my searches yet.

You are welcome.

Well the news is local if you live in Kitsap County in Washington State, in ye olde United States of America (no to be confused with DC!)

http://www.kitsapsun.com/news/2013/apr/06/kitsap-creators-of-dwarf-fortress-make-losing/

As a stalker of me you should know I love me some Dwarf Fortress! I envy Bay 12 in many ways. Being able to work on your life's work is pretty darn cool. I always fear that some day something awful requiring a lot of resources from Tarn and Zach Adams will cause them to be pressured to 'sell out'. I don't think I would mind. Actually all they have to do is ask and I bet thousands upon thousands of us would simply open our hearted wallets and help them through the dilemma.

Nuf said on that.

I just upgraded Xcode to v4.6 (yah yah it took me long enough, we have been VERY busy all over the place.) BUT I am not ready to update all my devices to the latest iOS version (6.1 at the time of this entry) I always forget that I need to go get the previous SDK's. By far the easiest method is to simply use xcode to install them.

From the menu choose Xcode->Preferences and the Downloads tab. I just installed everything since we support all the way back to v4.3, actually we have v3.2 support in most of our games. I think that will change this time around. With Apple's mandate to support, among many things, iOS 6 and the new iPhone screen size (to include updates...) we can't update our older titles with adverts for our new stuff... its a 1st world dev problem... The writing was on the wall last year for a lot of this. We really slacked off on updating. I promise you we will get to it! According to analytics this will screw a couple people who play with older devices... Typically less than three in a month... I hope they forgive us! (I am sorry!!! I really am!!! Apple made me do it!  )

For now I wait to test the Doodle Army client against my recent server changes...

I have been making great strides in reading through a book on cocos2d (for iPhone) and although I have yet to go cover to cover (I keep jumping around!) I want to get a quick review out for them of the parts I did get a chance to study.

http://www.packtpub.com/creating-games-with-cocos2d-for-iphone-2/book

Let me just open with how refreshing it was to pick up a book you are ready for skill wise. I have a few games I worked on in the App Store and I have some [street] experience with cocos2d and this book is a nice fit. So I dive in. You might not want to use this book to start learning cocos2d. And if you read warnings, prefaces, and intros you better pick up on that from the books description real early and IF you still got this not knowing a thing about cocos2d 1) I applaud your tenacity 2) I shame you for not doing some up front due diligence... You have failed yourself. But this post is not about you, BUT if this matches what you did then hang onto the book and go check out Ray Wenderlich's intro tutorials for that (I can't leave you with nothing, this is where I started my education btw. I owe Ray a couple dinners now... I'll settle that account someday.)

So back to the BOOK! As I said I tend to read a book cover to cover, that is my preference. Schedules, releases, bugs, family are just going to let that happen this quarter. But I have been in and out of the text every down moment I had. Which is telling, considering I chose soaking up some tech text versus firing up some Minecraft. I must admit I jumped around a lot! There are some parts that build on one another. Luckily in every case I encountered there is a reference back to the moment I should be building on. Depending on your experience level you might not need that though.

A little side note on finding a specific 'thing' using the TOC (table of contents) or the index...  Since Each chapter is covers a fairly familiar game 'type' unto itself the TOC does not lend itself for specific message lookup. If you are looking for a specific CC message you will want to start in the index. What I did find interesting was each chapters game had a detailed index, so you could scan that and get a *REAL* good idea what each chapter holds. I think that is the primary way since the TOC through me a loop initially. I appreciate the cute names and the text is fun like from time to time. If your not in a mood for that you need to steel yourself for those moments. Work through it! I did. So can you! ;)

This a great concept book with enough concrete examples to get your own code moving in the right direction (including reasoning for the choice of convention in several places, which if was your only awareness of the way something was done *cough* *cough* you [I] would never have known otherwise.) I learned something new (old) from this book I missed in my grueling on-the-street training... For that I give the book high marks. Your mileage may vary, but I appreciate the alternate takes on approaches. I feel stronger because of it. Knowing they exist. 

So the best thing for me in the book... I wish the book was out when we figured out how to do Bluetooth that would have saved us some serious pain in the making of Doodle Army 2. You kids don't know how good you have it! Now get off my lawn! (and you might want to go check out this book!)

The price is not bad at all either! Check it out.

http://www.packtpub.com/creating-games-with-cocos2d-for-iphone-2/book

A totally thought filled review of Doodle Army. Doodle Army is not original, but it is meant to embody the best of the genre in its execution. Which is likely why it is popular enough.

http://commonection.com/doodle-army-reminds-us-that-simple-concepts-make-for-the-best-games/

It has been a long time coming! But a stable x86 build passed muster in the store certification process. It is/was slated to release 2/27/2013 (in a few days) but I found a huge bug in the zombie mini game level... In this mini game you spend the night fighting the zombie horde off... Eventually they overrun you, but you get break and a random resupply at days break. You also get to spend your points earned on ammo and health every day (if you live to see the light of day that is...)

By far this is my favorite mini game. It was sad to find an app crashing bug in it, but after I did I got it fixed... Now do I let it release or fix it with a zero day patch? I think I have to try and push it through with all the other fixes I have done.

Here is a screen shot of a bad night to get you excited... With 11 seconds to go to day, I thought I could take my hands off the keyboard to capture the moment...

Every time I make a new game this comes up. Your game's name is a trademark, and in a sad twist of events your chosen name is someone else's trademark! :(

For US check the trademark database (TESS) and see if they have even bothered to trademark into more than just music and extended their trademark to cover digital entertainment markets. Take some time to look at companies trademarks (e.g., Rovio's Angry Birds) and compare it with other popular titles. The grey areas crop up quick. The language and breadth of a trademark's declared written language matters. There is all kinds of fair use laws too. Infringement on an artists likeness, is it parody? How much likeness is allowed. I read about these going both ways all the time... and I am drawing a blank on an example on good examples both ways! (help! anyone?) Weird Al comes to mind, but he asks artists if they mind... Although even that can get messy in the telephone game world of he said she said (for the record I really like Mr. Yankovich's response to all that drama.)

So where to start. I promised an entry point... I always check out TESS http://www.uspto.gov/trademarks/index.jsp

It costs a bit of money to get trademark, and more so if you pay a lawyer to go research a conflict. Then once you have it you must defend it to keep it. That is why any mention/use of another's trademark is frequently met with swift responses oftentimes. Then there is parody, even that is a minefield of potential litigation to navigate... :P

Even before you acquire the full legal trademark a step, that I am aware of, is to start MARKING your stuff (tm), You see that little TM everywhere... That is the warning sign that you intend to or have trademarked what is marked. And it more than just names. It gets complicated rather quickly... too quickly...

I am not familiar with the governing agencies outside the US and I must also declare IANAL (I am not a lawyer), but I know a good one who has done me right, steered me clear, and has a background in patent and dabbled in trademark law. If you get serious, consider a lawyer, it might lead to something (not just fees paid out!) We recently had to defend a property that someone tried to trademark (and claimed WE infringed on) only to discover they had little ground because we had been in market on the App store a year before they even announced development (luckily for all we worked it out and were happy to be compensated to give up rights to the name so they could use it. great game too! Keeping our name was likely to occur if we fought it, and royally screwing them. I hope we get treated the same way when we are big and screw up with a trademark snafu (or in this case a lawyer team screwed up!)

I'll ask my lawyer friend if they want to be publicly named before doing giving him a plug... I think they like working in the shadows... That is a lawyer thing isn't it?

I got hit with this issue the other day after importing a project out of Team Foundation Server, but this 'can' happens when switching workspaces which is where I saw it before, but the fix is the same and is trivial. Simply clean your project.

Go to the menu Project -> Clean

Then rebuild.

Profit.

Share the profit by shouting your love for me far and wide. Twitter will do... @orionnoir

It has worked every time for me (once I remembered.) I am hoping taking time to write this down does the following:

1) helps someone else in their time of need.

2) helps me remember this simple task instead of me staring dim witted at the error message and throwing my arms up in another fit of nerd rage...

#2 is likely behavior that will remain unchanged. For the rest of you I hope this helps. ;)

Meredith Cook, of MulchMedia.com, gave a great talk to the local Adobe user group meeting (PDX Adobe) here in PDX about her experiences helping make Flip the Bird. I was her colleague/wing man to handle any technical questions, but that is not what made it great. She is a thoughtful, well organized speaker, no ones time was wasted for the sake of the well organized narrative she gave. I may be biased, but her story was well received.

http://mulchmedia.com/blog/post/2013/01/08/Presentation-The-Design-Development-of-Flip-the-Bird.aspx

All the nitty gritty details (and links to the updated slide deck) can be found here on her Blog.

She did a great job, the meeting location was much improved over the closet they got stuck in last time (so I am told.) It was fantastic to meet the organizers and people in the community interested in learning and already doing this kind of thing.