Before contacting me make sure to read the Frequently Asked Questions.
You shouldn't waste your time typing up an e-mail and waiting for a reply if the answer is there waiting for you.
If you have questions about SDL but they don't have to do directly with the tutorials, I recommend asking on GameDev.There are many SDL programmers on there that can help better than I can alone. I frequent these boards so you'll be getting my help along with the help of others.
I am currently studying OpenGL and I am no expert. For OpenGL questions I recommend asking on either GameDev or OpenGL.org. There are plenty of experts with years of experience that can help you better than I can. I also frequent these boards. You can ask questions about the OpenGL tutorial (tutorial 36) or the OpenGL article (article 10). Anything outside the scope of the articles I recommend asking someone more experienced.
Also don't forget that google is your friend.
The search box can also search the site's 50+ pages for answers. I just put it in so it's going to take a while for it to spider the new stuff on the site.
It's important to know how to use google when learning how to program. Say if you wanted to find out how to rotate images in SDL. I don't cover that on my site (because SDL doesn't support it natively) so e-mailing me about it isn't a good idea. If you put "Rotating in SDL" in the search box you get tons of answers. The same thing works if you put "playing video in SDL", "stretching SDL surfaces", "OpenGL TTF libraries", or what ever else you can think of. It's better to get an answer after a quick search than waiting for an e-mail reply.
If you have anything about the site you want to ask about, you can e-mail me. I'm a college student that's trying to balance a site along with a job so it can take me a day or two reply.
When asking for help make sure to include all needed information. This means things like your OS, compiler/IDE, and all relevant code. Also clearly state what's the problem. Make sure to type clearly, too.
Also when asking for help on a tutorial refer to the tutorial by title not by it's number. I've rearranged the tutorial order a few times and I don't know the tutorials by number off the top of the head.
Don't be shy with bug/typo reports or asking for tutorial clarifications. I want my tutorials to be the best they can be.
There's just a few things you should remember before e-mailing me:
My e-mail is lazyfoo < at > gmail.com. I have to type it like that to prevent spam. I'll be happy to hear from you.
PS: please no volunteering services or game design suggestions for any game projects I'm working on. It's a solo project and I don't want to be accused of stealing ideas. Plus you never know, I could get rich off your idea. =)
If you have questions about SDL but they don't have to do directly with the tutorials, I recommend asking on GameDev.There are many SDL programmers on there that can help better than I can alone. I frequent these boards so you'll be getting my help along with the help of others.
I am currently studying OpenGL and I am no expert. For OpenGL questions I recommend asking on either GameDev or OpenGL.org. There are plenty of experts with years of experience that can help you better than I can. I also frequent these boards. You can ask questions about the OpenGL tutorial (tutorial 36) or the OpenGL article (article 10). Anything outside the scope of the articles I recommend asking someone more experienced.
Also don't forget that google is your friend.
The search box can also search the site's 50+ pages for answers. I just put it in so it's going to take a while for it to spider the new stuff on the site.
It's important to know how to use google when learning how to program. Say if you wanted to find out how to rotate images in SDL. I don't cover that on my site (because SDL doesn't support it natively) so e-mailing me about it isn't a good idea. If you put "Rotating in SDL" in the search box you get tons of answers. The same thing works if you put "playing video in SDL", "stretching SDL surfaces", "OpenGL TTF libraries", or what ever else you can think of. It's better to get an answer after a quick search than waiting for an e-mail reply.
If you have anything about the site you want to ask about, you can e-mail me. I'm a college student that's trying to balance a site along with a job so it can take me a day or two reply.
When asking for help make sure to include all needed information. This means things like your OS, compiler/IDE, and all relevant code. Also clearly state what's the problem. Make sure to type clearly, too.
Also when asking for help on a tutorial refer to the tutorial by title not by it's number. I've rearranged the tutorial order a few times and I don't know the tutorials by number off the top of the head.
Don't be shy with bug/typo reports or asking for tutorial clarifications. I want my tutorials to be the best they can be.
There's just a few things you should remember before e-mailing me:
- Don't just skim over over the tutorials or, worse yet, just download the source code. You can only learn from the tutorials if you actually read them.
- Don't skip tutorials. Most of the time a lesson assumes you've read the lessons before it. Again, you can only learn from the tutorials if you actually read them.
- Don't copy and paste pieces my code into a frankenstien program. If all you're doing is copying and pasting you're not really learning.
- Be as specific as possible when asking questions. "It isn't working" is not a good description of the problem. A good description is at least 2 - 3 sentences long and gives examples of what happens under different circumstances.
- If you're having problems with a piece of code I'll be happy to help you debug it. However, don't dump all your code on me and expect me to fix it. You can't expect other people to debug your code for you.
My e-mail is lazyfoo < at > gmail.com. I have to type it like that to prevent spam. I'll be happy to hear from you.
PS: please no volunteering services or game design suggestions for any game projects I'm working on. It's a solo project and I don't want to be accused of stealing ideas. Plus you never know, I could get rich off your idea. =)