I think you're close but missing a few vital pieces.
First, programmers that answer questions on SO would generally rather "Teach a man to fish" than simply hand you fish for dinner. Certainly not all are like that, but enough are that this is important.
In order to Teach a man to fish, it is usually a good idea to understand whether that man even knows what a fishing pole is. Once we've established a baseline of knowledge then we can more readily help.
The second piece is that a lot of those answering questions may never have done exactly what it is you are doing but can certainly help with giving alternative approaches or even simply seeing that one piece you are missing. We might even have better GoogleFu skills, as long as there is a starting point. A lot of us have day jobs and can't spend hours putting together a fully functional test case for your issue. However, most of us can lend a few minutes to correct items or point you in the right direction when there is something to work with.
In your referenced question, you mention you want to use SproutCore; however, there is absolutely no code or direction in how it's usage is necessary.
My question to you would be: have you even looked through the SproutCore API to figure this out? If not, then see #1 above. If you have, then post what interesting thing you've found AND the code you tried to get it to work.
My next question would be: why SproutCore? If you don't know if it will accomplish your goals, then why are you tying yourself to it? In other words, what other dependencies exist that you haven't referenced in your question? This line of questioning is only important if you haven't looked through SproutCore.
As others, and yourself, have noted simply saying "I looked all other the internet and couldn't find an answer" isn't enough.
The summary here is that there is almost no information to go by in order to answer your question. So, you got lucky that hvgotcodes was able to make a few assumptions and give you a few lines to get you going.