--nextPart13241848.L4nzgcHRLF Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 26 January 2006 01:40, Alexander Dymo wrote: > But I have my own experience that tells me that KDevelop is usually > not a best tool for my development tasks. It's a cool IDE, but not > for me. Wtf? I participated in its development, I implemented many > things and now I don't use it much. This question bothers me every > day and I'm going to get an answer from myself at the first place. Ok, I think we need a supporting mail as well. I use KDevelop almost=20 exclusively to develop anything for KDE, ever since KDevelop 2 which=20 was way inferior to the current one. I only use Kate or mcedit (hi=20 Ossi) when I have to quickly patch something which I usually do not=20 work on. For your own application I find KDevelop to be quite good,=20 altough it has several problems: =2D it is hard to set up when your application is together with other=20 applications in a module =2D the automake manager has quite some problems =2D the UI is somewhat cluttered =2D the debugger wants to do some things on his own =2D in the standard mode there is no split view (and no, the mode which=20 has is not that good for me) =2D compilation inside is slower due to the compiler output filtering =2D from time to time it has problems with the code completion (mainly=20 because of BDB) =2D it is hard to use/set up for library developing=20 =2D feels unfinished in lot of places But these are things that can be and should be improved and they are not=20 something that is very hard to solve, at least part of them. And it has=20 quite some strengths and pros compared to other editors: =2D it can be learned easily (yes, this comes from Kate), compared to vim=20 or emacs.=20 =2D syntax highlighting is good (again, thanks to Kate) =2D it can be used both with the mouse (after all its a GUI application),=20 and for the basic tasks with the keyboard as well. Keyboard handling=20 needs to be improved though =2D the integrated debugger is very handy =2D the code completion and the integrated help system helps a lot =2D for me it saves a lot of time that I could do everything from inside=20 one application I find an invaluable tool and I'm sure it is for many others, especially=20 those who were not Unix/Linux hackers before switching to KDE. And I=20 think here is the problem and the small adoption of KDevelop (and for=20 that matter Kate) inside the "core" KDE developers: they are many times=20 long time Linux users before the modern Linux desktops appeared and=20 they are so accustomed with their command line (or similar, but with=20 the same idea behind) tools, that it is hard for them to switch to a=20 completely new style. This is understandable, but there is always a=20 but: why do we create a GUI desktop and applications than? So give it a=20 try and use from time to time our own applications, maybe you will find=20 the good in them and will help to improve them. Your ideas and=20 experience from other fields could help a lot existing KDE=20 applications, and as you are almost all developers, in this case it=20 could help KDevelop and Kate as an editor. Andras =2D-=20 Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org --nextPart13241848.L4nzgcHRLF Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD2Jx1TQdfac6L/08RArToAJ9SZBWawuTWmPn+IohUzyzvxXdu/gCfToEs 1IogX9UZvVSfIai+DxOd3eQ= =eUYL -----END PGP SIGNATURE----- --nextPart13241848.L4nzgcHRLF--