Application that return ticket information for a client using the UserInterface
Behavior: Stores user input in a new ticket object input: Fast 16, 12, 8pm output: Ticket object {name: Fast 16, age: 12, showtime: 8pm}
Behavior: Site will store each movie in a object input: Fast 16, 8pm, R rating, matinee output: movie {name: Fast 16, showtime: 8pm, rating: R, type: matinee}
Behavior: Will store movie objects in a movie theater object input: Fast 16, Monsters Inc., Despicable me output: Movie Theater {movies = [Fast 16, Monsters Inc., Despicable Me]}
Behavior: Calculate the cost of the ticket. input: Fast 16, 12, 8pm output: Ticket object {name: Fast 16, age: 12, showtime: 8pm, price: 14.99}
Behavior: Site lists out names of movies input: user selects movie output: Offers showtimes
Behavior: users enter an age and the site only lists movies with appropriate ratings input: 12 output: Despicable Me (PG), Monsters Inc (PG), etc.
Behavior: site allows users to select a movie and view showtimes input: Despicable Me output: noon, 8pm, 12am
- This is a great place
- to list setup instructions
- in a simple
- easy-to-understand
- format *_Go to https://github.com/chyoon2/movie-tickets to check out the code!
{Leave nothing to chance! You want it to be easy for potential users, employers and collaborators to run your app. Do I need to run a server? How should I set up my databases? Is there other code this app depends on?}
{Are there issues that have not yet been resolved that you want to let users know you know? Outline any issues that would impact use of your application. Share any workarounds that are in place. }
{Let people know what to do if they run into any issues or have questions, ideas or concerns. Encourage them to contact you or make a contribution to the code.}
{Tell me about the languages and tools you used to create this app. Assume that I know you probably used HTML and CSS. If you did something really cool using only HTML, point that out.}
{Determine the license under which this application can be used. See below for more details on licensing.}
Copyright (c) 2016 {List of contributors or company name}