| Age | Commit message (Collapse) | Author |
|---|
|
Also, we attempt to start the proofing at the
currently-being-viewed page.
|
|
In the proof dialog, when the document has an embedded print
profile, add it to the top of the list of choices. If it's
selected, send <EMBEDDED> into gs instead of a file name.
|
|
Enable Apply button in proofing only when color checkboxes are changed.
|
|
Out of platform/java and into the platform/android/example.
|
|
Java has a convention that 'toString' should return a printable
version of an object. We cannot both support this, and support
a sane naming of functions to interpret pdf objects that begins
with 'to'. Instead use 'as'.
This means we have 'asBoolean', 'asInteger', 'asString' which
expect to work just on pdf objects of the required type. 'toString'
continues to work on all types and gives a printable version.
We split 'toByteString' into 2 separate functions, one for acting
on strings (asByteString) and one for acting on names (asByteName)
more nicely mirroring the C level functions (pdf_to_string and
pdf_to_name).
For simplicity of use, we add asString and asName functions that
return using java Strings rather than byte arrays. There are
potential encoding issues with these, but then there are throughout
our string handling at the moment, so we will deal with those in a
followup commit.
We also update the internal workings of several functions so
that they never return NULL pointers, but rather return the null
object. To avoid repeatedly creating new null objects we introduce
a global static PDFObject.Null object.
This is important as we want get("SomethingNonexistent") to return a
valid java object, so we can safely do things like:
get("Foo").get("Bar").get("Baz").asInteger()
without having to error check at every stage.
Update DocViewActivity to call the new versions.
|
|
To be used to make correct profile invocations.
|
|
|
|
The separation class had a member renamed. Rename it here too.
|
|
pages after use.
|
|
|
|
|
|
This commit puts in the UI for drawing with color
and line thickness. But it does not yet save this to
the document.
|
|
|
|
add five icons to the File toolbar (not yet functioning)
add a dialog to collect the password from the user for protected documents.
|
|
|
|
|
|
also, change DocPageView to paint a white background before doing anything else. Makes for smoother-looking scrolling.
And, re-introduce the slower scrolling (400 msec) when moving between pages.
|
|
|
|
ul/dr=upperLeft/lowerRight
|
|
page text (one page at a time) is converted to HTML and shown in
a class that extends WebView.
|
|
|
|
|
|
|
|
- move UI into the "mupdf" module.
The app simply sets up a DocView and starts it with a file path.
The app can call DocView.showUI to determine whether the built-in UI
is used. The plan is for apps to be able to use the built-in UI,
or supply their own.
Also includes some rudimentary UI for show/hiding annotations, and
listing links and outlines. Just for testing JNI features.
- add toolbar and tabs at the top of the view.
- refactoring
DocView becomes DocActivityView, DocViewInner becomes DocView.
- add Pages toolbar and page list view.
make the page list a little narrower.
give the document view and the pages view separate bitmaps,
and have DocPageView implement clipping when it draws.
- fix tabbing and brace style.
- add simple text selection and highlighting.
This is still a work in progress.
- various code review items.
fix tabs and brace styles
remove function calls from loop statements
use "highlight", not "hilight"
put a few strings into resources
avoid Right Hand Drift (tm)
Rects are inclusive...exclusive for the purpose of testing limits
put "else" on a separate line
put "catch" and "finally" on separate lines
|
|
|
|
zooming and scrolling.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- uses AndroidDrawDevice for rendering
- very simple sample app
- mupdf-specific functionality in a module called "mupdf"
- N-up page display
- page rendering in a background task
Signed-off-by: fredrossperry <fredrossperry@gmail.com>
|
|
Thanks to Fred Ross-Perry.
|
