| |||||||||||||||
Produktinformation
|
A quick rundown of the sections:
1: Ultra Simplistic - 2 stars
2: Brilliant! Worth buying the book for 5 stars
3: Rushed, Too Concise, doesnt explain anything and useless- terrible : 1 star
(hence my rating of 3 stars - interger average of these values)
I was glad that I had read C# The Complete Reference by Herb Schildt before reading this book. The first section on programming basics is VERY basic - teaching very beginner concepts such as loops, descisions etc that most people reading this book would already know. As someone who must read a book cover to cover I read all this, resisting the strong temptation to skim to the next section. It provides a simple introduction to C#, but not particularly useful,
The second section concerns itself with game creation using Windows Forms and GDI+. The first example in this section, Paddle Tennis, is quite good, and probably worth buying the book for this one example, if you have never done any windows forms or GDI+ programming in C# before (as I hadnt). On the accompanying CD there are all these application files you need to add to your project, which is not explicitly stated in the book, and left me scratching my head when I entered all the source code, compiled and got about 200 errors. Actually mentioning that these prewritten classes needed to be added would have been of tremendous help.
But these prewritten classes are the downfall of the book. Basically the example teaches you how to display images, initialize a form, override the OnPaint & OnKeyPress methods - but thats it. All the code for collision detection is prewritten for you with only very oblique references to it in the text. I built a version of Pong and Arkanoid from what I learnt from this book, but most of what I learnt came from analyzing the source code on the CD...
Unfortunately its downhill from here. There are about 7 more games in the book however there is a very brief introduction with very vague descriptions of the new features in the games followed by source code (that again uses the prewritten classes) - basically the text doesnt really teach you how the games were made, you have to read the code and work it out.
The final section on OOP is a very condensed coverage of all 77 keywords in the C# language. This section is utterly useless - it describes the entire language in 100 pages - meaning there is a very brief introduction on the topic (such as overloading or constructors) a single example and then its next topic! If I already didnt know the language I would be completely lost...
I said however this was a Dichotomous Book as I believe I would still have bought it knowing what I do now. It is worth it for the middle section, which is excellent. I recommend strongly that you analyze the source code on the cd (and remember to add it to your projects!!!) - this taught me more than the book. The very final part of section 3 goes over the classes in these prewritten functions (attempting to save grace)- but in the style of the latter half of the book is ultra condensed and basically mirrors the code - teaching you no more than the code itself does - there is no reasoning as to why the code is written in that way.
Something must have gone into my head however because within a week of reading I could make fairly complicated Forms/GDI+ applications - the book works for a good introduction.
In conclusion, dont buy it to learn the language (I recommend reading C# the Complete Reference - it is excellent), but buy it if you want to know something about GDI+ and Windows Forms - it teaches this well. Just skip sections 1 and 3 and read section 2 (which is brilliant by the way).
Deon Poncini
It is not.
A brief summery of the book would be: Intro to C# with some game examples. The problems is that the C# topics are spread, somewhat haphazardly, through out the book, and the examples are LONG. There really is no reason why complete programs need to be printed, especially after describing methods used in them. I'd say that of the 550 pages about 300 is simply code. Combined with the fact that formatting is not perfect makes the book a difficult read.
Another complaint is the horrible quality of the games provided. The look bad, and play even worse. The fact that all of them run without crashing maybe seen as an improvement over some other books. Typically the reader should be impressed or at least inspired with what you can do with the knowledge in the book, this is almost the opposite, I know that I won't show any of these demos simply because it could drive people away.
Finally there is almost no actual Game design. All games are one or two files with limited number of classes. The book tries to focus on object oriented design, however it is poorly done with little thought given to non-player objects, such as program structure. Program structure, or lack there of, is simply the Windows.Forms model with its event model driving the game. Unmodified this model is unsuitable for actual game creation.
Conclusion.
You might be able to learn C# from this book, however it will take you a while. You also might be able to make a game however you won't learn how real games are designed and made, also you won't find this book useful as a reference as once basic knowledge is acquired nearly anyone should be able to surpass this content.
I won't be using this as a textbook, probably stick with a tried and true classic like LaMothe's TWGPG which does a much better job in all categories.
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
|