I have recently broken my work block for working on #ShotLiner. I had the epiphany that maybe a schedule is a pretty much flat structure in linear order. So like, a Vec basically. I am still confused as to why it took me several months to understand this, but ok. #programming #softwaredev

I formalized the return types in the "reports" module for the screenplay_doc_parser crate. I'm now shifting focus to the shotliner-core crate.

I've got basic data modeling, structs to represent ShotLines, Tags, and TaggedElements.

What does this mean?

Broadly, I'm still putting things like "Dual Dialogue" handling, or parsing complex scene headings with multiple locations (e.g. INT./EXT. HOUSE/STADIUM) on the backburner. I'm anxious to really start building the core for #ShotLiner soon. I can go back and add edge-case stuff later.

...That way, any additional Shots can be added to the storyboard file non-destructively. And old deleted shots can be flagged in some way, instead of being just deleted.

So, when viewing the storyboards in #ShotLiner, you can see each board in a sidebar or floating next to each ShotLine...

A future feature for #ShotLiner : Storyboard Template generation.

In #ShotLiner, you'd be able to define Shots, which span some distance over the screenplay. From these, you could get a list of all the shots for the script in linear order, and the shot type per Shot (wide, medium, close, etc.) ...

The crate is basically "done enough" where I feel comfortable leaving it be, and soon switching focus to work on the #ShotLiner core itself. The core will rely on the basic parsing and reports from the screenplay_doc_parser crate, but will of course extend that with tagged elements and shotlines...

This crate will be used in #ShotLiner, but it could also be used independently for other apps or programs that need a semantically-parsed screenplay.

Right now, I've just finished testing basic reports. That is, you can query the scenes, characters, locations, pages, and lines, and cross-filter...

This is a brief demo of a crude proof-of-concept for ShotLiner, an open-source screenplay breakdown / preproduction tool; A FOSS alternative to something like Scriptation on mac/ios, Fuzzlecheck, or StudioBinder.

I built this last year with a messy codebase. Now, I'm rewriting it from scratch.