luisggpina / open-pdf-presenter

Automatically exported from code.google.com/p/open-pdf-presenter
GNU General Public License v3.0
0 stars 0 forks source link

Feature request: support links #10

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Many PDF files have links that allow someone to freely navigate the 
presentation file (specially those created by latex beamer). Unfortunately, 
those links don't work inside open-pdf-presenter. It would be great no have 
those links working to navigate the presentation.

Original issue reported on code.google.com by mfrade.e...@gmail.com on 26 Oct 2012 at 2:28

GoogleCodeExporter commented 9 years ago
That is a good idea!

At this moment, open-pdf-presenter uses libpoppler to render the PDF to an 
image, therefore losing all the associated metadata. Issue7 is similar/related 
with this.

I'm marking this issue as an enhancement.

Original comment by zait...@gmail.com on 26 Oct 2012 at 9:16

GoogleCodeExporter commented 9 years ago
Hi,
do you know the project "Pdf Presenter Console" (
http://westhoffswelt.de/projects/pdf_presenter_console.html)?
It has the same goals of open-pdf-presenter and it also uses the
libpoppler. Maybe you could work together ...

I've tried both apps:

   - open-pdf-presenter:
      - it has a better looking interface
      - it has notes
      - the "S" button only works well if the outside monitor/projector is
      configured to be on the left or right side of the main monitor; if it is
      configured above or bellow it doesn't work.
      - consumes lots of memory - for a presentation with 107 pages creates
      3 processes of 1.5 GB in RAM each!!
   - Pdf Presenter Console:
      - links inside PDF work,
      - doesn't have notes
      - it works well for external monitors configured in the right, left,
      above and bellow of the main monitor
      - consumes less memory - for the same presentation with 107 pages
      creates 2 processes of 330 MB in RAM each

Regards,
Miguel Frade

Original comment by mfrade.e...@gmail.com on 29 Oct 2012 at 9:28

GoogleCodeExporter commented 9 years ago
Hi,

I did not know about pdf presenter console also using libpoppler. I definitely 
have to check that out!

Yes, there are some problems on open-pdf-presenter computing the size of the 
slides. These are worsened when you switch to OSX. I am working on that at the 
moment.

About the memory footprint: Open-pdf-presenter main goals are (1) beautifully 
rendered slides and (2) fast, as in immediate, slide switch. To that purpose, 
open-pdf-presenter uses libpoppler to render slides exactly to the size of the 
main screen and keeps all slides in memory after rendered. This increases the 
memory footprint proportionally with the resolution of the main screen and the 
total number of slides.

Even though 1.5GB seem like a huge memory footprint, I am not willing to change 
open-pdf-presenter to use less memory and compromise either goal 1, 2, or both. 
At its current state, open-pdf-presenter does a great job showing presentations 
on computers with low computational power, such as atom netbooks. It will 
switch slides really fast and I am not willing to compromise that. How fast is 
pdf presenter console switching slides on an atom?

Besides, realistically speaking, most presentations are shown on projectors 
that are not able to handle resolutions greater than 1024x768, which keeps the 
memory footprint down.

Thanks,
Luís Pina

Original comment by zait...@gmail.com on 29 Oct 2012 at 2:18