Ideas About Page Locking and Revisions

[thegreentimtam]

I've got some ideas to enable revisions and page locking in Better Fountain.

1. Implement the locked page numbers proposed by Paul Rankin a few years ago, by adding the page number after a forced page break.
   === 12
=== 12A
   This would work basically in the same way as scene numbers do currently, with Number Pages - Overwrite, and Number Pages - Update buttons in the Fountain command pallette.

2. The ability to export a PDF with revision marks. Here you'll be able to select two versions of a script, and it will find the changes for a correctly formatted revision PDF. This could compare two different Fountain files, or - my preference since we're in VS Code - two different git commits.

[thegreentimtam]

I think perhaps the list of revisions should be kept in the Fountain document. As this list is usually included on the title page, you could use this to store that information.

Revision 1: White Draft
Revision 1 date: 06/02/22
Revision 1 file: original.fountain
Revision 2: Blue Revision
Revision 2 date: 09/28/22
Revision 2 commit: ef3135025dfd312bfae200d021f263ac0735dc34
Revision 3: Pink Revision
Revision 3 date: 10/30/22
Revision 3 branch: revision-3
Revision: Yellow Revision
Revision date: 12/25/22