vitamin wrote:
> Again, what do you want to accomplish?
Long story short I want to be able to contribute code at the lowest possible level doing the dirty work that nobody intellectual have any interest in. The rest of my goals is complicated - the end.
vitamin wrote:
>
> You don't have to do this one after the other. Most you can do in parallel. Or even backwards if you so desire. Just please don't ask people to teach you C. That's what the step #1 is for. And most people won't tell you exactly what each function does.
My brain is like a rusty 80's computer I need procedural { $instructions = goals } in order to accomplish something relevant. Giving me a procedural strategy is very important too me so please try and be as procedural with your advices as can be. I don't mean explain to me what certain C-functions does I mean goals you set before sitting down and start reading and coding.
============================================
A Newbie's strategy plan.
1.) K & R book.
Read "The C Programming Language" and do all the excercises.
2.) Read the Win API tutorial.
http://winprog.org/tutorial/start.html
3.) start with Simple projects.
http://wiki.winehq.org/JanitorialProjects
> If you need some simple projects to start with you can find one list of them here. Most don't require too much of API knowledge. Some don't even need programming experiance. Of course you do need to understand plain C.
Parallel reading
Skim through these links as often as possible preferably on a daily basis with no intention of learning at all just look for what parts can be useful to me at a certain instance.
http://msdn.microsoft.com # API reference
http://winehq.org/site/docs/winedev-guide/index
============================================
Sorry for my obvious extra questions but I'm really ultra-newbie I can't find the links that might already have answered my questions. I can't see the trees because of the forest of information and links on this website.
When I work with 3.) Simple projects do I need to prepare by subscribing to this mailing list
<wine-patches@xxxxxxxxxx> and read the entire wine-patches history in order to start coding properly? How do I know what's already coded or not?
/Questions from a procedural-headed Newbie.
