Chrome PDF plugin - Javascript

[multidev]

Hello,
I would like to know if it is possible to send javascript commands (or
other language/technology) to the Chrome PDF plugin like it is
possible for Adobe plugin and listen to its events like page-change
(still possible for Adobe plugin with some script inside Adobe
folders). If not, will it be possible in the future? I am interested
both in web and Chrome app (or plugin) development. Thanks in advance.

[Lei Zhang]

The PDF plugin takes Javascript commands. Can you describe the
functionality you are looking for? It sounds like you want to set a
callback to get called every time the user navigates to a new page.

> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
>    http://groups.google.com/a/chromium.org/group/chromium-dev

[Lei Zhang]

For the record, there's a bug open for this. http://crbug.com/135146

On Wed, May 9, 2012 at 2:38 AM, multidev <insig...@libero.it> wrote:

[insig...@libero.it]

I wrote a comment to that, hope to hear some opinion on this thread.
Regards

- my comment - 
I think a PDF Viewer API would trigger a bit of innovation, like the creators 
of pdf.js, the BDF licensed PDF plugin for Firefox, say. That plugin is slower 
than the native Chrome PDF Viewer but it is open and liberally licensed. So the 
above mentioned API would be very useful for Chrome WebStore app developers.
I ask the following features are in the API (pdf.js is too slow for me) for 
Chrome:
- choose one page or two page view
- set positioning and viewport
- set dimensions
- choose full screen view
- setPage
- userSetPage / userJumpPage event handler
- link handling
- bookmark and outline handling
- user mouse events on page handling
- user selection handling
- user search
- cache of PDF file paths and names to manage a library (google drive sync?)
- annotations handling and creation
- [put here other features]

Other possibility: translate pdf.js into C++ and release with same license so 
to liberate PDF technology from GPL or proprietary licenses.
Other possibility: improve pdf.js speed (text seems to be the cause of 
slowness) so to stay under 80ms average for a page.
Otherwise Apple will remain the only platform where a proprietary PDF 
application can be marketed without buying expensive and unreasonable licenses 
(but only if Apples likes it and approves it on the AppStore).

>----Messaggio originale----
>Da: the...@chromium.org
>Data: 22-ago-2012 8.49
>A: <insig...@libero.it>
>Cc: "Chromium-dev"<chromi...@chromium.org>
>Ogg: Re: [chromium-dev] Chrome PDF plugin - Javascript