Comments on: Tip: getting values from an options list http://www.yelotofu.com/2009/10/tip-getting-values-from-an-options-list/ "In building standards compliant sites we are creating a better Web for the future." Thu, 02 Feb 2012 00:55:06 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: Cloudgen http://www.yelotofu.com/2009/10/tip-getting-values-from-an-options-list/comment-page-1/#comment-12286 Cloudgen Fri, 14 May 2010 09:56:49 +0000 http://yelotofu.com/?p=579#comment-12286 Less code means less bandwidth and more efficiency in usage of cache for high traffic website (less hacking risk, less risk in DDOS attack, etc). Let's client's computers do the rest (that's the philosophy of Client-Side Javascript). So, as a software engineer from a B2B firm, I prefer one line version: var values=$.map($('#mySelectElement')[0].options, function(n){return n.value}); :P Less code means less bandwidth and more efficiency in usage of cache for high traffic website (less hacking risk, less risk in DDOS attack, etc). Let's client's computers do the rest (that's the philosophy of Client-Side Javascript). So, as a software engineer from a B2B firm, I prefer one line version:

var values=$.map($('#mySelectElement')[0].options, function(n){return n.value});

:P

]]> By: caphun http://www.yelotofu.com/2009/10/tip-getting-values-from-an-options-list/comment-page-1/#comment-8941 caphun Thu, 22 Oct 2009 17:38:32 +0000 http://yelotofu.com/?p=579#comment-8941 @dalin: Yes, definitely. Using values[] would be quicker than push but in most cases you won't notice. If I were wearing my optimization hat I'd also use <code>document.getElementById('mySelectElement')</code> to add to that. jQuery.map at its heart is a for loop with a callback. That's all it is. I see option one as a common pattern we run into often and option 2 as a possible solution to that pattern. @dalin: Yes, definitely. Using values[] would be quicker than push but in most cases you won't notice. If I were wearing my optimization hat I'd also use <code>document.getElementById('mySelectElement')</code> to add to that.

jQuery.map at its heart is a for loop with a callback. That's all it is. I see option one as a common pattern we run into often and option 2 as a possible solution to that pattern.

]]> By: dalin http://www.yelotofu.com/2009/10/tip-getting-values-from-an-options-list/comment-page-1/#comment-8937 dalin Thu, 22 Oct 2009 15:06:36 +0000 http://yelotofu.com/?p=579#comment-8937 If this was PHP I would say "bad idea". But I know much less about JavaScript so perhaps it's not. in option 1 you use language constructs (I would think it would be even better to use values[] rather than the method .push). In option 2 you use a method to run a callback function on each element. I'm guessing there's an order of magnitude difference in performance (if not more). Albeit with a select box there's probably not too many options to iterate through, but other scenarios may have significantly more. If this was PHP I would say "bad idea". But I know much less about JavaScript so perhaps it's not.

in option 1 you use language constructs (I would think it would be even better to use values[] rather than the method .push). In option 2 you use a method to run a callback function on each element. I'm guessing there's an order of magnitude difference in performance (if not more). Albeit with a select box there's probably not too many options to iterate through, but other scenarios may have significantly more.

]]>