When you ctrl + click on an action in a routes file, you get directly to the action's definition source code. E.g.
GET /show/:id controllers.Application.show(id: String) ==> // jump to Application.show
It would only be natural to enable the same navigation from action to template.
views.html.admin() // ==> jump to template source
But this is currently not implemented. Which makes the MVC model your enemy when the application grows, rather than your friend. See here for motivation.
BTW it would then also make sense to be able to see where a template is called from and where an action is wired from in a route, if not already implemented. This can be a separate ticket... this all would make Play make sense in Scala IDE.
When you ctrl + click on an action in a routes file, you get directly to the action's definition source code. E.g.
It would only be natural to enable the same navigation from action to template.
But this is currently not implemented. Which makes the MVC model your enemy when the application grows, rather than your friend. See here for motivation.
BTW it would then also make sense to be able to see where a template is called from and where an action is wired from in a route, if not already implemented. This can be a separate ticket... this all would make Play make sense in Scala IDE.