[Lift] Re: Changes in 1.1 production mode?
LiftRules.stripComments(false) generates following error message: Boot.scala:61: error: wrong number of arguments for method apply: ()() = Boolean in trait Vendor LiftRules.stripComments(false) On 27 Okt., 16:52, David Pollak feeder.of.the.be...@gmail.com wrote: Please see LiftRules.stripComments. You can do LiftRules.stripComments(false) On Tue, Oct 27, 2009 at 8:18 AM, Yousry Abdallah yous...@gmail.com wrote: Hi, at the moment I'm testing my application against 1.1 snapshot and I noticed that while running lift in production mode: - Drun.mode=production aside from blueprints IE6 fallback: !--[if IE]link rel=stylesheet href=/classpath/blueprint/ ie.css type=text/css media=screen, projection![endif]-- all other comments are removed from the html output. I'm using adsense and it is essential to pass key parameters via comments. Did I miss some options/parameters to deactivate this new feature? -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Surf the harmonics --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Changes in 1.1 production mode?
I downloaded the library source yesterday and stumbled on the
(abstract) factory pattern in the LiftRules Class.
Do you think this is the desired way to change a parameter?
Sometimes you use simple assignment:
LiftRules.useXhtmlMimeType = false
or you apply a value:
LiftRules.setSiteMap(...)
and now you do:
LiftRules.stripComments(false){}
Could this be simplified?
I think this is confusing and time-consuming at the moment to work
with LiftRules.
On 28 Okt., 15:00, Timothy Perrett timo...@getintheloop.eu wrote:
Looking at the definition:
val stripComments: FactoryMaker[() = Boolean] =
new FactoryMaker(() = {() = {
if (Props.devMode)
false
else true
}}) {}
try doing:
LiftRules.stripComments(false){}
Cheers, Tim
On 28 Oct 2009, at 13:22, Yousry Abdallah wrote:
LiftRules.stripComments(false)
generates following error message:
Boot.scala:61: error: wrong number of arguments for method apply: ()()
= Boolean in trait Vendor
LiftRules.stripComments(false)
On 27 Okt., 16:52, David Pollak feeder.of.the.be...@gmail.com wrote:
Please see LiftRules.stripComments.
You can do LiftRules.stripComments(false)
On Tue, Oct 27, 2009 at 8:18 AM, Yousry Abdallah
yous...@gmail.com wrote:
Hi,
at the moment I'm testing my application against 1.1 snapshot and I
noticed that while running lift in production mode: -
Drun.mode=production aside from blueprints IE6 fallback:
!--[if IE]link rel=stylesheet href=/classpath/blueprint/
ie.css type=text/css media=screen, projection![endif]--
all other comments are removed from the html output.
I'm using adsense and it is essential to pass key parameters via
comments.
Did I miss some options/parameters to deactivate this new feature?
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Surf the harmonics
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Changes in 1.1 production mode?
Hi, at the moment I'm testing my application against 1.1 snapshot and I noticed that while running lift in production mode: - Drun.mode=production aside from blueprints IE6 fallback: !--[if IE]link rel=stylesheet href=/classpath/blueprint/ ie.css type=text/css media=screen, projection![endif]-- all other comments are removed from the html output. I'm using adsense and it is essential to pass key parameters via comments. Did I miss some options/parameters to deactivate this new feature? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: May I know websites powered by Lift?
Try: http://www.kungle.de/ It's a news aggregator. On 3 Sep., 16:07, surfman chinasmile...@gmail.com wrote: I tried searching websites powered by Lift but failed. Any one knows any? I suggest that David should edit a page list all websites powered by Lift on Liftweb Project. It will be great useful. Thanks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Tomcat css access problem
Hi,
your suggestion didn't work for me because I'm using url-rewrite in my
application.
Something like
http://...application/parameterA/
http://...application/parameterA/parameterB/
Therefore the relative path wouldn't match.
The CSSHelper function fixes the absolute path.
This is important because I can deploy the same package in
development / and production /applicationFolder/ environment.
On 26 Aug., 23:12, Jefken De Vleesetenden Boterham
cultoftheholysquir...@gmail.com wrote:
Hi,
Then I guess my next question is: how do you define where your css is located?
I have a function that gives the location of my css in the following way:
def css = link href={ S.hostAndPath+/+scripts/cd.css}
rel=stylesheet type=text/css/
You shouldn't need the S.hostAndPath+/ part unless you're using
fancy redirecting like I'm doing. I call that function from my main
template. In fact, you shouldn't even need a function and could just
use link href=relativePathToFolderContainingCSS/cd.css
rel=stylesheet type=text/css/
In your case, I'd think that the
relativePathToFolderContainingCSS/cd.css would be
css/kungleNext.css, but I might be mistaken.
- Philippe
On Wed, Aug 26, 2009 at 1:23 PM, Yousry Abdallahyous...@gmail.com wrote:
Hi,
you are absolutely right.
I use mvn jetty:run in my development environment to test the
application.
Than I build a package with mvn package and copy it to the tomcat
webapp directory.
Thank you,
Yousry
On 26 Aug., 12:46, Jefken De Vleesetenden Boterham
cultoftheholysquir...@gmail.com wrote:
Hi,
I'm assuming you mean deploying under jetty and tomcat. I only know
derby to be a database.
How exactly do you deploy under jetty and tomcat?
Personally, I use jetty for testing and deploy with mvn jetty:run,
while I use tomcat on the test and production servers in which case I
just drop the war file under web-apps.
Thanks,
Philippe
On Wed, Aug 26, 2009 at 11:47 AM, Yousry Abdallahyous...@gmail.com wrote:
Hi,
I'm working with 1.1 snapshot (latest) and have the following problem
with a local css reference:
If I deploy my webapp under derby the resulting html output looks
fine:
link media=screen rel=stylesheet type=text/css
href=/KungleNext-0.1-SNAPSHOT/css/kungleNext.css /
The same application deployed under tomcat produces this buggy
reference:
link media=screen rel=stylesheet type=text/css
href=/css/kungleNext.css /
My snippet defines the ling as follows:
...
link href=/css/kungleNext.css type=text/css rel=stylesheet
media=screen /
..
--http://pmonnaie.blogspot.com/
--http://pmonnaie.blogspot.com/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
[Lift] Tomcat css access problem
Hi, I'm working with 1.1 snapshot (latest) and have the following problem with a local css reference: If I deploy my webapp under derby the resulting html output looks fine: link media=screen rel=stylesheet type=text/css href=/KungleNext-0.1-SNAPSHOT/css/kungleNext.css / The same application deployed under tomcat produces this buggy reference: link media=screen rel=stylesheet type=text/css href=/css/kungleNext.css / My snippet defines the ling as follows: ... link href=/css/kungleNext.css type=text/css rel=stylesheet media=screen / .. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Tomcat css access problem (SOLVED)
Hi, another rtfm case. Adding a CSSHelper to Boot.scala resolves the problem: LiftRules.fixCSS(css :: kungleNext :: Nil, Empty) Thanks, Yousry On 26 Aug., 12:46, Jefken De Vleesetenden Boterham cultoftheholysquir...@gmail.com wrote: Hi, I'm assuming you mean deploying under jetty and tomcat. I only know derby to be a database. How exactly do you deploy under jetty and tomcat? Personally, I use jetty for testing and deploy with mvn jetty:run, while I use tomcat on the test and production servers in which case I just drop the war file under web-apps. Thanks, Philippe On Wed, Aug 26, 2009 at 11:47 AM, Yousry Abdallahyous...@gmail.com wrote: Hi, I'm working with 1.1 snapshot (latest) and have the following problem with a local css reference: If I deploy my webapp under derby the resulting html output looks fine: link media=screen rel=stylesheet type=text/css href=/KungleNext-0.1-SNAPSHOT/css/kungleNext.css / The same application deployed under tomcat produces this buggy reference: link media=screen rel=stylesheet type=text/css href=/css/kungleNext.css / My snippet defines the ling as follows: ... link href=/css/kungleNext.css type=text/css rel=stylesheet media=screen / .. --http://pmonnaie.blogspot.com/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Tomcat css access problem
Hi, you are absolutely right. I use mvn jetty:run in my development environment to test the application. Than I build a package with mvn package and copy it to the tomcat webapp directory. Thank you, Yousry On 26 Aug., 12:46, Jefken De Vleesetenden Boterham cultoftheholysquir...@gmail.com wrote: Hi, I'm assuming you mean deploying under jetty and tomcat. I only know derby to be a database. How exactly do you deploy under jetty and tomcat? Personally, I use jetty for testing and deploy with mvn jetty:run, while I use tomcat on the test and production servers in which case I just drop the war file under web-apps. Thanks, Philippe On Wed, Aug 26, 2009 at 11:47 AM, Yousry Abdallahyous...@gmail.com wrote: Hi, I'm working with 1.1 snapshot (latest) and have the following problem with a local css reference: If I deploy my webapp under derby the resulting html output looks fine: link media=screen rel=stylesheet type=text/css href=/KungleNext-0.1-SNAPSHOT/css/kungleNext.css / The same application deployed under tomcat produces this buggy reference: link media=screen rel=stylesheet type=text/css href=/css/kungleNext.css / My snippet defines the ling as follows: ... link href=/css/kungleNext.css type=text/css rel=stylesheet media=screen / .. --http://pmonnaie.blogspot.com/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: *** BREAKING CHANGES COMING UP SOON ***
Could you setup a milestone before the merge? On 4 Aug., 21:51, Marius marius.dan...@gmail.com wrote: Folks, I spent a few days decoupling Lift from JEE web container dependencies: javax.servlet._ The code is currently in wip-marius-http- abstractions. I still need to nail down a few things but the idea is: 1. Lift will work with its own traits that abstracts HTTP request, response, HTTP sessions etc. 2. By default there will be the servlet implementation and it'll work as currently. 3. Certain function names will slightly change. 4. If your application explicitly wants to use HttpServletRequest obtained from S some explicit casts would be needed. Generally Lift application should probably not explicitly use javax.servlet._ references. I will post the details of the changes when I'll merge it to master (hopefully this week). Br's, Marius --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
