Quote from: Eminos at Nov 27, 2013, 04:22 AM
- It will not use ExtJS. Will use other/better/simpler front end tools. Angular.js is being heavily discussed.
Please correct me if any of the above statements are totally wrong.
It certainly won't use ExtJS. I'd say AngularJS is being discussed but wouldn't want to give the impression that any of the proposed front end frameworks are favored by the team at this point. What is favored by the community, well that is something we are trying to discover and always interested in hearing what people have to say.
It is true that I've advocated to try and reduce and eliminate as many dependencies as possible but whether or how much we adopt a given tool as part of the required or recommended toolkit is still to be determined.
After seeing some complaints about some of the tutorials and documentation from Angular users I decided I would go straight to the source and pick up the Angular book by O'reilly. I'm glad I did because it is an easy read and very informative.
I really like how both Angular and Ember take a markup based approach with templates. In ExtJS you can construct a component with JSON, but the markup it creates is overly complicated, full of inline styling and probably not the markup you would have written. Frameworks like Angular and Ember let you template your markup and then use data attributes and placeholders to define dynamic values. In other words, they stay much more out of your way.
☆ A M B ☆
☆ A M B ☆
☆ A M B ☆
]. Don't know about microservices. Sounds cool, but fraught with perils. Good to hear we're slowing crawling into the (early-)21st century way of doing things.
