Thanks. I did make some spaghetti that does something like that, and it works. Probably part of the learning process. I think the big issue is for me to approach problems in a different way: from the object-model perspective as opposed from the traditional DOM-oriented way.
Though I will say, I am not a huge fan of the rigid either/or ember attitude (not specific to ember, I realize). Learning ember is hard enough. Having to throw out all jquery almost makes it a dealbreaker. Yes, I know you can still use jquery for DOM stuff, but implementing it is a nightmare (at least for a beginner) and it's obviously frowned upon.
jquery and jquery plugins have added an incredible amount of richness to the web, and are deeply ingrained. All at a relatively low cost to developers - low learning curve, doesn't take alot of time/manpower to implement, alot of plugins available for re-use.
Ember and similar frameworks can provide the same level of richness and more, but the barriers to entry are enormous. It too me a whole day to figure out how to toggle a sub-set of a list without jquery (granted, I'm fairly dense), trying to re-create something like fancybox or bxslider in ember seems insurmountable.
Ember devs have gone to great lengths to make stuff "just work" - which is awesome. It's amazing what you can do with just 2 lines of code. If that same approach was taken to allow those new to ember to EASILY employ some of their old, trusted methods (like jquery DOM stuff), it would help ease the transition.
But, I'm still probably looking at it wrong!