Need to automatically test whitespace and coding style

Should be able to create an image surface from the PNG data without using any intermediate files.

• 1. We should reduce the thickness of the bar
• 2. Discuss possible functionalities such as page info, zoom level, zoom button (see review of pdf viewers as a starting point [link-should-be-added-here])

We need to test the ::App by first pushing a PDF file (use the one in test-data) onto @ARGV and then calling $app->process_arguments.

We need to figure out an alternative solution

Move the text to a tooltip. This will take up less room on the screen.

tab-pos and tab-reorderable are unavailable properties for libgdl 3.8.1 on ubuntu 14.04 LTS

Connects to #109.

Perhaps looking at this would be useful: http://tesla.duckdns.org/gtk3-perl-windows/ and https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/.

@ChiragGhanshani, could you add a new text area widget to the simple-gui branch (PR #6) that is between the back and forward buttons which

• shows the current page number and the number of pages
• and when the user enters a page in the text area, it should set the current page number to whatever was entered

Something like the following interface from xpdf:

Create a new branch off the simple-gui branch and open a pull request for your change.

If you get stuck, please ask.

• 1. When we are at the last page of a document/file the forward button should be disabled. In a similar fashion, when we are at the beginning of a file we should not be able to move backwards.
• 2. Page number entry does not display anything on open.
• 3. Page number entry does goes to 0 and goes to (#pages+1) with forward and backwards.

• gir1.2-gdl-3 travis-ci/apt-package-safelist#2700 , travis-ci/apt-package-safelist#2702

Look at Travis-CI docs, X11::GUITest, and the tests in the Gtk3 package

mutool can be used to get the same information

For taking notes, I believe OpenDocument is the most appropriate format to start with.

We may need to add our own tags to add annotation linking information.

From PR #37.

• Create functions that check if moving to the next/previous page is possible
• Change name from on_draw_pdf_page to on_draw_page
• Simplify if statement by storing boolean.

Goal: full-screen, but keyboard shortcuts continue working.

With transitions between slides (carousel, coverflow, etc.)

https://en.wikipedia.org/wiki/Web-based_slideshow

This makes their purpose clear and separates them from regular functions of the view.

so next_button_clicked becomes on_next_button_clicked_cb.

http://www.inside-r.org/packages/cran/cairoDevice/docs/asCairoDevice

Extend via Statistics::NiceR.

We need to figure out how to make the components extend Gtk3::Widget. There is a module on CPAN that does this very well: Gtk3::SimpleList.

See also https://metacpan.org/pod/Glib::Object::Subclass.

• https://developer.gnome.org/gtk3/stable/gtk3-Drag-and-Drop.html
• http://python-gtk-3-tutorial.readthedocs.io/en/latest/drag_and_drop.html
• http://www.openshotvideo.com/2008/09/drag-drop-with-gtk-and-python.html
• http://stackoverflow.com/questions/14273471/drag-and-drop-files-into-program

This should be fairly straightforward. The Debian packages are in a file in this repository.

Meeting log: https://project-renard.github.io/doc/development/meeting-log/posts/2016/01/24/initial-setup/

Add unit tests on pull request [#43 Max pages number] when [#41] is merged.

When opening a document, it should show how many pages are in the document next to the page entry field.

See:
pdfinfo:

$ pdfinfo test-data/PDF/Adobe/pdf_reference_1-7.pdf
Title:          PDF Reference, version 1.7
Subject:        Adobe Portable Document Format (PDF)
Author:         Adobe Systems Incorporated
Creator:        FrameMaker 7.2
Producer:       Acrobat Distiller 7.0.5 (Windows)
CreationDate:   Tue Oct 17 03:10:20 2006 CDT
ModDate:        Sat Nov 18 17:40:43 2006 CST
Tagged:         yes
UserProperties: no
Suspects:       no
Form:           AcroForm
JavaScript:     no
Pages:          1310
Encrypted:      no
Page size:      531 x 666 pts
Page rot:       0
File size:      32472771 bytes
Optimized:      yes
PDF version:    1.6

Foxit:

Adobe Acrobat Reader:

mutool

mutool show pdf_reference_1-7.pdf $(mutool show pdf_reference_1-7.pdf grep | grep 'Author(' | cut -d: -f2 | tail -1)
109959 0 obj
<<
  /CreationDate (D:20061017081020Z)
  /Subject (Adobe Portable Document Format \(PDF\))
  /Author (Adobe Systems Incorporated)
  /Creator (FrameMaker 7.2)
  /Producer (Acrobat Distiller 7.0.5 \(Windows\))
  /ModDate (D:20061118211043-02'30')
  /Title (PDF Reference, version 1.7)
>>
endobj

Note that \( ->( and \251 -> © (which is ordinal 251 in octal). More info about escaping objects is on page 54 of the PDF reference:

Should show when clicking the File > Open menu item

• PDF file extension filter (only show *.pdf files)
• Option to show all files

See #41 (comment).

This will allow for using the add method on Gtk::ScrolledWindow on older versions of Gtk+.

Use POD coverage tests to check that each class, method, and attribute has documentation.

I was thinking of creating a dictionary with all the important text so that when the language is selected the message in the correct language appears to the end user while the actual coding remains the same. The pool of messages probably should have a small degree of separation/clustering but not too much such as most terms can be used on multiple ages/occasions

From Zaki: in FOSS projects [https://github.com/GNOME/evince/tree/master/po], this is usually done using the gettext library and .po files.

The built-in icons are not very modern and the buttons are a little large.

We need menus because buttons will clutter the UI.

• File → Open
• File → Recent (submenu)
• File → Quit
• View → Continuous (toggle)
• View → Page mode→Single
• View → Page mode → Facing → First page center
• View → Page mode → Facing → First page right
• View → Page mode → Facing → First page left
• Help → About

Set the title of the application window to the currently open PDF filename.

Create a new branch off the simple-gui branch (PR #6) and open a pull request for your change.

Connects with #55.

Also create predicates to determine if already there.

• PgDown: next page
• PgUp: previous page
• Up/Down/Left/Right arrow keys: control scrolling

@StayerX, could you edit the run.pl code in simple-gui branch (PR #6) the to have the drawing area in a scrollable region? This will allow for moving the page around if it is larger than the window size.

Create a new branch off the simple-gui branch and open a pull request for your change.

It should scroll both horizontally and vertically and the scrollbars should appear automatically when needed.

If you get stuck, please ask. #simple-gui-scrollable

• Clutter (gir1.2-clutter-1.0)
  • Issue travis-ci/apt-package-safelist#2853
  • PR travis-ci/apt-package-safelist#2861
• Clutter-GTK (gir1.2-gtkclutter-1.0)
  • Issue travis-ci/apt-package-safelist#2852
  • PR travis-ci/apt-package-safelist#2860

These need to be associated with the particular document.

The PDF data model and rendering code can be independent of the GUI code.

Need to have HTML renderer

1. @StayerX: Look at #65 to see how to use Webkit in Gtk3.
2. @StayerX: Load a demo HTML file into the WebView.
3. @zmughal: Update the pdf2htmlEX distribution and record a video of it.
4. @StayerX: Run pdf2HTMLex on the PDF and use that HTML in the WebView.

Both the PDF and CairoImageSurface have shared code. Use a role to simplify that.