gfranko / jq-boilerplate Goto Github PK

The _callbackSupport() realization requires the plugin obj to be stored in the element's data.

callback.call(self.$element.data(dataName), self.$element);

but according tho this

                // Instantiates a new `Plugin` object and creates the plugin
                plugin = new Plugin(this, options, dataName).create();

                /*
                Stores the new `Plugin` object in the calling element's 
                jQuery `data` method
                */
                $.data(element[0], dataName, plugin);

when create is called, data is still not filled.
Therefore all callbacks originating from "create" will get empty context.

Found your plugin boilerplate searching wildly for how to provide an API so other programmers can add custom callbacks.

I'm still green regarding custom/namespaced events. You provide a private space for it, but i'm not sure what to do with it. A brief explanation:

My plugin builds on top of jQueryUI's Menu widget. It adds an activator button, hides the menu, and when the button is clicked it toggles visibility of the menu. Seems simple enough. But i wanted to use it in an environment with tables where each menu acts specifically on the data in a given table row. And jQueryUI doesn't provide a lot of sample info on how to give menu items custom callbacks. Also, when one menu is opened, others on the page should hide, etc...

So i have a working plugin, but i decided to see if i could clean it up with your boilerplate & want to know more about utilizing _events().