kdevelop1.4 - The state of the play

[John Birch]

Hi,

After browsing the forum it looks like a bit of info on this topic might be 
useful.

Q. kdevelop1.4 - do I need it?
 - if you have 1.3 working and are happy - that's fine.
 - if you are running kde2.x and have kde1 _only_ for kdevelop then update 
and remove kde1 (Well perhaps wait until release to delete :-)
 - If you are creating only kde2 apps (on a kde2 system) - update.
 - Running kde1 - you're fixed at kdevelop1.3 :( Move to kde2.1 ASAP after 
the release.

Q. Are there precompiled versions?
 - No - This is in beta and changing - precompiled versions are useless.
And really - are you not programmers? The source contains lots of valuable 
ideas and examples - read it and learn things to do and not to do.

Q. I've got kde2.1 with the beta - It doesn't work that well
 - yes - The cut for the beta was at least 2 weeks too early for me - sorry
 - Delete it right now and get the latest kdevelop1.4

Q. I've got kde2.0.1 - what now?
 - Update to kde2.1 :-) Okay, you may not want to do this (big mistake :-) 
so...
 - get the latest kdevelop1.4 and compile it. There is a compile problem 
(which I will look into) but just remove that line and it'll be fine (This 
may change - there is no guarentees here - kdevelop1.4 is for kde2.1 but, I 
hope, the problems are small and easily solvable)

Q. How do I get the latest version
- Use the anoncvs server (see http://www.kde.org for details)
   After the login use
     cvs -z4 co -rKDEVELOP_1_4 kdevelop
   every few days (or more often, if you want) update to the latest
     cvs -z4 up -rKDEVELOP_1_4 -dAP
 - tarballs are suboptimal as you will want to update the sources but there 
is the kde2.1 beta version. It is a bit buggy and missing lots of things and 
is _not_ the lastest.
 - I do not know if there are daily snapshot tarballs - look on kde websight 
for more info here.

Q. I've found a bug - what do I do?
 - Get the latest version of kdevelop and try that first.
 - Try and repeat it - see if it changes with different options
 - Give me some info about your system/distro (especially if you use RH7)
 - _Tell_ me what you were doing when the problem occurred. Be descriptive.
 - Supplying a backtrace of  a crash is a Good Thing(tm), but only if you 
compiled kdevelop with debug info.
 - Best is to run kdevelop under kdevelop and debug and fix it. Then supply a 
patch. (The project file in cvs is called kdevelop.kdevprj.save. Rename this 
to kdevelop.kdevprj)
 - Be prepared for me to contact you so that I can get you to test the fix.
 - Do not sit on it - investigate it and publicise it ASAP by supplying a bug 
report to the kde bug list - use the kdevelop1.4 bug report dialog to do this 
(I hope it works as it's changed since 1.3 :-)
 - Contact me directly, if problems with bug reporting system.

I simply cannot fix problems I don't know about. As with any project the 
better quality bug reports you supply the faster the fix will be.

Q. I've found a bug - and fixed it - now what?
 - Ha - excellent work :-)
 - tell me what the problem is and the solution - _in_ _words_ - It's a good 
practice to talk about the problem - the solution you have may only sort of 
work or cause non obvious problems that might be avoided because we've been 
in the code previous and know some of the issues.
 - generate a patch and send it to me
    To generate a patch
     . If you were using the anoncvs server then just do
         cvs diff -u filename
     . If you have the beta (or later tarball? if available) - You've really 
gone the hard way haven't you :-) Make sure you have a copy of the old 
file(s) and do
         diff -u oldfile newfile
       For many files its
         diff -Naur olddir newdir - but only on clean directories.

Q. kdevelop1.4 is sort of similar to kdevelop1.3 but it's looks different.
 - yes - it looks good, don't you think - enjoy it.

Q. What about kdevelop2.0?
 - It's coming along nicely - but it will take a while. Get kdevelop2.0 if 
you want to help develop kdevelop2.0.

Q. Why do kdevelop1.4 instead of getting kdevelop2.0 out now.
 - kdevelop1.4 was possible in the 2.1 timeframe.
 - kdevelop2.0 will take some time. If you want kdevelop2.0 soon then jump in 
and help develop it. Use kdevelop1.4 as the IDE to do this :-)

jbb

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«