change in approach to APIs that create persistent DOM objects
3 views
Skip to first unread message
Myk Melez
Oct 28, 2010, 2:31:33 PM10/28/10
to mozilla-la...@googlegroups.com
Rocketeers!
Bug 494238 hosted a discussion about our approach to APIs like Panel that create persistent DOM objects, for which our current approach is to require consumers to first construct the object (var panel = Panel({ ... })) and then call an add() function to create the persistent DOM objects (panels.add(panel)).
As a result of that discussion and other conversations, I decided in bug 596053 to switch to a model whereby constructing an object immediately creates those persistent DOM objects without requiring consumers to call an add() function.
This change will make addon development simpler and more efficient moving forward, so it's an important and valuable change to make (along with the E10S and EventEmitter changes we are making over these last few development cycles before we declare a beta release and stop making large breaking changes).
Nevertheless, it is a pretty significant change to a number of our APIs (Panel, Widget, etc.) that will affect many existing addons. Keep it in mind as you test the next version of the SDK, which is scheduled to contain this change!
-myk
Bug 494238 hosted a discussion about our approach to APIs like Panel that create persistent DOM objects, for which our current approach is to require consumers to first construct the object (var panel = Panel({ ... })) and then call an add() function to create the persistent DOM objects (panels.add(panel)).
As a result of that discussion and other conversations, I decided in bug 596053 to switch to a model whereby constructing an object immediately creates those persistent DOM objects without requiring consumers to call an add() function.
This change will make addon development simpler and more efficient moving forward, so it's an important and valuable change to make (along with the E10S and EventEmitter changes we are making over these last few development cycles before we declare a beta release and stop making large breaking changes).
Nevertheless, it is a pretty significant change to a number of our APIs (Panel, Widget, etc.) that will affect many existing addons. Keep it in mind as you test the next version of the SDK, which is scheduled to contain this change!
-myk
Reply all
Reply to author
Forward
0 new messages