qpdfview team mailing list archive

[Pascual Lucero <pascualucero@xxxxxxxxx>]

Sorry, I would like to mention just another thing: As the guys from Google
Chrome have realized in their internal plugin, the only keyboard shorcuts
and buttons that are very important to exist and work are: Move Page
(Previous, Next), The Zoom buttons and the "Save as" command. Of course, in
the plugin of qpdfview as it looks, even more things could be possible (for
example, we could open a local file as a new tab in the same browser
window!!, given that qpdfview allows tabs), which is really nice!

In my pictures, if the problems with the toolbars in vertical mode are
solved (how they look), if all these buttons are enabled in the default
.conf in the plugin, then the problem is solved in a 50% (we see easily
buttons to perform these basic actions). The only thing missing is to make
sure the keyboard shortcuts for these basic functions will work.

Thanks for your attention ... :)

(If this can be done, I will post qpdfview propaganda in the sites I use to
visit, hehe ... could you imagine? A tabbed lightweight PDF viewer in Linux
that includes its own PDF plugin that works correctly in all main browsers
in Linux -Chrome/Chromium, Firefox and Opera-) !!!



On Tue, Jul 10, 2012 at 11:08 PM, Pascual Lucero <pascualucero@xxxxxxxxx>wrote:

>
> Hello,
>
>
> As I am not a programmer :(  (I would like to learn someday),
> unfortunately I cannot contribute writing code; however I am trying to do
> my best as a tester and making some suggestions.
>
> 1) I would like to ask first how to test the qtbrowserplugin ... it is the
> first time I heard about this concept, so my knowledge is almost null.
> Where should I put the qtbrowserplugin folder? Does it need a different
> compilation? It is possible to include it in the tar.gz and the .deb
> package of qpdfview (in other words, build the plugin at the same time as
> the program?)
>
> 2) I have tried to test mozplugger in different browsers and with
> different programs (from gv, to evince, to okular, to qpdfview and xpdf)
> and these are my conclusions that might improve a pdf plugin:
>
> - First, a great problem in all cases is related to keyboard shortcuts.
> Specially change pages is problematic. Of course, in Mozilla things work
> better than other browsers; in Opera, keyboard shortcuts don't work.
>
> - Second, a small problem is that in order to open the files, in Evince
> and Qpdfview, the way the program look when embedded in the browser depends
> on the user settings for the respective programs. However, this shouldn't
> be the right way. Why? Because in browsers, usually windows are maximized,
> so vertical space is important (and then usually, the default way to view
> the PDF is the "Fit to Page" way; on the other hand, horizontal space is
> available, so by default, bookmarks, thumbnails and toolbars can be set to
> the left, and be visible without problem. And using the settings to save as
> much vertical space as possible.
>
> In other words, the right way to configure it could be to set a separate
> .conf file for the plugin, different from the .conf file for the default
> program (other settings for memory could be set differently also; in other
> words, it is highly convenient to separate both).
>
> Look at the following screenshots, showing an idea on how a PDF could look
> like using a browser plugin:
>
> Image 1:
> http://imageshack.us/photo/my-images/860/201207102250311366x768s.png/
>
> Image 2:
> http://imageshack.us/photo/my-images/4/201207102251041366x768s.png/
>
> Of course, the ideal would be the first image, but with the toolbars'
> width corrected as in image 2. This also shows a problem with qpdfview: The
> edit and view toolbars are not correctly set for vertical use.
>
> That's all. Hopefully my comments could be useful as an improvement of the
> program and the plugin (as mentioned in the last paragraph, improving a
> plugin could actually help to improve how the program and the toolbars
> looks).
>
> And I will be grateful for indications on how to use the plugin, or better
> if this could be integrated into the development builds like other PDF
> programs (which include the plugins in the install package).
>
>
> Thanks for your attention. Have a good night!
>
>
>
>