Geek Answers Handbook

Design guidelines needed for a one-page webapp

We need to modify / rewrite the existing series of page / workflow screens on one standard page. The project itself will be to create one web page application in the context of a larger existing application.

Our goal is to leave the server-side implementation as possible. This means that we will not use the REST model, but rather only some of the forms presented in the java server. Each endpoint points to a JSP.

Each shape will be created as a widget. When one widget sends it, it can affect the value of other widgets that need to change their values ​​on the fly.

There seem to be 2 main options for single-page web applications: Backbone.js or Ember.js.

Given our requirements, which of these two (or any other frameworks) will work best? Or is there some other approach we should take together?

+4
source share
3 answers

There are probably many things you should learn.

Emberjs is 42k minified + gzip, and Backbone.js is only 5.6kb. Emberjs puts a lot of energy into it that doesn't give you bean bases.

Analyze if you need all these features. If your requirements are covered only by Backbone, IMO, you should give Emberjs a pass. Delivering all of these extra bits to use is not stupid.

With Emberjs, you'll also have to use jQuery. Not sure if you are already using it or not.

IMHO, I would use Emberjs if the single-page web application is supercomputer with a lot of feature requirements that should be sufficient for Backbone.

+1
source

Have you watched AngularJS ? This is more like EmberJS.

I would recommend you EmberJS at the moment, as it is more mature in terms of the ecosystem (Routing, Data, ...)

The backbone has a lower level than both precedents.

+2
source

Or do what you want.

I partly relate to Ember, as it provides a Routing / statechart structure that really helps to block application behavior. Not to mention that it is an MVC that will help you sort out your problems. Each shape or widget in your application will be the view that you define by binding the input to your model layer.

+1
source

More articles:


All Articles