Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add some documentation about feature coverage #2

Open
vanto opened this issue Jan 24, 2013 · 1 comment
Open

Add some documentation about feature coverage #2

vanto opened this issue Jan 24, 2013 · 1 comment

Comments

@vanto
Copy link

vanto commented Jan 24, 2013

Currently it is pretty unclear which features of Rythm are fully supported and which PlayRythm features are supported. Is there a roadmap which PlayRythm features are supposed to be migrated to Spring MVC?

As a sidenote, is there a particular reason why PlayRythm has @msg(...)/&(...) for i18n and this project uses @message?

@LCTL
Copy link
Owner

LCTL commented Jan 24, 2013

Rythm Templat Engine features is fully supported e.g. @extends, @args, @section, etc..., but do not cover PlayRythm supported features e.g. &{i18n.code} or @url(Application.index), because Play Framework has many magic features and very hard to implement those in Spring Framework.

For the @message is not match PlayRythm i18n @msg syntax. Solution is create a JavaTag and extends com.ctlok.springframework.web.servlet.view.rythm.tag.Message then override getName() method to return "msg" and register in Rythm Engine. Next version may be support @message and @msg syntax for i18n message.

I will create a document for developer to know which Rythm Template Engine features is supported and help developer easily migrate form Play Framework to Spring Web MVC.

I am glad that you are interested. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants