Functionality

Each cue will have a few pieces of info: Corresponding LX Cue Number (Eos Cues; consider point cue handling), Spotlight Cue Number (The point cues as a subset of each cue), Cue Name (officially) contains: synopsis/description => Stage directions, end of dance break/musical number, new scene/act/song; Booleans: isSongBreak, isSceneBreak, isActBreak. (Scene numbering to be implemented in the future.)

As a subset of each master cuestack, each spotlight will have it's own cue stack containing the following: Color: (if frames, which frames; if other, which other); Size: (Head Shot, Full Body, etc.); Intensity: (if current intensity > previous intensity, display up arrow; else if current intensity < previous intensity, display down arrow); Time: nothing fancy here, just some integers or strings, if integers, append s/m to them; Pick Up (the toughest to implement IMO: Character + Spotlight Action in bold, blocking description not bolded.

We want to be able to set 8 presets for all of these, probably in a join table or something.

Intensity should have 10 preset options Out, 10, ..., 90, FL in 10% increments, FL = 100, so we need to add some sort of keyword in here too.

Based on the schema & current associations of the Color => Spotlight through Color_Frames association, we need to allow a spotlight to have as many or as few Color Frames as the user defines.

To do this, I want to use nested forms to 'add' or 'delete' associations through a form where we can add or subtract rows in the new/edit windows to create or remove color frames (with their associated colors) from a spotlight.

Basically, when a user creates a new spotlight, eg. Spotlight Name: Spotlight 2, we want to create a nested form where you can add/subtract rows depending as needed.

Further along the development pipeline, I'd like to add a dropdown with manufacturer_id filetering (not yet implemented).