Integration Guide
Migrate your current project from Groovy template engine to Rythm
PlayRythm is designed to support smooth migrating from Groovy template engine.
By default “system” (i.e. groovy) template engine is used. Meaning without special annotation, controller’s render request will be handled by groovy template engine. And this give developer a good base to move to Rythm template step by step.
- Step 1, rewrite a groovy template using rythm syntax and put the file into the corresponding place in
app/rythm Step 2, annotate the relevant controller action method with@UseRythmTemplateEngineannotation
Continue the above steps until all your controller migrated to rythm. You can annotate the controller with @UseRythmTemplateEngine and drop all that from action method
Tip: enclose all your rythm template with . This is not true. The groovy template engine will still parse the expressions. See Resolve groovy compilation error for workarounds.#{verbatim} and #{/verbatim} can help you avoid groovy compile exception and does not impact your rythm template
Resolve groovy compilation error
Because groovy template engine does not provide a way to skip parsing any part of the template file, the rythm template file might cause compilation error during precompile process, where rythm has no way to identify some files been a rythm template or groovy template, e.g. some json generation template. Start from version 0.9.5 it’s suggest to move all rythm templates or at least those compilation error causing templates to app/rythm folder from app/views folder.
More about tags
So far you can keep rythm tags file under app/views/tags/ryth folder. However it is recommened not to use tags folder at all since every rythm template is a tag and can be called from any other rythm templates. E.g. suppose you have a template file app/views/Order/list.html, while you can use it as an ordinary template file, you also free to call it as a tag from other rythm template like: @Order.list(myOrders)