ITB2016 Intro To ColdBox MVC
0 likes291 views
This document provides an overview of the ColdBox MVC framework. It introduces MVC architecture and how ColdBox implements it using conventions over configurations. This allows developers to focus on code organization by placing components in the appropriate folders/locations rather than through configuration. ColdBox also supports modularity through reusable modules that extend core application functionality and interceptors that trigger actions at specific points in the request/response lifecycle.
ITB2016 Intro To ColdBox MVC
- 2. ‣Computer Know How ‣CFML/JavaScript developer ‣APIs (REST) Who Am I?
- 3. As applications grow, complexity grows As complexity grows, complications multiply
- 4. How do we make complex applications while minimizing complications?
- 5. GOALS: make existing code organization simple while developing complex applications for teams to work on
- 6. GOALS: make developing new code simple to integrate into existing code
- 8. VIEW ‣what the user interacts with ‣UI/UX ‣browser/mobile stuff ‣“the site” or “the app” according to the user
- 9. MODEL ‣business logic ‣data interaction manipulation ‣services ‣data access
- 10. CONTROLLER ‣“confusing one” ‣controls application flow ‣mediator between model & view ‣request/response manager ‣different for different systems
- 11. The MVC Restaurant: an illustration in organization
- 12. ‣The menu ‣What the user sees ‣User Interface (UI) -> what the user interacts with View
- 13. Controller ‣The waiter/server ‣Go-between for the View and the Model ‣Takes orders from the View ‣Brings food from the Model
- 14. Model ‣The Chef ‣Makes the food ‣Data modeling ‣Data management ‣Business Logic
- 15. Model-View-Controller (MVC) Controller Brings requests from the View to the Model Brings data from the Model to the View Model handles the business logic View UI, what the client sees/interacts with
- 16. What MVC does for us ‣organization ‣file definition ‣every aspect of our app has a place ‣makes amazing coffee
- 17. Just the Basics!
- 18. brings more to the table ‣conventions over configurations ‣modularization ‣event management
- 20. Configurations You map this thing to that other thing and write this annotation if you need the third thing and if you make a new thing you have to map that to the first thing and…???
- 21. Conventions Put the right stuff in the right box and everything works
- 22. What this looks like…
- 23. Conventions: “put the right stuff in the right box & ColdBox does the work for you”
- 24. Beyond MVC
- 25. Modules program packages that give extra functionality to your core application. They are: ‣ Independent ‣Interchangeable ‣reusable
- 26. What this looks like… ‣Lives in modules folder (convention) ‣Has its own MVC ‣Independent, interchangeable, pluggable ‣Extensibility
- 27. Modules can be… ‣Libraries for extra functionality ‣Widgets ‣Anything that gives extends your core application ‣Example: ContentBox uses modules for its functionality
- 28. Interceptors ‣Intercept an event with action ‣“When” -> interception point ‣Default interception points ‣Custom interception points ‣Intercept time ‣“when this happens, do this…”
- 29. Putting it Back Together
- 30. @Francainath