Comments on: JSON Selects http://muffinresearch.co.uk/archives/2006/07/19/json-selects/ the personal blog of Stuart Colville covering modern web development techniques and best practices Sat, 06 Sep 2008 01:38:29 +0000 http://wordpress.org/?v=2.5.1 By: Ismael http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6873 Ismael Sun, 23 Jul 2006 21:46:36 +0000 http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6873 Wow, that's kinda shocking! I guess I'll have to go through thousands of lines of code I've made :( (it works, though) Wow, that’s kinda shocking! I guess I’ll have to go through thousands of lines of code I’ve made :( (it works, though)

]]> By: Stuart Colville http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6859 Stuart Colville Sun, 23 Jul 2006 12:00:27 +0000 http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6859 @Ismael: Thanks for the comment. Re: the quotes: That's not the case, in valid JSON, property names are always quoted. @Ismael: Thanks for the comment. Re: the quotes: That’s not the case, in valid JSON, property names are always quoted.

]]> By: Ismael http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6831 Ismael Sun, 23 Jul 2006 04:25:03 +0000 http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6831 Nice! But... Shouldn't this <code> keyboards:{ "HRP":"Harpsichord", "HOR":"Hammond Organ", "FRO":"Fender Rhodes", "WEP":"Wurlitzer EP200" } </code> be like this? <code> keyboards:{ HRP:"Harpsichord", HOR:"Hammond Organ", FRO:"Fender Rhodes", WEP:"Wurlitzer EP200" } </code> I mean, those are attribute names in an object, not keys in a hash, right? Nice!
But… Shouldn’t this


keyboards:{
"HRP":"Harpsichord",
"HOR":"Hammond Organ",
"FRO":"Fender Rhodes",
"WEP":"Wurlitzer EP200"
}

be like this?


keyboards:{
HRP:"Harpsichord",
HOR:"Hammond Organ",
FRO:"Fender Rhodes",
WEP:"Wurlitzer EP200"
}

I mean, those are attribute names in an object, not keys in a hash, right?

]]> By: Stuart Colville http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6637 Stuart Colville Wed, 19 Jul 2006 18:55:36 +0000 http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6637 @Chris: You make some good points there and those are some viable alternatives. I am not so anal that I <em>must</em> use the DOM for everything, and I can see that that setting the innerHTML to an empty string would be much more likely to be faster compared to my loop. @Chris: You make some good points there and those are some viable alternatives. I am not so anal that I must use the DOM for everything, and I can see that that setting the innerHTML to an empty string would be much more likely to be faster compared to my loop.

]]> By: Chris Heilmann http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6627 Chris Heilmann Wed, 19 Jul 2006 13:47:36 +0000 http://muffinresearch.co.uk/archives/2006/07/19/json-selects/#comment-6627 The removeChildren() is a good generic function but could be quite expensive. You could also remove all options by setting the options.length property to 0, or by simply setting innerHTML to an empty string. Sometimes the old school form stuff is much faster and straight forward. If I were a fetishist I'd do a benchmark, but the weather is too nice. The removeChildren() is a good generic function but could be quite expensive. You could also remove all options by setting the options.length property to 0, or by simply setting innerHTML to an empty string.
Sometimes the old school form stuff is much faster and straight forward. If I were a fetishist I’d do a benchmark, but the weather is too nice.

]]>