Papilot 0.8.7

Papilot 0.8.7 prepares the manuscript's PDF while you review, keeps long builds responsive, exports PDFs with notes and makes adding notes to a task feel like sending a message.

Added

• Export the PDF, with or without your notes. The paper's Open PDF button is now a Share menu: open the PDF, export it, or export it with your notes. With notes, every highlight and marked region keeps its colour, and each comment sits in a numbered card in a margin beside the page, joined to its mark. Chinese, Japanese and Korean comments are included. The paper's text, links and bookmarks still work. When a page has more comments than its margin can hold, the cut-off ones are printed in full at the end of the PDF and linked to and from their cards.
• Delete a finished task in one click. Once a task's changes are in your manuscript, applied or committed, its review offers Delete beside Archive. It removes the task with its conversation and worktree right away, without asking first; the changes stay in your manuscript. On a narrow phone the two buttons move below the result instead of squeezing it.

Changed

• The manuscript's PDF is ready when you commit a task. A reviewed task changes the manuscript only when you commit or apply it, and its PDF then compiled only once the manuscript was opened: one to four TeX passes, which on a 324-page paper took one and a half to three minutes. Papilot now compiles what committing the task will produce in the background, as soon as its round is ready and again after each decision, so the PDF is usually there the moment you commit: on that paper, 0.8 s after the commit instead of 94 s. Committing, applying a task, a Git action or a review decision starts the build right away, also when the manuscript is not open, and the PDF view updates as soon as a build starts or ends.
• An edit shows after one TeX pass. When an edit moves page numbers, references or the bibliography, LaTeX needs several passes. The manuscript now shows the pages of each pass as soon as the next one starts, so the edit appears after the first pass while the numbers settle, at the same place and zoom.
• The PDF you are waiting for compiles first. A compilation made ahead of time pauses while the manuscript you look at compiles, and on macOS drops to background priority while other TeX runs, so it takes little from your PDF or a review. When you start waiting for it, it gets full priority, and you see its passes. A build also continues from whichever recent build has the most similar sources, not only the newest one, so it keeps LaTeX's state from the closest version.
• Papilot keeps responding while it compiles. Neither Papilot nor the review engine waits for Git, the disk or a compiler while it compiles, so the task list, review page and PDF view stay responsive. After each build, moving your notes from the previous PDF searched every page's text in one go, which on a 324-page paper froze Papilot for about a second; it now lets other requests through between pages. On a 324-page paper the review engine stopped answering for over two seconds whenever a round was published, because each snapshot of the task rehashed all of its files twice, and for up to four seconds whenever a task was created, while its worktree was checked out; accepting a change, committing a task and removing a task also held it, for up to a quarter of a second. It now answers within a few tens of milliseconds throughout, and so does Papilot: from publishing a round to the committed manuscript's PDF, its event loop never waited more than 80 ms.
• Review rounds are ready sooner. A round compiles the text before and after the change at the same time, and so does the comparison of uncommitted changes.
• The whole paper in a review shows at once. A review shown in the whole paper waited, with only a timer on screen, until the complete new version had compiled, which on a 324-page paper took one to two and a half minutes after the round was ready. That build now starts as soon as the round starts compiling, not after it, and the review shows the round's own chapters with the changes in place right away, then each TeX pass of the whole paper, then the complete PDF, keeping the change you are looking at in place. On that paper the changes appeared 1.2–2.5 s after opening the review.
• Adding a PDF note to a task works like sending a chat message. A new note is one line that grows as you type, with a blue send arrow beside it like the chat box's; Enter sends it too. The note flies into the New task panel, or onto the New task tab when another panel is open, and its popover closes. A note already in the task shows Included × at the bottom right, wherever it appears: in its popover, in My notes and in the New task panel. Clicking it takes the note back out, and the note flies back. Clear selection is now Remove all from task. Your own notes no longer show a separate close button; Escape or a click elsewhere closes them, and a new note shows its delete button once it has text.

Fixed

• A decided change no longer offers Accept, Reject and Comment. In a task's review, a change that was already accepted or rejected, also after the task was applied, still showed buttons that did nothing. It now shows the way to the next undecided change, or that the review is complete; Undo changes a decision back.
• Quitting the desktop app leaves nothing running. After ⌘Q, the review server of each paper you had worked on kept running for up to 12 hours, so macOS listed Papilot under background activity. The desktop app now owns the review servers it starts, and they stop with it, even if it crashes. A PDF build that was still running is retried when you next open Papilot. In ps it is now called "Papilot review server" instead of node. Closing the window still keeps the app open, as on any Mac app.

npm install -g papilot@latest