Sign in through GitHub

Please read for an updated status on RailsCasts:

Learn more or hide this

Kevin Kornemann's Profile

GitHub User: baraka2000

Site: proofimaging.com

Comments by Kevin Kornemann

Avatar

'#each' feels a lot like ruby. e.g. array.each { |x| puts x }

Pretty sure that's by design. Made me smile when I saw that in ember.

I think it's interesting how emotional people get about frameworks, guess it's a matter of not wanting to waste your time learning something that may or may not be useful in the end. I know I've spent a lot of time learning ember, this better be the next big thing! :)

Avatar

holy crap, that's a awesome tutorial! Just what I was looking for, thanks!

Avatar

From my little research of angular I would agree, I can see using it here and there sort of thing. But ember has the potential to change how web apps are built moving forward, the way rails did 10 years ago... At least I think that's the ambition. Will depend in large part on the success or failure of ember-data which is still a work in progress. We shall see.

Avatar

http://reefpoints.dockyard.com/ember/2013/01/07/building-an-ember-app-with-rails-api-part-1.html

I just did this, pretty good. The promise of Ember, imho, is that everything runs on the client, and the server just becomes a database passing json back and forth for persistance... Ember-data still needs work from what I'm told.

Avatar

that's the million dollar question... If you find a good example, let me know...

Avatar

After trying to learn Ember for the past few weeks, starting with the peep code tutorial I can say I'm just starting to "get it." And like everyone on this post I've been reading a TON about ember vs angular. But I haven't actually tried angular. Angular is backed by google! While Ember is two guys in a room, and sure other contributors. But it's the old David and Goliath, and who doesn't want to route for the underdog?

I've also noticed the advanced js programmers tend to use Ember over angular (at least the ones I know), I can only think they have good reason. And from what I can gather it's that you can do more complex things with Ember, at greater speed, once past the learning curve.

Avatar

In my case I had to "wrap" in a jQuery function for it to work in development:

js
jQuery(function($){
        $("#announcement_<%= j params[:id] %>.announcement").remove();
});

no idea why, but it worked and all tests are passing!

Avatar

So, I have a riddle for the experts out there. Not sure if anyone checks these comments often, but here goes.

I'm using this in a custom spree app, so there is some name spacing going on. But I was able to get almost everything to work, making the required changes for the spree namespace. But the hide.js.erb just isn't firing. It's rendering fine, I can see in the log, the extra strange part is this works in production, just not in development...??? Which means my last test, "page.should_not have_content("Hello World")" fails...

Avatar

Like others who commented here I have been putting off learning js as long as possible. Rails is friendly, js is scary! But not anymore... Thanks Ryan! This really helped me. So much to learn still, but I have a lot more confidence now!

Avatar

I love the fact you did this TDD from the start, and I hope all future episodes have at least some TDD element. As a beginner, this actually made this more approachable for me, I know its working if my tests (your tests really) are passing. This is my first time reading comments on one of your episodes and man people are hard on you! Railscasts is my favorite tutorial site by far.... I always come back here and learn something new every time. Keep up the great work!