This means, creating a new project, we immediately have completion for
the ui file. Also adding stuff to the ui file now changes the codemodel
immediately.

Yet todo, are tests under windows and suppressing a warning if the form
contains a toplevel spacer.

The Qt4ProjectManagerPlugin needs that for the dynamic ui completion.

Reviewed-By: Friedemann Kleint <Friedemann.Kleint@nokia.com>

This adds a way for plugins to tell the cppmodel that for certain files,
the actual contents come from it, instead of reading from the disk.
(For texteditors the cppmodel does that automatically.)

Reviewed-By: Roberto Raggi <roberto.raggi@nokia.com>

Correctly draw the block highlighting after toggling.

Set/modify breakpoints using the new takeXX() APIs of the breakhandler.
Add API for inserted breakpoints (as a 2-step process for pending
breakpoints). Format breakpoint tooltip properly with tr() and
more esthetically pleasing. Get rid of the old scheme of retrieving
and matching the breakpoints from the debugger engine, use ids.

Not a brilliant solution, but it works. Changing the style itself would
cause problems in other places where the PE_IndicatorBranch is drawn.

Reviewed-by: Jens Bache-Wiig

Reviewed-by: Daniel Molkentin <daniel.molkentin@nokia.com>

Setting a parent makes sure the dialog is correctly centered and shares
the taskbar entry.

This reverts commit f56bdcd5.

Some twirks may be added, for keeping strings in-size.

Thanks to Oswald Buddenhagen for the instructions.

This means at the moment the PrettyPrinter isn't doing anything useful,
but the idea is that from here we can improve it to adapt the code to
a certain style.

Reviewed-by: Roberto Raggi

Mainly comma tokens. Referencing all tokens is necessary to be able to
implement pretty-printing based on the AST while maintaining user
formatting.

Reviewed-by: Roberto Raggi

Previously there was a lot of logic figuring out which files have
changed that are referenced a project. Leading to e.g. header files that
are part of the project, but not in a pro file, not being saved.

They don't have anything to do specifically with file wizards.

This is helpfull for building plugins from outside
the QtCreator source tree.

on QFileInfo to tell us that a file is not writable, but accept
that the attempt to save a file might actually fail (:-) ). This
solves the NT network domain issue without the insane slowness.

The stuff needs more work. We do not have any UI for failing save
operations when closing creator (other than it doesn't close). Bad.