Objects.
That video sent me on a spiraling google-express to depression until... Introduction to AMD Modules - The Dojo Toolkit
|
What is a module?
A module is a value that can be accessed by a single reference. If you have multiple pieces of data or functions that you want to expose in a module, they have to be properties on a single object that represents the module. Practically speaking, it's overkill to create a module for a simple value likevar tinyModule = 'simple value';, but it would be valid. Modules start to make a lot more sense for modularizing your code - splitting it up into logical subsets for handling specific functionality. If you want to represent a person with information like name and address, perhaps even add some methods to your person, it starts to make sense to put all that code in a single location. A module is stored in your file system in a single file.
|
I'm sure the developers working hard on custom widgets are chuckling at me, but this has eluded me from every tutorial I have watched and read on Dojo. Nobody has clarified this until something clicked just now.
Basically...
|
define({
library: 'dojo',
version: 1.10
});
|
The module becomes nothing more than a JS Object with two attributes in this instance. And...
|
define(function(){
var privateValue = 0;
return {
increment: function(){
privateValue++;
},
decrement: function(){
privateValue--;
},
getValue: function(){
return privateValue;
}
};
});
|
The module becomes a JS Object with three methods (increment, decrement, getValue) that all manipulate a variable / attribute that is untouchable any other way.
Everything clicked. Now... to the batmobile!
