Geek asks and answers

Best practice for building an app?

I am here because I am asking a few questions about the structure of emberjs and the best way to create an application with it ... There are some questions that I hope someone can answer me:

  • Is there an embedded system for efficient memory management?
  • How to manage the controllers / views / models that will be introduced and destroyed during the application life cycle?
  • Should we declare all our controllers and views when the application starts?
  • Is there a way to automatically instantiate a view controller when a view is added to the DOM using the main controller (or stateManager)?

To resume my situation, I am testing ember functions and I understand all this well. But now I'm a bit confused and don't know how to structure the application. When you need to create views and their controllers, where and when you need to destroy the view controller for memory performance, etc.

Are there some of you who were like me at this time and there are answers to me?

All answers and help are really appreciated, and I thank you for your feedback (reviews)

See you guys!

Edit: I am using emberjs with requireJs to be able to separate javascript files. Is there a better solution or one built in for this?

(sorry for my English)

+3
source share
2 answers

requirejs emberjs, Ember require() minispade.js, AMD.

- 2 ember.js

  • grunt-neuter: require ('module'), neuter
  • grunt-ember-template: template.js, .

i , HMVC, , moduleController, app.js , , , app.js

- app.js
- modules/
     -- module1
         - module1Controller.js // initiate this in the app.js, which ain't required for ember
         - module1Model.js      // (if non ember) returns static methods that can be used by other modules
         - module1View.whatever // this should be compiled into the template.js, just easier to manage in the same folder
     -- module2
     -- module3 ...
0

More articles:


All Articles