Too Young to Play 50

So auditions for To Kill a Mockingbird just came and went.  The director had asked me to come out for Atticus and I was feeling good.  Now, I never think I actually have a part until I have a script in my hand at the read-through, but I was feeling optimistic.

At least, I did until I got there.  I then realized that even though I'm in my 40s, I'm still too young to play Atticus.  The text says he's pushing 50 but it seems that the Dick Clark genes aren't on my side this time.  It's generally a good thing to look younger than you are in this profession, but this wasn't one of those times.  Another actor was there in the light suit who was doing a good job, too, and while I thought I might have edged him out with regard to the performance part, he looked the part more and thus, he landed the role.

I get to concentrate on work now.  I've been teaching myself JavaScript and I've been working on creating a clock script.  Not that hard, I know, but the issue has to do with where the scripts are going to run.  Our software allows the users to create customized pages and it will recognize scripting, but it doesn't provide access to the HEAD tag.  Thus, all scripting has to be capable of being run in-line.  Thus, the script is triggered by a window.onload function.  But, the users will want to have multiple clocks so I had to develop a method that would allow multiple clocks (for whatever time zones they choose) be loaded.

And on top of that, the designer where the users will build the page will actually run the script that's on the page.  Thus, since the clock is continually updating, leaving the page will always trigger the, "Your page changed.  If you leave without saving, you'll lose your changes," message...even if you just saved the page.  So, I developed a method to detect where you are in the system so that if you're in the design section, the clock doesn't run.  Anywhere else, it does.

But after a few days of going through JavaScript references (while continuing to support the users and do the trainings), I've managed to get them to work.  The users will still need to do a bit of coding to load the script and put in the correct DIV reference, but it's mostly plug-and-play and they'll be able to have a clock that isn't a third-party solution.

The Ultimate Special Effect

There was a significant earthquake Easter Sunday, April 4, about 3:40 pm Pacific time in Baja California.  We were just getting ready to start the second act of Into the Woods at OnStage Playhouse.  Now, for those who don't know Woods, it's an amalgamation of various fairy tales:  Cinderella, Jack and the Beanstalk, Little Red Riding Hood, Rapunzel, and includes a story of a Baker and his Wife.  At the end of the first act, everything seems to have been wrapped up:  Cinderella and Rapunzel have their Princes, Little Red is saved from the Wolf, and Jack has survived his trip to the land of the Giants in the sky.  The "happy ever after" is so complete that during the original run of the show, many people never came back for Act II because they thought the show was over.  They added a line to let people know that the show as "to be continued."

Alas, one of the magic beans is still around and another stalk grows into the sky.  At the top of Act II, the characters are expounding on how happy they are (despite some minor inconveniences) when there is a huge rumbling and what seems to an earthquake tosses everyone around.  It's the wife of the giant whom Jack killed coming down the second stalk and looking for the lad who killed her husband.

So we're walking on stage to start Act II...when an actual earthquake hits.  Now, we're all Southern Californians.  Earthquakes happen.  And there hasn't been a big earthquake in the San Diego area for quite some time.  So it started off as usual...people looking at each other thinking, "Was that an earthquake?"  And then it kept on going.  And going.  "Um, I don't think we want to be underneath the lights," and we all evacuate the theatre.  After about 15 minutes, it's clear that it's over, there's no damage, and we all go back in and start Act II.

Now, the timing was either just off or absolutely perfect, dpeending on how you look at it.  If it had happened about five minutes later (and we did need to hold both opening and intermission a bit longer because of slow patrons), it would have struck exactly when the giant was supposed to be attacking.  But if it had, we would have had to have evacuated in the middle of performing and then restart somehow in the middle.  As it was, since it happened right when intermission was over, we were able to start up Act II without any interruptions.  And when the characters experience the giants attack, thinking it was an earthquake, the audience got a good laugh...though there was one child in the house who got scared, thinking that another earthquake was happening, this time much more violent as the actors are thrown to the ground.

This was better than the last intermission interruption I had.  I was doing The Fantasticks at the Coronado Playhouse.  It was July.  Independence Day weekend.  So Act II is starting up, the audience is coming back in, when BOOM!  What the...?  BOOM!  CRACKLE!  Ah, yes, the fireworks display.  The Coronado Playhouse is on the bay and the city's fireworks display has just started.  Everybody leaves the theatre to watch the show.  Well, we're not going to start the show without the audience and even if we did, it's so loud that we really couldn't perform.  So the cast goes out the back to watch, too.

This is why I love live theatre.