Download as PDF, PPTX
Uploaded byMarcos Vinícius
Javascript toolkit
The document outlines a structured toolkit for web application developers to navigate the rapidly evolving landscape of JavaScript technologies and frameworks. It highlights agile methodologies, continuous integration, and various tools for build automation, dependency management, testing, and application development. The emphasis is on organizing practices and utilizing best design patterns to support increasingly complex web applications.
More Related Content
Javascript toolkit
- 1. THE JAVASCRIPT TOOLKIT An attemptto organize the recent explosion of Javascript based technologies and frameworks into a coherent toolkit to be used by a web application developer. 1 Marcos Vinicius @bymarkone Renan Martins @renan89
- 2. THE IDEA OFTHE TOOLKIT 2 The Idea Of A Toolkit
- 3. An attempt toorganize the recent explosion of Javascript based technologies and frameworks into a coherent toolkit to be used by a web application developer. purpose:
- 4.
- 5. AGILE PURPOSE FORDELIVERY 5 Deliver Fast Deliver Often Deliver Value
- 6. AGILE CHANGES INPROCESS 6 Iterations User Stores Planning Stand Ups Retrospectives Inception Scrum - Lean - XP Kanban Team Communication …
- 7. TECHNICAL SUPPORT FORAGILE 7 Continuous Delivery Continuous Integration Evolutionary Architecture Evolutive Design TDD Lot’s of Automation Programming Languages Design Patterns …
- 8. AGILE - TOOLKIT 8 Gradle,Maven, Ant, Ivy jUnit, TestNG, Cucumber Design, Analysis, Architecture Patterns Jenkins, GO, Snap, Bamboo Java, Ruby, Scala, Python, Clojure, Racket, Javascript www.thoughtworks.com/radar/
- 9.
- 10.
- 11.
- 12. NEED MOTIVATION TOOLS Scaffold Severaltools. Several ways. Several Practices. Need to organize, and give some good foundation - best practices, good design. yeoman Build / Automation Lots of tasks to execute. Compile. Test. Minify. Concat. Etc. grunt, gulp, broccoli Dependency Management Applications are getting complex. They rely on several other libraries and frameworks. bower, component, NPM Dynamic Loading Big projects are split among several pieces of js for the sake of modularization. No all of them should be loaded at the same time. require, curl, broserify, webpack Testing Testing is all around. Need to tests on different browsers, need to write the tests, need to run the tests, need to report test results. karma, jasmine, phatom, mocha, qunit, protractor, sinon, sourcelabs, duck angular Application Applications on web are getting complex, need for frameworks that support app development. angular, backbone, ember, knockout Dom Utilities DOM selection and maniputation, some auxiliary functions, need for utilities that make work simple (and cross- browser) jquey, zepto Language Utilities Clean code, functional programming style, reactive programming features, helpers and utilities lodash, underscore, promise, fn, q CI Continuous integration, continuous delivery, continuous deployment travis-ci, jenkins, concrete, semaphore, go, snap Other Languages Have a syntactic sugar element, or even completely different syntax (that in the end turn into javascript to run in the browser) coffeescript, clojurescript, typescript Other Javascript ?? concat, minify, uglify, lint, jshint, watch, page, director, crossroads, moment.js 12
- 13. 13 WHAT TOOLS CSS Preprocessorssass, less Preprocessors Libs compass, bourbon CSS Helpers susy, zenGrids, neat, normalize, modernizr, flexbox CSS Frameworks boostrap, foundation, skeleton
- 14. Let’s talk aboutthis needs, And take a look at some tools 14
- 15. SCAFFOLD 15 Several tools. Severalways. Several Practices. Need to organize, and give some good foundation - best practices, good design.
- 16.
- 17. BUILD - AUTOMATION 17 Lotsof tasks to execute. Compile. Test. Minify. Concat. Uglify. Etc.
- 18.
- 19. DEPENDENCY MANAGEMENT 19 Applications aregetting complex. They rely on several other libraries and frameworks.
- 20.
- 21. DYNAMIC LOADING 21 Big projectsare split among several pieces of javascript for the sake of modularisation. No all of them should be loaded at the same time.
- 22.
- 23. TESTING 23 Testing is allaround. Need to tests on different browsers, need to write the tests, need to run the tests, need to report test results.
- 24. 24 mocha, qunit, protractor,sinon, saucelabs, duck angular
- 25. APPLICATION 25 Applications on webare getting complex, need for frameworks that support app development.
- 26.
- 27. DOM UTILITIES 27 DOM selectionand manipulation, some auxiliary functions, need for utilities that make work simple (and cross-browser)
- 28.
- 29. LANGUAGE UTILITIES 29 Clean code,functional programming style, reactive programming features, helpers and utilities
- 30.
- 31.
- 32. CI 32 Continuous integration, continuous delivery,continuous deployment
- 33.
- 34. OTHER LANGUAGES 34 Have asyntactic sugar element, or even completely different syntax (that in the end turn into javascript to run in the browser)
- 35.
- 36. OTHER JAVASCRIPT 36 Several tools.Several ways. Several Practices. Need to organize, and give some good foundation - best practices, good design.
- 37.
- 38. WRAP UP 38 Difference Needs|Toolsand their relation Agile demands for you as a developer Keep your mind open
- 39. For questions orsuggestions: ! Marcos Vinicius @bymarkone github.com/bymarkone ! Renan Martins @renan89 THANK YOU