QueueOptimizer is really hard to read. Enough so that it's blocking my efforts to streamline the representation used for operator lists. This patch improves its readability in the following ways. - More descriptive variable names make the sequence checking much clearer, as do additional comments. - The addState() functions now return the index of the first op past the sequence, instead of setting context.currentOperation to the last op of the sequence. - The loop in optimize() is clearer. - The array modification in the fourth addState() function is much clearer -- we're just removing trios of ops. - All four |addState| functions are now more consistent with each other. I used some debug printfs to find documents where these optimizations are used and then checked that the number of optimized ops was the same before and after my changes. |
11 years ago | |
---|---|---|
docs | Creates make.js code to build jsdoc. | 11 years ago |
examples | Added paintJpegXObject | 11 years ago |
extensions | Adds telemetry to record embedding usages | 11 years ago |
external | Making sure we are not importing CRs and BOMs | 11 years ago |
l10n | Re-add Attachment strings to the Swedish l10n | 11 years ago |
src | Make QueueOptimizer easier to read. | 11 years ago |
test | Merge pull request #4944 from Snuffleupagus/issue-4934 | 11 years ago |
web | Do not run cleanup while printing is ongoing. | 11 years ago |
.gitattributes | Force Unix line endings for all files in new commits | 11 years ago |
.gitignore | Issue #2008 - Add jshint | 12 years ago |
.gitmodules | Migrating test.py to test.js | 11 years ago |
.jshintignore | Exclude B2G stubs from linting | 11 years ago |
.jshintrc | Update lint config to enforce braces for single line statements | 11 years ago |
.travis.yml | Switch to Node.js 0.10 | 11 years ago |
AUTHORS | Add @lovasoa to AUTHORS | 11 years ago |
CONTRIBUTING.md | Implements importl10n command | 11 years ago |
LICENSE | Change to the Apache v2 license. | 13 years ago |
README.md | Fixes versions of the jsbin.com examples | 11 years ago |
make.js | Splits shared/annotation.js into core/ and display/ | 11 years ago |
package.json | Move jshint & yargs to devDependencies | 11 years ago |
pdfjs.config | Version 1.0.277 | 11 years ago |
README.md
PDF.js
PDF.js is a Portable Document Format (PDF) viewer that is built with HTML5.
PDF.js is community-driven and supported by Mozilla Labs. Our goal is to create a general-purpose, web standards-based platform for parsing and rendering PDFs.
Contributing
PDF.js is an open source project and always looking for more contributors. To get involved checkout:
For further questions or guidance feel free to stop by #pdfjs on irc.mozilla.org.
Getting Started
Online demo
Browser Extensions
Firefox
PDF.js is built into version 19+ of Firefox, however two extensions are still available that are updated at a different rate:
- Development Version - This version is updated every time new code is merged into the PDF.js codebase. This should be quite stable but still might break from time to time.
- Stable Version - After version 24 of Firefox is released we no longer plan to support the stable extension. The stable version will then be considered whatever is built into Firefox.
Chrome and Opera
The Chromium extension is still somewhat experimental but it can be installed two ways:
- Unofficial Version - This extension is maintained by a PDF.js contributor.
- Build Your Own - Get the code as explained below and issue
node make chromium
. Then open Chrome, go toTools > Extension
and load the (unpackaged) extension from the directorybuild/chromium
.
The version of the extension for the Opera browser can be found at the Opera add-ons catalog.
Getting the Code
To get a local copy of the current code, clone it using git:
$ git clone git://github.com/mozilla/pdf.js.git pdfjs
$ cd pdfjs
Next, you need to start a local web server as some browsers don't allow opening PDF files for a file:// url:
$ node make server
You can install Node via nvm or the official package. If everything worked out, you can now serve
You can also view all the test pdf files on the right side serving
Building PDF.js
In order to bundle all src/
files into two productions scripts and build the generic
viewer, issue:
$ node make generic
This will generate pdf.js
and pdf.worker.js
in the build/generic/build/
directory.
Both scripts are needed but only pdf.js
needs to be included since pdf.worker.js
will
be loaded by pdf.js
. If you want to support more browsers than Firefox you'll also need
to include compatibility.js
from build/generic/web/
. The PDF.js files are large and
should be minified for production.
Learning
You can play with the PDF.js API directly from your browser through the live demos below:
- Hello world: http://jsbin.com/pdfjs-helloworld-v2/9612/edit#html,live
- Simple reader with prev/next page controls: http://jsbin.com/pdfjs-prevnext-v2/6865/edit#html,live
The repo contains a hello world example that you can run locally:
For an introduction to the PDF.js code, check out the presentation by our contributor Julian Viereck:
You can read more about PDF.js here:
- http://andreasgal.com/2011/06/15/pdf-js/
- http://blog.mozilla.com/cjones/2011/06/15/overview-of-pdf-js-guts/
Even more learning resources can be found at:
Questions
Check out our FAQs and get answers to common questions:
Talk to us on IRC:
- #pdfjs on irc.mozilla.org
Join our mailing list:
Subscribe either using lists.mozilla.org or Google Groups:
- https://lists.mozilla.org/listinfo/dev-pdf-js
- https://groups.google.com/group/mozilla.dev.pdf-js/topics
Follow us on twitter: @pdfjs
Weekly Public Meetings