Hello, I'm Kurvesh from India and I'm new to open-source and decided to
work for ocular for GSOC 2019 . I'm interested in this work so can anybody
guide me what specific work I want to learn for contribution for beginner
and how to start contributing. Thank you in advance!
sander added a comment.
> There's a GitHub project at https://github.com/giddie/poppler-cairo-backend
, but from how I read the related bug report, upstream integration is very
unlikely.
What I meant was rather
https://stackoverflow.com/questions/1639895/cairo-and-qt-integration .
REPO
https://bugs.kde.org/show_bug.cgi?id=400103
Michael changed:
What|Removed |Added
CC||tru...@gmx.de
--- Comment #6 from Michael ---
voting
joaonetto created this revision.
Herald added a project: Okular.
Herald added a subscriber: okular-devel.
joaonetto requested review of this revision.
REVISION SUMMARY
Implemented feature request to find from console.
BUG: 362038
REPOSITORY
R223 Okular
BRANCH
find (branched from maste
joaonetto updated this revision to Diff 49125.
joaonetto added a comment.
Deleted iostream used in main for debugging
REPOSITORY
R223 Okular
CHANGES SINCE LAST UPDATE
https://phabricator.kde.org/D18144?vs=49124&id=49125
BRANCH
find (branched from master)
REVISION DETAIL
https://phab
joaonetto added inline comments.
INLINE COMMENTS
> part.cpp:1724
> }
>
> +if( url.hasQuery() ){
Is this some bad practices? I'm sending as ID for search 1, since it's the
first search, fromStart is set as false, since the document could be in another
page. Change viewport is set as
yurchor added inline comments.
INLINE COMMENTS
> shellutils.cpp:85
> {
> -return
> QStringLiteral("%1:%2:%3:%4:%5:%6").arg(startInPresentation).arg(showPrintDialog).arg(showPrintDialogAndExit).arg(unique).arg(noRaise).arg(page);
> +return
> QStringLiteral("%1:%2:%3:%4:%5:%6:%7").arg(st