pax_global_header00006660000000000000000000000064130513412760014514gustar00rootroot0000000000000052 comment=908a732aeb1c6094c04a7539095352a3349998bc pdfpc-4.0.6/000077500000000000000000000000001305134127600126175ustar00rootroot00000000000000pdfpc-4.0.6/.gitignore000066400000000000000000000001001305134127600145760ustar00rootroot00000000000000.history .*.swp build/ src/paths.vala man/pdfpc.1 man/pdfpcrc.5 pdfpc-4.0.6/.gitmodules000066400000000000000000000000001305134127600147620ustar00rootroot00000000000000pdfpc-4.0.6/CHANGELOG.txt000066400000000000000000000145151305134127600146550ustar00rootroot00000000000000=============== pdfpc Changelog =============== Version 4.0.6 ============= *Released: February 2017* - New command line option: -P/--page jump to a specific page after startup - HiDPI support. Respect GDK Hints about HiDPI screens. This resolves an issue, where the slides where rendered blurry - Escape special characters in text nodes. This resolves an issue where all text notes got lost if special characters where used. - Allow more permanent config options per pdf/globally - Resolve unfullscreening/out of screen bugs in low resolution or HiDPI scenarios - Better Wayland support - Overview slides contain the actual slide number to find specific slides faster - Documentation improvements Version 4.0.5 ============= *Released: January 2017* - Persistent PNG cache for faster startup - Layout fix: - CSS fix for older GTK versions - Fixed prev-slide semantics - Next-slide view shows full slide in case of overlays - Fix highlighting in overview mode (removed pixman error in logs) - Enforced timer/status bar height. this area no longer "jumps" if icons are displayed - Overview mode: click on slide goes to full slide (in case of overlays), SHIFT + click goes to the first slide - Fixed history-back semantics - Split man pages in pdfpc(1) for the program and pdfpcrc(5) for config file options Version 4.0.4 ============= *Released: November 2016* - auto-workaround for notes and auto-grouping bug - fix CSS for newer GTK versions Version 4.0.3 ============= *Released: October 2016* - Compiles with vala 0.32 - pdfpc can now show some highlighting pointer - Adds D-Bus Server for controlling pdfpc - Minor Improvements: - Search pdfpcrc files in XDG compliant directories - Key shortcut to jump to the last overlay - Made progress bar in movie playback optional Version 4.0.2 ============= *Released: February 2016* - Adds a option, -g, to disable auto-grouping of overlay slides - Removes some command line options in favor of a configuration file, pdfpcrc - Bug fixes: - Movies with an end-time now correctly loop - Fixes cut-off text in a number of cases - Fixes issues where the screens might not move to the correct monitor - Other small fixes Version 4.0.1 ============= *Released: November 2015* - Keybindings for changing font size of the notes view - Hyperlinks to web pages are now opened in the web browser - Instead of count downs, the current time can be displayed - start/stop, noaudio attributes for movies - The user can now configure the presenter view layout according to their needs - Movie support can be disabled to allow compilation on Mac OS X / Windows (via cmake -DMOVIES=OFF) - Bug fixes Version 4.0 ============= *Released: June 2015* - *Major* Moved to GTK+3 - New Maintainer - Movie playback, based on gstreamer 1.0 - Support LaTeX beamer slides with notes - Option to sepcify size in windowed mode - Various bug fixed and documentation improvements Version 3.1.1 ============= *Released: July 2012* - Bug fix for released C sources Version 3.1 =========== *Released: June 2012* - Revamped overview mode, with better keyboard navigation support and better visual appearance (thanks to rschroll) - Support for configuration files. Now all keybindings are configurable - Improved layout management (thanks to rschroll) - (Hopefully) Improved handling of fullscreen modes Version 3.0 =========== *Released: May 2012* - Renamed to pdfpc (forked from Pdf Presenter Console) - Support for new poppler version - Support for (textual) notes - Support for overlays - Overview mode - Jump to slides by inputting the slide number - Movement in 10-slide blocks allowed using shift - Two additional timer modes: countup and end time of presentation - Pause timer (useful for rehearsal talks) - Support for mouse wheel (thanks to mikerofone) and bluetooth headset controls (thanks to NerdyProjects) - Freezing and blacking out of presentation view - Presenter view starts on primary screen - Definition of "end slide" - Navigable history of jumps =============================== Pdf Presenter Console Changelog =============================== Version 2.0 =========== *Released: 16. Jan 2010* - Complete rewrite of rendering system to allow more sophisticated actions. - Changed license of the project from GPLv3 to GPLv2+ because of incompatibilities with Poppler. (Thanks to Jakub Wilk and Barak A. Pearlmutter for pointing out this out). - Implemented: Usage of left-/right mousebuttons for slide navigation. - Implemented: Handling of navigational links inside of PDF files. - Implemented: Abstraction to cache prerendered slides. - Implemented: Compressed cache for prerendered slides. - Implemented: Alternative way of executing the prerendering process to allow for smoother navigation while slides are generated. - Implemented: Means to switch displays in single monitor mode as well as dual monitor mode - Implemented: Disabled timer if a duration of 0 is provided - Fixed: Build problems on Fedora 13 due to changed linking procedure - Fixed: Slightly changed image data formats due to update of Gtk to Version 2.22 or higher. - Implemented: Removed usage of deprecated Gdk.GC in favor of Cairo. Version 1.1.1 ============= - Fixed: Compile error with newer vala versions due to wrong property visibility - Fixed: Typo in help text Version 1.1 =========== - Implemented: Controllable interface for cleaner controller code. - Fixed: Install target is now executable. - Fixed: Warnings shown in one-screen-presentation-mode, due to non existant process indicator. - Implemented: Presentation timer as its own GTK Widget - Implemented: Support for negative timer values (aka overtime) - Implemented: Different Timer colors for normal time, the last x minutes and overtime - Implemented: Made last-minutes time configurable - Fixed: Library paths were not used correctly for compilation - Implemented: Fullscreen window as own Gtk class - Fixed: Problem which caused the windows not be displayed on the correct displays using the Xfce4 Xfwm window mananger. - Implemented: Command line option to set the size of the current slide in the presenter screen - Implemented: A few more common key bindings - Implemented: Hide cursor after 5 seconds timeout Version 1.0 =========== - Initial release pdfpc-4.0.6/CMakeLists.txt000066400000000000000000000010211305134127600153510ustar00rootroot00000000000000project("pdfpc" C) cmake_minimum_required(VERSION 2.6) list(APPEND CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/cmake/vala) find_package(Vala "0.26" REQUIRED) include(${VALA_USE_FILE}) set(SYSCONFDIR "${CMAKE_INSTALL_PREFIX}/etc" CACHE FILEPATH "sysconfdir") set(MANDIR "share/man" CACHE FILEPATH "mandir") set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin) option(MOVIES "Compile support for movie playback (requires gdk-x11)" ON) add_subdirectory(src) add_subdirectory(icons) add_subdirectory(man) add_subdirectory(rc) pdfpc-4.0.6/LICENSE.txt000066400000000000000000000432541305134127600144520ustar00rootroot00000000000000 GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. pdfpc-4.0.6/README.rst000066400000000000000000000125601305134127600143120ustar00rootroot00000000000000===== pdfpc ===== About ===== pdfpc is a GTK based presentation viewer application which uses Keynote like multi-monitor output to provide meta information to the speaker during the presentation. It is able to show a normal presentation window on one screen, while showing a more sophisticated overview on the other one providing information like a picture of the next slide, as well as the left over time till the end of the presentation. The input files processed by pdfpc are PDF documents, which can be created using nearly any of today's presentation software. More information, including screenshots and a demo presentation, can be found at https://pdfpc.github.io/ Installation ============ - On Ubuntu or Debian systems:: sudo apt-get install pdf-presenter-console - On Fedora:: sudo dnf install pdfpc - `Compiling from source <#compile-and-install>`_ Sample presentations -------------------- - `Simple demo `_ - `Embedded movies `_ Try it out:: pdfpc pdfpc-demo.pdf Compile and install =================== Requirements ------------ In order to compile and run pdfpc the following requirements need to be met: - CMake Version >=2.6 - vala >= 0.26 - GTK+ >= 3.10 - gee 0.8 - poppler with glib bindings - gstreamer 1.0 - pangocairo On Ubuntu systems, you can install these dependencies with:: sudo apt-get install cmake valac libgee-0.8-dev libpoppler-glib-dev libgtk-3-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev and you should consider installing all the available gstreamer codecs:: sudo apt-get install gstreamer1.0-* Compiling from source tarballs ------------------------------ You can download the latest stable release of pdfpc in the release section of github (https://github.com/pdfpc/pdfpc/releases). Uncompress the tarball (we use v4.0.2 as an example here):: tar xvf pdfpc-4.0.2.tar.gz Change to the extracted directory:: cd pdfpc-4.0.2 Compile and install:: mkdir build/ cd build/ cmake .. make sudo make install If there are no errors in the process, you just installed pdfpc on your system. Congratulations! If there were errors, they are probably due to missing dependencies. Please check that you have all the necessary libraries (in some distributions you may have to install *-devel* packages). Note: You may alter the final installation prefix in the cmake call. By default the pdfpc files will be installed under */usr/local/*. If you want to change that, for example to be installed under */usr/*, with config files under */etc/* you may specify another installation prefix as follows:: cmake -DCMAKE_INSTALL_PREFIX="/usr" -DSYSCONFDIR=/etc .. By default, pdfpc includes support for movie playback. This requires several gstreamer dependencies as well as gdk-x11. The requirement for these packages can be removed by compiling without support for movie playback by passing *-DMOVIES=OFF* to the cmake command. Compiling on Windows -------------------- On issue #106 there is a short tutorial on how to compile pdfpc on Windows. First a cygwin installation with the following dependencies is needed: - cmake - automake - make - gcc - gcc-c++ - libstdc++-4.8-dev - x11 For pdfpc the following compile time dependencies are necessary: - vala - gtk - gee - libpoppler - gstreamer - libgstinterfaces1.0-devel (has gstreamer.audio included) Compiling in Mac OS X (Yosemite) -------------------------------- First, install homebrew as described on their webpage, then install the dependencies:: brew install cmake vala gtk+3 libgee poppler librsvg libcroco You need to call cmake with:: cmake -DMOVIES=off since Yosemite has no X11 implementation, and the movie playback uses X11 features. Compiling Trouble Shooting -------------------------- Some distributions do not have a *valac* executable. Instead they ship with a version suffix like *valac-0.28*. If cmake can not find your compiler you can try running cmake with:: cmake -DVALA_EXECUTABLE:NAMES=valac-0.28 .. Usage ===== Now download some [sample presentations](#sample-presentations) and load them up:: pdfpc pdfpc-demo.pdf FAQ === Embedded video playback is not working. --------------------------------------- You likely have a ``gstreamer`` codec issue. Try loading the video file you want to play with the following command: ``gst-launch-1.0 filesrc location= ! decodebin ! autovideosink`` If the video plays, go ahead and `submit an issue `_. Otherwise, the command will likely output some good hints for why gstreamer cannot decode the video. Windows do not appear on the correct screen. --------------------------------------------------- For tiling window managers, the movement and fullscreening of the windows do not work reliable. It is therefore important to tell your WM to force floating the pdfpc windows. If you are using i3-wm add this to your config file:: for_window [ title="^pdfpc - present" ] border none floating enable Acknowledgements ================ pdfpc has been developed by Jakob Westhoff, David Vilar, Robert Schroll, Andreas Bilke, Andy Barry, Phillip Berndt and others. It was previously available at https://github.com/davvil/pdfpc pdfpc is a fork of Pdf Presenter Console by Jakob Westhoff, available at https://github.com/jakobwesthoff/Pdf-Presenter-Console pdfpc-4.0.6/cmake/000077500000000000000000000000001305134127600136775ustar00rootroot00000000000000pdfpc-4.0.6/cmake/vala/000077500000000000000000000000001305134127600146225ustar00rootroot00000000000000pdfpc-4.0.6/cmake/vala/FindVala.cmake000066400000000000000000000061131305134127600173110ustar00rootroot00000000000000## # Find module for the Vala compiler (valac) # # This module determines wheter a Vala compiler is installed on the current # system and where its executable is. # # Call the module using "find_package(Vala) from within your CMakeLists.txt. # # The following variables will be set after an invocation: # # VALA_FOUND Whether the vala compiler has been found or not # VALA_EXECUTABLE Full path to the valac executable if it has been found # VALA_VERSION Version number of the available valac # VALA_USE_FILE Include this file to define the vala_precompile function ## ## # Copyright 2009-2010 Jakob Westhoff. All rights reserved. # Copyright 2010-2011 Daniel Pfeifer # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions are met: # # 1. Redistributions of source code must retain the above copyright notice, # this list of conditions and the following disclaimer. # # 2. Redistributions in binary form must reproduce the above copyright notice, # this list of conditions and the following disclaimer in the documentation # and/or other materials provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY JAKOB WESTHOFF ``AS IS'' AND ANY EXPRESS OR # IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO # EVENT SHALL JAKOB WESTHOFF OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, # INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT # LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR # PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF # LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE # OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # # The views and conclusions contained in the software and documentation are those # of the authors and should not be interpreted as representing official policies, # either expressed or implied, of Jakob Westhoff ## # Search for the valac executable in the usual system paths # Some distributions rename the valac to contain the major.minor in the binary name find_program(VALA_EXECUTABLE NAMES valac valac-0.20 valac-0.18 valac-0.16 valac-0.14 valac-0.12 valac-0.10) mark_as_advanced(VALA_EXECUTABLE) # Determine the valac version if(VALA_EXECUTABLE) execute_process(COMMAND ${VALA_EXECUTABLE} "--version" OUTPUT_VARIABLE VALA_VERSION OUTPUT_STRIP_TRAILING_WHITESPACE) string(REPLACE "Vala " "" VALA_VERSION "${VALA_VERSION}") endif(VALA_EXECUTABLE) # Handle the QUIETLY and REQUIRED arguments, which may be given to the find call. # Furthermore set VALA_FOUND to TRUE if Vala has been found (aka. # VALA_EXECUTABLE is set) include(FindPackageHandleStandardArgs) find_package_handle_standard_args(Vala REQUIRED_VARS VALA_EXECUTABLE VERSION_VAR VALA_VERSION) set(VALA_USE_FILE "${CMAKE_CURRENT_LIST_DIR}/UseVala.cmake") pdfpc-4.0.6/cmake/vala/README.rst000066400000000000000000000125121305134127600163120ustar00rootroot00000000000000========== Vala CMake ========== :Author: Jakob Westhoff :Version: Draft Overview ======== Vala CMake is a collection of macros for the CMake_ build system to allow the creation and management of projects developed using the Vala_ programming language or its "Genie" flavor (less tested). Installation ============ To use the Vala macros in your own project you need to copy the macro files to an arbitrary folder in your projects directory and reference them in your ``CMakeLists.txt`` file. Assuming the macros are stored under ``cmake/vala`` in your projects folder you need to add the following information to your base ``CMakeLists.txt``:: list(APPEND CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/cmake/vala ) After the new module path as been added you can simply include the provided modules or use the provided find routines. Finding Vala ============ The find module for vala works like any other Find module in CMake. You can use it by simply calling the usual ``find_package`` function. Default parameters like ``REQUIRED`` and ``QUIETLY`` are supported. :: find_package(Vala REQUIRED) After a successful call to the find_package function the following variables will be set: VALA_FOUND Whether the vala compiler has been found or not VALA_EXECUTABLE Full path to the valac executable if it has been found VALA_VERSION Version number of the available valac Precompiling Vala sources ========================= CMake is mainly supposed to handle c or c++ based projects. Luckily every vala program is translated into plain c code using the vala compiler, followed by normal compilation of the generated c program using gcc. The macro ``vala_precompile`` uses that fact to create c files from your .vala sources for further CMake processing. The first parameter provided is a variable, which will be filled with a list of c files outputted by the vala compiler. This list can than be used in conjunction with functions like ``add_executable`` or others to create the necessary compile rules with CMake. The initial variable is followed by a list of .vala files to be compiled. Please take care to add every vala file belonging to the currently compiled project or library as Vala will otherwise not be able to resolve all dependencies. The following sections may be specified afterwards to provide certain options to the vala compiler: PACKAGES A list of vala packages/libraries to be used during the compile cycle. The package names are exactly the same, as they would be passed to the valac "--pkg=" option. OPTIONS A list of optional options to be passed to the valac executable. This can be used to pass "--thread" for example to enable multi-threading support. DIRECTORY Specify the directory where the output source files will be stored. If ommitted, the source files will be stored in CMAKE_CURRENT_BINARY_DIR. CUSTOM_VAPIS A list of custom vapi files to be included for compilation. This can be useful to include freshly created vala libraries without having to install them in the system. GENERATE_VAPI Pass all the needed flags to the compiler to create an internal vapi for the compiled library. The provided name will be used for this and a .vapi file will be created. GENERATE_HEADER Let the compiler generate a header file for the compiled code. There will be a header file as well as an internal header file being generated called .h and _internal.h The following call is a simple example to the vala_precompile macro showing an example to every of the optional sections:: vala_precompile(VALA_C source1.vala source2.vala source3.vala PACKAGES gtk+-2.0 gio-1.0 posix OPTIONS --thread CUSTOM_VAPIS some_vapi.vapi GENERATE_VAPI myvapi GENERATE_HEADER myheader ) Most important is the variable VALA_C which will contain all the generated c file names after the call. The easiest way to use this information is to tell CMake to create an executable out of it. :: add_executable(myexecutable ${VALA_C}) Building a debug build ====================== In the section OPTIONS add the '-g' option. This will instruct the Vala compiler to include the Vala source code line information in the compiled binary. Add the '--save-temps' option to keep the temporary C source files. When running cmake add '-DCMAKE_BUILD_TYPE=Debug' option. After building the program, it can then be debugged with ``gdb`` or ``nemiver``. Further reading =============== The `Pdf Presenter Console`__ , which is a vala based project of mine, makes heavy usage of the here described macros. To look at a real world example of these macros the mentioned project is the right place to take a look. The svn trunk of it can be found at:: svn://pureenergy.cc/pdf_presenter_console/trunk __ http://westhoffswelt.de/projects/pdf_presenter_console.html Acknowledgments =============== Thanks go out to Florian Sowade, a fellow local PHP-Usergroupie, who helped me a lot with the initial version of this macros and always answered my mostly dumb CMake questions. .. _CMake: http://cmake.org .. _Vala: http://live.gnome.org/Vala .. _Genie: http://live.gnome.org/Genie .. Local Variables: mode: rst fill-column: 79 End: vim: et syn=rst tw=79 pdfpc-4.0.6/cmake/vala/UseVala.cmake000066400000000000000000000163711305134127600171740ustar00rootroot00000000000000## # Compile vala files to their c equivalents for further processing. # # The "vala_precompile" function takes care of calling the valac executable on # the given source to produce c files which can then be processed further using # default cmake functions. # # The first parameter provided is a variable, which will be filled with a list # of c files outputted by the vala compiler. This list can than be used in # conjuction with functions like "add_executable" or others to create the # neccessary compile rules with CMake. # # The following sections may be specified afterwards to provide certain options # to the vala compiler: # # SOURCES # A list of .vala files to be compiled. Please take care to add every vala # file belonging to the currently compiled project or library as Vala will # otherwise not be able to resolve all dependencies. # # PACKAGES # A list of vala packages/libraries to be used during the compile cycle. The # package names are exactly the same, as they would be passed to the valac # "--pkg=" option. # # OPTIONS # A list of optional options to be passed to the valac executable. This can be # used to pass "--thread" for example to enable multi-threading support. # # DEFINITIONS # A list of symbols to be used for conditional compilation. They are the same # as they would be passed using the valac "--define=" option. # # CUSTOM_VAPIS # A list of custom vapi files to be included for compilation. This can be # useful to include freshly created vala libraries without having to install # them in the system. # # GENERATE_VAPI # Pass all the needed flags to the compiler to create a vapi for # the compiled library. The provided name will be used for this and a # .vapi file will be created. # # GENERATE_HEADER # Let the compiler generate a header file for the compiled code. There will # be a header file as well as an internal header file being generated called # .h and _internal.h # # The following call is a simple example to the vala_precompile macro showing # an example to every of the optional sections: # # find_package(Vala "0.12" REQUIRED) # include(${VALA_USE_FILE}) # # vala_precompile(VALA_C # SOURCES # source1.vala # source2.vala # source3.vala # PACKAGES # gtk+-2.0 # gio-1.0 # posix # DIRECTORY # gen # OPTIONS # --thread # CUSTOM_VAPIS # some_vapi.vapi # GENERATE_VAPI # myvapi # GENERATE_HEADER # myheader # ) # # Most important is the variable VALA_C which will contain all the generated c # file names after the call. ## ## # Copyright 2009-2010 Jakob Westhoff. All rights reserved. # Copyright 2010-2011 Daniel Pfeifer # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions are met: # # 1. Redistributions of source code must retain the above copyright notice, # this list of conditions and the following disclaimer. # # 2. Redistributions in binary form must reproduce the above copyright notice, # this list of conditions and the following disclaimer in the documentation # and/or other materials provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY JAKOB WESTHOFF ``AS IS'' AND ANY EXPRESS OR # IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO # EVENT SHALL JAKOB WESTHOFF OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, # INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT # LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR # PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF # LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE # OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # # The views and conclusions contained in the software and documentation are those # of the authors and should not be interpreted as representing official policies, # either expressed or implied, of Jakob Westhoff ## include(CMakeParseArguments) function(vala_precompile output) cmake_parse_arguments(ARGS "" "DIRECTORY;GENERATE_HEADER;GENERATE_VAPI" "SOURCES;PACKAGES;OPTIONS;DEFINITIONS;CUSTOM_VAPIS" ${ARGN}) if(ARGS_DIRECTORY) get_filename_component(DIRECTORY ${ARGS_DIRECTORY} ABSOLUTE) else(ARGS_DIRECTORY) set(DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}) endif(ARGS_DIRECTORY) include_directories(${DIRECTORY}) set(vala_pkg_opts "") foreach(pkg ${ARGS_PACKAGES}) list(APPEND vala_pkg_opts "--pkg=${pkg}") endforeach(pkg ${ARGS_PACKAGES}) set(vala_define_opts "") foreach(def ${ARGS_DEFINTIONS}) list(APPEND vala_define_opts "--define=${def}") endforeach(def ${ARGS_DEFINTIONS}) set(in_files "") set(out_files "") foreach(src ${ARGS_SOURCES} ${ARGS_UNPARSED_ARGUMENTS}) list(APPEND in_files "${CMAKE_CURRENT_SOURCE_DIR}/${src}") string(REPLACE ".vala" ".c" src ${src}) string(REPLACE ".gs" ".c" src ${src}) set(out_file "${DIRECTORY}/${src}") list(APPEND out_files "${DIRECTORY}/${src}") endforeach(src ${ARGS_SOURCES} ${ARGS_UNPARSED_ARGUMENTS}) set(custom_vapi_arguments "") if(ARGS_CUSTOM_VAPIS) foreach(vapi ${ARGS_CUSTOM_VAPIS}) if(${vapi} MATCHES ${CMAKE_SOURCE_DIR} OR ${vapi} MATCHES ${CMAKE_BINARY_DIR}) list(APPEND custom_vapi_arguments ${vapi}) else (${vapi} MATCHES ${CMAKE_SOURCE_DIR} OR ${vapi} MATCHES ${CMAKE_BINARY_DIR}) list(APPEND custom_vapi_arguments ${CMAKE_CURRENT_SOURCE_DIR}/${vapi}) endif(${vapi} MATCHES ${CMAKE_SOURCE_DIR} OR ${vapi} MATCHES ${CMAKE_BINARY_DIR}) endforeach(vapi ${ARGS_CUSTOM_VAPIS}) endif(ARGS_CUSTOM_VAPIS) set(vapi_arguments "") if(ARGS_GENERATE_VAPI) list(APPEND out_files "${DIRECTORY}/${ARGS_GENERATE_VAPI}.vapi") set(vapi_arguments "--vapi=${ARGS_GENERATE_VAPI}.vapi") # Header and internal header is needed to generate internal vapi if (NOT ARGS_GENERATE_HEADER) set(ARGS_GENERATE_HEADER ${ARGS_GENERATE_VAPI}) endif(NOT ARGS_GENERATE_HEADER) endif(ARGS_GENERATE_VAPI) set(header_arguments "") if(ARGS_GENERATE_HEADER) list(APPEND out_files "${DIRECTORY}/${ARGS_GENERATE_HEADER}.h") list(APPEND out_files "${DIRECTORY}/${ARGS_GENERATE_HEADER}_internal.h") list(APPEND header_arguments "--header=${DIRECTORY}/${ARGS_GENERATE_HEADER}.h") list(APPEND header_arguments "--internal-header=${DIRECTORY}/${ARGS_GENERATE_HEADER}_internal.h") endif(ARGS_GENERATE_HEADER) add_custom_command(OUTPUT ${out_files} COMMAND ${VALA_EXECUTABLE} ARGS "-C" ${header_arguments} ${vapi_arguments} "-b" ${CMAKE_CURRENT_SOURCE_DIR} "-d" ${DIRECTORY} ${vala_pkg_opts} ${vala_define_opts} ${ARGS_OPTIONS} ${in_files} ${custom_vapi_arguments} DEPENDS ${in_files} ${ARGS_CUSTOM_VAPIS} ) set(${output} ${out_files} PARENT_SCOPE) endfunction(vala_precompile) pdfpc-4.0.6/icons/000077500000000000000000000000001305134127600137325ustar00rootroot00000000000000pdfpc-4.0.6/icons/CMakeLists.txt000066400000000000000000000001361305134127600164720ustar00rootroot00000000000000install(FILES blank.svg snow.svg pause.svg DESTINATION share/pixmaps/pdfpc ) pdfpc-4.0.6/icons/README.icons000066400000000000000000000002241305134127600157220ustar00rootroot00000000000000All icons by jensbob (https://github.com/jensbob/pdfpc) snow.svg based on icon by bocian (http://openclipart.org/detail/30829/snowflake-by-bocian) pdfpc-4.0.6/icons/blank.svg000066400000000000000000000053561305134127600155530ustar00rootroot00000000000000 image/svg+xml image/svg+xml pdfpc-4.0.6/icons/pause.svg000066400000000000000000000047561305134127600156040ustar00rootroot00000000000000 image/svg+xml pdfpc-4.0.6/icons/snow.svg000066400000000000000000000122551305134127600154460ustar00rootroot00000000000000 image/svg+xml pdfpc-4.0.6/man/000077500000000000000000000000001305134127600133725ustar00rootroot00000000000000pdfpc-4.0.6/man/CMakeLists.txt000066400000000000000000000004601305134127600161320ustar00rootroot00000000000000CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/pdfpc.in ${CMAKE_CURRENT_SOURCE_DIR}/pdfpc.1) CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/pdfpcrc.in ${CMAKE_CURRENT_SOURCE_DIR}/pdfpcrc.5) install(FILES pdfpc.1 DESTINATION ${MANDIR}/man1 ) install(FILES pdfpcrc.5 DESTINATION ${MANDIR}/man5 ) pdfpc-4.0.6/man/pdfpc.in000066400000000000000000000363031305134127600150230ustar00rootroot00000000000000.TH PDFPC 1 .if !dURL \{\ .de URL \\$2 \(laURL: \\$1 \(ra\\$3 .. .\} .if \n[.g] .mso www.tmac .SH NAME pdfpc \- PDF presenter console with multi-monitor support .SH SYNOPSIS .B pdfpc [options] PDF-file .SH DESCRIPTION .PP pdfpc is a GTK-based presentation viewer which uses Keynote-like multi-monitor output to provide meta information to the speaker during the presentation. It is able to show a normal presentation window on one screen while showing a more sophisticated overview on the other one, providing information like a picture of the next slide, as well as the time left in the presentation. pdfpc processes PDF documents, which can be created using nearly all modern presentation software. .PP By default the presenter view appears in the primary monitor and the presentation view in the second monitor (provided you have two monitors). .SH OPTIONS .TP .BI "\-c, \-\-disable\-cache" Disable caching and pre-rendering of slides to save memory at the cost of speed. .TP .BI "\-C, \-\-time\-of\-day Display the time of the day .TP .BI "\-d, \-\-duration"=N Duration in minutes of the presentation used for timer display. If not given or if a value of 0 is specified, the clock just measures the time in the presentation. .TP .BI "\-e, \-\-end\-time"=T End time of the presentation. (Format: HH:MM (24h)) .TP .BI "\-g, \-\-disable\-auto\-grouping" Disable auto detection of overlay groups. (Default: enabled) .TP .BI "\-h, \-\-help" Shows the help .TP .BI "\-l, \-\-last\-minutes"=N Time in minutes, from which on the timer changes its color. (Default: 5 minutes) .TP .BI "\-L, \-\-list\-actions" List actions supported in the config file(s) .TP .BI "\-n, \-\-notes"=P Position of notes on the PDF page. Position can be either left, right, top or bottom. Disable slide auto-grouping (Default: none) .TP .BI "\-p, \-\-persist\-cache" Persist the PNG cache on disk for faster startup. .TP .BI "\-P, \-\-page" Goto a specific page directly after startup. In case of overlays, the first slide will be displayed. .TP .BI "\-s, \-\-switch\-screens" Switch the presentation and the presenter screen. .TP .BI "\-S, \-\-single\-screen" Force to use only one screen .TP .BI "\-t, \-\-start\-time"=T Start time of the presentation to be used as a countdown. (Format: HH:MM (24h)) .TP .BI "\-w, \-\-windowed" Run in windowed mode .TP .BI "\-z, \-\-disable\-compression" Disable the compression of slide images to trade memory consumption for speed. (Avg. factor 30) .TP .BI "\-Z, \-\-size" Size of the presentation window in width:height format (forces windowed mode) .PP Some previous command line options (like black-on-end) where moved to permanent config file options. See .B pdfpcrc(5) for further details. .SH KEYBINDINGS These are the default keybindings for pdfpc: .TP .B Right cursor key / Page down / Return / Space / Left mouse button Go forward one slide .TP .B Shift + Right cursor key / Page down / Return / Space / Left mouse button / Mouse wheel down or right Go forward 10 slides .TP .B Down cursor key Go forward one user slide (see .B Overlays below) .TP .B Left cursor key / Page up / Right mouse button / Mouse wheel up or left Go back one slide .TP .B Shift + Left cursor key / Page up / Right mouse button Go back 10 slides .TP .B Up cursor key Go back one "user slide" (see .B Overlays below) .TP .B Home Go to the first slide .TP .B End Go to the last slide .TP .B Backspace Go back in history. Note that history is defined by "jump" commands, not by normal slide movement. .TP .B Tab / Middle mouse button Overview mode .TP .B g Input a slide number to jump to .TP .B Plus / Equal / KP_Add / Bracket Left Increase Notes Font Size .TP .B Minus / KP_Substract / Bracket Right Decrease Notes Font Size .TP .B 8 Toggle Pointer Mode .TP .B 7 Decrease pointer size .TP .B 9 Increase pointer size .TP .B Escape / q Exit pdfpc .TP .B b Turn off the presentation view (i.e. fill it with a black color) .TP .B n Edit note for current slide .TP .B f Freeze the current presentation display (the presenter display is still fully active) .TP .B o Toggle the overlay flag for one particular slide (see Overlays below) .TP .B p Pause timer .TP .B r Reset presentation (reset timer and go back to first slide) .TP .B e Define end slide .P Within overview mode the following key bindings are used .TP .B Return / Left mouse button Goto currently selected page (last page of overlay) .TP .B Shift + Return / Shift + Left mouse button Goto currently selected page (first page of overlay) .TP .B Cursor left / Page up Select previous slide .TP .B Cursor right / Page down Select next slide .P See .B pdfpcrc(5) if you want to customize the keybindings. .SH FEATURES .SS Caching / Pre-rendering .PP To allow fast changes between the different slides of the presentation the PDF pages are pre-rendered to memory. The progress bar on the bottom of the presenter screen indicates how many percent of the slides have been pre-rendered already. During the initial rendering phase this will slow down slide changes, as most CPU power is used for the rendering process in the background. After the cache is fully primed however the changing of slides should be much faster, as with normal PDF viewers. .PP As the pre-rendering takes a lot of memory it can be disabled using the \-\-disable\-cache switch at the cost of speed. .PP It it also possible to store the pre-rendered slides on the disk (see \-\-persist-cache). This speeds up the start of the program if the slide-set is used for a second time. .SS Cache compression .PP The pre-rendered and cached slides can be compressed in memory to save up some memory. Without compression a set of about 100 PDF pages can easily grow up to about 1.5 GB size. Netbooks with only 1 GB of memory would swap themselves to death if pre-rendering is enabled in such a situation. The compression is enabled by default as it does not harm rendering speed in a noticeable way on most systems. It does however slow down pre-rendering by about a factor of two. If you have got enough memory and want to ensure the fastest possible pre-rendering you can disable slide compression by using the \-z switch. But be warned using the uncompressed pre-rendering storage will use about 30 times the memory the new compressed storage utilizes (e.g. 50 MB will become about 1.5 GB). .SS Timer .PP If a duration is given (\-d option), the timer will show a countdown with the given parameters. If no duration is specified (or if a value of 0 is given to the \-d option), the timer will show how much time has been spent. The duration is stored automatically, so you do not need to repeat it for every invocation. .PP The timer is started if you are navigating away from the first page for the first time. This feature is quite useful as you may want to show the title page of your presentation while people are still entering the room and the presentation has not really begun yet. If you want to start over you can use the \[aq]r\[aq] key which will make the presenter reset the timer. .PP If a duration is given, at the moment the timer reaches the defined last-minutes value it will change color to indicate your talk is nearing its end. As soon as the timer reaches the zero mark (00:00:00) it will turn red and count further down showing a negative time, to provide information on how many minutes you are overtime. .SS Notes .PP Textual notes can be displayed for each slide. While in the presentation, pressing \[aq]n\[aq] will allow you to take notes for the screen. To go out of editing mode, press the Escape key. Note that while editing a note the keybindings stop working, i.e. you are not able to change slides. .PP The notes are stored in the given file in a plain text format, easy to edit also from outside the program. See the section about the pdfpc format below. .SS Overview mode .PP Pressing tab you can enter the overview mode, where miniatures for the slides are shown. You can select one slide to jump to with the mouse or with the arrow keys. You can also define overlays and the end slide (see next sections) in this mode. .SS Overlays .PP Many slide preparation systems allow for overlays, i.e. sets of slides that are logically grouped together as a single, changing slide. Examples include enumerations where the single items are displayed one after another or rough "animations", where parts of a picture change from slide to slide. Pdfpc includes facilities for dealing with such overlays. .PP In this description, we will differentiate between slides (i.e. pages in the PDF document) and "user slides", that are the logical slides. The standard forward movement command (page down, enter, etc.) moves through one slide at a time, as expected. That means that every step in the overlay is traversed. The backward movement command works differently depending if the current and previous slides are part of an overlay: .IP \[bu] 2 If the current slide is part of an overlay we just jump to the previous slide. That means that we are in the middle of an overlay we can jump forward and backward through the single steps of it .IP \[bu] 2 If the current slide is not part of an overlay (or if it is the first one), but the previous slides are, we jump to the previous user slide. This means that when going back in the presentation you do not have to go through every step of the overlay, pdfpc just shows the first slide of the each overlay. As you normally only go back in a presentation when looking for a concrete slide, this is more convenient. .PP The up and down cursor keys work on a user slide basis. You can use them to skip the rest of an overlay or to jump to the previous user slide, ignoring the state of the current slide. .PP When going through an overlay, two additional previews may be activated in the presenter view, just below the main view, showing the next and the previous slide in an overlay. .PP Pdfpc tries to find these overlays automatically by looking into the page labels in the PDF file. For LaTeX this works correctly at least with the beamer class and also modifying the page numbers manually (compiling with pdflatex). If your preferred slide-producing method does not work correctly with this detection, you can supply this information using the \[aq]o\[aq] key for each slide that is part of an overlay (except the first one!). The page numbering is also adapted. This information is automatically stored. .SS End slide .PP Some people like to have some additional, backup slides after the last slide in the actual presentation. Things like bibliographic references or slides referring to specialized questions are typical examples. Pdfpc lets you define which is the last slide in the actual presentation via the \[aq]e\[aq] key. This just changes the progress display in the presenter screen, as to have a better overview of how many slides are left. .SS Movies .PP Pdfpc can play back movies included in the PDF file. Movies may be started and stopped by clicking within their area. For the presenter, a progress bar is drawn along the bottom of the movie. This expands when the mouse hovers over it, allowing one to seek by clicking or dragging within the progress bar. Switching slides automatically stops playback, and movies will be reset after leaving and returning to a slide. .PP Movies may be included in PDF files as "screen annotations". pdfpc does not yet support options that modify the playback of these movies. In LaTeX, such movies may be added to a presentation with the "movie15" or "multimedia" package. Note that the poster, autoplay, and repeat options are not yet supported. (Also, run ps2pdf with the \-dNOSAFER flag.) .PP As a perhaps simpler option, pdfpc will play back movies linked from a hyperlink of type "launch". A query string may be added to the URL of the movie to enable the "autostart", "loop" and "noprogress" properties, if necessary. (E.g., a link to "movie.avi?autostart&loop&noprogress" will add a video that starts playing automatically, loops when it reaches the end, and does not show the progress bar.) In LaTeX, such links are created with .RS \\usepackage{hyperref} .br \\href{run:}{} .RE .PP The movie will playback in the area taken by the placeholder content. Using a frame of the movie will ensure the correct aspect ratio. .PP See .URL http://pdfpc.github.io/demo/pdfpc-video-example.zip "our website" for a full example. .SS Pointer Mode .PP If needed it is possible to turn on a pointer which draws a red dot in the place pointed by mouse cursor on both - presenter and presentation screens. It is also possible to increase and decrease the pointer size. Additionally when the pointer is enabled it is possible to drag & drop some area of the presenter screen causing it to be highlighted in both views as well. Area outside the selected region will be dimmed. .SS pdfpc Files .PP The several additional information are stored in a file with the extension "pdfpc". When pdfpc is invoked with a PDF file, it automatically checks for and loads the associated pdfpc file, if it exists. This means that you normally do not have to deal with this kind of files explicitly. .PP Beside internal configiration, the following user contributed command line options are stored within the pdfpc file for later usage: .IP \[bu] 2 duration .IP \[bu] 2 end_time .IP \[bu] 2 last_minutes .IP \[bu] 2 notes (position) .IP \[bu] 2 start_time .PP There are however cases where you may want to edit the files manually. The most typical case is if you add or remove some slides after you have edited notes or defined overlays. It may be quicker to edit the pdfpc file than to re-enter the whole information. .PP The files are plain-text files that should be fairly self-explanatory. A couple of things to note: .IP \[bu] 2 The slide numbers of the notes refer to user slides .IP \[bu] 2 Slide indexes start at 1 .SS Appearance .PP With GTK3 it is possible to modify the appearance of pdfpc. There are two locations where pdfpc is looking for files. The default location is @CMAKE_INSTALL_PREFIX@/share/pixmaps/pdfpc/pdfpc.css. A user can copy it to $XDG_CONFIG_HOME/pdfpc/pdfpc.css and change the attributes as he likes. .SS Integration with other tools .PP Pdfpc provides a dbus interface that other tools can use to execute any action listed by \fB--list-actions\fR. The interface appears on the session bus as \fI io.github.pdfpc\fR. .SH BUGS .PP Bugs can be reported at .URL https://github.com/pdfpc/pdfpc/issues "our issue tracker" . .SH ACKNOWLEDGEMENTS pdfpc was previously developed by .URL https://github.com/davvil/pdfpc "davvil" . pdfpc is a fork of Pdf Presenter Console, available .URL https://github.com/jakobwesthoff/Pdf-Presenter-Console "online" . .SH SEE ALSO .PP pdfpcrc(5) There are several other programs with similar functionality. .BR impressive (1) has nice transition effects. .BR hpdfp (1) is the .URL http://michaeldadams.org/projects/haskell-pdf-presenter/ "Haskell PDF Presenter" program, which packs an amazing level of functionality into not many lines of Haskell. .BR pympress (1) is a little .URL https://github.com/Cimbali/pympress "PDF reader written in Python" which handles dual screens and beamer notes. .BR dspdfviewer (1) is also specialized for beamer-produced wide PDF with notes. Many PDF viewers have full-screen presentation modes, but without dual-monitor preview or notes or a timer. These include .BR zathura (1), .BR evince (1), and .BR okular (1). pdfpc-4.0.6/man/pdfpcrc.in000066400000000000000000000047061305134127600153520ustar00rootroot00000000000000.TH PDFPCRC 5 .if !dURL \{\ .de URL \\$2 \(laURL: \\$1 \(ra\\$3 .. .\} .if \n[.g] .mso www.tmac .SH NAME pdfpcrc \- pdfpc configuration file .SH SYNOPSIS .B @SYSCONFDIR@/pdfpcrc / $XDG_CONFIG_DIR/pdfpc/pdfpcrc .SH DESCRIPTION .PP pdfpc(1) reads its configuration file from @SYSCONFDIR@/pdfpcrc. It also reads, if present, the file $XDG_CONFIG_DIR/pdfpc/pdfpcrc. If $XDG_CONFIG_DIR is not set, it uses $HOME/.config . .SS Keybindings .PP Following commands are aceepted: .TP .B bind Bind a key to a function .TP .B unbind Unbinds the given key .TP .B unbind_all Unbinds all the keybindings .TP .B mouse