Handling application/pdf content type

[almailer]

Implement rendering of PDF files on labbook pages.

[almailer]

Should also get javascript to provide visual feedback (on drag over) for supported/unsupported mimetypes

[almailer]

Branch iss6_pdfjs addresses this, as exemplified in 3c6d23e. Remaining to be done:

• [x] Wrap it all in an imgbox, to allow resize/move.
• [x] Allow select page functionality - waiting on pdf parameter storage
• [ ] Handle PDF zoom ability - waiting on pdf parameter storage
• [ ] Test with some more complex pdfs

[almailer]

Idea: Handle storage of attributes (e.g. pdf page, pdf zoom) as query string at end of file url, e.g.

pdfbox = row(x,y,w,h,content_type='application/pdf', content_id='/path/to/pdf/file.pdf?page=1&zoom=1.0

I finally realised how to properly do content-type specific parameters in the database.

Separate tables, e.g. content_box, content_image, content_pdf for each content type with a constraint on an id in the boxes table. For example, content_box has two fields, box_id and child_box_id, both of which must be references to boxes.id.

When rendering a box, a left join of boxes on all the content tables (if the convention is used that the table names all begin with content_, then processing db.tables will suffice to find all content tables) will provide all the information on a specific box.

[almailer]

Basic support is now in. You can:

• Insert PDFs into pages
• Set the displayed page of the PDF (default: 1)
• See the PDF when printing a page to PDF with printing.print_page() Not in:
• So far the HTML engine does all of the PDF scaling etc. For optimisation, pdfjs should be used for this.
• It seems that scaling the image within the box functionality broke somewhere along the line for the PDF boxes...