summaryrefslogtreecommitdiffstats
path: root/examples/wayland/pure-qml
Commit message (Collapse)AuthorAgeFilesLines
* Rename QtCompositor to QtWaylandCompositorJørgen Lind2015-09-101-1/+1
| | | | | | | enable building QtWaylandCompositor by default Change-Id: I7cf34052b304ca9fef55b7e30ef6a6367b5d75f1 Reviewed-by: Jørgen Lind <jorgen.lind@theqtcompany.com>
* Make it possible to connect to a createSurface signalJørgen Lind2015-09-041-0/+13
| | | | | | | | | | | | Remove the QWaylandSurface factory function from QWaylandCompositor. Add a default constructor to QWaylandSurface and a initialize function. Add som housekeeping code in debug builds that ensures the user calls initialize. Add a fallback factory function on the compositor if the user is fine with getting the default implementation of QWaylandSurface or QWaylandQuickSurface Change-Id: Ib9289c323b6723f0d1119a484cf9e0c26c95b549
* Rename primary(Output|OutputSpace) to default(Output|OutputSpace)Jørgen Lind2015-09-041-7/+2
| | | | Change-Id: I0bbe6dd6bd8e9f6972cc88b832029ac98aa2af49
* Make it possible to construct QWaylandOutputJørgen Lind2015-09-042-30/+30
| | | | | | | | | | | | | | | This requires QWaylandOutput to be initialized. This will happend when the QWaylandCompositor of the QWaylandOutputSpace that is set on the QWaylandOutput is created. QWaylandCompositor will send or post a Polish event to the QWaylandOutput which again will call QWaylandOutput::initialize. This function will create the global that will be put on the wl_displays registry This makes it possible to Create WaylandOutputs in QML (see the pure-qml example) and also gives a better programming model in C++ Change-Id: Iaf907ae18a283678eda6d04390dc9790ae0bced8
* Rename automaticFrameCallbacks to automaticFrameCallbackJørgen Lind2015-09-041-1/+1
| | | | | | | | and: - add a signal for when it changes - change default to true Change-Id: Ifb7d29756f554dbd2a2594c935442ba9f4956c5c
* Move the curser surface signal to QWaylandInputDeviceJørgen Lind2015-09-041-1/+1
| | | | Change-Id: Ib2b1ee81a5216e348e6014927c1cc818f848384b
* Make Manufacturer & Model modifiable properties of QWaylandOutputJørgen Lind2015-09-021-1/+1
| | | | | | This to make construction look nicer and make them modifyable from QML Change-Id: I5f5ffffb34f664914cdb531736c42a6873bfe18c
* Make it possible to create the shell surface from qmlJørgen Lind2015-08-281-8/+15
| | | | Change-Id: I83dceff36d1027b24c1dafb3bc44e07f7502bc54
* Remove followRequestedPosition from QWaylandQuickItemJørgen Lind2015-08-281-1/+0
| | | | | | | | since it is not needed anymore, and it is trivial to modify QWaylandQuickItem in qml to have this behavior as pure-qml's Chrome.qml shows Change-Id: I795881fde4ecf3e2ec877222e7283b1052b7c27a
* Make the default wl_shell available from QMLJørgen Lind2015-08-282-11/+24
| | | | | | | | | | | | | | This finaly ties together how to use QWaylandQuickItems with different shells It was required to decouple QWaylandView from the QWaylandQuickItem since QML doesn't play to well with muliple inheritance. The QWaylandQuickItem can be retrieved from the QWaylandView which is now conveniently a QObject. Also the QWaylandQuickItem owns the QWaylandView. This architecture also leaves room for creating a QWaylandWidget :) Change-Id: Ib8a00e6f17f0f1bfc3ff244753f021c76db22cb1
* Remove output from QWaylandSurfaceJørgen Lind2015-08-281-1/+1
| | | | | | | | | | | | | | | It is the views that belong to outputs. This leads to a couple of interesting cases with enter and leave events, but the implementation says you will get enter events for the first view of a surface entering an output, and for the last view being removed from an output. Also to throttle a surface, there has to be 1 surface which takes care of this. This is because if multiple views throttle, then the client might render to quick. Change-Id: If4bba380fd4d7f506fd769606cbdea4ce58b908d
* Remove the default shell functionalityJørgen Lind2015-08-282-22/+9
| | | | | | | | This will be readded in a different way. Also, remove the WaylandSurfaceChrome since it is no longer needed, and just use WaylandView directly Change-Id: I8d4a7b2135d9fdaea7dd3fcd729e55cceebf48fb
* Rework how we manage extensionsJørgen Lind2015-08-281-1/+1
| | | | Change-Id: If2cbf096e7419bc1bda007d5167ce39d1a5d50ae
* Introducing QWaylandOutputSpaceJørgen Lind2015-08-281-1/+1
| | | | | | | | | | Its purpose is to make it possible to have multiscreen environments, and also multiple multioutput environments It is also an abstraction to make it clear that outputs are arranged in a 2d space Change-Id: I418509996a03b2ca1a12aec9c9e25e143a15a10f
* add a multi output exampleJørgen Lind2015-08-281-1/+1
| | | | Change-Id: I99397d1bf794c1fce483cb5d008d7701a32b2b44
* Move the output from QWaylandSurface to the QWaylandSurfaceViewJørgen Lind2015-08-281-0/+4
| | | | | | | | | and add a property called primaryOutput on the QWaylandSurface. Also add some bookkeeping in QtWayland::Output so it knows what surfaces and views it currently holds, sending the enter and leave events automatically. Change-Id: Ib6efbc6f8157657fb4451b751bba1cb5345b7906
* Add a pure-qml compositor exampleJørgen Lind2015-08-287-0/+322
It uses the new qml compositor api and implements all the user logic in qml Change-Id: Iac5eca61a9ca71c7d760d32d7aae4910ba5465b3
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-09 16:52:29 +0000