StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6045614
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-05-18T13:36:12.353
FavoriteCount
0
LastActivityDate
2011-05-18T17:35:51.090
LastEditDate
2011-05-18T17:35:51.090
LastEditorUserId
607874
OwnerUserId
607874
ParentId
6044986
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
You need to define your default name and foo events in your defaults declaration: <pre><code>$.fn.myPlugin.defaults = { name: 'test', onFoo: function() { alert(this.name); }, onFoo2: function() { // your default behaviour for foo2 } }; </code></pre> Then, when someone calls your plugin, they can override the defaults, in this case <code>name</code>: <pre><code> $("#myControl").myPlugin({ name: 'test2' }); </code></pre> Note that they don't need to override onFoo, because it will display an alert with test2. Anyway, if they need to override it to do something different, then they should: <pre><code> $("#myControl").myPlugin({ name: 'test2', onFoo: function() { alert('onFoo overrired'); }, onFoo2: function() { alert('onFoo2 overrired'); } }); </code></pre> In your plugin, you invoke the foo methods as <pre><code>(function($) { $.fn.myPlugin = function(options) { var opt = $.extend({}, $.fn.myPlugin.defaults, options); // if onFoo is defined then call it if (opt.onFoo) { opt.onFoo(); } // if onFoo2 is defined then call it if (opt.onFoo2) { opt.onFoo2(); } } $.fn.myPlugin.defaults = { name: 'test', onFoo: function() { alert(this.name); }, onFoo2: function() { // your default behaviour for foo2 } }; }); </code></pre> You should use this technique for public methods/properties that you want to expose to the users of your plugin. I didn't tested but should work Edit You need to check if the event is set before calling it: <pre><code>// if onFoo is defined (not null) then call it if (opt.onFoo) { opt.onFoo(); } </code></pre> You are setting already an event for onFoo and onFoo2, but the user of your plugin might choose to disable it: <pre><code> $("#myControl").myPlugin({ onFoo: null }); </code></pre> In this case, although you have defined an <code>onFoo</code> event, the user of your plugin decided to ignore it, by setting it to <code>null</code>. So, even though you have defined an event, you never know what others will do with it, therefore it's better to be on the safe side and check for nullity. Once again, you need to be careful with what you expose to the end user, because setting/unsetting events should not break the basic functionality of your plugin
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAdding and overriding functions in existing plugin
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJose Rui Santos
UserOwnerUserId
1. USJose Rui Santos
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAdding and overriding functions in existing plugin
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.