Remove unnecessary caveat in plugins docs about the require used in load.

jrburke · jrburke · commit d72e722e9546 · 2011-05-24T14:37:54.000-07:00
diff --git a/docs/plugins.html b/docs/plugins.html
@@ -86,7 +86,7 @@ <h3>
 
 <ul>
     <li><b>name</b>: String. The name of the resource to load. This is the part after the ! separator in the name. So, if a module asks for 'foo!something/for/foo', the foo module's load function will receive 'something/for/foo' as the name.</li>
-    <li><b>parentRequire</b>: Function. A local "require" function to use to load other modules. It is suggested that you <b>do not</b> use the name "require" for this argument name to avoid any possible undesired behavior with the static analysis done by the optimizer when it looks for require() calls. The text! and i18n! plugins normally use "req" for this argument. This require function has some utilities on it:
+    <li><b>parentRequire</b>: Function. A local "require" function to use to load other modules. This require function has some utilities on it:
     <ul>
         <li><b>parentRequire.toUrl(moduleResource)</b>:where moduleResource is a module name plus an extension. For instance "view/templates/main.html". It will return a full path to the resource, obeying any RequireJS configuration.</li>
         <li><b>parentRequire.isDefined(moduleName)</b>: Returns true if the module has already been loaded and defined.</li>
diff --git a/tasks.txt b/tasks.txt
@@ -9,19 +9,29 @@ Release Notes
 Next release
 --------------
 
+- text plugins after a build load xdomain?
+
 - relative modules IDs?
   - excludeShallow not excluding files loaded with the text plugin: email thread. Exclusions.
 
-- text plugins after a build load xdomain?
+- https://github.com/jrburke/requirejs/issues/104: define as a special dependency?
+- domReady plugin
+
+- empty: protocol support for build profiles?
+
 - Why can't plugins have dependencies? It is because the dependency is not fully evaluated.
   Maybe rethink it, there have been some cases where creating a plugin that uses the
   text plugin would be useful. However, would that mean the optimized result would include
-  the string twice in the output?
+  the string twice in the output? Well for the text plugin, could allow other plugins to
+  indicate "do not inline this dependency" to help with that.
 - replacement for modify that intercepts callbacks, holds off until another module loads them?
   - A way to show dependency graph too?
-- Set up official IE9 release VM
 - localeList for i18n.js support, for better Dojo support.
 - Minify the require.js files with UglifyJS.
+
+Docs:
+- http://requirejs.org/docs/api.html#jsfiles make the "plain script tag rules"
+  more of a bulleted list to call them out.
 - Pointer to motivations behind current thing, reason for dependencies.
 
 - https://github.com/jrburke/requirejs/pull/71: process by 2/21
