Enhance documentation, jsFiddle examples, and test suite parametrization for different f2 packages

[ilinkuo]

There are three f2 files under sdk/

• f2.debug.js
• f2.min.js
• f2.no-third-party.js which needs a little more documentation as to what they are.

f2.min.js is the same as f2.js at the top-level. Both are the minified version of f2.debug.js, with all dependencies wrapped in a closure. f2.no-third-party.js is the same code with all dependencies removed.

• Should there also be a f2.no-third-party.js minified version, or at least, a documented grunt task to produce one?
• The f2.no-third-party.js will need some dependencies to work -- json2, eventemitter2, easyxdm, jquery, etc. A jsfiddle showing this would be nice.
• If the automated jasmine testing involves testing f2.no-third-party.js separately from f2.min.js, that would be good. Ideally, the entire test suite can be parametrized so that a user can pass in particular combinations of versions of jQuery, f2.no-third-party.js, etc. to see if they pass the tests.
• If no iframes secure loading of F2 Apps is done, then easyXDM isn't needed, right? Adding notes like this would be useful as an interim measure before the switch to AMD. After the switch, https://github.com/jensarps/AMD-feature can be used to manage this kind of dependency.

[markhealey]

Hi, version 1.2 introduces many jsFiddles on the documentation site. We will evaluate the other items in this issue.

[markhealey]

@ilinkuo, regarding your f2.no-third-party.js comments made here, review the changelog for version 1.2.1. New F2 packages were added which allow Container Developers to pick-and-choose a version of F2 most suited for their needs. To your point, if no secure apps are required, then easyXDM isn't needed. In this case, f2.no-easyXDM.js is the answer. There are 4 packages available.

Let us know if there's anything else.