Hi everyone, Two significant updates to the xournal code base today (in cvs and git on sourceforge.net):
1. the auto-save feature. I wasn't happy with the (several) existing patches so I wrote my own code. If the option is enabled (Options -> Auto-Save Files), Xournal will check periodically (default: 5 seconds; see config file to change) whether there are unsaved changes, and if so, it will create a file named filename.xoj.autosaveN.xoj where N varies between 0 and 9 (between 0 and 1 if you only have one instance of xournal editing the same file at the same time). When a file is opened, Xournal checks for autosave files and offers the option to attempt a recovery (or to ignore the autosave file, or to delete the autosaves). (If there are several autosaves for the same xoj file, the user is prompted to choose one). The autosave files can of course also be opened directly and saved back over the original xoj file; xournal does this automatically (and erases the autosave file) when recovering an autosave. 2. new "export to PDF" code. The built-in PDF parser and generator were getting a bit dusty (no longer able to parse all PDF files; exported text items would not copy-paste to readable text; etc). So the new default "export to PDF" behavior is to use poppler and cairo code to generate a PDF file. This is very similar to File -> Print -> Print to PDF except it preserves the page sizes of the xoj file instead of adopting a standard printer paper size, and doesn't bring up a print dialog. The legacy "export to PDF" code remains available if you select Options -> Legacy PDF Export. However, when the xoj file annotates a PDF file that can't be parsed (e.g. PDF 1.5+ compression), instead of stupidly generating a low-resolution bitmap version, we will always fall back to the new cairo/poppler code. Please test if you have interest and time. Especially, the stress-test features are: - test auto-save recovery in the presence of attached files (e.g. files that annotate screenshots (Page -> Background Screenshot), and of multiple concurrent instances of xournal editing the same file. - test pdf export with text in a variety of fonts, highlighter/transparency effects, and mixed page sizes within the same xoj document; also when annotating a compressed pdf file that previously caused xournal to export a low-resolution bitmap. (Highlighter transparency remains imperfect in the exported PDF but should not be worse than with the legacy code). Let me know if you spot issues that need fixing; release 0.4.8 might come sooner rather than later, and I'd rather make sure that things work properly. Thanks in advance! Denis -- Denis Auroux aur...@math.berkeley.edu University of California, Berkeley Tel: 510-642-4367 Department of Mathematics Fax: 510-642-8204 817 Evans Hall # 3840 Berkeley, CA 94720-3840 ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Xournal-devel mailing list Xournal-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xournal-devel
