KDevelop/ViennaSprint2012

Things to be discussed:

KDevelop as an SDK: Frameworks/Epics/KDevelop_based_SDK
KDevelop on Windows, anybody knows what's going on?
Static Analysis and KDevelop, what can we do?
Reusable libs/tools for C++ preprocessing, parsing, semantic analysis
- even preprocessing lib can't be reused because it uses IndexedString which requires item repository
- clang is the future
Operations
- Mailing lists moving to KDE? What will we have to change, if anything?
- kdevelop.org domain transfer to KDE e.V.?
- extract quanta repositories to playground: css, sql, xml, crossfire, phpformatter
- first alpha releases: qmake, css(?), ruby, python, ...?
review, fixup, test, merge
- Miha's branches
  - Can we merge yet?
  - Can we better integrate the unit tests?
- kdev-valgrind
- perforce
- mercurial
- control flow graph
General stuff
- More default colour schemes for kate/kdevelop editor component?
- New splash screen! :)
- add a C++/KDE application template which uses a QtDesigner .ui file?
- Different default settings for kate:
  - Who uses 8-width tab indent?
  - Who does not want backspace at the beginning of a line to unindent? etc.
Bugs to discuss
- fix debugger tooltips (they behave in an annoying way if the mouseover target is changed quickly)
- Crash bugs on pressing enter? What's the status here? Those are *really* bad.
- Crash bugs on switching areas / closing all files
Things to improve
- Better launch config dialog! It's unusable currently.
- minor: only suggest include completion entries for 1 or 2-char names if requested explicitly? I often accidentially include stuff which defines a struct called "c" or so.
- Search in Files: The "new search" icon / button is not obvious. It looks like a settings button. Maybe give it a text, or a different icon?
- make quickopen delay configurable? it still annoys me significantly.
- a visually more attractive "pick session" dialog
- multi core performance
- general memory and single core performance
Technical
- Formatting of autocompletion list entries: incredibly difficult, can we get something less complicated like HTML/CSS text formatting?
- kate autocompletion API: can we get a way to mark items as "unimportant", sorting them at the very end of the list regardless of alphabetic sorting? Otherwise it's very difficult to offer 20 different entries starting with __ without being annoying.
- kate autocompletion: do not complete when only single option is presented
- discuss how to properly implement class/function aliases for scripting languages in the duchain
- different/other backends for duchain