Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First, you will generally want to handle the command within your extension method. Second, you should be attaching configurations to each item...</p> <pre><code>(function($){ var defaultOptions = { /* default settings here */ }; //called on the native object directly, wrap with $(obj) if needed. function initializeObject(obj, options) { //assign the options to the object instance. $(obj).data('myPlugin-options', $.extend(defaultOptions, options) ); //do other initialization tasks on the individual item here... } function updateObject(obj) { // use $(obj).data('myPlugin-options'); } function setOption(obj, key, value) { var d = $(obj).data('myPlugin-options'); d[key] = value; $(obj).data('myPlugin-options', d); } $.fn.myPlugin = function(command, option, val) { if (typeof command == "object") { //initialization return this.each(function(){ initializeObject(this, command); }); } if (typeof command == "string") { // method or argument query switch (command.toLowerCase()) { case 'option': //get value, return the first item's value if (typeof val == undefined) return this.eq(0).data('myPlugin-options')[option]; //set option value return this.each(function() { setOption(this, option, val); }); case 'update': return this.each(function() { updateObject(this); }); //other commands here. } } } })(jQuery) </code></pre> <p>With the above example, you have a generic template for a jQuery extension, It's usually good form to have the following convention for use..</p> <pre><code>Initialization: $(...).myPlugin({ initialization-options-here }); Command: $(...).myPlugin('command-name'); //where command can be update, etc. Get Option: var myValue = $(...).myPlugin('option', 'option-name'); Set Option: $(...).myPlugin('option', 'option-name', newValue); </code></pre> <p>Updated to use .data off of each individual obj.</p>
    singulars
    1. This table or related slice is empty.
    1. POjQuery Plugin Authoring - Set different options for different elements
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTracker1
    1. USTracker1
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POjQuery Plugin Authoring - Set different options for different elements
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAwesome, thanks. I was missing the 'attaching configurations to each object' part. I ended up using $.data to attach the config instead of your suggestion. Are there any pros/cons to either method? I figure they are probably about the same. Also, I like your plugin setup a lot, very similar to jQuery UI. I have adopted that as well =) Thanks!!
      singulars
      1. PO
      1. USRyan
    2. COI wouldn't use .data for every object, since the plugin might use event delegation..also, if the plugin is called without any arguments, what then? in your example nothing would happen..
      singulars
      1. PO
      1. USvsync
    3. CO@vsync It was mainly a guideline... could check for undefined as well as object initializing to defaults. I also think data application should apply to each item, since each plugged item could be adjusted to have different options later. I know that it's not perfect... just trying to point out the general pattern that seems to be used in UI and other jQuery extensions.
      singulars
      1. PO
      1. USTracker1
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload