jQuery Plugin To Return Delimited Value List Of Stack Element Attributes

Posted July 11, 2007 at 3:07 PM

Tags: Javascript / DHTML

I was trying to give Tony Petruzzi some feedback on his record sorting algorithm when I mentioned that with jQuery it would probably be quite easy to get a comma-delimited list of database IDs for use with the sort update. I assumed that there would be something already built into the jQuery API for doing this; however, with a quick look at the API, it looks like all the attribute-getting methods (attr()) work on the first item in the jQuery stack, not the set of elements.

I am sure that this ability is already part of the vast API (that I am just not seeing) or at least it is already covered by an existing plugin, but I thought this would be a perfect time for me to exercise some of my jQuery plugin writing skills. Below, I wrote a jQuery plugin called attrList(). This returns a delimited list of a given attribute for all elements in the current jQuery stack. You can also pass in an optional second argument, the delimiter, which is defaulting to comma.

 Launch code in new window » Download code as text file »

  • <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  • <html>
  • <head>
  • <title>Writing jQuery Plugin Demo</title>
  •  
  • <!-- Linked Files. -->
  • <script type="text/javascript" src="jquery.pack.js"></script>
  • <script type="text/javascript">
  •  
  • // This jQuery v1.1.3 plugin will return an delimited
  • // list of the given attribute of all elements in the
  • // current jQuery stack.
  •  
  • jQuery.fn.attrList = function( strAttribute, strDelimiter ){
  • // Start out with an empty value list. This list
  • // will eventually contain a delimited list of
  • // each attribute value.
  • var strValueList = "";
  •  
  • // Check to see if we were given a delimiter.
  • // By default, we will use the comma.
  • strDelimiter = (strDelimiter ? strDelimiter : ",");
  •  
  • // Loop over each element in the jQuery stack and
  • // add the given attribute value to the list.
  • this.each(
  • function( intI ){
  • // Get a jQuery version of the current
  • // stack element.
  • var jNode = $( this );
  •  
  • // Add the attribute to the list. When
  • // adding the value, check to see if
  • // we need to add the leading delimiter.
  • strValueList += (
  • (strValueList.length ? strDelimiter : "") +
  • jNode.attr( strAttribute )
  • );
  •  
  • }
  • );
  •  
  • // Return the value list.
  • return( strValueList );
  • }
  •  
  •  
  • // This will return the ID list of all inputs
  • // with the name, "ID".
  •  
  • function GetIDs(){
  • return(
  • $( "input[@name='id']" ).attrList( "value" )
  • );
  • }
  •  
  • </script>
  • </head>
  • <body>
  •  
  • <form>
  •  
  • <!---
  • Get some hidden values. The order of the
  • value is important. We want to make sure
  • this is reflected in the value list.
  • --->
  • <input type="hidden" name="id" value="4" />
  • <input type="hidden" name="id" value="5" />
  • <input type="hidden" name="id" value="1" />
  • <input type="hidden" name="id" value="2" />
  • <input type="hidden" name="id" value="3" />
  •  
  • <input
  • type="button"
  • value="Alert Value List"
  • onclick="alert( GetIDs() );"
  • />
  •  
  • </form>
  •  
  • </body>
  • </html>

Normally, the jQuery plugin code would be written to a separate Javascript file, but for demo purposes, I have just put it in the HEAD of the HTML page. If you were to click on the input button, the page would alert the following text:

4,5,1,2,3

This is the comma delimited list of the Value attribute of all input fields with the name "id". Look how freakin' easy jQuery makes things like this:

 Launch code in new window » Download code as text file »

  • $( "input[@name='id']" ).attrList( "value" )

As you can see in the code, the alerted value is reflective of the order that the hidden input fields appear in the document. This works because jQuery collects elements in its stack based on a top-down search. Meaning, elements that it finds earlier in the document are added to the stack first. Man, I love jQuery and I really finding it fun to write jQuery plugins.

Also, on a side note, this was run using the new and ultra fast jQuery v1.1.3. Good stuff!

Download Code Snippet ZIP File

Post Comment  |  Ask Ben  |  Permalink  |  Other Searches  |  Print Page




Learning ColdFusion 9 - ColdFusion 9 tutorials, samples, examples, demos

Reader Comments

Jul 11, 2007 at 6:21 PM // reply »
95 Comments

Neato, thanks for posting this. I'm still using prototype.js but jQuery seems pretty damn nice.


Jul 11, 2007 at 6:21 PM // reply »
56 Comments

Ben,

Thank you for all your help today. :)


Jul 12, 2007 at 7:17 AM // reply »
6,516 Comments

Hey guys, I just realized there is a big mistake in the above code. Once inside of a jQuery plugin, you are not supposed to refer to the "$" object any more (as jQuery might release it back to be compatible with existing code). Instead, in the above, all the "$" should be replaced with the "jQuery" variable reference.


Jul 12, 2007 at 12:17 PM // reply »
111 Comments

@Ben:

I'd recommend using arrays instead of strings. If the attribute value would contain a comma, the list will be wrong.

Even if you prefer to return a string instead of an array, use an array and then use the join() method. This is much more efficient than concatenating a string together. The performance won't be noticable in with a small dataset like in your example, but it's really noticeable when you string size grows.


Jul 12, 2007 at 12:23 PM // reply »
6,516 Comments

@Dan,

Good point. And, in fact, after I wrote this, someone pointed out to me a similar algorithm that mapped jQuery stack elements to an array of values and then joined the array at the end.

It's really cool how flexible jQuery is.


Post Comment  |  Ask Ben

Recent Blog Comments
Nov 20, 2009 at 11:32 PM
Five Months Without Hungarian Notation And I'm Loving It
I've used headless camel case for years for not only ColdFusion variables, but also SQL tables and fields... pretty much everything involving code. I also subscribe to the "don't abbreviate and clea ... read »
Nov 20, 2009 at 11:00 PM
Five Months Without Hungarian Notation And I'm Loving It
@Marcel, Yeah, I always err on the side of longer but more readable variable names. As for the camel casing of CF methods and the headless camel casing of custom items, I get around this by always ... read »
Nov 20, 2009 at 10:56 PM
Five Months Without Hungarian Notation And I'm Loving It
I use the following and love it: my.namespace.MyComponents.functionMethodsOrUDF() CONSTANT_VALUES_OR_PROPERTIES One thing I always try is to CamelCaseBuiltInColdFusionFunctions() so others can tell ... read »
Nov 20, 2009 at 5:38 PM
Learning ColdFusion 8: CFImage Part I - Reading And Writing Images
Hi Ben, Great article. I've been looking around to see if ColdFusion image engine can programatically create the following "wrap around" effect: http://www.creativepro.com/article/photoshop-s-she ... read »
Nov 20, 2009 at 5:35 PM
Maintaining ColdFusion Sessions Across SMS Text Message Requests Without Cookies
@Dave: I talked to Gert he suggested: <cfhttp method="get" url="http://{some cf website}" result="stuff" addtoken="yes" /> Note the addition of cfhttp attribute addtoken. That should persist y ... read »
Nov 20, 2009 at 5:23 PM
Maintaining ColdFusion Sessions Across SMS Text Message Requests Without Cookies
@Todd, Ahh, gotcha, yeah that makes sense. ... read »
Nov 20, 2009 at 5:17 PM
Maintaining ColdFusion Sessions Across SMS Text Message Requests Without Cookies
Ben, sorry if I didn't make this clear. You can make it work like that if you want, just put <cfset session.foo = 1> (and <cfset application.foo = 1>) in your OnRequestStart() and it reve ... read »