I've been using linux for about 5 years now and have always been interested in learning to program and have now decided I'd like to help develop KDE. My question is which would be the best language to learn first that would help me start developing/bug fixing on kde?
Also links to good websites, tutorials and ebooks would be great.
Thanks

Have a look at http://techbase.kde.org/Contribute first, there you find links to some resources for learning a language.
If you then want to learn hacking on KDE directly you will find a bunch of tutorials here:
http://techbase.kde.org/Development/Tutorials

But generally, techbase really gives a great overview.

Thanks, looks like I'll start learning C++ then as it says KDE is mostly written in it.

Better start learning a scripting language like Ruby or Python and use Korundum or PyKDE for KDE programming

Thanks, had a look around on a few sites and most recommend learning python as a first language and it does look easier than C++ so I'm going to start learning python and then C++ after that

super.rad the problem with python and ruby is that your programs are generally slower and most memory-consuming (because of the python-virutal machine and the ruby virtual machine) than with c++ that's compiled to machine-specific-code.
I'v learned c++ in 2 weeks ( but I had a little programming experience before ).
It could be userful a forum for general kde programming here, right?

Tomaz wrote:It could be userful a forum for general kde programming here, right?

just a silly idea: here are many KDE developers: what about a weekly tutorial lesson: a simple task from KDE's todo lists for us wannabe beginners under the helpful eyes of skilled programmers?

Tomaz wrote:super.rad the problem with python and ruby is that your programs are generally slower and most memory-consuming

And? super.rad wants to learn to program, not to write software capable of painting "Hello world" millions of times per second.

Even a professional programmer finds scripting as a viable solution to many problems.
[quote='michael4910']just a silly idea: here are many KDE developers: what about a weekly tutorial lesson: a simple task from KDE's todo lists for us wannabe beginners under the helpful eyes of skilled programmers? Wink[/quote]
Check http://techbase.kde.org/ and then we can talk

michael4910 wrote:

Tomaz wrote:It could be userful a forum for general kde programming here, right?

just a silly idea: here are many KDE developers: what about a weekly tutorial lesson: a simple task from KDE's todo lists for us wannabe beginners under the helpful eyes of skilled programmers?

I think it is a good idea. The tutorial can be discussed and the feedback can be used to improve the tutorial text. Afterwards, it can be moved to techbase.kde.org

Cheers, m.

I've got nothing to object regarding scripting languages in general, but I always advise people to learn C++ first. In my opinion, it's easier to switch from C++ to Python than the other way around. E.g., if you're experienced in programing in a strongly typed language, you have no problem to use a typeless scripting language, but if you learned only the typeless language, it's quite hard to grasp the concept of types and casts in C++. It's like learning an automatic or manual gear first. I would always advise to learn the manual gear...
Also, learning in a stricter environment will discipline you regarding some common pitfalls. Just have a look at one of the countless PHP applications out there, a lot of them are horrible to look at for a programmer.

Since I will be giving a talk about Qt/KDE4 here on latinoware, I will publish the slides afterwith.
the only problem is that they are in brazilian portuguese

michael4910 wrote:just a silly idea: here are many KDE developers: what about a weekly tutorial lesson: a simple task from KDE's todo lists for us wannabe beginners under the helpful eyes of skilled programmers?

Hey, I think that's a wonderful idea. How about creating groups of maybe 4 newbies and one mentor? Each week the group is assigned to fix a simple bug. The group can discuss how to solve the problem here in the forums and on IRC. The mentor is there to answer simple questions and point out flaws in the code.

These kind of groups would be a great way to start KDE development.

EDIT: The number 4 is just a suggestion. I think maybe 3-5 people would be optimal.

This is a great idea. But perhaps it also works well with one "newbie" and one mentor. There should also start a videocast soon by aseigo:

http://aseigo.blogspot.com/2008/10/kde-videocast-but-when.html

Cheers, m.

The idea of a group with newbies is that you can discuss various approaches and solutions with each other. The mentor's role wouldn't be as vital, and s/he doesn't have to spend that much time to do this. I'm sure most developers are quite busy as it already is.

I find this idea great. And it doesn't need to stop at developers, what about artists, translators, documenters etc?

Anyway, someone willing to step up as a mentor?