What JavaScript structure do you use with trigger.io? (trunk, knockout, ember, angular)

What JavaScript structure do you use with Trigger.io? I mean client structures of JS applications such as trunk, knockout, ember, angular?

We use angular.js here, but we have some significant problems when using a router for our application ... more details here https://groups.google.com/forum/?fromgroups#!topic/angular/XGDRAskA8qs , Trigger.io and using angular.js router does not work together (at least we could not get it to work)

Are you using some other JS infrastructure that you can recommend while working perfectly with trigger.io using the capabilities of the application router? (For example, I could see a similar router function in ember or backbone)

+5
source share
3 answers

Although we do not support one specific library, and our goal is to be compatible with them, I usually come to Backbone when starting the Trigger application. It is simple, lightweight, but powerful and has tons of nice extensions .

Angular, (, 12), - , Amber Smalltalk, .

- Backbone Sencha , - jQuery Mobile.

+5

jQuery, Backbonejs, Handlebars, Coffeescript, - -. .

, , , , .

+1

Angular JS JavaScript Framework. Angular, Trigger .

, -!!! IOS, Android WEB

, Angular . XHR Cross Origin.

-, Angular.JS + Zepto/JQuery. , CSS- .

The reason I recommend creating your own user interface, rather than using something like JQuery Mobile, or Sencha Touch 2 over the past 3 days, I have done extensive research and testing on a mesh-based JS Mobile UI Framework, and JQmobi is the only one which was close to fast, but he did not look good.

Creating your own system will reduce the size of the application, give you full control and ensure the smooth operation of the application. Your use will never know that it is not native, P

0
source

All Articles