Re: help
Mantia Andras <[email protected]> Mon, 29 Sep 2008 07:31:22 +0300
| Newsgroups | gmane.comp.kde.devel.quanta |
|---|---|
| Message-ID | <[email protected]> |
Hi, On Friday 26 September 2008, Alwin Augustin wrote: > hi, > > I am just joined and could you tell me the detail of the development > ??? Welcome here. I'm not sure if you followed the discussion on the user list (quanta@, not quanta-devel@), the current state of development is unfortunately on hold from my side. We can also say that there is no active development at this point. Neverthless, I hope this won't stop you to work on Quanta in the future. I can tell from my pats experience that it was fun also when I started to work on Quanta as a single developer. In that case it was somewhat worse, because the old developers wanted the project to die, so I got no help aside of Eric telling me what to fix and implement. :) In any case, even with a somewhat delay, I'm here to answer and help. After this introduction, i can give some details. The code is in the KDE svn, trunk "branch". The techbase.kde.org site contains lot of documentation how to check out it and compile. What you need (in case you run KDE 4.1.x) is are the kdevplatform and kdewebdev modules. At the moment I'm not sure if kdevplatform required kdelibs trunk or not, but ceratinly it is better to work on trunk kdelibs. kdepimlibs is also a dependency, because of the addressbook lookup inside Quanta. If you are still on KDE 3.5.x, then of course you need to build the kdelibs dependencies as well. See techbase about it. There is no need to run KDE 4.1.x or KDE4 trunk if you don't want to, you can develop just fine KDE 4 applications from under KDE3. I still use KDevelop3 for KDE4 development, but now from under a KDE4 session. :) Under kdewebdev/quanta you will find the DESIGN and HACKING documents, please read them. The README is outdated, refers to KDE3 days... Shortly, the idea is to build KDevplatform plugins that can be used in Quanta and KDevelop. Similarly Quanta can use plugins from the kdevplatform module, like the CVS/Subversion plugin, search and replace, and even project manager. For Quanta specific functionality we either build plugins that require "quantacore" to be loaded, or put the code directly to quantacore. In the future it might make sense to make this quantacore a language support plugin. I'm sure you don't know what I talk about, so here it makes sense to subscribe to the kdevelop developer mailing list as well or ask question on the #kdevelop IRC channel on irc.kde.org. The kdewebdev/plugins dir contains some plugins that are disabled (check the CMakeLists.txt). This is either because they are not ported completely or outdated because we can use something from kdevplatform itself. > and in what areas i have to have kowledge? Of course C++ and Qt is something that is needed. Subversion (or any other version control system) knowledge is also needed, but that one is easy to learn, especially if you used something like that in the past. Aside, you will need to familiarize yourself with the KDE and KDevPlatform libraries. For these we are here to help. Don't hesistate to ask if you are stuck at some point. Andras