Live data from Hacker News

Show HN: Ember Table by Addepar

addepar.github.com

31–40 of 51 posts

Re: Show HN: Ember Table by Addepar

#32
post #4

This looks great. Can anybody recommend a similar library (i.e. lazy-rendering table component) that either doesn't depend on a JS framework or uses backbone.js? I know Slickgrid but find it a bit too clunky on the whole, and re-styling it is awkward since its DOM isn't exactly straightforward.

[deleted]

Re: Show HN: Ember Table by Addepar

#34
post #27
post #20

A feature rich, reliable table view in SproutCore (from which Ember was forked) has been a highly requested feature for at least 4 years. I'm glad that someone has finally done so, but I am also disappointed that it was so difficult.

This is incorrect. Ember.js is not a fork of SproutCore, and they share no code. Ember.js just borrows some of the best features of SproutCore, like bindings and computed properties. Additionally, the Addepar guys put this together in a few weeks. I'm unsure where your claim that this was difficult is coming from.

Perhaps they no longer share code, but they share architecture which was responsible for the lack of table view in SproutCore. The history of the two projects is long and complicated, and most of the people working on Ember were SproutCore developers. Ember was even "SproutCore 2.0" for a long time.

SproutCore's current table view demo still stutters and lacks the features of the table view featured here[1]. If the Addepar guys put this together quickly, it's because there are no longer architectural road blocks preventing them.

[ 1 http://demo.sproutcore.com/table_view/ ]

Re: Show HN: Ember Table by Addepar

#35
post #34
post #27

Earlier quoted context omitted.

This is incorrect. Ember.js is not a fork of SproutCore, and they share no code. Ember.js just borrows some of the best features of SproutCore, like bindings and computed properties. Additionally, the Addepar guys put this together in a few weeks. I'm unsure where your claim that this was difficult is coming from.

Perhaps they no longer share code, but they share architecture which was responsible for the lack of table view in SproutCore. The history of the two projects is long and complicated, and most of the people working on Ember were SproutCore developers. Ember was even "SproutCore 2.0" for a long time. SproutCore's current table view demo still stutters and lacks the features of the table view featured here[1]. If the A…

Tom is one of the two main developers you're talking about when you say "most of the people working on Ember were SproutCore developers."

I think the "lack of architectural road blocks" is called ember.js. If you're working with Sproutcore and haven't spent time with ember.js, you should take a look. It has a bit of a learning curve but it's very powerful once you get past that. The guys who built the table would tell you that instead of being an architectural road block, ember.js was the power that made the table possible. That's why it's called ember-table.

Re: Show HN: Ember Table by Addepar

#36
post #35
post #34

Earlier quoted context omitted.

Perhaps they no longer share code, but they share architecture which was responsible for the lack of table view in SproutCore. The history of the two projects is long and complicated, and most of the people working on Ember were SproutCore developers. Ember was even "SproutCore 2.0" for a long time. SproutCore's current table view demo still stutters and lacks the features of the table view featured here[1]. If the A…

Tom is one of the two main developers you're talking about when you say "most of the people working on Ember were SproutCore developers." I think the "lack of architectural road blocks" is called ember.js. If you're working with Sproutcore and haven't spent time with ember.js, you should take a look. It has a bit of a learning curve but it's very powerful once you get past that. The guys who built the table would tel…

I am well aware that he is, but since he didn't say so it sounds accusatory if I point that out. If you read my original comment, I said that SproutCore has been missing a table view for years, and that it wasn't an oversight but something that people attempted to fix a number of times. So if Ember has solved the problem, I am glad it has finally happened. But as someone who has been trying to build projects on SproutCore for years and finding roadblocks, this was long overdue. Perhaps Ember has attained the maturity that SproutCore never seemed to be able to find.

The guys who built the table would tell you that instead of being an architectural road block, ember.js was the power that made the table possible.

That's what it means to be a roadblock... if you don't run into one, you would never imagine that there could have been one. A roadblock is what happens when you attempt to do something logical and find out that due to something outside of your control, it's realistically never going to happen.

Re: Show HN: Ember Table by Addepar

#39
post #2

Congratulations to the guys at Addepar on releasing this. They have been contributing an amazing amount of stuff to the Ember.js community—not least of which is helping us build Ember Data. Probably my favorite thing about Ember is that it isn't built by academics toiling away in an ivory tower; it's driven by real-world problems that web developers are facing. Our goal is to provide a set of tools that allow develop…

"Probably my favorite thing about Ember is that it isn't built by academics toiling away in an ivory tower; it's driven by real-world problems that web developers are facing."

So your favorite thing about your project is that it was written by you?

Re: Show HN: Ember Table by Addepar

#40
Your table looks very nice, thanks a lot for sharing. We have one in our app that is pretty similar, but not as well developed. I am considering replacing the one in our app with this one.

My only reservation is adding underscore.js to our codebase. Not that I have anything against underscore, but we already Ember, jQuery and jQuery UI. I'm hesitant to add another major dependency. How hard of a dependency is Underscore.js? Could it be easily separated.

Post reply on HN