Well, no, not for the purpose he is claiming he is writing it for. It would focus on Allegro (just an API) and make example games with it. You would have to make it a language specific game programming book that teaches game programming while teaching a language and using Allegro API (and that would make for a huge 1000+ page book.

Sorry to say, but the your grammar actually sucks... The first paragraph in that chapter is enough to make me feel sorry for anyone who would buy it. And honestly I don't think anyone will if they get the chance to look in the book before buying it.

Maybe you should write the book in your native language (someone wrote a German book for Allegro 4 for example). Then have it translated once it's done. On the other hand, writing a book might be a good way to improve your English, so if you see it as an exercise for yourself, go for it anyway.

Is a good example in itself as it uses a wrong word order, it should be: "Post a single grammar problem in here."

There are a lot of grammar errors, but it's easy to understand. I wouldn't really worry about it. (Of course if you plan on selling it, then you will need to find a good editor.)

Even if the book is nothing more than a collection of tutorials like that chapter, it might still help people out, so I wouldn't listen to any of the useless criticism. Just be sure the stuff is factually correct.

The more i write, the more it gets complex. I have writen 68 pages in total. I wrote about math real numbers. I explain negative and positive numbers and what is an XY graph in math. The differences with Allegro. I dont want to let it just an example book. I want to add in great math and physic. I am very good at math and physic so it will be a very good bet from my side. I have one big question though:
I am writing the chapter of geometrical objects. When i write the chapter of advanced geometrical objects, i want to add a 3D object, for example a simple cube, pyramid or the max it could get a sphere. Is there a function to make it, or a way?
I even want to know if you can create an experiment using allegro for the Einstein theory, so objects will deform when a speed variable gets to a point with an if statement. I mean, can you deform objects, if you want to?

@weapon
Thank you very much! I was really afraid none was going to understand it!
I will add other things in the first chapter, after i finish.

You're using the wrong terminology. main is not a class. It is a function or subroutine. The editor is going to have a lot of work on his hands. He had better be a native English speaker...

Your al_show_native_message_box call seems wrong as well. You are passing the flags parameter as a string, but it is supposed to be an int. Also, the way you've described the arguments is strange. The reader will likely memorize the parameters by position all on their own. When describing them, you should associate the description with the semantic name to keep things easy.

It's ridiculous to say that the reader is adept at creating boxes. They aren't creating dialog boxes. Allegro is. They are just asking Allegro to make them. And it's only one function call. It's hard to be good or bad at that. You either do it or you don't.

I would suggest that you focus on the facts and avoid subjective content.

I fall under this comment, I think. If the book is just to teach Allegro 5 to programmers then that is fine. I just don't agree with the saying the wiki and manual are bad or saying they have grammar errors just because they don't make sense to him. A book of tutorials for doing things in A5 would be nice.

Now, let me re-iterate a previous comment. You cannot get a person into programming with just teaching them A5. You book would have to be written so that the first few chapters would cover a language you are using (C, C++, C#, D, etc.) and the basics of that language. Following chapters could cover setup, installation, and first test example to show A5 is properly installed and working. Then after that you would have to have examples that show A5 and the language features with it ultimately finishing in either multiple games or one complete game at the end of the book.

Late to the party, but I just got a sig quote!

EDIT:

I see now what you were talking about on #allegro. I need to stop by more often; I miss all the juicy bits.

AleX, I highly recommend you review pure C and C++. Before you do too much more with your book, you should check out http://www.cprogramming.com/tutorial/c++-tutorial.html and http://www.cprogramming.com/tutorial/c-tutorial.html . I think you would benefit from at least a quick review. If nothing else, it might help you better understand the terminology in English. You seem to be off to a decent start, but spending a day or two refreshing your c/c++ understanding may make your endeavor easier.

Also, I read through the pdf you uploaded. I think it could be useful to somebody, but you will need to editing and revising. However, since its a first draft don't worry about that yet. That said, you should be aware that when you are ready to finalize it in whatever your preferred format is, and after editing and correcting the font size, the book will most likely be about 1/4 its size as a draft. I say this because upon editing your work, the document becomes around 1 page + code.

Finally, you may be interested in using LATEX for layout. It will help make the images more standardized and there is a plug-in which will give your source code context highlighting.

Reading the draft you have attached reminds me of this wiki, which I wrote 2-3 years ago for my classmates (which is an epic fail because I suck at explaining, the tutorials are badly structured, and most of my classmates are not interested in game programming AT ALL). IMO, you should just turn your book into a wiki (or a website) for several reasons:

• It mostly deals with practical stuff like how to initialize Allegro, popup a dialog box, etc. Things like these are more suitable to live on a website. I mean, ask yourself. If you don't how to use a specific function, or perform a specific action, would your rather google it, or flip through some random 69-pages book?

• It is littered with code examples. Most programmers (or maybe just me) are lazy, and they don't like having to retype these code just to test them out. They'll just copy paste it. And you can't copy-paste it if it's in a book. And copying from a PDF is still annoying (not to mention it screws up the formatting). Oh, and what if you have a long code example? I don't think PDF supports scroll-able DIVs, so you're stuck with a block of code that spans over a single page, making it even harder to copy.

• It makes it more accessible on mobile devices. I guess.

• It's easier to update. If it's on a PDF, the readers have to re-download it.

Thank you very much!
Actually, i work until 4 AM to make the book. I started in an attempt to create a book where people who want to make games, can start making their dreams come true. It is not exactly for programmers. I am basing the book on 13 years old to advanced game programmers so they can both benefit and understand each other if they talk about the book. I have to include 1 or 2 chapters for C++, but i really need to learn C++ myself! I don't know which is the right one to go C or C++ to benefit the most from allegro 5. Since i am very keen on C++ i will try it. Unfortunately, i start test at college on September so it will take longer than expected. One thing to be noted is that when i started the book, i intended to make it to 100 pages at max with 10 chapters, but at the time of writing i am on page 105 explaining events which are on chapter 8. But i have added a lot more than expected so it is going to be around 15 chapters. I want to finish the book with 250 pages to include everything possible even C++ for total beginners. People can read the book and at the end they can combine the codes the way they want to create whatever game they want.
I was really considering the idea of the website and i think i will try it.
I will review the book when i finish it.
The questions for me, are the same on this forum. I will go and read C++ tomorrow and will write the book when i will feel more prepared.

C++ is an extremely complicated language. C++ is the kind of language where the more you know the less you know. And you can do everything in C that you would in C++, if a little bit more verbosely. You should focus on C and leave C++ to specialized books and resources.

Well if you get a portion written, I'll edit and index it. Maybe I'll contribute, in the unlikely event I have something intelligent to say.