[okular] [Bug 390588] Wish: Display a notification when a PDF with fillable forms is detected (UX)

[Oliver Sander]

https://bugs.kde.org/show_bug.cgi?id=390588

--- Comment #2 from Oliver Sander  ---
Created attachment 110740
  --> https://bugs.kde.org/attachment.cgi?id=110740=edit
Screenshot with a "fillable forms" info field

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 390588] Wish: Display a notification when a PDF with fillable forms is detected (UX)

[Oliver Sander]

https://bugs.kde.org/show_bug.cgi?id=390588

Oliver Sander  changed:

   What|Removed |Added

 CC||oliver.san...@tu-dresden.de

--- Comment #1 from Oliver Sander  ---
Okular has had this as long as I remember.  See the attached screenshot.  Or am
I misunderstanding your wish?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 390588] New: Wish: Display a notification when a PDF with fillable forms is detected (UX)

[Tn]

https://bugs.kde.org/show_bug.cgi?id=390588

Bug ID: 390588
   Summary: Wish: Display a notification when a PDF with fillable
forms is detected (UX)
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-devel@kde.org
  Reporter: whyeven3...@outlook.com
  Target Milestone: ---

Displaying a notification to the user with an option to toggle the Show Form
option when they open a PDF with fillable forms would drastically improve the
UX of this feature.

I was previously unaware of Okular's ability to fill in forms until I looked it
up on the web and realised that it had this functionality all along. With this
very handy feature hidden in the confines of the View menu, it's extremely
easily to be entirely oblivious of its presence. Adding a notification could go
a long way in addressing this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

D10566: Fictionbook: Add support for code, superscript, & subscript tags

[Abdel-Rahman A .]

abogical updated this revision to Diff 27378.
abogical added a comment.


  Use `QStringLiteral` .

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D10566?vs=27376=27378

REVISION DETAIL
  https://phabricator.kde.org/D10566

AFFECTED FILES
  generators/fictionbook/converter.cpp
  generators/fictionbook/converter.h

To: abogical, #okular
Cc: cfeck, ngraham, michaelweghorn, simgunz, aacid

D10566: Fictionbook: Add support for code, superscript, & subscript tags

[Abdel-Rahman A .]

abogical updated this revision to Diff 27376.
abogical added a comment.


  Used QStringLiteral

REPOSITORY
  R223 Okular

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D10566?vs=27335=27376

REVISION DETAIL
  https://phabricator.kde.org/D10566

AFFECTED FILES
  generators/fictionbook/converter.cpp
  generators/fictionbook/converter.h

To: abogical, #okular
Cc: cfeck, ngraham, michaelweghorn, simgunz, aacid

Need help regarding heading into the Okular Feature: 388450

[Dileep Sankhla]

Hello devs,

I have spent the past three days in heading into this feature request [1]
regarding scrolling the annotations along with the scrollbar and I have
been finding out how to unfix the position of the annotation window that
remains fixed to its position while scrolling the pageview.
I'm trying to get an idea from the annotations that remains glued to the
pageview and do scroll with the scrollbar and hence applying the same
approach ( and a bit of the similar code too) in order to achieve this on
the annotation window.
But now the problem is I'm confused inside the large codebase and I tried
to search for the keywords like "mouseMove", "scroll", "fixed"  but without
any success in finding the relevant section.
I also did minor tweaks and changes in order to understand the behavior but
until now, I'm nowhere.

I'm still searching but now I doubt my way of fixing a bug. Can you please
suggest me how to proceed to fix/implement the bug/feature and how to
search the code, inspect the Qt elements and all? What to do now?
I have read 'get started' guide but it doesn't emphasis on my own dilemma.

‌[1] https://bugs.kde.org/show_bug.cgi?id=388450

Thanks and Regards
Dileep

D10566: Fictionbook: Add support for code, superscript, & subscript tags

[Abdel-Rahman A .]

abogical edited the test plan for this revision.

REPOSITORY
  R223 Okular

REVISION DETAIL
  https://phabricator.kde.org/D10566

To: abogical, #okular
Cc: cfeck, ngraham, michaelweghorn, simgunz, aacid

D10566: Fictionbook: Add support for code, superscript, & subscript tags

[Abdel-Rahman A .]

abogical retitled this revision from "Add support for code, superscript, & 
subscript tags in fictionbook" to "Fictionbook: Add support for code, 
superscript, & subscript tags".
abogical edited the summary of this revision.

REPOSITORY
  R223 Okular

REVISION DETAIL
  https://phabricator.kde.org/D10566

To: abogical, #okular
Cc: cfeck, ngraham, michaelweghorn, simgunz, aacid

D10566: Add support for code, superscript, & subscript tags in fictionbook

[Abdel-Rahman A .]

abogical retitled this revision from "Add support for code tags in fictionbook" 
to "Add support for code, superscript, & subscript tags in fictionbook".

REPOSITORY
  R223 Okular

REVISION DETAIL
  https://phabricator.kde.org/D10566

To: abogical, #okular
Cc: cfeck, ngraham, michaelweghorn, simgunz, aacid

D10566: Add support for code tags in fictionbook

[Abdel-Rahman A .]

abogical updated this revision to Diff 27335.
abogical edited the test plan for this revision.
abogical added a comment.


  Added support for superscript and subscript tags, also fixed formatting 
issues. Just a question, what tools does the KDE developers use for linting the 
formatting of their code?

REPOSITORY
  R223 Okular

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D10566?vs=27314=27335

REVISION DETAIL
  https://phabricator.kde.org/D10566

AFFECTED FILES
  generators/fictionbook/converter.cpp
  generators/fictionbook/converter.h

To: abogical, #okular
Cc: cfeck, ngraham, michaelweghorn, simgunz, aacid

[okular] [Bug 169847] split view feature

[Germano Massullo]

https://bugs.kde.org/show_bug.cgi?id=169847

--- Comment #29 from Germano Massullo  ---
Does KDE allow a bounty program?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 383651] Custom/image stamp annotations are not saved into the PDF file in a way that can be printed or that other readers can see

[Oliver Sander]

https://bugs.kde.org/show_bug.cgi?id=383651

--- Comment #11 from Oliver Sander  ---
Can somebody please post this on the gsoc project list for me?  Thanks!

Project: Improve custom stamp annotation handling

Brief explanation: Okular does display stamp annotations, but the support
is somewhat incomplete. This particularly shows when trying to use stamp
annotations with a custom image.  For example, such annotations can be
added in Okular, but they cannot be saved to the pdf file in a way
that any other pdf viewer can read.  Also, they will not appear on print-outs.

The underlying reason for this is that Okular renders these stamps itself,
rather than relying on the poppler library, which does all other pdf
rendering.  Goal of this project is therefore to teach poppler how to
render stamp annotations, and then make Okular use that new functionality.
More details can be found in the bug report [0].

[0] https://bugs.kde.org/show_bug.cgi?id=383651

Expected results:  Poppler should render stamp annotations.  Annotations
should be printable from Okular. Custom stamps inserted via the Okular GUI
should be visible in other pdf readers.

Knowledge prerequisite: C++, and a bit about the pdf format.

-- 
You are receiving this mail because:
You are the assignee for the bug.