[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 sombrag...@sombragris.org changed: What|Removed |Added CC||sombrag...@sombragris.org --- Comment #16 from sombrag...@sombragris.org --- Second this,. A "Typewriter Tool" equivalent (for an explanation in case it's necessary: http://documentgeek.blogspot.com/2011/01/acrobat-typewriter-tool-just-embrace-it_05.html) is something I sorely need to cut ties with the likes of Acrobat. -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 ANKIT YADAVchanged: What|Removed |Added CC||any65...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 Simone Gaiarinchanged: What|Removed |Added CC||simg...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 --- Comment #15 from Simone Gaiarin--- *** Bug 358062 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 --- Comment #14 from noric--- This is where I asked Poppler's devs: https://bugs.freedesktop.org/show_bug.cgi?id=93213 Yesterday I reported your findings to them. Let's see if they can help. -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 --- Comment #11 from Sumit Sahrawat--- I looked through the poppler source once again. I realized that even though the freeText annotation is implemented internally, the poppler-qt4 package doesn't export it. Specifically, the Annotation class from poppler-qt4 has a SubType enumeration, which contains only 15 values. The Annot class from poppler has an AnnotSubtype enumeration, which contains 27 values. FreeText is one of the values in poppler but not in poppler-qt4. -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 --- Comment #9 from noric--- I asked Poppler's devs and they say FreeText is already implemented in Poppler. They say the actual typewriter tool needs to be implemented by Okular (and other readers relying on Poppler). -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 --- Comment #8 from Sumit Sahrawat--- Seems like I underestimated the issues. 2-3 cannot be implemented without poppler support, sadly. -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 --- Comment #6 from Sumit Sahrawat--- I forgot to mention it here, the review request I made has been merged. 1) There are still some improvements to be made, but the code that was merged works perfectly when it comes to removing borders. Issue #332887. 2-3) They are valid feature requests, and would make for good junior jobs I think. I will see if I can get atleast one of them done. 4) I will work on this in the current season of KDE session. Issue #18. -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 Manuel López-Ibáñezchanged: What|Removed |Added CC||lopeziba...@gmail.com --- Comment #1 from Manuel López-Ibáñez --- I think this can be approximated already with an inline note with white background. The downside is that currently is not possible to remove the border around the note, nor set the background to transparent. If those two things were possible, it would be exactly what is needed (and perhaps it could be provided by default). -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 Gus Gustafsonchanged: What|Removed |Added CC||efelthau...@gmail.com --- Comment #3 from Gus Gustafson --- Some thoughts: --What if the color of the "page" is not white? User will have to try to match the comment background color to page color, as best as possible. This can be difficult. Transparent background option would be important. --Also, what will the experience be if there are very many places needing "typewriter"-type function on a page or document, if using inline comments? Have to change background color and border width for every one? That can be very user-unfriendly... Will Okular remember the last-used style setting for comments, and replicate it for next inline comment? -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 Sumit Sahrawatchanged: What|Removed |Added CC||sumit.sahrawat.apm13@iitbhu ||.ac.in --- Comment #2 from Sumit Sahrawat --- I'm working on making the border width customizable, which when set to 0 removes the border entirely. -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 --- Comment #4 from Manuel López-Ibáñez--- (In reply to Gus Gustafson from comment #3) > --Also, what will the experience be if there are very many places needing > "typewriter"-type function on a page or document, if using inline comments? > Have to change background color and border width for every one? That can be > very user-unfriendly... Will Okular remember the last-used style setting for > comments, and replicate it for next inline comment? You can create customized annotation styles. See the Okular Settings. -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel