4 ms·

I really wish there was some thorough examples of using Ember + Ember-Data. Ideally it would be backend agnostic (mocked client side xmlhttprequest) and go from

by Nemcue 12y ago

I really wish there was some thorough examples of using Ember + Ember-Data. Ideally it would be backend agnostic (mocked client side xmlhttprequest) and go from doing simple things like saving a model all the way to doing more complex things like you showed. Drupal for instance has a /really/ great project that maintains a bunch of thorough examples (https://drupal.org/project/examples https://drupal.org/project/examples) which were indispensable when I did Drupal a while back.

adamnemecek 12y ago
There really should be better examples. In the mean time, you should check out the Balanced Dashboard, I've learned a good amount from it https://github.com/balanced/balanced-dashboard https://github.com/balanced/balanced-dashboard
pyre 12y ago
It's kind of funny, but I don't even remember simple things being spelled out. For example, in their use cases all of the models and routes are single words like: post, comment, todo, etc. In some places, you see 'Post' and others 'post', but there is nothing explicitly spelling out how that works for multi-word items (e.g. MultiWord => multiWord). Same with underscores in route names (e.g. route name 'multi_word.item.index' => MultiWordItemIndexRoute).
- deleted 12y ago
  [deleted]
- zyxley 12y ago
  Yeah, the magic rejiggering of names everywhere with no clear documentation of what mapped to what† killed my interest in Ember the first time I tried to actually use it for even a fairly simple app. † Plus the enforced snakeCase/CamelCase everywhere, but that's more to do with me far preferring names_with_underscores in general.
  - pyre 12y ago
    This is one of the reasons that Ember.js + Rails seems like the preferred setup. Ember.js + Python gets you into converting underscored names to camelcase names.
  - steveklabnik 12y ago
    http://emberjs.com/guides/concepts/naming-conventions/ http://emberjs.com/guides/concepts/naming-conventions/ ?
    - pyre 12y ago
      That's a good generic overview but doesn't hit how the code handles the edge-cases.
  - basiliothecat 12y ago
    Maybe to clear some confussion, snake case is exactly naming_things_with_underscores.
    - steveklabnik 12y ago
      And SCREAMING_SNAKE_CASE, one of my favourite names for a convention ever, is when snake case is in all caps ;)
- calgaryeng 12y ago
  Replying to the sibling. There was documentation of how the names changed - you just need to know where to look: https://github.com/emberjs/data/blob/master/TRANSITION.md https://github.com/emberjs/data/blob/master/TRANSITION.md
  - pyre 12y ago
    I'm not talking about transitioning from 'old' Ember Data to 'new' Ember Data. I'm talking about someone completely new to Ember looking through the examples and documentation. Even if they were looking through the repository, it would be easy to overload a file called "TRANSITION.md" if you don't need to transition from an older Ember Data version.

by Nemcue 12y ago

adamnemecek 12y ago

There really should be better examples. In the mean time, you should check out the Balanced Dashboard, I've learned a good amount from it https://github.com/balanced/balanced-dashboard https://github.com/balanced/balanced-dashboard

pyre 12y ago

It's kind of funny, but I don't even remember simple things being spelled out. For example, in their use cases all of the models and routes are single words like: post, comment, todo, etc. In some places, you see 'Post' and others 'post', but there is nothing explicitly spelling out how that works for multi-word items (e.g. MultiWord => multiWord). Same with underscores in route names (e.g. route name 'multi_word.item.index' => MultiWordItemIndexRoute).

deleted 12y ago
[deleted]
zyxley 12y ago
Yeah, the magic rejiggering of names everywhere with no clear documentation of what mapped to what† killed my interest in Ember the first time I tried to actually use it for even a fairly simple app. † Plus the enforced snakeCase/CamelCase everywhere, but that's more to do with me far preferring names_with_underscores in general.
- pyre 12y ago
  This is one of the reasons that Ember.js + Rails seems like the preferred setup. Ember.js + Python gets you into converting underscored names to camelcase names.
- steveklabnik 12y ago
  http://emberjs.com/guides/concepts/naming-conventions/ http://emberjs.com/guides/concepts/naming-conventions/ ?
  - pyre 12y ago
    That's a good generic overview but doesn't hit how the code handles the edge-cases.
- basiliothecat 12y ago
  Maybe to clear some confussion, snake case is exactly naming_things_with_underscores.
  - steveklabnik 12y ago
    And SCREAMING_SNAKE_CASE, one of my favourite names for a convention ever, is when snake case is in all caps ;)
calgaryeng 12y ago
Replying to the sibling. There was documentation of how the names changed - you just need to know where to look: https://github.com/emberjs/data/blob/master/TRANSITION.md https://github.com/emberjs/data/blob/master/TRANSITION.md
- pyre 12y ago
  I'm not talking about transitioning from 'old' Ember Data to 'new' Ember Data. I'm talking about someone completely new to Ember looking through the examples and documentation. Even if they were looking through the repository, it would be easy to overload a file called "TRANSITION.md" if you don't need to transition from an older Ember Data version.