AMD and Dojo 1.7 questions

Question

Simple question.

Does AMD DOJO implementation support these type of declarations?

1. text!./plain.html

   define(["../Widget","text!./plain.html"],
     function(Widget,plain){
     return new Widget({name:"mainApp",template:plain});
   }); 
   

2. Load non-modules, let's say underscore.js

   require(['dir/underscore.js'], function(){
    _.reduce ...
   });
   

Answer 1

Yes, but the precise syntax is different to that used in the question.

• The Dojo Loader (1.7)
  • Plugins
    • dojo/text

The plugin for loading character data is dojo/text.

The extension should not be used when loading a JavaScript library and the location of the file is set via either a relative of the dojotoolkit base or a packages location declaration in dojoConfig:

require(['underscore'], function( _ ){
 _.reduce ...
});

Configure the namespace in the Dojo configuration to avoid messy import paths - see dojoConfig in the loader documentation.

Also, consider using the dojo/global module and/or defining a Dojo module as a wrapper for Underscore.js:

//_.js
define(['dojo/global', 'underscore'], function(global){
  return global._
});

With the above consideration, you must have loaded the actual .js file manually. If in conjunction with the dojo/text plugin, one would create a wrapper which also loads the required JS and evaluates it, following could do the trick.

/var/www/dojo-release-1.7/ext_lib/_.js - this sample file is hierachially placed in a library namespace, alongside dojo, dijit, dojox

define(['dojo/global', 'dojo/text!./Underscore.js'], function(global, scriptContents){
  global.eval(scriptContents);
  return global._ // '_' is the evaluated reference from window['_']
  /** 
   * Alternatively, wrap even further to maintain a closure scope thus hiding _ from global
   *  - so adapt global.eval to simply eval
   *  - remove above return statement
   *  - return a dojo declared module with a getInstance simple method
  */
  function get_ () { return _ };
  var __Underscore = declare('ext_lib._', [/*mixins - none*/], {
        getInstance: get_
  });
  // practical 'static' reference too, callable by 'ext_lib.getInstance' without creating a 'new ext_lib._'
  __Underscore.getInstance = get_;
  return __Underscore;
});

A sample of defining own modules using declare here Note: this code is untested; feel free to add corrections.