KDevelop-3.1 feature plan

[Jens Dagerbo]

[remailing this again.. seems to never have reached the ml earlier.]

Hi! 

IIRC, we technically have until June 1st to get any major feature additions
into the KDE-3.3 Feature Plan
(http://developer.kde.org/development-versions/kde-3.3-features.html).

Maybe it's high time to decide what we want to finish for KDevelop-3.1? :)
I can update the feature document if only people respond with what they are
working on.


This is what I personally want to finish for 3.1 (unless someone else does
it.. ;) )

Minor stuff:
#Make the cpp context menu optional (I hate it!)
#Make the classbrowser combos optional (I never use it and it takes up space)
#Port splash to KSplashScreen (contact Ramón about an updated graphic)

Stuff:
#Clean up KDevPlugin - move 5 methods to KDevVersionControl that makes no
sense in the generic interface. Only the versionControl() method feels like
it should be there.
#Create a settings dialog for the CTAGS2 plugin. Fix any remaining UI
usability issues
#Create a toolbar that can display the info we currently put in the statusbar.
This way we can hide the space-sucking statusbar and at least pretend to have
an UI mode (IDEAl) that adheres to "Fitt's Law".)

Major stuff:
#Better external file modification detection and resulting action. (at least
optional automatic reload)
#A new simple classbrowser-type plugin that can handle two things: 1. in-file
navigation between methods, and 2. display in what method the cursor is
#Implement plugin profiles and have it interact with project setup (this
requires minor changes to the appwizard)


Regards,

jd