Update documentation for IES

doc/source/dev/interactive_environments.rst

@@ -205,9 +205,10 @@ We'll continue appending to our ``helloworld.mako`` the HTML code that's actuall
 
     <html>
     <head>
-    <!-- Loads some necessary javascript libraries. Specifically jquery,
-         toastr, and requirejs -->
+    <!-- Loads core Galaxy javascript libraries for a 'generic' entrypoint. -->
     ${ ie.load_default_js() }
+    <!-- This will load code from static/main.js, often used to handle things like login  -->
+    ${ ie.load_default_app() }
     </head>
     <body>
 
@@ -217,17 +218,11 @@ We'll continue appending to our ``helloworld.mako`` the HTML code that's actuall
     var notebook_login_url = 'unused';
     var notebook_access_url = '${ notebook_access_url }';
 
-    // Load code with require.js
-    ${ ie.plugin_require_config() }
 
     // Load notebook
-    // This will load code from static/helloworld.js, often used to handle
-    // things like Login. The load_notebook function will eventually append
-    // an IFrame to the <div id="main" /> below.
-    requirejs(['plugin/helloworld'], function(){
-        IES.load_when_ready(ie_readiness_url, function(){
-            load_notebook(notebook_access_url);
-        });
+    // The load_notebook function will eventually append an IFrame to the <div id="main" /> below.
+    IES.load_when_ready(ie_readiness_url, function(){
+        load_notebook(notebook_access_url);
     });
     </script>
     <div id="main" width="100%" height="100%">
@@ -261,7 +256,7 @@ authentication of users, so you don't have to worry about it, and can just
 assume that only the correct user will have access to a given notebook.
 
 In the ``static/`` directory, we generally create a ``js/`` directory below that,
-and create a ``{gie}.js`` (so, ``static/js/helloworld.js``) file in there.
+and create a ``main.js`` file in there.
 That file will have a function, ``load_notebook`` which will check if the GIE is available,
 and when it is, display it to the user.