Nyall Dawson cf488d34a4 Split layout item registry into two separate registries ...

Instead of relying on forward declared c++ classes from
gui in QgsLayoutItemRegistry, instead create a
QgsLayoutItemGuiRegistry which handles registration
of all the GUI specific behavior relating to layout items.

Remove all GUI related code from QgsLayoutItemRegistry.

This creates a cleaner split between core/gui code, and
given that there'll be a lot of gui specific behavior
which needs to be handled by a registry it makes sense
to keep this isolated in gui.

It also plays nicer with the sip bindings, which can't
handle forward declared gui classes in core.

2017-07-11 11:06:36 +10:00

..

qgslayout.sip

Subclass QMouseEvent to QgsLayoutViewMouseEvent

2017-07-11 11:06:35 +10:00

qgslayoutitem.sip

Fix build warnings

2017-07-03 15:00:00 +10:00

qgslayoutitemregistry.sip

Split layout item registry into two separate registries

2017-07-11 11:06:36 +10:00

qgslayoutmeasurement.sip

…

qgslayoutmeasurementconverter.sip

Modernise some code

2017-06-26 11:17:04 +10:00

qgslayoutobject.sip

Add some base classes for layouts

2017-06-30 17:01:52 +10:00

qgslayoutpoint.sip

…

qgslayoutsize.sip

…

qgspagesizeregistry.sip

[layout] Create a page size registry for layout

2017-06-30 16:23:18 +10:00