Many texteditors have a plugin for this framework for example TextMate, Sublime Text and VIM
‘app’ contains the assets, controllers, models and views. Global.scala contains global settings and can hook onto application events such as start/stop. ‘conf’ contains evolutions, application.config-file, i18n-files, play-plugins and routes-file. ‘project’ contains build settings and a file to specify SBT plugins ‘public’ contains static assets (images, css, js,…) In the root a build.sbt exists for specifying the version of your app and dependencies
Version of your app and dependencies
Main configuration file for your application.
Translations, change create different messages-files for other languages
Routes configured here can also be used in your views and code for example: routes.PizzaController.index So there is only one place to update the URLs
Texteditor and browser is sufficient, no need to keep an eye on your console since errors are shown in the browser
The activator web application can be used to go through interactive tutorials that guide you through existing application or help you learn new things with the framework.
Play framework 2
Play Framework 2
Yannick De Turck
Play, just another web framework?
Based on a lightweight, stateless and web-friendly architecture
Develop in Scala and/or Java
- Focus on productivity
- Only need a texteditor and browser
- Hit refresh workflow
- Type safety
Inspired on Rails and Django