CALVIN COLLEGE

THEARTRE SOFTWARE SUITE

RELEASE 1.0

CS 262 CLASS

 

POINTS OF CONTACT

NATHANIEL DICK – PROJECT MANAGER

MATT SWEDA – LEAD ARCHITECT

SARAH GRIFFIOEN – LEAD ANALYST

DAVID WIDJAJA –  LEAD QUALITY ASSURANCE

ADAM FISCHER - LEAD CONFIGURATION MANAGER

TABLE OF CONTENTS

GENERAL INFORMATON ………………...…………………………………………………............. 1.0

Project Outcome and Deliverables ………………………………………………......………..…1.1

SYSTEM SUMMARY ……………………….……..……………………………...................................2.0

HOW TO GET STARTED …………………….………………………………………………………...3.0

Logging on ...………………………………………...…...….………………….......……….......3.1

System Menu …………………………….…………………….……………..............................3.2

USING THE SYSTEM …………………...……………………………………………………….……. 4.0

Script ….....…………….……………………………………….………………………………..4.1

Blocking………….….………………………………………….………………………………..4.2

Notes.………………….……………………………………….…………………….…………..4.3

1.0 GENERAL INFORMATION

GENERAL INFORMATION

The CS 262 class of 2017 was tasked with creating a suite of software products that will support the creative process of producing theatrical plays. The goal of this project is to provide the theater company with a tool to help in their preparation for shows.

Project Outcome and Deliverables

At the completion of the semester, the class is expected to provide a working prototype of the products listed below.

 

  • A standard XML schema that will support traditional elements of a play script and director notes.
  • A mechanism for theater students to record pre-rehearsal blocking decisions within an XML formed script.
  • A mechanism to share an XML formatted play script between production roles (director, props, actors, lighting).
  • A mechanism to assist actors in line memorization.
  • A mechanism for directors to alter stage directions with immediate automated sharing of those directions among cast and crew.  In essence, the system will support an electronic prompt book for use across the production.
  • A mechanism to capture existing printed scripts and transform the content into the XML standard.
  • A mechanism to apply property notes to the XML formatted script.
  • An application to render blocking decisions in 2D.
  • An application to render blocking decisions in 3D.
  • A mechanism to identify French scenes in a script.
  • A mechanism to build rehearsal schedules.
  • A service to distribute/download pre-XML formatted scripts with appropriate licensing information.
  • An application to support writing a script which will be saved in the standard XML format.

2.0 SYSTEM SUMMARY

SYSTEM SUMMARY

The system runs on React JS and Node.JS. For the back-end it runs on Express back-end. The whole application is written in JavaScript and React JS, which is a Java Script Library. React renders the front-end portion of the app, which is what the user sees in their browser. Node.JS runs the application locally and downloads any packages that are needed for the application to function.

Terminology:

Renders: Render refers to the process of adding three dimensional qualities, colors and shadows.

Front-end: Front-end is the user interface, the part the user uses.

Back-end: back-end refers to where the application’s processes interact with the front-end.

Locally: Locally refers to applications that are located on your personal device.  

Packages: A package usually means software that perform similar functions.

Script: A script refers to a list of commands that can be executed without user interaction.

XML: This refers to Extensible Markup Language, it is used to define rules for encoding documents.

JavaScript: This refers to a high-level programming language that makes webpages more interactive.

React JS: This is used to build user interfaces.

 

3.0 HOW TO GET STARTED

HOW TO GET STARTED

3.1 Logging In:

NEW USER: If you are a new user, hit the “New user? Request an account here.” button. This will take you to a page that will allow you to enter your information to create an account. Once you enter that information and press “Create Account,” then it will bring you to the login page. Once you are there, follow the instructions below for a returning user.

RETURNING USER: The login page looks like the page below. Enter your credentials and hit “Sign In,” this should bring you to the Home Page. (this is going to be changed)

LOGIN PAGE

4.0 USING THE SYSTEM

USING THE SYSTEM

4.1 Script:

 

The script page is where the deliverables come together. As a user, after logging in you have access to the script page. The first thing to do is select a play. When this is done you will realize that new acts show up in the act bar. You can then select an act and also a scene that needs to be edited. The lines for the scene will show up.  Once the lines are clicked, the property notes will show up, and the user can select blocking instructions, lighting and props for that particular scene or line.

4.2 Blocking:

The blocking page is where the director and any one with clearance can make edits to lines and scenes.

The blocking page starts blank with no blocking. The actors involved in the scene will be below in the loading zone. Each circle represents an actor and its denoted with an identity for each actor. The colors of the circles are randomized to the names of the actors.

Using the blocking Application:

To start you have to click on actor and drag them onto the stage to a desired location. An arrow will show the movement of the actor from the original location to the new location. As the director edits the blocking instructions get imprinted on the lines and is carried

There is a save button that takes your blocking instructions takes it back to the database to save the changes. There also is a cancel button to cancel the edits and sets the edit for that line or scene to its original.

 

Created by KWABENA AGYEI BOAHENE