Re:Pdf.js reached its first milestone
by ZeroGravitas on Monday July 04, 2011 @06:29AM
(#2726096)
I like this project. I sometimes feel Chrome has a slight advantage because Google is also building really cool services, so they can get both sides in sync (e.g. returning WebP images in page previews, or encoding to WebM with Youtube).
By building things like Pdf.js and butter/popcorn.js and giving them away for other projects to use Mozilla gets to have the same impact and feedback loop, which helps to further their mission to improve the web.
Re:Pdf.js reached its first milestone
by ajays on Monday July 04, 2011 @01:36PM
(#2727183)
I must be doing something wrong, because I'm getting fairly shitty rendering. I'm on FF5, Ubuntu 10.04. Anyone else have problems viewing their demo paper?
Re:Pdf.js reached its first milestone
by notatoad on Monday July 04, 2011 @10:00PM
(#2728410)
"We said above that pdf.js renders the Tracemonkey paper perfectly … if you’re running a Firefox nightly. On a Windows 7 machine where Firefox can use Direct2D and DirectWrite. If you ignore what appears to be a bug in DirectWrite’s font hinting. The paper is rendered less well on other platforms and in older FIrefoxen, and even worse in other browsers"
Re:Pdf.js reached its first milestone
by carterschonwald on Monday July 04, 2011 @01:20PM
(#2727115)
This is pretty cool!
Theres a pretty interesting feature in the pdf standard that few viewers support is embedded animations driven by javascript. As far as I know, only adobe properly supports it, bu there are some nice visualization tools such as pgf/tikz which allow for producing such visuals.
Re:Pdf.js reached its first milestone
by panabee on Monday July 04, 2011 @03:22PM
(#2727536)
This is awesome. Anything to streamline the UX and eliminate the overt loading of a separate application is terrific. Hopefully Mozilla can continue to innovate and push Google on the browser front.
Re:Pdf.js reached its first milestone
by Lagged2Death on Monday July 04, 2011 @08:35PM
(#2728286)
I am surprised by this point of view. It seems to me that extending the web-browser UI to display complex non-web-page documents is a bad idea, that it makes the user experience more complicated and mysterious.
Most of the time, the user-experience problem with PDFs on the web isn't that a separate app has to be started to read the PDF, but that the information in question is in a PDF at all, when a simple HTML page is generally safer and more useful.
By building things like Pdf.js and butter/popcorn.js and giving them away for other projects to use Mozilla gets to have the same impact and feedback loop, which helps to further their mission to improve the web.
Screenshots: http://imgur.com/a/hESRv
http://www.texample.net/tikz/examples/tag/animations/
Most of the time, the user-experience problem with PDFs on the web isn't that a separate app has to be started to read the PDF, but that the information in question is in a PDF at all, when a simple HTML page is generally safer and more useful.