moved the debugger stuff to a.o.pdfbox.debugger
- I've created a new application subproject containing the debugger only.
PDFDebugger is configured as default application
IMHO we are done here
> Replace PDFReader with PDFDebugger
> --
>
>
2905:
-
Commit 1706115 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1706115 ]
PDFBOX-2905: added new package for debugger app
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: h
2905:
-
Commit 1706112 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1706112 ]
PDFBOX-2905: adjust PDFDebugger package, revert former changes
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
&g
2905:
-
Commit 1706109 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1706109 ]
PDFBOX-2905: move images to the new main package o.a.pdfbox.debugger
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
&g
2905:
-
Commit 1706107 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1706107 ]
PDFBOX-2905: move everything to the new main package o.a.pdfbox.debugger
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
&g
2905:
-
Commit 1706108 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1706108 ]
PDFBOX-2905: move everything to the new main package o.a.pdfbox.debugger
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
&g
2905:
-
Commit 1706106 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1706106 ]
PDFBOX-2905: move everything to the new main package o.a.pdfbox.debugger
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
&g
2905:
-
Commit 1706105 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1706105 ]
PDFBOX-2905: move PDFDebugger to new main package
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> U
2905:
-
Commit 1706104 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1706104 ]
PDFBOX-2905: merged 3 directories into one
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: h
port questions.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
> Issue Type: Improvement
>
n in the app jar as well or should we remove it from
there?
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
ot;Double click to start" is a more pleasant user
experience than "open a shell, then enter java -jar .jar PDFDebugger
xxx.pdf"
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL
is a misunderstanding. The new debugger subproject provides a
simple jar containing the debugger classes only. There are still just the 2 app
jars which are executable.
Should we provide a third executable app jar for the debugger?
> Replace PDFReader with PDFD
erent jar?
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
> Issue Type: Improvement
>Affects Vers
gger as the top level name here and
merge/rename the three packages you mentioned.
If we keep tools.pdfdebugger maybe rename the package in pdbox-tools to
o.a.p.tools.cli
> Replace PDFReader with PDFDebugger
> --
>
>
ages org.apache.pdfbox.tools.gui,
org.apache.pdfbox.tools.utils and org.apache.pdfbox.tools.pdfdebugger.ui?
How about renaming the package (org.apache.pdfbox.tools.pdfdebugger ->
org.apache.pdfbox.debugger) ?
> Replace PDFReader with P
Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
> Issue Type: Improvement
>Affects Versions: 2.0.0
[
https://issues.apache.org/jira/browse/PDFBOX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935471#comment-14935471
]
Andreas Lehmkühler commented on PDFBOX-2905:
I've removed the
2905:
-
Commit 1705890 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1705890 ]
PDFBOX-2905: remove PDFReader
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apach
s of the jar the PDFBox app isn't available anymore.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
>
efault as originally intended. So we now have
-viewstucture instead.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: P
2905:
-
Commit 1705766 from [~jahewson] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1705766 ]
PDFBOX-2905: Make page view the default
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: h
I'd wish that the library launch PDFDebugger on
double click. (May have been done already, I'm 12 hours behind)
I've never used the same image feature, but I think it makes sense.
> Replace PDFReader with PDFDebugger
> --
>
>
mand line parameter to PDFDebugger to activate the page
mode on startup
- I've added a print menu to PDFDebugger
- I've replaced the PDFReader in PDFBox app with the PDFDebugger in page mode
I'm not sure if we really need the save current page as image option. Saying
that, are we r
2905:
-
Commit 1705738 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1705738 ]
PDFBOX-2905: add new command line parameter to usage message
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
&g
2905:
-
Commit 1705737 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1705737 ]
PDFBOX-2905: add print menu entry
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.
2905:
-
Commit 1705734 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1705734 ]
PDFBOX-2905: use PDFDebugger in "View Pages" mode instead of PDFReader
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFB
2905:
-
Commit 1705729 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1705729 ]
PDFBOX-2905: add a new comandline parameter to activate "View Pages" mode on
startup
> Replace PDFReader with PDFDebugger
> --
>
&
[
https://issues.apache.org/jira/browse/PDFBOX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Lehmkühler reassigned PDFBOX-2905:
--
Assignee: Andreas Lehmkühler (was: John Hewson)
> Replace PDFReader w
ttps://bugs.openjdk.java.net/browse/JDK-8041647]. Try setting the relevant
Java flags to enable/disable 2D acceleration, maybe try a 32-bit JVM.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https:
[
https://issues.apache.org/jira/browse/PDFBOX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14910007#comment-14910007
]
John Hewson commented on PDFBOX-2905:
-
(y)
> Replace PDFReader with PDFD
bugger to its own package. PDFReader is still there
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
>
2905:
-
Commit 1705561 from [~lehmi] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1705561 ]
PDFBOX-2905: create a new package for PDFDebugger
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> U
the difference is the used graphics object. The one
used by PDFReader is bigger than the page and has a transformation which is
non-identity and a clipping region cropping the graphics to the page size.
PDFBox transformes the graphics instance without taking those special
circumstances into acc
d on the page-tree-handling branch. I
wonder if it's OS or Java version dependent. I'm running the following
Linux Mint 17.2 Cinnamon 64-bit
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Replace PDFReader
uble rendering this file with the current
trunk. However I cannot render it with the
https://github.com/benmccann/pdfbox/tree/page-tree-handling version, I get an
ArrayIndexOutOfBoundsException.
> Replace PDFReader with PDFDebugger
> --
>
>
fbox-app-2.0.0-SNAPSHOT.jar PDFReader
007087-payment-due.pdf}} and got a stacktrace
Exception in thread "AWT-EventQueue-0" java.lang.InternalError: not implemented
yet
at sun.java2d.xr.XRSurfaceData.getRaster(XRSurfaceData.java:72)
at sun.java2d.loops.Blit$AnyBlit.Blit
[
https://issues.apache.org/jira/browse/PDFBOX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hewson updated PDFBOX-2905:
Fix Version/s: 2.0.0
> Replace PDFReader with PDFDebug
[
https://issues.apache.org/jira/browse/PDFBOX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hewson updated PDFBOX-2905:
Priority: Blocker (was: Minor)
> Replace PDFReader with PDFDebug
the tools project that is designed to be used in a
different way than just calling its main()?
{quote}
Yes, the org.apache.pdfbox.tools.imageio package, this is for saving images in
an easy way and with resolution metadata.
> Replace PDFReader with PDFD
ject that is designed to be used in a different way
than just calling its main()?
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
>
to make it clear
that the debugger is unstable, despite having public APIs.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
>
at these are public, but it's a technical requirement.
But from a stability point of view, we don't want to exposes these classes to
end users or make any sort of stability guarantee. So we need to make it clear
that the debugger is unstable, despite having public APIs.
&g
ever said that I want to make something public which isn't public now when
releasing. My statement is quite simple: every public api within PDFBox becomes
stable when releasing it and it doesn't matter if it's in in its onw jar bundle
or in another bundle together with other part
r is moved to its own package.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
> Is
t to make something public which isn't public now when
releasing. My statement is quite simple: every public api within PDFBox becomes
stable when releasing it and it doesn't matter if it's in in its onw jar bundle
or in another bundle together with other parts of the software.
>
elop with PDFBox.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
> Issue Type: Improvement
>Affec
why would it need to be stable? If we expose
the debugger APIs as public and stable, then we can't make any significant
changes for the entire lifetime of 2.0...
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
&g
ased version is as stable as all the other jars
belonging to that specific release.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
>
ncluding it with what are currently stable public APIs in the tools jar.
Also, anyone shipping the tools jar isn't shipping the debugger too - because
the debugger is getting quite large now.
> Replace PDFReader with PDFDebugger
> --
>
the debugger is getting quite large now.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
> Is
few months ago and then gave up, but what I
remember is that the graphics transform is non-identity, i.e. there is a
translation.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apa
with its own releases?
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
> Issue Type: Impro
d to PDFRenderer#renderPageToGraphics().
There's something about rendering onto and existing Graphics surface which is
causing differences.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https:
s (Author: jahewson):
Yep, the difference is somehow related to PDFRenderer#renderPageToGraphics().
There's something about rendering onto and existing Graphics surface which is
causing differences.
> Replace PDFReader with PDFDebugger
> --
>
>
5 PM:
--
There's one thing I'd like to be looked at before PDFReader gets removed -
cases where the rendering is different when done with PDFReader and PDFDebugger
or PDFToImage, e.g. the attached file (007087-payment-due.pdf). PDFReader shows
a vertical line in the orange segmen
2 PM:
--
There's one thing I'd like to be looked at before PDFReader gets removed -
cases where the rendering is different when done with PDFReader and PDFDebugger
or PDFToImage, e.g. the attached file (007087-payment-due.pdf). PDFReader shows
a vertical line in the orange segmen
7;d like to be looked at before PDFReader gets removed -
cases where the rendering is different when done with PDFReader and PDFDebugger
or PDFToImage, e.g. the attached file (007087-payment-due.pdf). PDFReader shows
a vertical line in the orange segment. When making the window wider, the line
go
[
https://issues.apache.org/jira/browse/PDFBOX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr updated PDFBOX-2905:
Attachment: 007087-payment-due.pdf
> Replace PDFReader with PDFDebug
can
live in peace, away from the tools jar's public APIs.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
FDebugger into its own jar, where it can
live in peace, away from the tools jar's public APIs.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
6 AM:
--
Yes, we could do that!
was (Author: jahewson):
Not without breaking PDFReader's API, you can't. Do you just mean the command
line "PDFReader" could launch PDFDebugger instead - yes, we could do that!
> Replace
4 AM:
--
Not without breaking PDFReader's API, you can't. Do you just mean the command
line "PDFReader" could launch PDFDebugger instead - yes, we could do that!
was (Author: jahewson):
Not without breaking PDFReader's API, you can't.
&g
API, you can't.
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
> Issue Type: Impro
2 PM:
--
One could use "PDFReader" to call the debugger in page mode :-)
was (Author: tilman):
One could use "PDReader" to call the debugger in page mode :-)
> Replace PDFReader with PDFDebugger
> --
>
> Ke
t; to call the debugger in page mode :-)
> Replace PDFReader with PDFDebugger
> --
>
> Key: PDFBOX-2905
> URL: https://issues.apache.org/jira/browse/PDFBOX-2905
> Project: PDFBox
> Issue Type
[
https://issues.apache.org/jira/browse/PDFBOX-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Lehmkühler closed PDFBOX-1183.
--
Resolution: Won't Fix
We won't fix that as the PDFReader will be removed,
eady complete, the arrow keys can be used for single page
flipping and the page up/down keys for pagebased (not pdf pages but pages
within the treeview) flipping within the tree containing all pages.
There are only two PDFReader features missing, printing and saving single pages
as image.
Should we a
[
https://issues.apache.org/jira/browse/PDFBOX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hewson reassigned PDFBOX-2905:
---
Assignee: John Hewson
> Replace PDFReader with PDFDebug
John Hewson created PDFBOX-2905:
---
Summary: Replace PDFReader with PDFDebugger
Key: PDFBOX-2905
URL: https://issues.apache.org/jira/browse/PDFBOX-2905
Project: PDFBox
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/PDFBOX-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hewson updated PDFBOX-2905:
Affects Version/s: 2.0.0
> Replace PDFReader with PDFDebug
schrieb Andreas Lehmkuehler:
>>>>> Hi,
>>>>>
>>>>> I like all those new features which were added to PDFDebugger lately, as
>>>>> far as I've already found them ;-)
>>>>>
>>>>> I'm thinking about re
ready found them ;-)
I'm thinking about removing PDFReader as PDFDebugger is now able to
render single pages as well and it is doing it even better.
-1
I've seen this coming... but although I had a part in including
reader features in PDFDebugger, I think that PDFDebugger is for th
t removing PDFReader as PDFDebugger is now able to render
single pages as well and it is doing it even better.
-1
I've seen this coming... but although I had a part in including reader features in PDFDebugger, I
think that PDFDebugger is for the professional "PDF detective", while PDFRe
dreas Lehmkuehler :
>>>>
>>>> Hi,
>>>>
>>>> I like all those new features which were added to PDFDebugger lately, as
>>>> far as I've already found them ;-)
>>>>
>>>> I'm thinking about removing PDFRea
> On 26 Jul 2015, at 13:11, Tilman Hausherr wrote:
>
>> Am 26.07.2015 um 22:00 schrieb Andreas Lehmkuehler:
>> Hi,
>>
>> I like all those new features which were added to PDFDebugger lately, as far
>> as I've already found them ;-)
>>
>>
> On 26 Jul 2015, at 13:00, Andreas Lehmkuehler wrote:
>
> Hi,
>
> I like all those new features which were added to PDFDebugger lately, as far
> as I've already found them ;-)
>
> I'm thinking about removing PDFReader as PDFDebugger is now able to render
w features which were added to PDFDebugger lately, as
>>> far as I've already found them ;-)
>>>
>>> I'm thinking about removing PDFReader as PDFDebugger is now able to render
>>> single pages as well and it is doing it even better.
>>
>>
> On 26 Jul 2015, at 13:11, Maruan Sahyoun wrote:
>
> Hi,
>
>> Am 26.07.2015 um 22:00 schrieb Andreas Lehmkuehler :
>>
>> Hi,
>>
>> I like all those new features which were added to PDFDebugger lately, as far
>> as I've already found the
Hi,
> Am 26.07.2015 um 22:00 schrieb Andreas Lehmkuehler :
>
> Hi,
>
> I like all those new features which were added to PDFDebugger lately, as far
> as I've already found them ;-)
>
> I'm thinking about removing PDFReader as PDFDebugger is now able to render
Am 26.07.2015 um 22:00 schrieb Andreas Lehmkuehler:
Hi,
I like all those new features which were added to PDFDebugger lately,
as far as I've already found them ;-)
I'm thinking about removing PDFReader as PDFDebugger is now able to
render single pages as well and it is doing it e
Hi,
I like all those new features which were added to PDFDebugger lately, as far as
I've already found them ;-)
I'm thinking about removing PDFReader as PDFDebugger is now able to render
single pages as well and it is doing it even better.
WDYT?
[
https://issues.apache.org/jira/browse/PDFBOX-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr resolved PDFBOX-2826.
-
Resolution: Fixed
> Mouse position shown when mouse outside of PDFReader win
2826:
-
Commit 1684474 from [~tilman] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1684474 ]
PDFBOX-2826: clear mouse position from status bar when outside the window
> Mouse position shown when mouse outside of
Tilman Hausherr created PDFBOX-2826:
---
Summary: Mouse position shown when mouse outside of PDFReader
window
Key: PDFBOX-2826
URL: https://issues.apache.org/jira/browse/PDFBOX-2826
Project: PDFBox
in PDFReader
>
>
> Key: PDFBOX-2736
> URL: https://issues.apache.org/jira/browse/PDFBOX-2736
> Project: PDFBox
> Issue Type: Improvement
> Components
2736:
-
Commit 1670201 from [~tilman] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1670201 ]
PDFBOX-2736: added first and last page navigation, by Khyrul Bashar
> First page and last page navigation with keyboard short
uts in PDFReader
>
>
> Key: PDFBOX-2736
> URL: https://issues.apache.org/jira/browse/PDFBOX-2736
> Project: PDFBox
> Issue Type: Improvement
>
ntry is added i.e "First page", "Last Page". And view
menu items are made responsive e.g. e.g. when I'm at the first page "previous
page" and "first page" menu entries are disabled.
> First page and last page navigation with keyboard shortcut
ard shortcuts in PDFReader
>
>
> Key: PDFBOX-2736
> URL: https://issues.apache.org/jira/browse/PDFBOX-2736
> Project: PDFBox
> Issue Type: Improvement
>
khyrul bashar created PDFBOX-2736:
-
Summary: First page and last page navigation with keyboard
shortcuts in PDFReader
Key: PDFBOX-2736
URL: https://issues.apache.org/jira/browse/PDFBOX-2736
Project
gt; Keyboard shortcuts in PDFReader
> ---
>
> Key: PDFBOX-2735
> URL: https://issues.apache.org/jira/browse/PDFBOX-2735
> Project: PDFBox
> Issue Type: Improvement
> Components: Swing
[
https://issues.apache.org/jira/browse/PDFBOX-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr resolved PDFBOX-2735.
-
Resolution: Fixed
> Keyboard shortcuts in PDFRea
ue is closed without resolving (e.g. duplicate, can't reproduce, not a
problem etc). So the best is not to press "close" at all. We'll do it :-)
> Keyboard shortcuts in PDFReader
> ---
>
> Key: PDFBOX-2735
>
[
https://issues.apache.org/jira/browse/PDFBOX-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
khyrul bashar closed PDFBOX-2735.
-
> Keyboard shortcuts in PDFReader
> ---
>
>
[
https://issues.apache.org/jira/browse/PDFBOX-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr resolved PDFBOX-2735.
-
Resolution: Fixed
> Keyboard shortcuts in PDFRea
[
https://issues.apache.org/jira/browse/PDFBOX-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr reassigned PDFBOX-2735:
---
Assignee: Tilman Hausherr
> Keyboard shortcuts in PDFRea
n and git services" is down. The text would have been:
Commit 1669953 from [~tilman] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1669953]
PDFBOX-2735: add PgUp and PgDn to PDFReader and additional keyboard shortcuts,
by Khyrul Bashar
> Keyb
uot;as is" with minor reformatting (see
https://pdfbox.apache.org/codingconventions.html ). Btw, the trunk version is
2.0. 1.8.* are the released versions, we only make changes there if either very
easy or if it corrects a bug.
> Keyboard short
in PDFReader
> ---
>
> Key: PDFBOX-2735
> URL: https://issues.apache.org/jira/browse/PDFBOX-2735
> Project: PDFBox
> Issue Type: Improvement
> Components: Swing GUI
>Affects Versions:
1 - 100 of 186 matches
Mail list logo
