Method Schedule 0.7.0

Method Schedule 0.7.0

Method Schedule makes merging two copies of a schedule easier to follow, keeps each merge's conflicts with the file until someone reviews them, and weighs strip orders by a cost you can check by hand.

Merging two copies

• Conflicts kept for review. Every conflict a merge settles stays in the schedule file, with what each side had and which was kept. File > Merge Conflicts to Review lists them, each a link to its sheet, element or category, with Done for one and All Done for all. Merges run from the command line or by git keep them too.
• What Changed links to each change. A change to a sheet, element, strip or calendar date still in the schedule is a link to it. Merge conflicts show yours, theirs and the earlier value side by side.
• A rename meets a new element. When one copy renames an element and the other adds an element with that new name in the same category, the merge makes them one, instead of keeping two of the same name.
• Merging in the browser. The browser version of Method Schedule can merge two copies when it is given the version both started from.

Strip orders

• A cost to compare orders. Suggest Strip Order adds up a cost for each order: actors' work days, location changes within a day, switches between day and night scenes, and red flag clashes, each with a plain weight. It tries three orders, suggests the cheapest, and shows every one's cost. When none beats the order on the board, nothing moves.

Script drafts

• On the Breakdown tab. Each sheet's header names the newest draft that changed or added it.
• Printed. Plan > Script Drafts prints, a row for each draft and kind of change.

Smaller changes

• Files from this version. A schedule with merge conflicts to review opens in 0.7.0 and later, not in 0.6.0 or earlier; mark them done first to open it in an older version. A schedule that uses call times of its own or script drafts still won't open in 0.5.0 or earlier. Every other file opens as before.
• Security fixes in the connection the app uses to check for updates.

Known gaps

• On an Intel Mac, the app has been tested by the automated tests, run the way an Intel Mac runs them, but not yet by a person on one.
• Windows and Linux builds are made and tested automatically, but nobody has installed them by hand yet. The Windows installer is unsigned, so Windows shows a warning before it runs.
• On Windows and Linux, opening a second file while the app is running starts a second copy of the app.
• Printing uses Letter paper only.

Thanks

• Everyone who has tried Method Schedule so far. Bugs go to Issues and questions to Discussions, both on GitHub.