1. Web Applications Development Using Coldbox Platform Eddie Johnston

2.  Model View Controller event- driven Coldfusion Framework.  Tool Set & Software foundation  Object Oriented Principles  Established on Code Controllers

3.  Application features: bug reporting, logging, caching, debug tools, and much more.  Unit Test the entire application.

4.  Coldbox provides these defaults  Allows for files, classes, or methods to be put in the correct location  Faster production

5.  Provides for the development of:  Dynamic websites  Web applications  Web services

6.  Commonly called CFML  Scripting Language for Web Development  Runs on common engines  Open source implementations of CFML engines  Adobe ColdFusion  BlueDragon  Many More

7. Rundown:  Supplements normal HTML files  database commands  conditional operators  formatting functions  CFCs, “CFML objects”

8. Does not just generate HTML  CSS  XML  JavaScript  Much More

9.  Not a markup language  Not SGML  CFML engine:  handles.cfm or.cfc files  processes CFML tags and functions

10. CFML syntax  CFML tags similar to HTML tags  or  #value# Class!

11. CFML Custom Tags  Line to call myOwnCustTag.cfm 

12.  Reusable code  Libraries for accessing databases  Handling sessions

13. Web Application Framework Architecture:  Most follow: Model View Controller (MVC)  Examples:.NET  PHP  Python  Java  JavaScript  much more 

14.  Coldbox  AJAX  MVC Framework  ORM  Testing Framework  Caching Utilities and Services  And much more

15. Application Client View Model Controller DB

16.  Key ideas:  Model: directs the data or behavior of an application domain  View: Renders data into a form typically to appeal to a UI  Controller: retrieves input and starts the response. Guides the model and view based on the input

17. Architecture Not Framework:  Can be implemented without object oriented programming or a class hierarchy.

18. Advantages:  View is separate from Model: no dependency directly  UI can render many different views of the same data at once.  Changes are easy to maintain  Layouts are simple to change that will not effect the data that is rendered

19.  Original Designed for multiple tier web application in 2005.  Became open source July 2006.  Developed by Luis Majano of Ortus Solutions  Continued development by Team Coldbox  Build: 3.1.0

20.  Unit test an entire application  Enterprise debugging, monitoring, caching, etc.  Code controllers (based on CFCs)  More than just MVC framework  Development tools and event-driven

21.  Documentation  250+ pages of documentation  30 Step by Step Guides  Coldbox Dictionary  The reason why we document: makes life easier for the developer.

22.  Code Controllers  No XML Dialect to describe your application  Based on CFC’s and conventions  Multiple applications with concise and common configuration files  Smart Caching

23.  Custom Convention  Coldbox knows where to find code  Coldbox knows what to execute  Customizable  Create own layouts, handlers, configuration files

24.  Debugging tools  Gives a lot of information for what is happening  Times events & code  Built in timer plugin  Visual feedback  Debugging monitors

25.  Software Aspects  Logging Facilities  Helper classes  Query helpers(sorting or filtering), java utilities, file utilities  Environment detection  Can detect between development, or production (multi-tier)  Bug reports to send wherever you want  Create own plugins

26. Request Collection Layouts Views View Controller Model Plugins Event Handlers Interceptor s Model Business Layer Plugins

27.  Imitates a User Request  Set values into, Get values from  Request Scope  Framework access

28. Ins and Outs:  CFC  Coldfuison Events are Public or Remote Methods  Execution Points  Event = handler.method

29.  CFC  Extends functionality of Coldbox Framework  Visual  Smart Caching  How to call a plugin  Messagebox plugin:

30.  Framework executes interceptors at execution points  preEvent, afterConfigurationLoad, etc.  Custom Interceptor points  Broadcasted through Application Programming Interface

31. Define a main default layout Define in Configuration File: Views to be rendered instead of layouts Layouts View s

34. Files in the Handler Directory

35. Code inside the Main handler

36. Layout Directory

37. Sidebar to a web application generated by Coldbox Framework

38. Snippet from Add Customer of Sidebar

39.  Web applications are not just websites  Convention Framework  More than MVC framework

40. Visit Coldbox online at http://www.coldbox.org/

41. Thank you