Is this PrintPDF thing something that could be run (or ported to run) on the DR itself?

If the main functionality can be, I think it could be extremely useful (for me, that is) if it could be merged with the main UI so annotated PDFs can be generated right away from PDFs + annotations. I think it shouldn't be too hard to implement something along the lines of:

Oh, I see. My idea was to somehow call the script from the main DR UI to skip Xournal altogether. Not that I think it's useless, but all I do with it is 'import annotations -> export to PDF', and a simple UI addition + script as I described would be far more practical for that.

Hi all, I have been away on holidays for almost two weeks (: so that is why I reply only now.

Quote:

Originally Posted by godel10

@Mackx: I have not succeed to make it work (under python 2.8), but I am not very familiar with python scripts. Could you tell us the command line syntax you use?. And, what is the output of this script?

The answer that Iņigo gave is correct for the first version. The 2nd version should open a window in which you can select a directory (preferably a copy) of the SD card using the open-menu-command. All documents that contain annotations (in the metadata.db file) will be processed. (Original files are not changed but a few new files are generated.)
Did you already get it to work?

Quote:

Originally Posted by Iņigo

I think it's definitively doable, at least as an external script.
Python is already ported, pyPdf is pure python, and ReportLab only C module is for speed.
So I guess it should run on DR.

The main purpose of this 'exercise' was to create a tool for PC, I did not think of porting it to the DR itself. But I guess that it should be possible. It will not be my main focus. While reading documents I make some annotations at interesting part so I can look at them in more detail later (I use my DR in the train). So I created this tool to merge the annotations off-line, so that I can quickly look-up the interesting parts and follow-up on them.

Quote:

Originally Posted by MrWarper

Oh, I see. My idea was to somehow call the script from the main DR UI to skip Xournal altogether. Not that I think it's useless, but all I do with it is 'import annotations -> export to PDF', and a simple UI addition + script as I described would be far more practical for that.

Once the used modules gets ported, it should not be that difficult to create an 'open with'-command[1] that calls a python-script to convert a single file (for dr1000).

Did anyone use the (2nd) script already?

[1] See dr1000hackx, that allows to install alternative commands for extensions.

OK, while I try and devise methods of talking Mackx into implementing the non-interactive stuff I want , I heavily use Xournal to generate annotated versions of all my books so I can easily (but laboriously!) get as much of a misprint-free library as possible.

I hadn't commented any more on the virtues of this beast of a Xournal port in the hopes of not breaking the enchantment, and now several patches have been released and now we have v0.8d...

Turns out there's no enchantment to break when and where there's a competent programmer in charge. From v0.8 on it's all been improvements and no regressions I am aware of.

I just imported annotations, exported them to a new PDF and saved them as a native Xournal file without a glitch, and I'm talking a 402 page PDF here no less -- edit: 402 annotated pages, more like 500 in the original). Now, can Mackx cook, or can he cook?

I just imported annotations, exported them to a new PDF and saved them as a native Xournal file without a glitch, and I'm talking a 402 page PDF here no less -- edit: 402 annotated pages, more like 500 in the original).

Note that xournal only handles PDF up-to version 1.5 well. Higher versions might lead to rendering the page to a bitmap and merging the annotations with it. Since memory is not very well managed (it was written for desktop-computers) this will lead to problems even with medium size documents!