Extract "bootstrap-modal" code into a plugin

[montlebalm]

As an F2 developer, I'd like to remove the "bootstrap-modal" code from the core library, so I can remove the dependency on jQuery (Issue #39).

I haven't dug into it, but my gut feeling is that we can pull out the UI code around modals and put it an F2 plugin. This would be a great opportunity to create a real plugin and simplify the core lib at the same time.

[montlebalm]

I create a new branch and bootstrap plugin repo to attempt to solve this issue.

Changes:

• Add F2.UI.alert and F2.UI.confirm, which map directly to F2.UI({ ... }).Modals.alert and F2.UI({ ... }).Modals.confirm respectively. They can be called without instantiating F2.UI.
• Changes default F2 alert and confirm modals into system defaults (e.g., window.alert and window.confirm).

I think we should move towards a model where the container provides the styling and HTML for all modals. As it is, we're alienating container developers who choose not to use Bootstrap. We should instead standardize on an API to invoke a modal and allow the container to choose what form that takes. Plugins can be created to drop in fully baked solutions for various UI frameworks.

[markhealey]

In general, good stuff here, thanks.

We'd discussed separation between the F2 development standard (the spec) and any UI a while back though I couldn't track down the comments. I recall a consensus on the subject so let's move on it.

[brianbaker]

F2.UI is no more for v2.