Remove MemoryViewWidget/RegisterMemoryViewWidget
in favour of MemoryView/RegisterMemoryView based on the bin
editor widget.

Add markup for displaying class layouts in the debugger.
Add a factory registered with the plugin manager
for creation of widgets by soft-dependent plugins.

Task-number: QTCREATORBUG-4589

Get debug output for all GUI applications at once. This should
stop the "Cannot retrieve debugging output".

Task-number: QTCREATORBUG-4569

Task-number: QTCREATORBUG-4451

Reviewed-by: Kai Koehne

it was apparent only with qt 4.8

for one, entirely stop monitoring the own IFile.
second, expect changes on the filename - in case other IFiles use it as
well.
these two ensure that nothing weird happens, especially if we show a dialog
and thus enter an event loop.

there only two classes of files anyway: regularly editable ones which may
ask for interaction, and "background" files which always operate silently.
the regular case is the more complex one, so put that into the base class.

it's bogus. and the ProWriter will take care not to add stray empty lines now.

- use Utils::FileSaver
- as a side effect, don't rewrite the desktop file with the same content
  if it already exists
- pop up message boxes on errors - this is likely to be more visible
  than qWarning()s/nothing
  - this is implemented in a somewhat strange way with the model itself
    doing the gui interaction, but that seems to be the simplest
    solution given the qt class design

easier to handle errors that way

lots of use of Utils::FileSaver and Utils::FileReader

Task-number: QTCREATORBUG-1619

add/unify read error handling in all affected classes

this centralizes error reporting (in fact, in most cases it adds any in
the first place).

Task-number: QTCREATORBUG-1619

no need to pass in the current file name

this replaces the ever-repeating idiom block/save/unblock with a single
call.

the internal use of SaveFile ensures that we don't leave truncated
pre-existing files behind if the disk is full or something else bad
happens.

Task-number: QTCREATORBUG-1619

inspired by KSaveFile

no point in checking for file's existence before opening it - the
errorString is verbose enough.

it's only qWarning()s, but anyway ...

it doesn't change the emitting object

Conflicts:
	qtcreator.pri
	src/plugins/debugger/breakhandler.cpp
	src/plugins/qt4projectmanager/qtversionmanager.cpp

the executable dialog that pops up.

Reviewed-by: dt