Fix selectize misordering on updateSelectInput

Repro case at https://gist.github.com/jcheng5/9403917
Make showcase mode work with .r files
Merge pull request #415 from jcheng5/bugfix/showcase-case

Make showcase mode work with .r files
Merge pull request #414 from jcheng5/bugfix/selectize-order

Fix selectize misordering on updateSelectInput
Change example licenses to MIT
fixes #416: use tags$code() to escape the code in showcase mode

and format(..., indent = FALSE) to prevent indentation of <code>
Merge pull request #417 from yihui/bugfix/showcase-escape

fixes #416: use tags$code() to escape the code in showcase mode
Allow '.' character in input/output IDs

I always thought dots and colons were illegal in HTML ID attributes,
but I was wrong. They are legal and because they are commonly used
in identifier names in R, Shiny users often like to use them. Worse,
Shiny gave no warnings when using dots and only a pretty advanced
subset of functionality would NOT work when using dots, causing
everyone to think they were fully supported in Shiny.

This commit ought to bring reality in line with perception. It turns
out that jQuery has an escaping scheme in its queries that allow us
to support dots after all. As long as we are always careful to
surround IDs with $escape when putting them in a query, we'll be in
good shape.

Colons will probably still cause problems at the moment because we
use colons internally to separate input type from input name. But
we've never seen users try to use colon in IDs before, so we can
wait to fix it until that becomes a problem.
It's important to return values in JS. heh.
Wrap for= value in double quotes
Proper escaping of name, value, and type queries
Merge pull request #418 from jcheng5/allow-dots

Allow '.' character in input/output IDs

Fixes #358
Mention showcase mode and allow-dots in NEWS
use `skipStartupTypeset: true` for MathJax config, and call MathJax.Hub.Typeset() later

setTimeout() is necessary for uiOutput(); we need to wait for a short while before typesetting math, otherwise two bad things can happen:

1. a math expression may be rendered twice (static output)
2. it is not rendered at all (dynamic ui output)

so the compromise is to typeset math after a short while when the document is ready; 200 ms is an arbitrary choice here
submit shiny 0.9.0 to CRAN
Fix 'Error in Context$new : could not find function "loadMethod"'

This warning was happening to dependent packages on R CMD check.

The problem is due to delayedAssign; it appears this can't be used safely, at least not to define package-level symbols that contain S4 or reference class objects.

If you call this in a package's .R file:

`delayedAssign("hello", stop("boom"))`

but don't refer to "hello" anywhere, when you run R CMD check on a dependent package you'll see the error.

If the expression needs the methods package (like Context$new()), you'll get an error unless the dependent package itself depends on methods.
Merge pull request #421 from jcheng5/bugfix/context-new

Fix 'Error in Context$new : could not find function "loadMethod"'