Transcript of a presentation about the Play framework. The actual presentation was dynamic, and hard to capture in a slideshow (see slide 22 for why).

5. List of all JEE JSRs
It goes on

9. Download Activator at:
http://www.typesafe.com/activator

12. That’s it - application created!

14. Note the “localhost” - server is running locally

17. The router maps HTTP requests to actions,
which are static methods*
*in Scala - methods of an object

18. Also deals with parameter bindings

19. And can be exported to use in client-side
Javascript

22. The slides you’ve seen are actually
a Play application

23. The slides you’ve seen are actually
a Play application
(in the presentation itself, these are annotated screenshots, of course)
(but feel free to fork it on GitHub, as they say, and run locally)

25. Here is the application controller

26. Here is the application controller
Note that I’ve created a toy DSL
for standard slides.

27. Here is the application controller
Note that I’ve created a toy DSL
for standard slides.
Let’s look at the object hierarchy
of the elements in this DSL

30. Pretty small template for
rendering recursive structure,
and wrapping it in Bootstrap3, I’d say

32. Here’s where the recursive rendering happens.
Note the usage of pattern matching, to route
the element to the proper render function

39. Type “activator console” at the command prompt
to get to the console.
Or, “activator” to start the activator shell, and then “console”

40. Type “activator console” at the command prompt
to get to the console.
Or, “activator” to start the activator shell, and then “console”
We can play with the model objects, even when the application
is not running

42. We can even render templates when the application
is not running.

43. We can even render templates when the application
is not running.
Big news for testing UI layer - you can just inject
data to it directly, instead of forcing the application
into a certain state.

44. We can even render templates when the application
is not running.
Big news for testing UI layer - you can just inject
data to it directly, instead of forcing the application
into a certain state.
Very different from JSF, where the page is the “leader”
of the rendering process, and calls backing beans.
This approach has its advantages, but it also makes
it hard to separate the page from the back-end.

50. Easy to write non-blocking code, thus easy to scale