Databases
StackOverflow2013
Postsdbo
POWeb app architecture using Ember. Where should animation logic sit?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWeb app architecture using Ember. Where should animation logic sit?
    primarykey
    data
    text
    <p>I am building a web app using Ember. Drag and drop ( and other animations such as automatic slide ) is a significant part of how the user will interact with the app. </p> <p>I've already decided all animation logic will sit by itself in an Ember mixin class vis a vis this blog:</p> <p><a href="http://www.dynopia.com/index.php/en/blog/article/771/ember-js-animations-with-jquery-animate" rel="nofollow">http://www.dynopia.com/index.php/en/blog/article/771/ember-js-animations-with-jquery-animate</a></p> <p>However, I am little confused whether I should have two Views per draggable element, one to render the element and one to handle the animation logic?</p> <p>In addition, after the animations is complete, the current css attributes of the element should be updated in its corresponding model. I can take care of this with a simple two way binding between view and model, ie:</p> <pre><code>/** element view **/ App.elemOneView = Ember.View.create({ name: 'element One', cssAttr: {}, ... }); /** element controller**/ App.elemController = Ember.ArrayController.create({ content: [], .... }); /** element model **/ App.elemOneModel = Ember.Model.create({ name: 'element one', cssAttrBinding: 'App.elemOneView.cssAttr' ... }); </code></pre> <p>My question is that it frowned upon that model is directly bound to view, even though there is a controller layer in between them? Should I have both view and model sync to an intermediate object?</p> <p>Note: currently, I plan on declaring view ( for animation logic ) and model ( to store css attributes, among other things ) for each element that appears on the page, so there will be lots of views and models. I should ask whether this is bad too?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKristian
    1. USchibro2
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWeb app architecture using Ember. Where should animation logic sit?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWeb app architecture using Ember. Where should animation logic sit?
      1. USKristian
      1. VTFavorite
    3. VO
      singulars
      1. POWeb app architecture using Ember. Where should animation logic sit?
      1. USJack Johnson
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload