Permalink
Browse files

Advanced Plugin Concepts: Changed "Firebug console" to "console"

Closes gh-453
  • Loading branch information...
1 parent ba4f586 commit b88d135f921d0a812371dba7e48bb05f9cb3e8d9 @scottgonzalez scottgonzalez committed Jan 8, 2014
Showing with 1 addition and 1 deletion.
  1. +1 −1 page/plugins/advanced-plugin-concepts.md
@@ -110,7 +110,7 @@ This technique makes it possible for others to define and ship transition defini
The technique of exposing part of your plugin to be overridden can be very powerful. But you need to think carefully about what parts of your implementation to expose. Once it's exposed, you need to keep in mind that any changes to the calling arguments or semantics may break backward compatibility. As a general rule, if you're not sure whether to expose a particular function, then you probably shouldn't.
-So how then do we define more functions without cluttering the namespace and without exposing the implementation? This is a job for closures. To demonstrate, we'll add another function to our plugin called "debug". The debug function will log the number of selected elements to the Firebug console. To create a closure, we wrap the entire plugin definition in a function (as detailed in the jQuery Authoring Guidelines).
+So how then do we define more functions without cluttering the namespace and without exposing the implementation? This is a job for closures. To demonstrate, we'll add another function to our plugin called "debug". The debug function will log the number of selected elements to the console. To create a closure, we wrap the entire plugin definition in a function (as detailed in the jQuery Authoring Guidelines).
```
// Create closure.

0 comments on commit b88d135

Please sign in to comment.