Hello catch_up, I appreciate the feedback.
In all honesty, and not really a bash on other tutorials out there, I don’t really pay a large amount of attention to them, except when deciding if I should do a tutorial series or not. For example, I won’t be writing an SDL series anytime soon, as Lazy Foo pretty much has that topic nailed, and things haven’t changed enough to change that fact. I also don’t really consider video tutorials as “competition”, although that is totally the wrong word to use. Having more tutorials available is almost always a good thing, assuming of course the tutorials are teaching correct information. Generally though I find that people prefer either video tutorials or written tutorials, or video tutorials for some tasks and written for others. So even if something is covered, and covered very well, in video form, I still thing there is a large group of people out there that want a text version. More so, until Google has the ability to search into Youtube videos and jump to the exact spot people are searching for, this will always remain true.
The biggest part why I don’t really pay all that much attention to the other tutorials, and write my accordingly, is if I cover everything myself, I know what the reader knows. Plus of course I’m a bit of a control freak. I actually take more or less the same approach to writing tutorials that I do when writing books. In the end, when I am done with my series, I want the result to be as good or better than any book that’s available on the market.
In the end though, the reason I take the approach I take is ultimately because of exactly what you just said: [quote=“catch_up, post:20, topic:17373”]“Anyways I like your work so far although I had to learn these things either by asking in forums or by reading documentation and all.”[/quote]
This is what I seek to solve. I want to provide a single learning resource so people new to Cocos2d-x don’t have to hunt around through the documentation and across forums, which gets exceptionally confusing in the case of Cocos2d-x because of the v2 vs v3 differences coupled with all the other Cocos version results muddling up the results. I don’t aim to be the be all resource on Cocos2d-x development information, that’s just silly considering how well documented the library tends to be. But I do want to be as good or better than any books that come along, and the perfect introduction to Cocos2d-x for beginning programmers. At least, that’s my end goal.
Of course, it’s all predicated by popularity. If ultimately it doesn’t prove all that popular I can’t see investing a huge amount of time on new content. Fortunately I think even in the worst case scenario, what’s written should still be of use to new and returning developers.
So, in a rather large nutshell, that’s why I’m taking the approach I have and my goals for this series. Hope that made sense and you didn’t fall asleep reading it.
EDIT - I suppose in the end what I am working on is very similar in scope to the in progress programmers guide. As I said earlier, multiple options are almost never a bad thing, much as multiple books can cover the same subject and succeed.