There is no shortcut associated with these actions, the user has to
set them up by himself.

Use BreakpointData objects for communicaition instead of random
collection of some of their attributes.

application

Reviewed-by: hjk

This mainly reverts commit ba47987e.

Conflicts:

	src/plugins/debugger/debugger.pro
	src/plugins/debugger/debuggermanager.cpp
	src/plugins/debugger/debuggermanager.h
	src/plugins/debugger/debuggerplugin.cpp
	src/plugins/debugger/debuggerplugin.h

Discussed-with: hjk

Do it in the destructor instead.

Reviewed-by: hjk

The TextEditorSettings class already provides the appropriate signal.

Reviewed-by: hjk

if an executable was specified.

backtrace in the main editor.

Useful for sending bug reports.

Some categories do not have icons yet, unfortunately.

Task-number: QTCREATORBUG-450

Reviewed-by: Thorbjørn

While before you had to call add, then remove for each context id and
then call update, now you call updateAdditionalContexts with a list of
contexts to remove and add. It has the update step built in.

Reviewed-by: con

* We now consistently avoid punctuation when possible
* Renamed usage of "Inferior" and "Program" to "Application" for
  increased readability
* Fixed inconsistent spacing in front of statusbar label

Reviewed-by:hjk

the previous implementation relied on poking around with setVisible
of the menu actions. Now, command attribute CA_Hide is used instead for
the necessary entries.

Reviewed-by: hjk

Additionally, hiding of debugger menu entries was done as most of
them are irrelevant for QML debugging.

Try to detect engine by looking at toolchain, executable,
attach mode. Find out path to executable in attach to running
dialog.

Reviewed-by: hjk

Needs polishing.

The dependency was there for a while. No need to jump through hoops hoping
to maintain a stand-alone debugger anymore.

editor or re-used an existing one