Scalate support in Lift change proposal

[farr]

I recently tried to use scalate as the template engine in lift and
noticed that the lift: tags didn't appear to be working.

After some inspection I believe this is due to the ScalateView being
registered with LiftRules.dispatch and not LiftRules.viewDispatch. In
effective, the rendering of HTML is currently completely in control of
Scalate and all the Lift goodness is passed by.

I modified the view it is now working more in line with what I had
hoped the integration would be. The change can be found in my fork on
github[1].

Effectively just switch index.html or default.html to index.scaml or
default.scaml respectively. Lift tags work as expected.

My question is this more in line with the functionality the community
expects from the Scalate integration with Lift?

I'm working on updating the lift-helloscalate example to reflect all
the functionality from the lift-hellolift example and will push it
shortly.

[1] https://github.com/rfarrjr/modules/compare/scalate

[David Pollak]

Unfortunately, the person that added Scalate support to Lift has not maintained the package.  Unless there's a committer who will step up to maintain the package, it will be deprecated.

Sorry.

--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.

--
Lift, the simply functional web framework http://liftweb.net

Simply Lift http://simply.liftweb.net
Follow me: http://twitter.com/dpp
Blog: http://goodstuff.im

[Tony Kay]

I know this is an old thread, but it seems the most recent comment I found.

I was just looking at the scalate support, and would be willing to step up and maintain the source. As it stands, it still bypasses all Lift goodness, but with the support for external template loaders in LiftRules, it would be pretty simple to put it into the resource loading chain so that it acted more as a template loader than a response generator. 

How do I go about becoming said maintainer?

Tony

[Richard Dallaway]

Hello Tony

As you probably know, the Scalate module is now here: https://github.com/liftmodules/scalate

I'd suggest forking that, make it work the way you want, discuss changes here with other Scalate users (I'm not one, but others are interested I believe), and make pull requests against the module.

Hope that helps

Richard

--

--
Lift, the simply functional web framework: http://liftweb.net

Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
 
---

You received this message because you are subscribed to the Google Groups "Lift" group.

To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Tony Kay]

Great! Thanks Richard.

Working on it now...

Tony

[Tony Kay]

OK, I've got an initial version almost complete, but I have a feature that I want to add that I need a little help with.

The code so far (with a long README.md to explain how it works) is at:

https://github.com/awkay/scalate

I've added a "Lifted Scaml" mode, which allows you to write your XHTML/HTML5 via scaml, but pushes that result through the lift pipeline...so scaml becomes a template pre-processor.

Thing is, I want to be able to offer template caching in production mode (so that the scaml is not re-processed, encouraging no side-effect code in the view at least).

What is the best entry point into the template caching system already present in Lift?

The routine that would need to use it is this file:

https://github.com/awkay/scalate/blob/master/src/main/scala/net/liftmodules/scalate/LiftedScaml.scala

around line 60...

Thanks,

Tony

On Sunday, February 10, 2013 1:07:02 AM UTC-8, Richard Dallaway wrote:

[Tony Kay]

Nevermind....I think I found it...