AngularJS and Ionic (pdf) - PUG Challenge （AngularJS和离子(pdf)哈巴狗挑战）.pdfVIP

AngularJS and Ionic Building Mobile Applications by Aliaksandr Tarasevich Aliaksandr Tarasevich • Co-founder of Smart Web Squad • Work with Progress ~10 years (starting from 9.1D) • CHUI / GUI / GUI for .NET • Building hybrid Mobile solutions ~4 years • jQuery Mobile • mGWT • Ionic Framework • Was a big fan of GWT (and still like it) • 1/2 projects built using MongoDB with NodeJs Why we chose it: 1. It’s Java 1. Team still can write back-end and front-end in Java 2. You have all advantages of Java IDE 3. You can use all cool Java tools your like (for example Maven) 4. Need only a couple developers to wrap HTML/JS/CSS into Java classes 2. Compiler 1. Generates optimized JS/HTML/CSS code for each browser 2. Your generated code evolves as compiler evolving 3. You can extend compiler (write generator) to generate any code 3. Debugging 1. Debug your application right in IDE 4. uiBinder 1. Keep UI layer separate (designer / developers separation) 2. Allow to write UI in natural way (using HTML/CSS) 5. GWT Designer 1. Drag-and-drop designed (very similar to PDSOE) Why we moved from it: 1. It’s Java, but 1. Your web team MUST have JS/CSS/HTML experience to build good UX 2. You need to compile code to see result: 1. GWT DevMode is dead Browsers stopped supporting APIs 2. GWT SuperDevMode was very slow Supposedly fixed using incremental compile (available in 2.7) 3. Many popular WEB libraries are not available in GWT You can integrate any library you like using JSNI, but this can be time consuming 2. Compiler 1. Today’s browsers compatibility is not that big a problem 3. Debugging