Depreciate pagination.py

[obtitus]

Hi, @TheChymera I just wrote render.py as a replacement for pagination.py. It does not do exactly the same thing, and is not syntax-compatible. Instead of producing an a4 document, it creates a 'standalone' minimal image file, which I personally find more usefull.

Feel free to improve render.py, I am not currently using it in any projects, so do not worry about backward-compatibility.

Are there any features of pagination.py that you would like to see in render.py?

Can we remove pagination.py?

[TheChymera]

I wrote pagination.py to allow me to easily create tables for print. Stuff like checklists or duty allocation tables for the lab - so for me the capacity to output a .pdf file in a given format is actually important.

I would prefer this to an image file since LaTeX typesetting is customized for dimensions - so I see no benefit in having an image which I could technically print at whatever size/resolution I wanted. I do however, see a disadvantage with having to worry about where the image gets placed on the page, whether the printer scales it, etc. This is not the case if I can just output an a4 (or maybe a3) document.

I do agree, however, that pagination.py is not particularly elegantly written. If you can include an option in render.py which allows the user to specify an a4/a3 (or maybe whatever else) document class, then we should delete it, yes.

[obtitus]

By default, the .pdf image produces by render can (at least on my system) be printed with a 'scale=100%' to a4/a3 paper. Having an image is in my mind more flexible, since the image can be included in a html page or office-like-document.

But, I made some changes, so that the latex preamble is more easily customisable, so outputting a a4 page should now be trivial.