GitLab

Nicolas Fella authored Mar 09, 2021 and Albert Astals Cid committed Mar 09, 2021

It's not needed

Source files are no longer separated by UI and non-UI and similar,
but only by their build target.

* ui/ -> part/
* Move all source files from conf/ to part/
* Keep config skeleton definitions in conf/, needed for the mobile target too
* Move editdrawingtooldialogtest.h from conf/autotests/ to autotests/
* ui/data/icons/ -> icons/
* Move /part.cpp, /part.rc and similar files to part/
* Adapt include paths in source files
* Adapt CMakeLists.txt files (in / and in subdirectories)
* Adapt /Messages.sh

Nicolas Fella authored Oct 25, 2019 and Ben Cooksley committed Nov 03, 2019

(cherry picked from commit 187c4740)

Summary:
This only depended on okularpart due to the export header used in the
kcfgc file, so use a dedicated one for the mobile components that doesn't
export anything.

This enables disabling the part build for mobile-only builds such as
Android, and thus removing the need for some difficult dependencies
like KParts.

Reviewers: aacid

Reviewed By: aacid

Subscribers: aacid, okular-devel

Tags: #okular

Differential Revision: https://phabricator.kde.org/D19037

It's wrong to link against plugins anyway.

REVIEW: 127328

okularplugin target from mobile/components suffers from the same problem as okularpart in https://git.reviewboard.kde.org/r/125741/
But the cause is a bit different now. okularplugin uses settings.cpp generated by KConfig and its header declares Settings class with OKULARCORE_EXPORT. For okularplugin target this macro gets expanded to __declspec(dllimport) and it makes linker to look for Settings class symbols in okularcore.

Fix this by tricking VS that we are building okularcore target.

REVIEW: 125742

It supports changing pages by a swipe gesture, pinch zoom
and flicking to scroll around.
The mobile application will be ported to this new component

don't link to okularpart, it won't be able to find it where
it's installed (under plugins)

remove qt4_automoc, and reference to KDE4_DEFINITIONS

lik to okularcore and okularpart instead of including the settings code multiple times, which breaks the exports

this is an initial port of the qml component set of okular to qtquick2

it's straightforward, except pageitem that right now is a qquickpainteditem, that works fine, but a bit slower than generating and uploading the textures by hand (that may be an eventual future port)

the okular active application is still missing, but the components can be used from anywhere in qml
REVIEW:121326

Bogdan Cristea authored Oct 16, 2012 and Albert Astals Cid committed Oct 16, 2012

Will make it easier to make separate apps based on the core in the future
Note this will most probably break your settings if you are not running a very up to date kdelibs (4.9 or 4.10)
so be careful on updating
REVIEW: 104947

todo: license issues

two components:
Document, represents an Okular::Document
Page: represents an Okular::Page, once connected to a Document can display a single page