I may be a bad student, but let's talk abou that....
I have been reading the beginner's guide about canvas'. It's 15 pages long. It has needeles and a compass. It's one big long code of getting angles and rotation correct. How is that going to help me???????
OK, this is what SHOULD be the canvas tutorial.
1) this is how to put up a backgorund
end of lesson
2) this is how you put up a pac-man character on screen.
end of lesson
3) this is how you move pac-man around the screen.
end of lesson
4) this is how you put up a ghost
end of lesson
5) this is how pac-man dies when touches ghost
end of lesson
First off I think I know what your problem is. You want someone to write your programs for you. The reason why tutorials aren't written that way, for the most part, is because when you teach someone how to do something, you don't just say put a ghost here, put pacman there. You tell them why you put them there. If I gave you the code every time you needed it, you wouldn't learn. You learn by adapting what you know to your own code.
If I tell you a button is to click and do stuff, it helps you none. But if I explain to you that the button has the function of firing a click event in which you can add code to the click event and when the button is clicked your code is executed. You know know how to use a button.
You say that none of the tutorials help you, then I'm thinking the problem is with you. Because the tutorials on this site are made by several different people with many different writing styles and they cant all be wrong in how they are doing it.
The reason people say to read the forums is because, after a while of answering the same thing over and over again, it is just easier to redirect the people to the already established information. If there where donuts in your workplace and everyone kept coming to you asking where they were, first you would find out where they are because, "hey there's donuts". Then you would answer the questions of where they are to everyone else, but after a while of loosing productivity, you would put up a sign that said donuts with an arrow.
Normally when someone says read the forums, they don't just say "read the forums". When you ask "how do I get pacman to die when he touches a ghost?" They usually say "search the forums for collision detection". The reason for this is simple. In programming you have two kinds of people, one kind wants to learn how to do something, so they can implement that concept into their own work. They want to know the concept not the code. The second kind wants you to write their code for them so they can say hey look what I did. They don't care about learning the concept, they just want others to do it for them. In either case the answer "search the forums for collision detection" is the correct answer.
The person who wants to learn, knows the only way they will learn is by reading mass quantities of information and then trial and error on what they have learned. That's the way you learn. The person who wants you to program for them is just being lazy and you shouldn't give them anything. Make that lazy bastard work for it. In either case when someone asks how to do this, most times you don't know what kind of programmer they are, so the same answer works on both.
Just like a chef makes money by cooking for people that are to lazy to cook for themselves, I am a programmer. I sell my programs I make to people that are to lazy to learn how to do what I am doing and do it themselves. Why should I write code for someone for free, just cause they don't want to do a little reading. Especially when they are going to take credit for my work anyway as their own, and possibly make money off of it themselves.
Now don't get me wrong. You should always help people that have less knowledge than you. And if they truly cant figure something out, then by all means, write a bit of code for them. Because that person that spent three hours trying to figure out what was wrong, will see your code and say "now I see what you did."
But when you see someone post a thread saying "how do I kill pacman when he hits a ghost", and you reply with search collision detection and 5 minutes later he says "well I cant figure it out, cant you just tell me?" You know the answer to what kind of programmer they are.
The reason there are so many books out about vb6 and vb.net and java and everything else is because of the long time between new full releases of the software. And as soon as a new release comes out that book is outdated. Sometimes the old book is still useful, but sometimes they need rewritten. Think about using a vb6 book to program vb.net. Although somewhat useful it would do more harm than good. you would have to learn vb6, then learn whats different in vb.net. Way counterproductive.
And lastly the main reason no one wants to write a book is because books take time to write. Months and sometimes years. Then you have to get it to a publisher who has to have it proofread, analyzed and approved which can take months to years sometimes.
If I was to start a book right now on the subject of basic4android. First I would have to learn every aspect of it so I could explain it. How can i teach what I don't know? I have been using it for almost a year now and still haven't learned everything. So baring learning everything, I would need to collaborate with someone who did know. So now Erel and I sit down and start writing. To get a very concise easy to read book it would take a few months, we'll say 4. Finally we get it done. I take it to my agent, who shops it around. He finds that Simon Suester says they will publish it. (More realistically we would have to self publish cause basic4android is so unknown of a language, but we are looking at best case scenario here.) So Simon says they will publish. They take the script, and they have their editor read it. It has a few things that need redone, so its sent back to us for a rewrite. This all took a month. Now we have it back to them, and they get it to their proof readers, they proofread it that takes a week, then another week to set it up for print. Then they print off 50000 copies. (50000 is a small print for a big publisher) By the time they are done another month has passed but now we have the book in our hands. We can finally start selling it. At this point 6 months has passed and many of the references to how to do things are outdated because a new release has come out of b4a and the old way is no longer implemented.
And yes this is a very realistic timeline. Well actually it is very unrealistic because it never goes this smooth. Trust me. This is a best case scenario. More realistic would be closer to a year! There have been times that the publisher has asked for two or three rewrites. And none of this even is considering the money aspect of it. For them six months you worked on the book, what did you do for money? And since you aren't going to be able to get in the door at a publisher without and agent, even if you do write a good book you will only be making a small percentage of the profits, and that's if the book sells at all. We just printed off a book with a 50000 print run on a software that only has 25000 users. I don't know about you but I wouldn't even be buying the book, let alone two. Now you may get that oddball buyer like a library that orders ten copies, or a school ordering 20 but unless you truly believe you need two copies just in case you want to read it twice, you would only buy one. Even if we got 10 percent (which would be a miracle, more realistic would be closer to 2-3 percent) of the b4a community to buy the book we would only sell 2500 copies. All of which the publisher would have figured out when researching which is why I said you would have to self publish.
Now to self publish a book your looking at about $1000 for a professional editor, another $2000 per 10000 copies (its usually between $.20 and a dollar per book) then about $1000 per month for a professional publicist to help promote the book and most of them ask for a minimum of two month contract.
So if you are still interested, you can pay me to write your book, as I am a professional writer, and I will only charge you $2000 to do the book with a 1% back end on the royalties. You will have to talk to Erel on how much he will charge you to collaborate with me but that is between you two. I'm guessing another thousand or two. I can have you a manuscript in about 6 to 8 months (I know I said 4 earlier, but honestly that wouldn't be enough time for me to get one done correctly. Hell, it has taken almost an hour just to write this after a few spell checks and rewrites!) Then you can do with it what you want, and if you would like I can even get you in touch with my agent so he can help you get it published. But be prepared to self publish. Cause no one is going to pick up the rights to a book that might sell 2500 copies.
So for $9000 bucks you get your wish. Which isn't bad considering you would have a book that would be written exactly how you want, to help you learn exactly the way you want to learn. So when can I be expecting that check???