Le Wed, 23 Nov 2011 09:13:32 -0800 (PST), Darrell Anderson <humanreadable@...> a �crit : > > Nobody said we wouldn't help. I'd have > > already been submitting patches if I knew how to code. > > I never got the impression anybody was implying we all dump on > Tim. :) I think all statements on this list suggesting improvements, > possible road maps, etc., all imply team involvement. > > From what I see on the list and watching the bug list, many people > are indeed helping. Not all patches are C++ hacks, but when people > can they have been submitting patches to config files, desktop files, > graphics, etc. Many who don't code are involved with testing. Based > on the discussions we have had about quality assurance, we need those > people too. :) > > > Then now is the time to learn :) > > We need developers and the more the better. > > I would like to learn. I have a sufficient programming background > that I should be able to learn C++. I would love to help in a small > way. I need a decent tutorial, one that is specific to this project, > how to bootstrap myself. Yes, I need to read a few generic C++ > tutorials, but how do I use KDevelop? How do I create a working > environment? Would be nice to sit with somebody for a few hours to > learn in a rapid manner. People who do this every day tend to forget > that even the basic tasks like setting up an IDE is daunting without > help. Sure, an experienced coder can work with only a text editor, > but not the newbie. An IDE helps validate code, syntax, etc. > > IDEs, classes, namespaces.... Where to begin? :) I would answer: with standard C++. You won't have to know every detail of C++ (actually I don't think many people do, except Bjarne Stroustrup). Especially STL won't be useful for you since Qt3/Qt4/TQt has its own standard templates (QList, QString, etc. while STL containers are std::list, std::string, etc.). I don't know much about Qt3/KDE3 API but the few times I used the Qt3 documentation (directly from the Nokia website) I found it really good. About IDE's, you don't really need a full-blown IDE like Code::Blocks or KDevelop to validate syntax; Kate, vim and Emacs also have syntax colouring and bracket matching. Anyway the only real check against bad code is compiling and testing ;). For class/function searching, I actually use find/grep but Emacs and vim support ctags which makes jumping through functions much quicker. If you think KDevelop is better for you, feel free to use it but I'm not sure at all whether KDE3 KDevelop supports cmake-based source code. KDE4 KDevelop does. With KDE4 KDevelop I'm able to open the kdebase 3.5.13 CMakeLists.txt, and it loads automatically the full source code. However, I didn't find how to change the include path, so TQt calls are either not found or attributed to Qt4. > > Darrell > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > trinity-devel-unsubscribe@... For additional > commands, e-mail: trinity-devel-help@... Read > list messsages on the Web archive: > http://trinity-devel.pearsoncomputing.net/ Please remember not to > top-post: > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting >