* Ease cross device development by introducing 'targets' which
group build- and runsettings that are valid for this one target
Most of the kudos for the code review go to dt. Con, thorbjorn,
ckandler and others did also review parts of this patch.
Reviewed-by: dt
* Use id() for methods returning a string used to represent
some type of object.
* Use displayName() for strings that are meant to be user
visible.
* Quieten some warnings while touching the files anyway.
* Move Factories to their products in the plugins where that
was not done before.
Reviewed-by: dt
We are targetting nothing below netbooks. These devices have screens
that usually are 1024px wide (or wider), so this increase should be OK
there.
The 100px bonus do help a bit when editing environment variables, etc.
Reviewed-by: dt
* Indent widgets using contentsmargins. That way the individual
widgets can override this.
* Remove spme spacers in favour of yet more contents margins.
* Remove unused headers and forward declarations.
* Define some constants for spacings we might want to tweak later on.
Reviewed-by: dt
* Rename it to IPropertiesPanel in accordance with new naming standards.
* Do not derive from Context. That is not needed.
* Add an icon() method.
* Fix all usages of this interface.
Reviewed-By: dt
This isn't a nice fix but the least evil version of a hack i could come
up. The source of the flickering is: We have a deeply nested structure
of widgets on the project pane. If we call hide() on such a deeply
nested widget, it will activate() it's parent layout synchronously.
That will then post an event (via updateGeometries() ) to its parent
layout that it needs relayouting. Which then will post to its parent
layout the same. And for each LayoutRequested, there's a painting in
between. The fix instead calls activate() up the chain until we are at
the viewport. This immediately relayouts everything. This adds a non
obvoius potentially for breakeage if the widgets are embedded in a
different widget hierarchy. But well, that's life.
This has still a few missing things, but this enough to start getting
some feedback. Missing are non qt projects, a solution for the
runconfiguration, a missing black line between the treeview on top and
the project settings at the bottom. Some flickering with removing/adding
widgets to the QScrollArea and not showing the expanded widget if the
Details button is right at the bottom.
Removing the last project did set startupproject to zero and unloaded
the project. Thus the check that the project for the current item and
the startup project are both null and the same.
