Merge branch 'master' into dev
Disable use of firebugesqe console objects from WebView applications, because as far as I know it's a /dev/null (and yet perversely still thread-unsafe and willing to segfault you to death).

Now that I can actually get messages on stderr, I'm noticing something else pretty unhappy: jquery seems to be failing miserably at standardization of dom events now.  It's zeroing all coordinates on all mouse events and failing to report modifier keys.  Really the only thing it's getting right aside from the event type itself is the srcElement and timestamp.
Refactor Beard to be an interface.  The previous implementation is now called Beard_Direct, and is package-visible since it is an implementation detail.
Add target to build.xml for compiling test code.
the normalizePage() function is now private to Beard_Direct, since no code outside of the beard library will have the visibility to access it anyway, and it will always be called during beard initialization instead of being optional.
Created a new Beard implementation that wraps an existing Beard and delegates commands to it in a thread-safe way using the Pipe<Ackable<?>> design from AHSlib.

Right now it's only designed to work within a JavaFX standalone application, since applets already have thread safety built in around the kind of JSObject they give you.  It wouldn't be at all hard to make more general if the need presents itself, though.

Can't quite use it yet since currently JavaFX standalone applications still call the Beardlet.start method from the JavaFX thread, which means the kind of scheduling Beard_Insulated does would block itself forever.  So, next up is making sure the Beardlet gets its own nice safe scheduler to play around in instead of running directly in the JavaFX thread and wasting time that should be spent on rendering alone.
Beardlet is now an abstract class instead of an interface, so I could define a scheduler() method and give it a reasonable default behavior.  The WorkScheduler returned by that method will powered by a thread that's *not* the UI thread, and in the future this scheduler used to power the start and stop methods as well as being available for all the work scheduling needs of the application.
Add package-visible WorkTarget implementations that will invoke the start and stop methods of a Beardlet.
First pass at putting Beardlet lifecycle outside the JavaFX UI thread.

The commentted out gob of code was an attempt at making sure the Beardlet start logic can throw stuff up for display before we actually show the stage, but using a blocking thing there creates deadlocks.  Will fix this in the near future; for now it works without it.
More serious testing -- scheduling period updates of the screen contents.  Works :D
Fix a deadlock in shutdown; shutdown is now graceful.
Defer showing the stage until after the Beardlet has finished start()ing, and make sure that on the off chance the application was closed before start was ever called then we don't call stop.
refactor some repeated build config.
whitespace police.
add "run-test" target to build config.
Transition the beard launcher for applets to use the same threading model as standalone applications (namely, that the start() and stop() lifecycle methods are powered by the same thing you get a handle to by calling scheduler()).
shifting dependency on lib/ahslib to version v0.6.4.
Javadocs for the start and stop lifecycle methods of Beardlet.
Javadocs on the Beardlet.scheduler() method.
Schedule the BeardBus work target that shuttles events around for periodic execution when starting the application.