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.

Sign up for GitHub

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

Jump to bottom

Scalate template conventions #87

Closed
rossabaker opened this issue Aug 9, 2011 · 2 comments
Closed

Scalate template conventions #87

rossabaker opened this issue Aug 9, 2011 · 2 comments
Assignees
@rossabaker
Labels
enhancement
Milestone
2.0.0

Comments

@rossabaker
Copy link
Member

Add methods to render Scalate templates by convention. The recommended layout:

  • src/main/webapp: static assets
  • src/main/webapp/WEB-INF/views: Scalate templates
  • src/main/webapp/WEB-INF/layouts: Scalate layouts

This more or less corresponds to Sinatra conventions translated into WAR conventions.
@ghost ghost assigned jlarmstrong and rossabaker Aug 15, 2011
rossabaker added a commit that referenced this issue Aug 18, 2011
@rossabaker
Look for layouts in /WEB-INF/layouts/default.*. #87
2a26abe
rossabaker added a commit that referenced this issue Aug 19, 2011
@rossabaker
Clean up default layout strategy. #87
7d17cc5 
This looks more like the ServletTemplateEngine code.
@rossabaker
Copy link
Member Author

If no route matches, should ScalateSupport look for a template before invoking the notFound handler? I think this would make a nice a variable (like the error page). Should it be the default? I'm on the fence here.

I propose implementing this with Scalate's TemplateFinder, and also using it in renderTemplate.

@rossabaker
Copy link
Member Author

Closed by ffb382d.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rossabaker rossabaker

Labels
enhancement
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
2 participants
@jlarmstrong @rossabaker