Make it possible to open inputs generated in the build directory

It's not very useful because one shouldn't use the project view to debug
generated files, but considering that it wasn't working anyway I thought
it made sense to make it work.

BUG: 295521
Force the plasma's appdashboard theme in KDevelop's dashboard
Only link to plasma if needed
SVN_SILENT made messages (.desktop file)
set version to 4.3.80, i.e. 4.4 beta 1
Don't use raw Declaration pointers across unlocked DUChain code paths.

Since the declarations might be randomly deleted by the cleanup thread
or something else, it is potentially dangerous to use raw declaration
pointers after the duchain was unlocked and locked again.

Instead, always use either the DeclarationPointer or an IndexedDeclaration.

Furthermore, it is often not a good idea to search for declarations
holding a read lock, then unlocking it, just to acquire a write lock
and finally do something useful with the found declarations. This
would only be a safe operation if we use e.g. DeclarationPointers.

Finally I severly doubt that the code snippets changed here have
a worse performance now. Granted, now there is no chance that another
thread can operate on the DUChain while we search for the declarations,
yet we also have less context switching and don't need the DeclarationPointer
indirection and thus might be done faster...

BUG: 302744
Instead of forcing a theme, force a text color to the QPalette

For some reason, PlasmaComponents' Label follows the color scheme
from QPalette only for text, but not for the components of course.
Fix memory leaks of Ui objects.
Don't tell the user the make config has changed when he first sees it.

The reason it that we didn't set a default value, hence the default
which is probably 0 was taken. Yet our spin box has a minimum value
of 1. Thus, the KConfigDialogManager saw a property difference in
it's updateWidgets method, which is called from KCModule::load. Due
to that, it triggered a delayed call to changed(true).

Now we set a proper default of 2, which should be suitable for most
machines. This fixes the issue - yay!
Don't call load() in our ctor, that is done automatically.
Directly set the model's data when we toggle a checkbox.

By default the editor is only closed when it loses focus.
This actually means the 'apply' button *does* get enabled
properly, but the user first has to click somewhere in order
to loose the editor's focus.

Now, we just close the editor whenever a checkbox gets toggled
which should make the behavior much less confusing.

BUG: 304352
remove dead code
SVN_SILENT made messages (.desktop file)
Let the OutputView take ownership of the make output delegate.

This is basically the fix for the two bugs below that does not
require any ABI break and can thus be done in the 1.4 branch.

CCBUG: 207669
CCBUG: 204399
Be less strict about named and unnamed arguments.

Recent GDB versions can report multiple breakpoints
but do so using an invalid MI format, see e.g. the
upstream bug report:
http://sourceware.org/bugzilla/show_bug.cgi?id=9659

Since we cannot expect GDB to be fixed anytime soon,
just make our parser less strict. This was actually
the recommendation in #gdb on freenode IRC as well...

BUG: 304730
Explicitly disable "Apply" button after re-reading CMake cache.

Otherwise, we had "Apply" button automatically reenabled after
user press "Apply" and the project is reconfigured.
Properly initialize CMAKE_INCLUDE_CURRENT_DIR

Conflicts:
	projectmanagers/cmake/tests/cmakeloadprojecttest.cpp
Properly add the build directory

when requested because CMAKE_INCLUDE_CURRENT_DIR is ON.

Conflicts:
	projectmanagers/cmake/cmakemanager.cpp
SVN_SILENT made messages (.desktop file)
SVN_SILENT made messages (.desktop file)