开发者

Asynchronous Module Definition (AMD) and tight coupling?

开发者 https://www.devze.com 2023-03-30 23:59 出处:网络
So I have been reading up on the CommonJs Modules spec and looking at the dojo implementation and google closure implementation.The concept is pretty cool but I had the question of tight coupling of y

So I have been reading up on the CommonJs Modules spec and looking at the dojo implementation and google closure implementation. The concept is pretty cool but I had the question of tight coupling of your application using AMD.

Example from closure site:

goog.provide('tutorial.notepad');
goog.provide('tutorial.notepad.Note');

goog.require('goog.dom');
goog.require('goog.ui.Zi开发者_如何学Goppy');

/**
 * Iterates over a list of note data objects, creates a Note instance
 * for each one, and tells the instance to build its DOM structure.
 */
tutorial.notepad.makeNotes = function(data, noteContainer) {
  var notes = [];
  for (var i = 0; i < data.length; i++) {
    var note = 
      new tutorial.notepad.Note(data[i].title, data[i].content, noteContainer);
    notes.push(note);
    note.makeNoteDom();
  }
  return notes;
};

/**
 * Manages the data and interface for a single note.
 */
tutorial.notepad.Note = function(title, content, noteContainer) {
  this.title = title;
  this.content = content;
  this.parent = noteContainer;
};

/**
 * Creates the DOM structure for the note and adds it to the document.
 */
tutorial.notepad.Note.prototype.makeNoteDom = function() {
  // Create DOM structure to represent the note.
  this.headerElement = goog.dom.createDom('div',
      {'style': 'background-color:#EEE'}, this.title);
  this.contentElement = goog.dom.createDom('div', null, this.content);
  var newNote = goog.dom.createDom('div', null,
      this.headerElement, this.contentElement);

  // Add the note's DOM structure to the document.
  goog.dom.appendChild(this.parent, newNote);
  return new goog.ui.Zippy(this.headerElement, this.contentElement);
};

So my question isn't there tight coupling occurring here? If you provide tutorial.notepad to the application and some other module requires it and functionality changes within tutorial.notepad isn't there a tight coupling problem here. Basically you are chaining together modules that should be able to live on there own thus creating a fragile architecture.

I could be thinking about this wrong, if anyone can talk about this in an architecture context that would be appreciated or any resources about architecting a loosely coupled AMD architecture.

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号