WinJS App creation
Loading babylon demos scenes links dynamically instead of hard coding links.
Merge remote-tracking branch 'remotes/nicolas-obre/WinJSApplication' into ourOwnBabylonJSWinJSApp
Added MSBuild target to automatically add personal demo files into application package.

Your files must be placed under "addToPackage" folder
WinJS application now using listView to show available scenes.
Listing all babylon demos scene in a group, and user customs scenes in an other group.
Adding a back button to go back to scenes listing page.
Adding a sandbox view to quickly test your own .babylon files
Starting renderLoop only on scene loaded, stopping on scene unload.
Testing if an activeCamera is set before trying to attach control since user can specify a default camera on his sceneLoadedCallback.
Creating a method to create default camera and light if not found in loaded scene.
Sandbox can now load a scene without camera or light, they will be created if not found in babylon file.
Adding a sandbox view on WinJSApplication.
Adding a link on the main page for the sandbox, with a different color.
Merge branch 'master' into WinJSApplication
Fixing an issue while trying to load babylon.*.*.js to BabylonJS project (wrong wildcard)
Generating last version of ourOwnBabylon.js
Adding a loading message when loading a scene on website and WinJS App (same as babylonjs website)
Adding a indication to highlight the sandbox when empty and locate the dropping zone.
Secured BuildOurOwnBabylonJSController actions
Call BuildOurOwnBabylonJS.exe once BuildOurOwnBabylonJSWinJSApp has been built

Note: whereas ourOwnBabylon.js is regenerated when F5 is pressed for BuildOurOwnBabylonJSServer, it's not when F5 is pressed for BuildOurOwnBabylonJSWinJSApp (you have to first build the app)
Refactoring loading message management, creation a new class to handle that (in a new project).
Merge pull request #182 from nicolas-obre/WinJSApplication

Tools improvement