Re: [Lift] Re: Tricky question regarding menus
Heiko Seeberger writes:
> Hi,
>
> Sorry for being pushy, but this one is really urgent. Maybe I did not
> describe my issue properly, so I will give it another and simpler try:
>
> I want a menu to link to a "subpage", i.e. have the same link as one of its
> child menus. But the menu shall also be "active" for every other active
> child menu.
I have the same scenario and it works for me. In the parent menu I do this:
Menu(Loc("parent", List("parent", "index"), "Parent", Loc.EarlyResponse(() =>
Full(RedirectResponse("/subpage"
We're using our own menu snippet and I can't recall if this was one of
the things we changed :-(
/Jeppe
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@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.
Re: [Lift] Welcome John De Goes as a Lift committer
David Pollak writes: > Folks, > > Please join me in welcoming John De Goes as a Lift committer. John burst > onto the Lift scene a week or so ago with some excellent enhancements to the > Lift-json stuff and the rest is history. > > Welcome John... looking forward to excellent contributions from you and your > latest partner in crime, Kris Nuttycombe, a long-time Lift committer. > > Thanks, > > David Welcome John! /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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: Tricky question regarding menus
Hi, Sorry for being pushy, but this one is really urgent. Maybe I did not describe my issue properly, so I will give it another and simpler try: I want a menu to link to a "subpage", i.e. have the same link as one of its child menus. But the menu shall also be "active" for every other active child menu. Thank you, Heiko On 22 February 2010 15:15, Heiko Seeberger wrote: > Hi, > > I want to create a menu with the following structure: > > main1 main2 main3... > sub1a sub1b sub2a sub2b sub3a ... > page1a1 page1a2 ... > > Now I want some of the main and sub menus not to have "their own pages" but > have the same link as certain child pages. > > Example: When the user clicks main1 the page page1a1 is to be shown. Of > course main1 and sub1a are to be marked as "currently selected" menu, hence > Loc.doesMatch_? must return true. If I create the Locs for main1 and sub1a > with the link to page1a1 (main1/sub1a/paga1a1) then doesMatch_? will not be > true for all other child pages of main1 and sub1a. > > Is there a simple solution to this? Or do I have to write my own Loc > implementation? > > Thank you, > > Heiko Seeberger > > Work: weiglewilczek.com > Blog: heikoseeberger.name > Follow me: twitter.com/hseeberger > OSGi on Scala: scalamodules.org > Lift, the simply functional web framework: liftweb.net > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Documenting the source code / supplementing the API docs
The easiest thing is if Stuart signs an IP assignment, becomes a full-fledged committer and thus we keep the IP clean. Stuart, if you're interested in learning more, please contact me off-list. In terms of the documentation standards, I'm okay with anything that the rest of you-all want. I'm neither the best producer or consumer of docs, so my voice is a small one on this issue, other than to give hearty thanks to those who write documentation. On Mon, Feb 22, 2010 at 1:05 PM, Stuart Roebuck wrote: > Great... okay, I’d better do some writing :-) > > In the absence of a decision I’ll try to minimise special coding in > comments but use Scaladoc 2 standard if necessary rather than HTML as that > makes it future proof but still readable for both. > > Stuart > > On 22 Feb 2010, at 17:32, Ross Mellgren wrote: > > > I will do this, and give feed back if it ever becomes too much load. > > > > -Ross > > > > On Feb 22, 2010, at 12:05 PM, Timothy Perrett wrote: > > > >> We are interested in the contribution of course... I think the issue is > mostly about how we take patches for this. Someone on the team would need to > own this and merge your documentation changes into the master (provided DPP > has no objections to this - seeing as its documentation I doubt he has) > >> > >> Any takers from the team? > >> > >> Cheers, Tim > >> > >> On 22 Feb 2010, at 16:14, Stuart Roebuck wrote: > >> > >>> Sorry for the slow response—was away for a family weekend! > >>> > >>> I have limited knowledge of Lift internals… > >>> > >>> However, my view is that it is often easier to document code when you > >>> don't know it well than when you do, because you soon loose interest > >>> in documenting things that are obvious to you. What I hope to do is > >>> document the things that I need to know as I go along on the basis > >>> that many of these things will also be important to others. It's an > >>> agile rather than systematic approach if you see what I mean. > >>> > >>> I have no ego issues here. It's just a small way of giving to the > >>> community in a win-win kind of way. If my contributions don't seem > >>> helpful to anyone else then folk can say and I'm not going to > >>> disappear in a torrent of abuse :-) > >>> > >>> Similarly, I'm not proposing some big project here. I'm talking about > >>> a drip-drip of updates as I spot things that need documenting—I've got > >>> plenty other stuff on my plate right now as I'm launching a company > >>> based on a Lift based product in mid-year. > >>> > >>> Enough said… > >>> > >>> How do we resolve the documentation standard issue? (Scala 2.8 > >>> Scaladoc2 or prior) David? > >>> > >>> Stuart. > >>> > >>> On Feb 19, 4:11 pm, Timothy Perrett wrote: > This could work - although, some parts of lift are very non-trivial > and require good knowledge of lift internals. Do you have such knowledge or > are you just hoping to contribute where you can with helpful information? > Both are good, just trying to establish what you had in mind. > > Lift-util probably has the best docs at the moment, so if we could > emulate that it would be good. > > Cheers, Tim > > On 19 Feb 2010, at 15:56, Ross Mellgren wrote: > > > > > If you can get an established standard on what the content and format > should be, I can work with you reviewing the patches and applying them. > > > But, need to get a concordance from the list on the content first. > > > -Ross > > > On Feb 19, 2010, at 10:53 AM, Stuart Roebuck wrote: > > >> I've had a bit of a break from Lift and coming back I find myself > >> annoyed that I didn't write some notes last time and am having to go > >> back to searching through the various bits of documentation to > figure > >> things out. > > >> Anyway, after much thought I decided that the best way to write my > >> notes would be to supplement the API docs (ie. the Scaladoc > >> documentation in the code base). so that I can view context > sensitive > >> help in my IDE of choice and others can benefit from my labours! > > >> So, question 1… > > >> The current API docs are very light on documentation and sometime > ago > >> I noticed some notice about removing documentation from the code > >> base. Is there some policy about not having documentation in the > >> code or any thought on whether it should adhere to the Scaladoc 2 > >> syntax? > > >> Question 2… > > >> This is only really going to work if the process of submitting the > >> documentation is reasonably straightforward so… What's the easiest > >> possible way of submitting documentation changes to the code base? > (if > >> indeed this is something the core team would welcome). I was > >> thinking of perhaps emailing git patch files to someone in the core > >> team who can verify that the comments are right before checking them > >
Re: [Lift] Re: Confused about request scope, session scope
On Mon, Feb 22, 2010 at 5:58 PM, Strom wrote: > Sometimes the best solution is the simplest, and in this case, > overlooked. > Please keep in mind that if you carry the primary key around in the URL, then (1) you've exposed the primary key to the world (this can have negatives including giving people an idea of home many of a given item you have in your RDBMS) and (2) you have to do a lot of value checking on each page submit to make sure that whoever is accessing the record has permission to access the record. > > Thanks Ross! > Strom > > On Feb 22, 5:46 pm, Ross Mellgren wrote: > > On Feb 22, 2010, at 8:39 PM, Strom wrote: > > > > > Thanks for responding Ross. Always helpful. > > > > > On Feb 22, 5:25 pm, Ross Mellgren wrote: > > >> Session scope is until the LiftSession expires (which is tied to the > container session) and is longer. > > > How does one determine the container session scope? Anywhere I can > > > read up on this basic knowledge? > > > > Well the precise details depend on the container, but most containers by > default set a cookie called JSESSIONID that is used to maintain the session > ID and the cookie last until browser logout. The server-side session data is > usually kept alive 20 minutes from the most recent time a request used that > session ID, but it's configurable in web.xml, and perhaps overridable in > whatever container-specific config is available. > > > > >> Request scope is during the "current page" which means the original > page request and any associated AJAX callbacks and other function bindings. > > > Does this include redirects to the same page with additional query > > > parameters? I'm using this to search, and would like to have the query > > > params so people can bookmark their search. > > > > I don't believe it includes these. If you want something bookmarkable, > you should explicitly place whatever parameters need to persist in the query > string -- function mapping bindings are ephemeral, and even so the session > would be expired by the time the bookmark was used. > > > > > Thanks again! > > > > No problem. > > > > -Ross > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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, the simply functional web framework http://liftweb.net Beginning Scala http://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 lift...@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: Confused about request scope, session scope
Sometimes the best solution is the simplest, and in this case, overlooked. Thanks Ross! Strom On Feb 22, 5:46 pm, Ross Mellgren wrote: > On Feb 22, 2010, at 8:39 PM, Strom wrote: > > > Thanks for responding Ross. Always helpful. > > > On Feb 22, 5:25 pm, Ross Mellgren wrote: > >> Session scope is until the LiftSession expires (which is tied to the > >> container session) and is longer. > > How does one determine the container session scope? Anywhere I can > > read up on this basic knowledge? > > Well the precise details depend on the container, but most containers by > default set a cookie called JSESSIONID that is used to maintain the session > ID and the cookie last until browser logout. The server-side session data is > usually kept alive 20 minutes from the most recent time a request used that > session ID, but it's configurable in web.xml, and perhaps overridable in > whatever container-specific config is available. > > >> Request scope is during the "current page" which means the original page > >> request and any associated AJAX callbacks and other function bindings. > > Does this include redirects to the same page with additional query > > parameters? I'm using this to search, and would like to have the query > > params so people can bookmark their search. > > I don't believe it includes these. If you want something bookmarkable, you > should explicitly place whatever parameters need to persist in the query > string -- function mapping bindings are ephemeral, and even so the session > would be expired by the time the bookmark was used. > > > Thanks again! > > No problem. > > -Ross -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Confused about request scope, session scope
On Feb 22, 2010, at 8:39 PM, Strom wrote: > Thanks for responding Ross. Always helpful. > > On Feb 22, 5:25 pm, Ross Mellgren wrote: >> Session scope is until the LiftSession expires (which is tied to the >> container session) and is longer. > How does one determine the container session scope? Anywhere I can > read up on this basic knowledge? Well the precise details depend on the container, but most containers by default set a cookie called JSESSIONID that is used to maintain the session ID and the cookie last until browser logout. The server-side session data is usually kept alive 20 minutes from the most recent time a request used that session ID, but it's configurable in web.xml, and perhaps overridable in whatever container-specific config is available. >> Request scope is during the "current page" which means the original page >> request and any associated AJAX callbacks and other function bindings. > Does this include redirects to the same page with additional query > parameters? I'm using this to search, and would like to have the query > params so people can bookmark their search. I don't believe it includes these. If you want something bookmarkable, you should explicitly place whatever parameters need to persist in the query string -- function mapping bindings are ephemeral, and even so the session would be expired by the time the bookmark was used. > Thanks again! No problem. -Ross -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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: Confused about request scope, session scope
Thanks for responding Ross. Always helpful. On Feb 22, 5:25 pm, Ross Mellgren wrote: > Session scope is until the LiftSession expires (which is tied to the > container session) and is longer. How does one determine the container session scope? Anywhere I can read up on this basic knowledge? > Request scope is during the "current page" which means the original page > request and any associated AJAX callbacks and other function bindings. Does this include redirects to the same page with additional query parameters? I'm using this to search, and would like to have the query params so people can bookmark their search. Thanks again! Strom > > -Ross > > On Feb 22, 2010, at 8:20 PM, Strom wrote: > > > This seems like a silly question to me, but what is considered the > > scope of a request vs the scope of a session? Which is longer? > > > I'm trying to figure how to go about having an object fetched from the > > DB in memory so I don't have to fetch from the DB every time someone > > submits the form. In my case, I would like to have a search involving > > zip code that has some associated info in the DB that I would need for > > distance calculations, and I would like to keep that DB object around > > until the user clears or changes the zip code field, making the > > fetched object obsolete. > > > I am considering using sessionmemoize or requestmemoize objects to > > suit my needs, but I don't know how long each one would stay around (I > > can't think of concrete examples of request vs session...I always > > though request happened every time you clicked a link to go somewhere > > on a webpage, whereas session is as long as the browser is on the > > site). > > > I've also considered a stateful snippet, but I don't think that's the > > right way to go about it since there is no clear start and finish to > > the snippet from where to unregister from. > > > Thanks, > > Strom > > > -- > > You received this message because you are subscribed to the Google Groups > > "Lift" group. > > To post to this group, send email to lift...@googlegroups.com. > > To unsubscribe from this group, send email to > > liftweb+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Confused about request scope, session scope
Session scope is until the LiftSession expires (which is tied to the container session) and is longer. Request scope is during the "current page" which means the original page request and any associated AJAX callbacks and other function bindings. -Ross On Feb 22, 2010, at 8:20 PM, Strom wrote: > This seems like a silly question to me, but what is considered the > scope of a request vs the scope of a session? Which is longer? > > I'm trying to figure how to go about having an object fetched from the > DB in memory so I don't have to fetch from the DB every time someone > submits the form. In my case, I would like to have a search involving > zip code that has some associated info in the DB that I would need for > distance calculations, and I would like to keep that DB object around > until the user clears or changes the zip code field, making the > fetched object obsolete. > > I am considering using sessionmemoize or requestmemoize objects to > suit my needs, but I don't know how long each one would stay around (I > can't think of concrete examples of request vs session...I always > though request happened every time you clicked a link to go somewhere > on a webpage, whereas session is as long as the browser is on the > site). > > I've also considered a stateful snippet, but I don't think that's the > right way to go about it since there is no clear start and finish to > the snippet from where to unregister from. > > Thanks, > Strom > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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. > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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] Confused about request scope, session scope
This seems like a silly question to me, but what is considered the scope of a request vs the scope of a session? Which is longer? I'm trying to figure how to go about having an object fetched from the DB in memory so I don't have to fetch from the DB every time someone submits the form. In my case, I would like to have a search involving zip code that has some associated info in the DB that I would need for distance calculations, and I would like to keep that DB object around until the user clears or changes the zip code field, making the fetched object obsolete. I am considering using sessionmemoize or requestmemoize objects to suit my needs, but I don't know how long each one would stay around (I can't think of concrete examples of request vs session...I always though request happened every time you clicked a link to go somewhere on a webpage, whereas session is as long as the browser is on the site). I've also considered a stateful snippet, but I don't think that's the right way to go about it since there is no clear start and finish to the snippet from where to unregister from. Thanks, Strom -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Welcome John De Goes as a Lift committer
Welcome John De Goes! On Tue, Feb 23, 2010 at 5:55 AM, David Pollak wrote: > Folks, > > Please join me in welcoming John De Goes as a Lift committer. John burst > onto the Lift scene a week or so ago with some excellent enhancements to the > Lift-json stuff and the rest is history. > > Welcome John... looking forward to excellent contributions from you and your > latest partner in crime, Kris Nuttycombe, a long-time Lift committer. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Welcome John De Goes as a Lift committer
John De Goes as in the author of "Cutting-Edge 3d Game Programming With C++" ? That book convinced me that I could be a professional computer (and game) programmer. I still have that book on my bookshelf :) I look forward to seeing what you can do with Lift. I might decide to become a web programmer ;) "The greatest obstacle to discovering the shape of the earth, the continents, and the oceans was not ignorance but the illusion of knowledge." - Daniel J. Boorstin On Mon, Feb 22, 2010 at 3:55 PM, David Pollak wrote: > Folks, > > Please join me in welcoming John De Goes as a Lift committer. John burst > onto the Lift scene a week or so ago with some excellent enhancements to the > Lift-json stuff and the rest is history. > > Welcome John... looking forward to excellent contributions from you and your > latest partner in crime, Kris Nuttycombe, a long-time Lift committer. > > Thanks, > > David > > -- > Lift, the simply functional web framework http://liftweb.net > Beginning Scala http://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 lift...@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. > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Comet issue for Lift-2.0-scala280-SNAPSHOT
On Mon, Feb 22, 2010 at 3:15 PM, Arie wrote:
> Hi,
>
> Can I clarify, is this a general issue to do with 2.8 Scala/Comet
> Actors? I think I may be having the same problem.
>
It's not CometActors that are causing the issue. In Scala 2.8, XML Node
equality testing is changed and supplying a label method that returns a
String (rather than Nothing) is a requirement. The fix for this issue is on
Review Board and has been approved. I'll likely get it rolled into
master/280_port_refresh tomorrow.
>
> Arie
>
> On Feb 22, 12:02 pm, Indrajit Raychaudhuri
> wrote:
> > Understood, just wanted to ensure.
> >
> > Cheers, Indrajit
> >
> > On 22/02/10 4:25 PM, tbje wrote:
> >
> >
> >
> > > Hi Indrajit,
> > > I was a little bit lazy and updated an old pom by hand.
> >
> > > Just pushed a new pom.xml using the following mvn
> > > archetype:generate :
> >
> > > mvn archetype:generate -U -DarchetypeGroupId=net.liftweb -
> > > DarchetypeArtifactId=lift-archetype-blank -DarchetypeVersion=2.0-
> > > scala280-SNAPSHOT -DarchetypeRepository=http://scala-tools.org/repo-
> > > snapshots -DremoteRepositories=http://scala-tools.org/repo-snapshots
> >
> > > Didn't solve the problem :(
> >
> > > Best regards
> > > Trond
> >
> > > On 19 Feb, 16:32, Indrajit Raychaudhuri wrote:
> > >> Trond,
> >
> > >> From cursory glance it appears that some old form of archetype (pre
> > >>Lift2.0) had been used to generate the project. What command line
> > >> option did you use in "mvn archetype:generate" to create the project?
> >
> > >> This is just a request for qualification.
> >
> > >> Cheers, Indrajit
> >
> > >> On 19/02/10 8:22 PM, tbje wrote:
> >
> > >>> Thank you for rapid replies and a great framework. I opened ticket
> > >>> #357 for this issue.
> >
> > >>> Best regards
> > >>> Trond
> >
> > >>> On 19 Feb, 15:22, Mariuswrote:
> > Yeah AFAIK Scala 2.8 integration is not 100% done and fully tested.
> >
> > Br's,
> > Marius
> >
> > On Feb 19, 3:52 pm, tbjewrote:
> >
> > > Hi Marius,
> > > I discovered the issue while porting a working application from
> 2.7.7
> > > tolift2.0-scala280-SNAPSHOT and scala 2.8.0.Beta1.
> >
> > > In the example application I provided it's possible to change the
> > > pom.xml by replacing
> > > 2.8.0.Beta1
> > > 2.0-scala280-SNAPSHOT
> > > with
> > > 2.7.7
> > > 2.0-SNAPSHOT
> > > and the application is working as I'd like it to :)
> >
> > > I therefor believe it's alift2.0-scala280 issue.
> >
> > > Best regards
> > > Trond
> >
> > > On 19 Feb, 14:12, Mariuswrote:
> >
> > >> Can you also try with Scala 2.7.7 ?
> >
> > >> On Feb 19, 2:26 pm, tbjewrote:
> >
> > >>> Hi,
> > >>> I've been testing out theLift-2.0-scala280-SNAPSHOT a little bit
> and
> > >>> found a issue with Cometactor, setHtml and ajaxInvoke.
> >
> > >>> When trying to invoke the following partial update nothing seems
> to
> > >>> happen:
> > >>> partialUpdate(SetHtml("field", > >>> onclick={ajaxInvoke(() =>JsRaw("alert('hi')"))._2} value="Say
> hi" /
> >
> > ))
> >
> > >>> This works as expected however:
> > >>> partialUpdate(SetHtml("field", a(() =>JsRaw("alert('hi')"),
> > >>> Link)))
> >
> > >>> I've created a example app to illustrate the problem if someone
> is
> > >>> interested:
> >
> > >>> git://github.com/tbje/Lift-2.0-scala280-SNAPSHOT-issue.git
> >
> > >>> Best regards
> > >>> Trond
>
> --
> You received this message because you are subscribed to the Google Groups
> "Lift" group.
> To post to this group, send email to lift...@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, the simply functional web framework http://liftweb.net
Beginning Scala http://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 lift...@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: Comet issue for Lift-2.0-scala280-SNAPSHOT
Hi,
Can I clarify, is this a general issue to do with 2.8 Scala/Comet
Actors? I think I may be having the same problem.
Arie
On Feb 22, 12:02 pm, Indrajit Raychaudhuri
wrote:
> Understood, just wanted to ensure.
>
> Cheers, Indrajit
>
> On 22/02/10 4:25 PM, tbje wrote:
>
>
>
> > Hi Indrajit,
> > I was a little bit lazy and updated an old pom by hand.
>
> > Just pushed a new pom.xml using the following mvn
> > archetype:generate :
>
> > mvn archetype:generate -U -DarchetypeGroupId=net.liftweb -
> > DarchetypeArtifactId=lift-archetype-blank -DarchetypeVersion=2.0-
> > scala280-SNAPSHOT -DarchetypeRepository=http://scala-tools.org/repo-
> > snapshots -DremoteRepositories=http://scala-tools.org/repo-snapshots
>
> > Didn't solve the problem :(
>
> > Best regards
> > Trond
>
> > On 19 Feb, 16:32, Indrajit Raychaudhuri wrote:
> >> Trond,
>
> >> From cursory glance it appears that some old form of archetype (pre
> >>Lift2.0) had been used to generate the project. What command line
> >> option did you use in "mvn archetype:generate" to create the project?
>
> >> This is just a request for qualification.
>
> >> Cheers, Indrajit
>
> >> On 19/02/10 8:22 PM, tbje wrote:
>
> >>> Thank you for rapid replies and a great framework. I opened ticket
> >>> #357 for this issue.
>
> >>> Best regards
> >>> Trond
>
> >>> On 19 Feb, 15:22, Marius wrote:
> Yeah AFAIK Scala 2.8 integration is not 100% done and fully tested.
>
> Br's,
> Marius
>
> On Feb 19, 3:52 pm, tbje wrote:
>
> > Hi Marius,
> > I discovered the issue while porting a working application from 2.7.7
> > tolift2.0-scala280-SNAPSHOT and scala 2.8.0.Beta1.
>
> > In the example application I provided it's possible to change the
> > pom.xml by replacing
> > 2.8.0.Beta1
> > 2.0-scala280-SNAPSHOT
> > with
> > 2.7.7
> > 2.0-SNAPSHOT
> > and the application is working as I'd like it to :)
>
> > I therefor believe it's alift2.0-scala280 issue.
>
> > Best regards
> > Trond
>
> > On 19 Feb, 14:12, Marius wrote:
>
> >> Can you also try with Scala 2.7.7 ?
>
> >> On Feb 19, 2:26 pm, tbje wrote:
>
> >>> Hi,
> >>> I've been testing out theLift-2.0-scala280-SNAPSHOT a little bit and
> >>> found a issue with Cometactor, setHtml and ajaxInvoke.
>
> >>> When trying to invoke the following partial update nothing seems to
> >>> happen:
> >>> partialUpdate(SetHtml("field", >>> onclick={ajaxInvoke(() => JsRaw("alert('hi')"))._2} value="Say hi"
> >>> /
>
> ))
>
> >>> This works as expected however:
> >>> partialUpdate(SetHtml("field", a(() => JsRaw("alert('hi')"),
> >>> Link)))
>
> >>> I've created a example app to illustrate the problem if someone is
> >>> interested:
>
> >>> git://github.com/tbje/Lift-2.0-scala280-SNAPSHOT-issue.git
>
> >>> Best regards
> >>> Trond
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@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.
Re: [Lift] Welcome John De Goes as a Lift committer
re-welcome! All official this time and everything. -Ross On Feb 22, 2010, at 3:55 PM, David Pollak wrote: > Folks, > > Please join me in welcoming John De Goes as a Lift committer. John burst > onto the Lift scene a week or so ago with some excellent enhancements to the > Lift-json stuff and the rest is history. > > Welcome John... looking forward to excellent contributions from you and your > latest partner in crime, Kris Nuttycombe, a long-time Lift committer. > > Thanks, > > David > > -- > Lift, the simply functional web framework http://liftweb.net > Beginning Scala http://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 lift...@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. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Welcome John De Goes as a Lift committer
Hi John ;-) On 22 February 2010 21:55, David Pollak wrote: > Folks, > > Please join me in welcoming John De Goes as a Lift committer. John burst > onto the Lift scene a week or so ago with some excellent enhancements to the > Lift-json stuff and the rest is history. > > Welcome John... looking forward to excellent contributions from you and > your latest partner in crime, Kris Nuttycombe, a long-time Lift committer. > > Thanks, > > David > > -- > Lift, the simply functional web framework http://liftweb.net > Beginning Scala http://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 lift...@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. > -- Heiko Seeberger Work: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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: What is the current working pattern for storing timestamps?
Yep, the consensus seems to be that you should use JodaTime (and scala- time). You can use scala-time with Maven (URL: http://scala-tools.org/repo-releases/org/scala-tools/time/) but it was compiled with Scala 2.7.4. However, I didn't have any noticeable problems running it on 2.7.7. Peter On Feb 22, 10:41 am, Hannes wrote: > Hi Peter, > > Thanks in advance. > > I was browsing through the list and read, that there's a lot of problems > with the Java stuff. That's why I asked. I'll have a look at this > JodaTime thing... > > thanks. > > > > > Hi Hannes, > > > Jonathan's suggestion of MappedDateTime is a good one and one that I > > have used. However, I haven't been super happy about how time is > > handled by, in my case, MappedDateTime + java.util.Date + MySQL > > Datetime. I played around a little with making a MappedField that > > holds a ScalaTime (ie JodaTime) object that would be persisted in a > > database as a millisecond UTC timestamp but didn't get very far with > > it. I believe if you look through this mailing list you'll find > > someone else (sorry, I forget who!) talking about basically doing just > > this and sharing some code. Anyway, just another possible approach... > > > Peter > > > On Feb 21, 10:59 am, Jonathan Hoffman wrote: > > >> Does MappedDateTime do what you want? > > >> Also look at MappedEnum for the status > > >> On Feb 21, 2010, at 6:07 AM, Hannes wrote: > > >>> Hi Lifters, > > >>> I'm using Mapper with Lift 1.1-M7 and I need to have some information > >>> about time. > > >>> Especially I wanna store a time-stamp for a status field that can have > >>> three values: NEW; OPEN; CLOSED; > > >>> So, what I thought about was defining two new fields open_time and > >>> close_time that I'd use to filter/sort items. > > >>> thanks for any ideas! > > >>> -- > >>> You received this message because you are subscribed to the Google Groups > >>> "Lift" group. > >>> To post to this group, send email to lift...@googlegroups.com. > >>> To unsubscribe from this group, send email to > >>> liftweb+unsubscr...@googlegroups.com. > >>> For more options, visit this group > >>> athttp://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Lift tool survey
Mads, What is your timeline? I have something cooking with the boys over at SBT if your interested... we have laid the ground work and made modifications to SBT itself but it requires an implementation on the Lift side (of which we have I fairly good plan for) Interested? Ping me off list and lets chat. Cheers, Tim On 22 Feb 2010, at 21:52, Mads Hartmann wrote: > Hello everyone > > Coming from other web-frameworks or just in general what are the tools > you miss the most when working on your lift project? > > I'm trying to create the foundation for a Google of Summer Code > project and would really like to work on tooling for lift, so if you > would take the time to help me out by answering the question, I would > truly appreciate it :) > > Thanks, > Mads Hartmann Jensen > > > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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. > > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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: Welcome John De Goes as a Lift committer
Welcome John De Goes! On Feb 22, 9:55 pm, David Pollak wrote: > Folks, > > Please join me in welcoming John De Goes as a Lift committer. John burst > onto the Lift scene a week or so ago with some excellent enhancements to the > Lift-json stuff and the rest is history. > > Welcome John... looking forward to excellent contributions from you and your > latest partner in crime, Kris Nuttycombe, a long-time Lift committer. > > Thanks, > > David > > -- > 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 lift...@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] Lift tool survey
Hello everyone Coming from other web-frameworks or just in general what are the tools you miss the most when working on your lift project? I'm trying to create the foundation for a Google of Summer Code project and would really like to work on tooling for lift, so if you would take the time to help me out by answering the question, I would truly appreciate it :) Thanks, Mads Hartmann Jensen -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] anybody used OPA?
> This is related to Lift how? It appears to be a framework itself... ja, i figure people who use Lift are the kinds of people who might have their ear to the ground for other approaches to the web problem, and might have insight into Competitor X, Y, or Z. i've certainly seen people talk about other Java solutions before, admittedly ML is further afield, although given Scala, not that much. sincerely. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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: Lift security vulnerability
More information on this in case anyone is interested. If you go to the lift demo website, it appears the issue with characters is mostly addressed except for the "Misc code" section. Specifically, the "Wizard", "Wizard Challenge" and "Arc Challenge #1" examples will generate XML parsing errors. For these problems, I am not sure if the issue if the example or the framework. If the issue is with the example, it would be good to know what Lift apps need to do to avoid getting bitten by binary characters entered into form fields. Thanks in advance. Dan On Feb 17, 11:06 am, Dano wrote: > Hello, > > I was wondering if the fix for the control characters issue was > included in 2.0-M2. I just did a test with our Lift application built > with 2.0-M2 and I am still seeing problems (i.e. javascript exceptions > - NS_ERROR_INVALID_POINTER). > > Thanks in advance. > > Dan > > On Feb 3, 9:08 am, David Pollak wrote: > > > > > Thanks for pointing that out. There are other problems as well... I'll fix > > them (in both the Scala and Lift diffs) > > > On Wed, Feb 3, 2010 at 7:39 AM, Feng Zhang wrote: > > > I found that in the fix, \n is changed to \t, while \t to \n. Is this > > > desired behavior? > > > > Thank you, > > > > Feng > > > > On Wed, Feb 3, 2010 at 9:20 AM, Indrajit Raychaudhuri > > > wrote: > > > >> 1. Fix in head/master (2.0-SNAPSHOT) and prepone 2.0-M2. > > > >> 2. Backport in 1.0.x branch and spin 1.0.4. We haven't marked 1.0.x > > >> 'unsupported' yet. Forcing apps to move to 2.0-M2 just for this > > >> vulnerability fix isn't fun. > > > >> Cheers, Indrajit > > > >> On 03/02/10 3:34 PM, Timothy Perrett wrote: > > > >>> +1 > > > >>> Fix it in head, no need to back-port; M2 is only around the corner. > > > >>> Cheers, Tim > > > >>> On 3 Feb 2010, at 09:49, Jeppe Nejsum Madsen wrote: > > > >>> David Pollak writes: > > > I'd like to get a sense of how important the community views this > > > defect. > > > Is it a "backport the fix to every milestone and release yesterday" or > > > is it > > > a "fix it in 2.0-M2" or someplace in between. > > > For me, it's fix it in 2.0-SNAPSHOT > > > /Jeppe > > > -- > > You received this message because you are subscribed to the Google > > Groups "Lift" group. > > To post to this group, send email to lift...@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. > > > >> -- > > >> You received this message because you are subscribed to the Google Groups > > >> "Lift" group. > > >> To post to this group, send email to lift...@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. > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Lift" group. > > > To post to this group, send email to lift...@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, 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 lift...@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.
Re: [Lift] Re: Documenting the source code / supplementing the API docs
Great... okay, I’d better do some writing :-) In the absence of a decision I’ll try to minimise special coding in comments but use Scaladoc 2 standard if necessary rather than HTML as that makes it future proof but still readable for both. Stuart On 22 Feb 2010, at 17:32, Ross Mellgren wrote: > I will do this, and give feed back if it ever becomes too much load. > > -Ross > > On Feb 22, 2010, at 12:05 PM, Timothy Perrett wrote: > >> We are interested in the contribution of course... I think the issue is >> mostly about how we take patches for this. Someone on the team would need to >> own this and merge your documentation changes into the master (provided DPP >> has no objections to this - seeing as its documentation I doubt he has) >> >> Any takers from the team? >> >> Cheers, Tim >> >> On 22 Feb 2010, at 16:14, Stuart Roebuck wrote: >> >>> Sorry for the slow response—was away for a family weekend! >>> >>> I have limited knowledge of Lift internals… >>> >>> However, my view is that it is often easier to document code when you >>> don't know it well than when you do, because you soon loose interest >>> in documenting things that are obvious to you. What I hope to do is >>> document the things that I need to know as I go along on the basis >>> that many of these things will also be important to others. It's an >>> agile rather than systematic approach if you see what I mean. >>> >>> I have no ego issues here. It's just a small way of giving to the >>> community in a win-win kind of way. If my contributions don't seem >>> helpful to anyone else then folk can say and I'm not going to >>> disappear in a torrent of abuse :-) >>> >>> Similarly, I'm not proposing some big project here. I'm talking about >>> a drip-drip of updates as I spot things that need documenting—I've got >>> plenty other stuff on my plate right now as I'm launching a company >>> based on a Lift based product in mid-year. >>> >>> Enough said… >>> >>> How do we resolve the documentation standard issue? (Scala 2.8 >>> Scaladoc2 or prior) David? >>> >>> Stuart. >>> >>> On Feb 19, 4:11 pm, Timothy Perrett wrote: This could work - although, some parts of lift are very non-trivial and require good knowledge of lift internals. Do you have such knowledge or are you just hoping to contribute where you can with helpful information? Both are good, just trying to establish what you had in mind. Lift-util probably has the best docs at the moment, so if we could emulate that it would be good. Cheers, Tim On 19 Feb 2010, at 15:56, Ross Mellgren wrote: > If you can get an established standard on what the content and format > should be, I can work with you reviewing the patches and applying them. > But, need to get a concordance from the list on the content first. > -Ross > On Feb 19, 2010, at 10:53 AM, Stuart Roebuck wrote: >> I've had a bit of a break from Lift and coming back I find myself >> annoyed that I didn't write some notes last time and am having to go >> back to searching through the various bits of documentation to figure >> things out. >> Anyway, after much thought I decided that the best way to write my >> notes would be to supplement the API docs (ie. the Scaladoc >> documentation in the code base). so that I can view context sensitive >> help in my IDE of choice and others can benefit from my labours! >> So, question 1… >> The current API docs are very light on documentation and sometime ago >> I noticed some notice about removing documentation from the code >> base. Is there some policy about not having documentation in the >> code or any thought on whether it should adhere to the Scaladoc 2 >> syntax? >> Question 2… >> This is only really going to work if the process of submitting the >> documentation is reasonably straightforward so… What's the easiest >> possible way of submitting documentation changes to the code base? (if >> indeed this is something the core team would welcome). I was >> thinking of perhaps emailing git patch files to someone in the core >> team who can verify that the comments are right before checking them >> in. Any thoughts? >> If there is a reasonably explainable approach, it could be added as a >> Wiki page to encourage wider participation. >> Best, >> Stuart. >> -- >> You received this message because you are subscribed to the Google >> Groups "Lift" group. >> To post to this group, send email to lift...@googlegroups.com. >> To unsubscribe from this group, send email to >> liftweb+unsubscr...@googlegroups.com. >> For more options, visit this group >> athttp://groups.google.com/group/liftweb?hl=en. > -- > You received this message because you are subs
[Lift] Welcome John De Goes as a Lift committer
Folks, Please join me in welcoming John De Goes as a Lift committer. John burst onto the Lift scene a week or so ago with some excellent enhancements to the Lift-json stuff and the rest is history. Welcome John... looking forward to excellent contributions from you and your latest partner in crime, Kris Nuttycombe, a long-time Lift committer. Thanks, David -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://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 lift...@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.
Re: [Lift] anybody used OPA?
This is related to Lift how? It appears to be a framework itself... Cheers, Tim On 22 Feb 2010, at 19:51, Raoul Duke wrote: > http://mlstate.com > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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. > > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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] anybody used OPA?
http://mlstate.com -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
Sorry David, do you mean you don't like configgy because it can change configurations at runtime? It can only do that if you specifically tell it to. Without registered observers, changes to the .conf file are ignored. Certainly, thats the way it works within all my applications that i've used configgy to date. Cheers, Tim On 22 Feb 2010, at 18:51, David Pollak wrote: > > > On Mon, Feb 22, 2010 at 10:42 AM, Timothy Perrett > wrote: > Whilst we are talking about Props, I wouldn't mind seeing a level of > abstraction on Props so that it can load stuff from things other than .props > files. For instance, Im using configgy more and more these days as its much > more preferable to properties files for app configuration. > > Anyone got any thoughts on this? > > I'd love to see a more flexible file format for properties as well as support > for merging a "secret" set of properties (e.g., ones that contain passwords > that you don't want to put into source control) during property file parsing. > > The thing I'm not keen on with Configgy is the ability to change > configurations during runtime. > > > Cheers, Tim > > On 22 Feb 2010, at 18:34, Jeppe Nejsum Madsen wrote: > > > On Mon, Feb 22, 2010 at 7:13 PM, David Pollak > > wrote: > >> I've closed Jeppe's ticket. Why? > >> > >> WebKit depends on util. Props (where the runmode is defined) is in util, > >> so > >> there would be a circular reference if LiftRules was used to calculate the > >> runmode. > >> > >> Further, util can be used outside of the context of WebKit/Boot. We want > >> to > >> encourage that. > > > > Fair point. I keep forgetting about those other uses :-) > > > > /Jeppe > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Lift" group. > > To post to this group, send email to lift...@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. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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, the simply functional web framework http://liftweb.net > Beginning Scala http://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 lift...@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. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
On Mon, Feb 22, 2010 at 10:42 AM, Timothy Perrett wrote: > Whilst we are talking about Props, I wouldn't mind seeing a level of > abstraction on Props so that it can load stuff from things other than .props > files. For instance, Im using configgy more and more these days as its much > more preferable to properties files for app configuration. > > Anyone got any thoughts on this? > I'd love to see a more flexible file format for properties as well as support for merging a "secret" set of properties (e.g., ones that contain passwords that you don't want to put into source control) during property file parsing. The thing I'm not keen on with Configgy is the ability to change configurations during runtime. > > Cheers, Tim > > On 22 Feb 2010, at 18:34, Jeppe Nejsum Madsen wrote: > > > On Mon, Feb 22, 2010 at 7:13 PM, David Pollak > > wrote: > >> I've closed Jeppe's ticket. Why? > >> > >> WebKit depends on util. Props (where the runmode is defined) is in > util, so > >> there would be a circular reference if LiftRules was used to calculate > the > >> runmode. > >> > >> Further, util can be used outside of the context of WebKit/Boot. We > want to > >> encourage that. > > > > Fair point. I keep forgetting about those other uses :-) > > > > /Jeppe > > > > -- > > You received this message because you are subscribed to the Google Groups > "Lift" group. > > To post to this group, send email to lift...@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. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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, the simply functional web framework http://liftweb.net Beginning Scala http://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 lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
Whilst we are talking about Props, I wouldn't mind seeing a level of abstraction on Props so that it can load stuff from things other than .props files. For instance, Im using configgy more and more these days as its much more preferable to properties files for app configuration. Anyone got any thoughts on this? Cheers, Tim On 22 Feb 2010, at 18:34, Jeppe Nejsum Madsen wrote: > On Mon, Feb 22, 2010 at 7:13 PM, David Pollak > wrote: >> I've closed Jeppe's ticket. Why? >> >> WebKit depends on util. Props (where the runmode is defined) is in util, so >> there would be a circular reference if LiftRules was used to calculate the >> runmode. >> >> Further, util can be used outside of the context of WebKit/Boot. We want to >> encourage that. > > Fair point. I keep forgetting about those other uses :-) > > /Jeppe > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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. > > -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: What is the current working pattern for storing timestamps?
Hi Peter, Thanks in advance. I was browsing through the list and read, that there's a lot of problems with the Java stuff. That's why I asked. I'll have a look at this JodaTime thing... thanks. Hi Hannes, Jonathan's suggestion of MappedDateTime is a good one and one that I have used. However, I haven't been super happy about how time is handled by, in my case, MappedDateTime + java.util.Date + MySQL Datetime. I played around a little with making a MappedField that holds a ScalaTime (ie JodaTime) object that would be persisted in a database as a millisecond UTC timestamp but didn't get very far with it. I believe if you look through this mailing list you'll find someone else (sorry, I forget who!) talking about basically doing just this and sharing some code. Anyway, just another possible approach... Peter On Feb 21, 10:59 am, Jonathan Hoffman wrote: Does MappedDateTime do what you want? Also look at MappedEnum for the status On Feb 21, 2010, at 6:07 AM, Hannes wrote: Hi Lifters, I'm using Mapper with Lift 1.1-M7 and I need to have some information about time. Especially I wanna store a time-stamp for a status field that can have three values: NEW; OPEN; CLOSED; So, what I thought about was defining two new fields open_time and close_time that I'd use to filter/sort items. thanks for any ideas! -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
On Mon, Feb 22, 2010 at 7:13 PM, David Pollak wrote: > I've closed Jeppe's ticket. Why? > > WebKit depends on util. Props (where the runmode is defined) is in util, so > there would be a circular reference if LiftRules was used to calculate the > runmode. > > Further, util can be used outside of the context of WebKit/Boot. We want to > encourage that. Fair point. I keep forgetting about those other uses :-) /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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: Versions: Netbeans, Scala and Lift
Thanks very much, this is great support. I e-mailed Caoyuan separately, to hedge my bet and prompted by him I ended up finding this post - http://groups.google.com/group/liftweb/browse_thread/thread/768c6798017b5b6b/9961710446c7dd20- which managed to clear everything up, I didn't know about 6.7.1 though. NetBeans is great, much better than Eclipse I find. On Feb 22, 6:16 pm, David Pollak wrote: > On Mon, Feb 22, 2010 at 9:56 AM, Peter Robinett > wrote: > > > I'm running Netbeans 6.7.1 with the Maven and Scala 2.7 plugins quite > > happily on OS X. > > For mainline Lift development, I'm very happily using NB 6.7.1 and the 2.7.7 > plugin. > > For 2.8.0 related Lift and Goat Rodeo development, I'm using NB 6.8 and the > 2.8 plugin. > > In both cases, I set the maximum heap size for NB to 2.5GB (from the default > max of 512MB). > > The 2.7 plugin is good and stable and functional. The 2.8 plugin is > awesome. It's got the same code navigation tools the IntelliJ does and it's > very, very fast. I love it. > > > > > > > > > Peter > > > On Feb 21, 10:34 pm, Caoyuan wrote: > > > Yes, Scala plugin for NetBeans 6.8 needs Scala 2.8, thus lift's 280 > > branches. > > > > For Maven project, there is no need to set Scala home and dependent > > > libs in NetBeans, all these setting are in pom.xml. > > > > Cheers, > > > -Caoyuan > > > > On Mon, Feb 22, 2010 at 5:51 AM, Ross Mellgren wrote: > > > > Lift 1.1 and 2.0 are the same code stream by the way, just 1.1 was > > renamed to 2.0 after 1.1-M8. That said, the most recent versions of > > 2.0-SNAPSHOT and 1.1-SNAPSHOT run on Scala 2.7.7. The new 2.0-SNAPSHOT > > branch for Scala 2.8.0 (280_port_refresh, built as 2.0-scala280-SNAPSHOT I > > believe) runs on Scala 2.8.0 Beta 1. > > > > > I have no idea about NetBeans, though I've heard on the list a couple > > times that the most recent versions are Scala 2.8 only. > > > > > Keep in mind that Scala is extremely version sensitive and not backward > > compatible. > > > > > Hope that helps, > > > > -Ross > > > > > On Feb 21, 2010, at 4:06 PM, Arie wrote: > > > > >> I've been going through as many posts as possible to try to establish > > > >> how to use Netbeans (on a Mac) with Lift. > > > > >> I think I'm correct in saying that Netbeans 6.8 will only work with > > > >> Scala 2.8 (beta/snapshot -http://wiki.netbeans.org/Scala68v1), and > > > >> that from this (http://old.nabble.com/Lift-1.1-SNAPSHOT-under- > > > >> Scala-2.8-with-NetBeans-and-the-Scala-plugin-td25302936.html) Lift 1.1 > > > >> will only work with Scala 2.7.5. > > > > >> What will Lift 1.0 work with in Netbeans (if it will), and related, > > > >> how do I square getting Lift (version 1.0/1.1), to work in Netbeans > > > >> 6.8 which seems to require Scala 2.8? > > > > >> Will any of these problems be solved by Lift 2.0, and when is 2.0 > > > >> scheduled to come out!? > > > > >> Thanks. > > > > >> -- > > > >> You received this message because you are subscribed to the Google > > Groups "Lift" group. > > > >> To post to this group, send email to lift...@googlegroups.com. > > > >> To unsubscribe from this group, send email to > > liftweb+unsubscr...@googlegroups.com > > > > . > > > >> For more options, visit this group athttp:// > > groups.google.com/group/liftweb?hl=en. > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups "Lift" group. > > > > To post to this group, send email to lift...@googlegroups.com. > > > > To unsubscribe from this group, send email to > > liftweb+unsubscr...@googlegroups.com > > > > . > > > > For more options, visit this group athttp:// > > groups.google.com/group/liftweb?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Lift" group. > > To post to this group, send email to lift...@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, 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 lift...@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] unCamelCase,camelCase & capify
Hi, I'm finally returning to #155 (support for snake_case in Mapper) and found a few inconsistencies In StringHelpers we have capify commafy (which I don't really understand, but never mind :-) In ClassHelpers we have camelCase camelCaseMethod unCamelCase The methods in ClassHelpers are just string manipulation functions so I think they belong in StringHelpers. Also it seems the naming is a bit inconsistent, with "-fying" being my preference. So I propose the following ClassHelpers.unCamelCase -> StringHelpers.snakify ClassHelpers.camelCase -> StringHelpers.camelify ClassHelpers.camelCaseMethod -> StringHelpers.camelifyMethod with due deprecation of old methods. capify seems to do almost the same as camelCase, but not quite so probably have to leave it. Thoughts? /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: how to put UTF string into the redirect URL?
On Sat, Feb 20, 2010 at 11:51 PM, Marius wrote:
> I think you need to URL encode it.
>
S.redirectTo("/foo?bar="+Helpers.urlEncode(str))
>
> On 21 feb., 04:33, wm wrote:
> > I need put some UTF string into the URL to be redirected, e.g.:
> >
> > str = 'some-UTF-str'
> > S.redirectTo("/foo?bar="+str)
> >
> > But after the redirection, in the browser address bar it becomes:
> http://localhost:8080//foo?bar=???
> >
> > '???' is the messed up UTF string.
> >
> > How can I fix this? thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Lift" group.
> To post to this group, send email to lift...@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, the simply functional web framework http://liftweb.net
Beginning Scala http://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 lift...@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.
Re: [Lift] Re: redirectTo in (Stateful)Snippets
On Mon, Feb 22, 2010 at 1:53 AM, Restel, Hannes <
hannes.res...@isst.fraunhofer.de> wrote:
> Hi Nico,
> thanks for your answer.
>
> I think you misunderstood me: I want to redirect to a HTML-page without
> using a SiteMap at all. So the page I redirect to is not registered in any
> place. It simply resides in my 'webapp' folder.
> But when trying to redirect to that page, the resource (i.e. my page) is
> not found.
>
Yes. This is correct behavior. If you have defined a SiteMap, Lift will
not serve any pages except those that are defined in the SiteMap. If you
are using Lift > 1.0.x, there will be a polite message as part of the 404
informing you why the page was not served (if you're running in development
mode.)
You have a couple of choices to serve additional pages. First, you can
include them in the SiteMap and mark them as "Hidden" such that there's no
menu item displayed, but the page will still be served. Second, you can
define a subdirectory that all content will be served from.
>
> So please try again :-)
>
> (And yes: I did read The Lift Book :-)
>
> Cheers,
> Hannes
>
>
>
> -Original Message-
> From: liftweb@googlegroups.com [mailto:lift...@googlegroups.com] On Behalf
> Of Nico Tromp
> Sent: Friday, February 19, 2010 2:46 PM
> To: Lift
> Subject: [Lift] Re: redirectTo in (Stateful)Snippets
>
> Hannes, sorry for the strange :) sentence. It should read:
>
> did you register the page in the Boot class?
>
> If you want to know more about the SiteMap have a look at chapter 5
> from the lift book. At the bottom of the page (http://
> groups.google.com/group/the-lift-book) there is a link to the PDF
> version.
>
> Happy reading
>
> Nico Tromp
>
> On Feb 19, 1:49 pm, Nico Tromp wrote:
> > Hannes,
> >
> > did you registered the page in the in the Boot class? Below is a small
> > example.
> >
> > ===
> > class Boot {
> > def boot {
> > // where to search snippet
> > // LiftRules.addToPackages("")
> >
> > // Build SiteMap
> > val entries = Menu(Loc("Home", List("index"), "Home")) ::
> > Menu(Loc("Search", List("search"), "Search page")) ::
> > Nil
> > LiftRules.setSiteMap(SiteMap(entries:_*))
> > }}
> >
> > ===
> > Hope this is helpfull
> >
> > Cheers Nico Tromp
> >
> > On Feb 19, 1:26 pm, "Restel, Hannes"
> >
> >
> >
> > wrote:
> > > Hi,
> >
> > > I am new to Lift (and Scala) and need help with dispatching/redirecting
> to a page after processing a form.
> >
> > > My problem: I get a "The Requested URL /search was not found on this
> server" error message although the page "search.html" does exist.
> >
> > > When adding the page "search.html" to the LiftRules-SiteMap, then the
> page does exist!
> > > So is there any need to register HTML pages? I hope not!
> >
> > > This is my HTML fragment:
> > >
> > > Search
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > > And this is the corresponding Scala code:
> > > class HelloWorld extends StatefulSnippet {
> >
> > > override def dispatch:DispatchIt = {
> > > case "search" => search _
> > > }
> >
> > > def search(xhtml : NodeSeq) : NodeSeq = {
> > > object searchExpression extends RequestVar("")
> >
> > > def processSearch () {
> > > if (searchExpression.isEmpty) {
> > > S.error("Must not be empty!")
> > > }
> > > else {
> > > S.notice("Value was: " + searchExpression)
> > > redirectTo("/search")
> > > }
> > > }
> >
> > > bind("entry", xhtml,
> > > "searchfield" -> SHtml.text(searchExpression.is,
> searchExpression(_)),
> > > "submit" -> SHtml.submit("Suche", processSearch)
> > > )
> > > }
> >
> > > }
> >
> > > Why cannot my "/search" page be found?
> >
> > > Thanks for help!
> > > Hannes
> >
> > > Hannes Restel | Fraunhofer Institut für Software- und Systemtechnik
> > > Sichere Business IT-Infrastrukuren, Studentischer Mitarbeiter
> > > Steinplatz 2, 10623 Berlin, Germany
> > > Telefon: +49 (0)30/24 306-324
> > > mailto:hannes.res...@isst.fraunhofer.dehttp://www.isst.fraunhofer.de
>
> --
> You received this message because you are subscribed to the Google Groups
> "Lift" group.
> To post to this group, send email to lift...@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.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Lift" group.
> To post to this group, send email to lift...@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, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf th
Re: [Lift] Re: Versions: Netbeans, Scala and Lift
On Mon, Feb 22, 2010 at 9:56 AM, Peter Robinett wrote: > I'm running Netbeans 6.7.1 with the Maven and Scala 2.7 plugins quite > happily on OS X. > For mainline Lift development, I'm very happily using NB 6.7.1 and the 2.7.7 plugin. For 2.8.0 related Lift and Goat Rodeo development, I'm using NB 6.8 and the 2.8 plugin. In both cases, I set the maximum heap size for NB to 2.5GB (from the default max of 512MB). The 2.7 plugin is good and stable and functional. The 2.8 plugin is awesome. It's got the same code navigation tools the IntelliJ does and it's very, very fast. I love it. > > Peter > > On Feb 21, 10:34 pm, Caoyuan wrote: > > Yes, Scala plugin for NetBeans 6.8 needs Scala 2.8, thus lift's 280 > branches. > > > > For Maven project, there is no need to set Scala home and dependent > > libs in NetBeans, all these setting are in pom.xml. > > > > Cheers, > > -Caoyuan > > > > > > > > On Mon, Feb 22, 2010 at 5:51 AM, Ross Mellgren wrote: > > > Lift 1.1 and 2.0 are the same code stream by the way, just 1.1 was > renamed to 2.0 after 1.1-M8. That said, the most recent versions of > 2.0-SNAPSHOT and 1.1-SNAPSHOT run on Scala 2.7.7. The new 2.0-SNAPSHOT > branch for Scala 2.8.0 (280_port_refresh, built as 2.0-scala280-SNAPSHOT I > believe) runs on Scala 2.8.0 Beta 1. > > > > > I have no idea about NetBeans, though I've heard on the list a couple > times that the most recent versions are Scala 2.8 only. > > > > > Keep in mind that Scala is extremely version sensitive and not backward > compatible. > > > > > Hope that helps, > > > -Ross > > > > > On Feb 21, 2010, at 4:06 PM, Arie wrote: > > > > >> I've been going through as many posts as possible to try to establish > > >> how to use Netbeans (on a Mac) with Lift. > > > > >> I think I'm correct in saying that Netbeans 6.8 will only work with > > >> Scala 2.8 (beta/snapshot -http://wiki.netbeans.org/Scala68v1), and > > >> that from this (http://old.nabble.com/Lift-1.1-SNAPSHOT-under- > > >> Scala-2.8-with-NetBeans-and-the-Scala-plugin-td25302936.html) Lift 1.1 > > >> will only work with Scala 2.7.5. > > > > >> What will Lift 1.0 work with in Netbeans (if it will), and related, > > >> how do I square getting Lift (version 1.0/1.1), to work in Netbeans > > >> 6.8 which seems to require Scala 2.8? > > > > >> Will any of these problems be solved by Lift 2.0, and when is 2.0 > > >> scheduled to come out!? > > > > >> Thanks. > > > > >> -- > > >> You received this message because you are subscribed to the Google > Groups "Lift" group. > > >> To post to this group, send email to lift...@googlegroups.com. > > >> To unsubscribe from this group, send email to > liftweb+unsubscr...@googlegroups.com > . > > >> For more options, visit this group athttp:// > groups.google.com/group/liftweb?hl=en. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups "Lift" group. > > > To post to this group, send email to lift...@googlegroups.com. > > > To unsubscribe from this group, send email to > liftweb+unsubscr...@googlegroups.com > . > > > For more options, visit this group athttp:// > groups.google.com/group/liftweb?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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, the simply functional web framework http://liftweb.net Beginning Scala http://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 lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
I've closed Jeppe's ticket. Why?
WebKit depends on util. Props (where the runmode is defined) is in util, so
there would be a circular reference if LiftRules was used to calculate the
runmode.
Further, util can be used outside of the context of WebKit/Boot. We want to
encourage that.
So, creating a "mode calculation function" that's consulted during the
evaluation of the run mode in props makes sense. But this function has to
be set super duper uper mooper early in the app initialization cycle because
the run mode is calculated in order to figure out which property file to
load and this is done the first time a property is accessed.
Put another way, if we do a "calculation function", it's going to be the
first thing that needs to be set in Boot. Then there's going to be
confusion.
It might be just as easy for the OP to write a mock filter that's
initialized before the Lift filter which does System.setProperty("run.mode",
)
On Mon, Feb 22, 2010 at 7:03 AM, Indrajit Raychaudhuri
wrote:
>
> On 22/02/10 3:22 PM, Indrajit Raychaudhuri wrote:
>
>> Given that setting initParams is the usual webapp idiom, should we not
>> consider that at all? That would have served the purpose for Petr.
>>
>> So the calcRunMode could roughly have something like:
>>
>> customRunMode or context.initParam("run.mode") or
>> Box.!!(System.getProperty("run.mode"))
>>
>> with provision for having customRunMode customized heartily.
>>
>
> On second thought, the order probably should be other way round.
>
> Box.!!(System.getProperty("run.mode")) or context.initParam("run.mode") or
> customRunMode
>
> -Drun.mode=... is more transient (and suitable for fast mode switching
> during development) than static definition in the code and thus to be tried
> first.
>
>
>
>> Cheers, Indrajit
>>
>>
>> On 22/02/10 1:50 PM, Jeppe Nejsum Madsen wrote:
>>
>>> On Mon, Feb 22, 2010 at 8:48 AM, Heiko Seeberger
>>> wrote:
>>>
Folks,
I really do not understand the value of setting the run mode
statically via
code in LiftRules. The run mode should be set externally, right? In
order to
use the same artifact (WAR) on a dev or a prod server.
Heiko
>>>
>>> Agreed. This was more so that people could change how "externally" is
>>> defined, ie in a hosted env you can't change system properties.
>>>
>>> The default would still be the current lookup in system properties,
>>> but you could change this to look at servlet params, hostname, day of
>>> month etc :-)
>>>
>>> /Jeppe
>>>
>>>
> --
> You received this message because you are subscribed to the Google Groups
> "Lift" group.
> To post to this group, send email to lift...@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, the simply functional web framework http://liftweb.net
Beginning Scala http://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 lift...@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.
Re: [Lift] Re: Cached CSS (and Javascript?) issue
On Sun, Feb 21, 2010 at 9:49 AM, Marius wrote: > Guys, > > I'm starting to have second thoughts about having css or js combine > (concatenation of multiple files into a single response) on lift side. > I'm starting to question that real benefits as in production sites in > many cases the lift app has a http reverse proxy front end that can > serve static content js/css etc. Thus combining multiple js/css with > simple tools seems more practical. > > Thoughts? By simple tools I assume you mean at build time? How would this handle classpath resources? I don't think that doing it on the lift side conflicts with the reverse proxy. If everything is configured correctly, the proxy should only fetch the resource from lift once, see that the resource expires far in the future and cache it. There are a number of (I think) conflicting scenarios that Lift should support: 1) Good defaults that deliver great performance out of the box without too much hassle during development/build/deploy time. This is where I think Lift combining resources would be used. 2) The absolute best performance no matter what. This probably includes multiple hosts for static resources, CDNs etc. If you're going this route you're willing to sacrifice ease of use for that last ounce of speed. If/when load time becomes an issue for us this will be one of the first things I'll try to investigate :-) /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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: Versions: Netbeans, Scala and Lift
I'm running Netbeans 6.7.1 with the Maven and Scala 2.7 plugins quite happily on OS X. Peter On Feb 21, 10:34 pm, Caoyuan wrote: > Yes, Scala plugin for NetBeans 6.8 needs Scala 2.8, thus lift's 280 branches. > > For Maven project, there is no need to set Scala home and dependent > libs in NetBeans, all these setting are in pom.xml. > > Cheers, > -Caoyuan > > > > On Mon, Feb 22, 2010 at 5:51 AM, Ross Mellgren wrote: > > Lift 1.1 and 2.0 are the same code stream by the way, just 1.1 was renamed > > to 2.0 after 1.1-M8. That said, the most recent versions of 2.0-SNAPSHOT > > and 1.1-SNAPSHOT run on Scala 2.7.7. The new 2.0-SNAPSHOT branch for Scala > > 2.8.0 (280_port_refresh, built as 2.0-scala280-SNAPSHOT I believe) runs on > > Scala 2.8.0 Beta 1. > > > I have no idea about NetBeans, though I've heard on the list a couple times > > that the most recent versions are Scala 2.8 only. > > > Keep in mind that Scala is extremely version sensitive and not backward > > compatible. > > > Hope that helps, > > -Ross > > > On Feb 21, 2010, at 4:06 PM, Arie wrote: > > >> I've been going through as many posts as possible to try to establish > >> how to use Netbeans (on a Mac) with Lift. > > >> I think I'm correct in saying that Netbeans 6.8 will only work with > >> Scala 2.8 (beta/snapshot -http://wiki.netbeans.org/Scala68v1), and > >> that from this (http://old.nabble.com/Lift-1.1-SNAPSHOT-under- > >> Scala-2.8-with-NetBeans-and-the-Scala-plugin-td25302936.html) Lift 1.1 > >> will only work with Scala 2.7.5. > > >> What will Lift 1.0 work with in Netbeans (if it will), and related, > >> how do I square getting Lift (version 1.0/1.1), to work in Netbeans > >> 6.8 which seems to require Scala 2.8? > > >> Will any of these problems be solved by Lift 2.0, and when is 2.0 > >> scheduled to come out!? > > >> Thanks. > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Lift" group. > >> To post to this group, send email to lift...@googlegroups.com. > >> To unsubscribe from this group, send email to > >> liftweb+unsubscr...@googlegroups.com. > >> For more options, visit this group > >> athttp://groups.google.com/group/liftweb?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Lift" group. > > To post to this group, send email to lift...@googlegroups.com. > > To unsubscribe from this group, send email to > > liftweb+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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] Advice for maintaining application state
Apologies in advance for the long post, but I have a question for the group about best practices for handling application state in Lift. By way of background, our team members are Lift newbies but have been building web applications for well over a decade, using many different languages and frameworks. The application that we are developing has a tabbed user experience. The tab usage is somewhat different from the norm in that, instead of representing a choice from fixed set of categories, each tab represents a complex record from our application's database (think a case file). Within each tab the same pages appear, but with the data on the pages focused around a the currently selected case. Users create/destroy tabs as they use the application. An analogy might be the use of Worksheets within Excel files. We have been using a SessionVar to store the IDs of the cases that the user has opened as tabs, as well as the ID currently selected case. And the following scenario has cropped up: User selects tab A, visits pages 1, 2, 3. User selects tab B and visits page 1 (but this time in the context of record B) User clicks "back" and sees page A 3. At this point the state of the application is out of sync with the page the user is seeing. Because the SessionVar holding the id of the current case ID is "B", clicking on any of the links on this page will display unexpected data (relative to "B" rather than the "A" that appears on the screen). Obviously this situation is as old as the web itself and isn't unique to Lift. In the past we would have baked these IDs into the page itself as form parameters and passed them around as query strings on links. However, I was wondering if there is a more idiomatic, Lift- like way of maintaining this kind of state. Certainly we could resort to the old techniques of passing this around from page to page, but it seems at odds with the stateful nature of Lift. And given our relative inexperience with the framework, we wanted to reach out and see if there is a better way of handling this before we proceed. Any advice appreciated. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Documenting the source code / supplementing the API docs
I will do this, and give feed back if it ever becomes too much load. -Ross On Feb 22, 2010, at 12:05 PM, Timothy Perrett wrote: > We are interested in the contribution of course... I think the issue is > mostly about how we take patches for this. Someone on the team would need to > own this and merge your documentation changes into the master (provided DPP > has no objections to this - seeing as its documentation I doubt he has) > > Any takers from the team? > > Cheers, Tim > > On 22 Feb 2010, at 16:14, Stuart Roebuck wrote: > >> Sorry for the slow response—was away for a family weekend! >> >> I have limited knowledge of Lift internals… >> >> However, my view is that it is often easier to document code when you >> don't know it well than when you do, because you soon loose interest >> in documenting things that are obvious to you. What I hope to do is >> document the things that I need to know as I go along on the basis >> that many of these things will also be important to others. It's an >> agile rather than systematic approach if you see what I mean. >> >> I have no ego issues here. It's just a small way of giving to the >> community in a win-win kind of way. If my contributions don't seem >> helpful to anyone else then folk can say and I'm not going to >> disappear in a torrent of abuse :-) >> >> Similarly, I'm not proposing some big project here. I'm talking about >> a drip-drip of updates as I spot things that need documenting—I've got >> plenty other stuff on my plate right now as I'm launching a company >> based on a Lift based product in mid-year. >> >> Enough said… >> >> How do we resolve the documentation standard issue? (Scala 2.8 >> Scaladoc2 or prior) David? >> >> Stuart. >> >> On Feb 19, 4:11 pm, Timothy Perrett wrote: >>> This could work - although, some parts of lift are very non-trivial and >>> require good knowledge of lift internals. Do you have such knowledge or are >>> you just hoping to contribute where you can with helpful information? Both >>> are good, just trying to establish what you had in mind. >>> >>> Lift-util probably has the best docs at the moment, so if we could emulate >>> that it would be good. >>> >>> Cheers, Tim >>> >>> On 19 Feb 2010, at 15:56, Ross Mellgren wrote: >>> >>> >>> If you can get an established standard on what the content and format should be, I can work with you reviewing the patches and applying them. >>> But, need to get a concordance from the list on the content first. >>> -Ross >>> On Feb 19, 2010, at 10:53 AM, Stuart Roebuck wrote: >>> > I've had a bit of a break from Lift and coming back I find myself > annoyed that I didn't write some notes last time and am having to go > back to searching through the various bits of documentation to figure > things out. >>> > Anyway, after much thought I decided that the best way to write my > notes would be to supplement the API docs (ie. the Scaladoc > documentation in the code base). so that I can view context sensitive > help in my IDE of choice and others can benefit from my labours! >>> > So, question 1… >>> > The current API docs are very light on documentation and sometime ago > I noticed some notice about removing documentation from the code > base. Is there some policy about not having documentation in the > code or any thought on whether it should adhere to the Scaladoc 2 > syntax? >>> > Question 2… >>> > This is only really going to work if the process of submitting the > documentation is reasonably straightforward so… What's the easiest > possible way of submitting documentation changes to the code base? (if > indeed this is something the core team would welcome). I was > thinking of perhaps emailing git patch files to someone in the core > team who can verify that the comments are right before checking them > in. Any thoughts? >>> > If there is a reasonably explainable approach, it could be added as a > Wiki page to encourage wider participation. >>> > Best, >>> > Stuart. >>> > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@googlegroups.com. > To unsubscribe from this group, send email to > liftweb+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/liftweb?hl=en. >>> -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/liftweb?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Lift" group. >> To post
Re: [Lift] Re: Documenting the source code / supplementing the API docs
Perhaps it's easier for me to do a fork on GitHub? Then any documentation submissions can be taken across at a time that suits whoever is doing it rather than synced with my submission timeline? On 22 Feb 2010, at 17:05, Timothy Perrett wrote: > We are interested in the contribution of course... I think the issue is > mostly about how we take patches for this. Someone on the team would need to > own this and merge your documentation changes into the master (provided DPP > has no objections to this - seeing as its documentation I doubt he has) > > Any takers from the team? > > Cheers, Tim > > On 22 Feb 2010, at 16:14, Stuart Roebuck wrote: > >> Sorry for the slow response—was away for a family weekend! >> >> I have limited knowledge of Lift internals… >> >> However, my view is that it is often easier to document code when you >> don't know it well than when you do, because you soon loose interest >> in documenting things that are obvious to you. What I hope to do is >> document the things that I need to know as I go along on the basis >> that many of these things will also be important to others. It's an >> agile rather than systematic approach if you see what I mean. >> >> I have no ego issues here. It's just a small way of giving to the >> community in a win-win kind of way. If my contributions don't seem >> helpful to anyone else then folk can say and I'm not going to >> disappear in a torrent of abuse :-) >> >> Similarly, I'm not proposing some big project here. I'm talking about >> a drip-drip of updates as I spot things that need documenting—I've got >> plenty other stuff on my plate right now as I'm launching a company >> based on a Lift based product in mid-year. >> >> Enough said… >> >> How do we resolve the documentation standard issue? (Scala 2.8 >> Scaladoc2 or prior) David? >> >> Stuart. >> >> On Feb 19, 4:11 pm, Timothy Perrett wrote: >>> This could work - although, some parts of lift are very non-trivial and >>> require good knowledge of lift internals. Do you have such knowledge or are >>> you just hoping to contribute where you can with helpful information? Both >>> are good, just trying to establish what you had in mind. >>> >>> Lift-util probably has the best docs at the moment, so if we could emulate >>> that it would be good. >>> >>> Cheers, Tim >>> >>> On 19 Feb 2010, at 15:56, Ross Mellgren wrote: >>> >>> >>> If you can get an established standard on what the content and format should be, I can work with you reviewing the patches and applying them. >>> But, need to get a concordance from the list on the content first. >>> -Ross >>> On Feb 19, 2010, at 10:53 AM, Stuart Roebuck wrote: >>> > I've had a bit of a break from Lift and coming back I find myself > annoyed that I didn't write some notes last time and am having to go > back to searching through the various bits of documentation to figure > things out. >>> > Anyway, after much thought I decided that the best way to write my > notes would be to supplement the API docs (ie. the Scaladoc > documentation in the code base). so that I can view context sensitive > help in my IDE of choice and others can benefit from my labours! >>> > So, question 1… >>> > The current API docs are very light on documentation and sometime ago > I noticed some notice about removing documentation from the code > base. Is there some policy about not having documentation in the > code or any thought on whether it should adhere to the Scaladoc 2 > syntax? >>> > Question 2… >>> > This is only really going to work if the process of submitting the > documentation is reasonably straightforward so… What's the easiest > possible way of submitting documentation changes to the code base? (if > indeed this is something the core team would welcome). I was > thinking of perhaps emailing git patch files to someone in the core > team who can verify that the comments are right before checking them > in. Any thoughts? >>> > If there is a reasonably explainable approach, it could be added as a > Wiki page to encourage wider participation. >>> > Best, >>> > Stuart. >>> > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@googlegroups.com. > To unsubscribe from this group, send email to > liftweb+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/liftweb?hl=en. >>> -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/liftweb?hl=e
Re: [Lift] Re: London Lift talk
The problem is that im based in the westcountry... so its more getting there in the first instance if im not in the city for work. Cheers, Tim On 22 Feb 2010, at 17:04, Richard Dallaway wrote: > > There'll be a trip to the pub after, if that's any use as an incentive > to come along :-) -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Documenting the source code / supplementing the API docs
We are interested in the contribution of course... I think the issue is mostly about how we take patches for this. Someone on the team would need to own this and merge your documentation changes into the master (provided DPP has no objections to this - seeing as its documentation I doubt he has) Any takers from the team? Cheers, Tim On 22 Feb 2010, at 16:14, Stuart Roebuck wrote: > Sorry for the slow response—was away for a family weekend! > > I have limited knowledge of Lift internals… > > However, my view is that it is often easier to document code when you > don't know it well than when you do, because you soon loose interest > in documenting things that are obvious to you. What I hope to do is > document the things that I need to know as I go along on the basis > that many of these things will also be important to others. It's an > agile rather than systematic approach if you see what I mean. > > I have no ego issues here. It's just a small way of giving to the > community in a win-win kind of way. If my contributions don't seem > helpful to anyone else then folk can say and I'm not going to > disappear in a torrent of abuse :-) > > Similarly, I'm not proposing some big project here. I'm talking about > a drip-drip of updates as I spot things that need documenting—I've got > plenty other stuff on my plate right now as I'm launching a company > based on a Lift based product in mid-year. > > Enough said… > > How do we resolve the documentation standard issue? (Scala 2.8 > Scaladoc2 or prior) David? > > Stuart. > > On Feb 19, 4:11 pm, Timothy Perrett wrote: >> This could work - although, some parts of lift are very non-trivial and >> require good knowledge of lift internals. Do you have such knowledge or are >> you just hoping to contribute where you can with helpful information? Both >> are good, just trying to establish what you had in mind. >> >> Lift-util probably has the best docs at the moment, so if we could emulate >> that it would be good. >> >> Cheers, Tim >> >> On 19 Feb 2010, at 15:56, Ross Mellgren wrote: >> >> >> >>> If you can get an established standard on what the content and format >>> should be, I can work with you reviewing the patches and applying them. >> >>> But, need to get a concordance from the list on the content first. >> >>> -Ross >> >>> On Feb 19, 2010, at 10:53 AM, Stuart Roebuck wrote: >> I've had a bit of a break from Lift and coming back I find myself annoyed that I didn't write some notes last time and am having to go back to searching through the various bits of documentation to figure things out. >> Anyway, after much thought I decided that the best way to write my notes would be to supplement the API docs (ie. the Scaladoc documentation in the code base). so that I can view context sensitive help in my IDE of choice and others can benefit from my labours! >> So, question 1… >> The current API docs are very light on documentation and sometime ago I noticed some notice about removing documentation from the code base. Is there some policy about not having documentation in the code or any thought on whether it should adhere to the Scaladoc 2 syntax? >> Question 2… >> This is only really going to work if the process of submitting the documentation is reasonably straightforward so… What's the easiest possible way of submitting documentation changes to the code base? (if indeed this is something the core team would welcome). I was thinking of perhaps emailing git patch files to someone in the core team who can verify that the comments are right before checking them in. Any thoughts? >> If there is a reasonably explainable approach, it could be added as a Wiki page to encourage wider participation. >> Best, >> Stuart. >> -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/liftweb?hl=en. >> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Lift" group. >>> To post to this group, send email to lift...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> liftweb+unsubscr...@googlegroups.com. >>> For more options, visit this group >>> athttp://groups.google.com/group/liftweb?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to lift...@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. > > -- You received this
Re: [Lift] Re: London Lift talk
On Sun, Feb 21, 2010 at 1:09 AM, Timothy Perrett wrote: > Man, I really must try and drag my ass along to this... There'll be a trip to the pub after, if that's any use as an incentive to come along :-) Cheers Richard -- @d6y -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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: Documenting the source code / supplementing the API docs
Sorry for the slow response—was away for a family weekend! I have limited knowledge of Lift internals… However, my view is that it is often easier to document code when you don't know it well than when you do, because you soon loose interest in documenting things that are obvious to you. What I hope to do is document the things that I need to know as I go along on the basis that many of these things will also be important to others. It's an agile rather than systematic approach if you see what I mean. I have no ego issues here. It's just a small way of giving to the community in a win-win kind of way. If my contributions don't seem helpful to anyone else then folk can say and I'm not going to disappear in a torrent of abuse :-) Similarly, I'm not proposing some big project here. I'm talking about a drip-drip of updates as I spot things that need documenting—I've got plenty other stuff on my plate right now as I'm launching a company based on a Lift based product in mid-year. Enough said… How do we resolve the documentation standard issue? (Scala 2.8 Scaladoc2 or prior) David? Stuart. On Feb 19, 4:11 pm, Timothy Perrett wrote: > This could work - although, some parts of lift are very non-trivial and > require good knowledge of lift internals. Do you have such knowledge or are > you just hoping to contribute where you can with helpful information? Both > are good, just trying to establish what you had in mind. > > Lift-util probably has the best docs at the moment, so if we could emulate > that it would be good. > > Cheers, Tim > > On 19 Feb 2010, at 15:56, Ross Mellgren wrote: > > > > > If you can get an established standard on what the content and format > > should be, I can work with you reviewing the patches and applying them. > > > But, need to get a concordance from the list on the content first. > > > -Ross > > > On Feb 19, 2010, at 10:53 AM, Stuart Roebuck wrote: > > >> I've had a bit of a break from Lift and coming back I find myself > >> annoyed that I didn't write some notes last time and am having to go > >> back to searching through the various bits of documentation to figure > >> things out. > > >> Anyway, after much thought I decided that the best way to write my > >> notes would be to supplement the API docs (ie. the Scaladoc > >> documentation in the code base). so that I can view context sensitive > >> help in my IDE of choice and others can benefit from my labours! > > >> So, question 1… > > >> The current API docs are very light on documentation and sometime ago > >> I noticed some notice about removing documentation from the code > >> base. Is there some policy about not having documentation in the > >> code or any thought on whether it should adhere to the Scaladoc 2 > >> syntax? > > >> Question 2… > > >> This is only really going to work if the process of submitting the > >> documentation is reasonably straightforward so… What's the easiest > >> possible way of submitting documentation changes to the code base? (if > >> indeed this is something the core team would welcome). I was > >> thinking of perhaps emailing git patch files to someone in the core > >> team who can verify that the comments are right before checking them > >> in. Any thoughts? > > >> If there is a reasonably explainable approach, it could be added as a > >> Wiki page to encourage wider participation. > > >> Best, > > >> Stuart. > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Lift" group. > >> To post to this group, send email to lift...@googlegroups.com. > >> To unsubscribe from this group, send email to > >> liftweb+unsubscr...@googlegroups.com. > >> For more options, visit this group > >> athttp://groups.google.com/group/liftweb?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Lift" group. > > To post to this group, send email to lift...@googlegroups.com. > > To unsubscribe from this group, send email to > > liftweb+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Has anyone gotten the uservoice javascript to work?
*grumble smurf* Ok. I'll just use the link then, and try to get an example up. On Sat, Feb 20, 2010 at 12:26 PM, David Pollak < feeder.of.the.be...@gmail.com> wrote: > > > On Sat, Feb 20, 2010 at 10:59 AM, Jeppe Nejsum Madsen wrote: > >> On Sat, Feb 20, 2010 at 7:36 PM, Marius wrote: >> > In boot try setting LiftRules.useXhtmlMimeType = false; >> >> I've had the same issues and iircc it's an issue with the Uservoice >> script not being fully xhtml compliant even if the problem is marked >> as fixed... >> >> What exactly does one loose by putting useXhtmlMimeType in Boot? >> > > In my experience, the layout deltas in XHTML are fewer across browsers. > > >> >> /Jeppe >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Lift" group. >> To post to this group, send email to lift...@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, the simply functional web framework http://liftweb.net > Beginning Scala http://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 lift...@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. > -- James A Barrows -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
On 22/02/10 3:22 PM, Indrajit Raychaudhuri wrote:
Given that setting initParams is the usual webapp idiom, should we not
consider that at all? That would have served the purpose for Petr.
So the calcRunMode could roughly have something like:
customRunMode or context.initParam("run.mode") or
Box.!!(System.getProperty("run.mode"))
with provision for having customRunMode customized heartily.
On second thought, the order probably should be other way round.
Box.!!(System.getProperty("run.mode")) or context.initParam("run.mode")
or customRunMode
-Drun.mode=... is more transient (and suitable for fast mode switching
during development) than static definition in the code and thus to be
tried first.
Cheers, Indrajit
On 22/02/10 1:50 PM, Jeppe Nejsum Madsen wrote:
On Mon, Feb 22, 2010 at 8:48 AM, Heiko Seeberger
wrote:
Folks,
I really do not understand the value of setting the run mode
statically via
code in LiftRules. The run mode should be set externally, right? In
order to
use the same artifact (WAR) on a dev or a prod server.
Heiko
Agreed. This was more so that people could change how "externally" is
defined, ie in a hosted env you can't change system properties.
The default would still be the current lookup in system properties,
but you could change this to look at servlet params, hostname, day of
month etc :-)
/Jeppe
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@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] **IMPORTANT** White space separator is discontinued for resource keys
Folks, If you are an i18n type, read it! Going forward we are making two policy changes in the naming convention for i18n resource keys; viz., Discontinuing the usage of white space to separate keys and preferring all.lower.case for the keys. So in you locale properties file, instead of: Current\ Mood=What ya up to? you would be writing: current.mood=What ya up to? While the former is perfectly valid in in Java (and thus in Scala), the usage is awkward and confusing. It also throws the IDE code inspectors off the track :) Further, it's good convention to have the keys in lower case character. All the built-in resources in lift-core.properties (and the other existing locale variant) have been updated. ProtoUser has also been updated to to reflect the same. Please reply back to this post if you see something missing. Cheers, Indrajit [1] http://groups.google.com/group/liftweb/browse_thread/thread/7c31bc68e33bf0e0/731da62cfc406821 [2] http://www.assembla.com/spaces/liftweb/tickets/320 [3] http://github.com/dpp/liftweb/commit/8d012190168574279369af19dd29f0b5d4086796 -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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] Tricky question regarding menus
Hi, I want to create a menu with the following structure: main1 main2 main3... sub1a sub1b sub2a sub2b sub3a ... page1a1 page1a2 ... Now I want some of the main and sub menus not to have "their own pages" but have the same link as certain child pages. Example: When the user clicks main1 the page page1a1 is to be shown. Of course main1 and sub1a are to be marked as "currently selected" menu, hence Loc.doesMatch_? must return true. If I create the Locs for main1 and sub1a with the link to page1a1 (main1/sub1a/paga1a1) then doesMatch_? will not be true for all other child pages of main1 and sub1a. Is there a simple solution to this? Or do I have to write my own Loc implementation? Thank you, Heiko Seeberger Work: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
RE: [Lift] Re: redirectTo in (Stateful)Snippets
Hi Nico,
thanks for your answer.
I think you misunderstood me: I want to redirect to a HTML-page without using a
SiteMap at all. So the page I redirect to is not registered in any place. It
simply resides in my 'webapp' folder.
But when trying to redirect to that page, the resource (i.e. my page) is not
found.
So please try again :-)
(And yes: I did read The Lift Book :-)
Cheers,
Hannes
-Original Message-
From: liftweb@googlegroups.com [mailto:lift...@googlegroups.com] On Behalf Of
Nico Tromp
Sent: Friday, February 19, 2010 2:46 PM
To: Lift
Subject: [Lift] Re: redirectTo in (Stateful)Snippets
Hannes, sorry for the strange :) sentence. It should read:
did you register the page in the Boot class?
If you want to know more about the SiteMap have a look at chapter 5
from the lift book. At the bottom of the page (http://
groups.google.com/group/the-lift-book) there is a link to the PDF
version.
Happy reading
Nico Tromp
On Feb 19, 1:49 pm, Nico Tromp wrote:
> Hannes,
>
> did you registered the page in the in the Boot class? Below is a small
> example.
>
> ===
> class Boot {
> def boot {
> // where to search snippet
> // LiftRules.addToPackages("")
>
> // Build SiteMap
> val entries = Menu(Loc("Home", List("index"), "Home")) ::
> Menu(Loc("Search", List("search"), "Search page")) ::
> Nil
> LiftRules.setSiteMap(SiteMap(entries:_*))
> }}
>
> ===
> Hope this is helpfull
>
> Cheers Nico Tromp
>
> On Feb 19, 1:26 pm, "Restel, Hannes"
>
>
>
> wrote:
> > Hi,
>
> > I am new to Lift (and Scala) and need help with dispatching/redirecting to
> > a page after processing a form.
>
> > My problem: I get a "The Requested URL /search was not found on this
> > server" error message although the page "search.html" does exist.
>
> > When adding the page "search.html" to the LiftRules-SiteMap, then the page
> > does exist!
> > So is there any need to register HTML pages? I hope not!
>
> > This is my HTML fragment:
> >
> > Search
> >
> >
> >
> >
> >
> >
>
> > And this is the corresponding Scala code:
> > class HelloWorld extends StatefulSnippet {
>
> > override def dispatch:DispatchIt = {
> > case "search" => search _
> > }
>
> > def search(xhtml : NodeSeq) : NodeSeq = {
> > object searchExpression extends RequestVar("")
>
> > def processSearch () {
> > if (searchExpression.isEmpty) {
> > S.error("Must not be empty!")
> > }
> > else {
> > S.notice("Value was: " + searchExpression)
> > redirectTo("/search")
> > }
> > }
>
> > bind("entry", xhtml,
> > "searchfield" -> SHtml.text(searchExpression.is,
> > searchExpression(_)),
> > "submit" -> SHtml.submit("Suche", processSearch)
> > )
> > }
>
> > }
>
> > Why cannot my "/search" page be found?
>
> > Thanks for help!
> > Hannes
>
> > Hannes Restel | Fraunhofer Institut für Software- und Systemtechnik
> > Sichere Business IT-Infrastrukuren, Studentischer Mitarbeiter
> > Steinplatz 2, 10623 Berlin, Germany
> > Telefon: +49 (0)30/24 306-324
> > mailto:hannes.res...@isst.fraunhofer.dehttp://www.isst.fraunhofer.de
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@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.
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@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: ProtoUser i18n
On RB: http://reviewboard.liftweb.net/r/223/ Cheers, Indrajit On Feb 3, 9:36 pm, Indrajit Raychaudhuri wrote: > Thanks Adam, I'll take this one up :) > > - Indrajit > > On 03/02/10 12:48 PM, Adam Warski wrote: > > > > > Sure: > > > (a)http://github.com/dpp/liftweb/issues/issue/320 > > (b)http://gist.github.com/293435 > > > I've also updated the wiki. > > > On Feb 2, 2010, at 8:10 PM, Indrajit Raychaudhuri wrote: > > >> Adam, can you please (a) open a ticket and (b) create a gist > >> (http://gist.github.com/) of the patch and refer to it from the ticket? > >> We'll take it up from there. > > >> Tim, +1 on not having spaces in properties. > > >> Cheers, Indrajit > > >> On 02/02/10 10:41 PM, Timothy Perrett wrote: > >>> Sure - one of us will take this up... its minor. > > >>> I propose we agree a policy, and use that going forward... should keys > >>> have spaces? "no" would be my default response... (i tend to separate > >>> with full stops) if thats so, lets just clear that out now, and do a > >>> breaking changes ann. > > >>> Cheers, Tim > > >>> On 2 Feb 2010, at 17:06, David Pollak wrote: > > I'm okay with breakage here. Jeppe, Indrajit, or Tim, can you guys > handle this issue going forward (making sure the patch is good, putting > it on a branch, opening a ticket, putting it on review board, and > sending out any breaking changes email)? > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Lift" group. > >> To post to this group, send email to lift...@googlegroups.com. > >> To unsubscribe from this group, send email to > >> liftweb+unsubscr...@googlegroups.com. > >> For more options, visit this group > >> athttp://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Textmate bundle with codecompletion (beta)
Don't get too excited, it's very beta right now ;) Sent from my iPhone On 22/02/2010, at 13.04, Indrajit Raychaudhuri wrote: Heavens! Need to give this a shot. On 22/02/10 4:55 PM, Mads Hartmann wrote: Hello everyone, I've been working a bit on a TextMate bundle for Lift projects that has codecompletion. It's still very beta but I'm sure someone would find it helpfull :) If you're interested you can read a bit more about it here: http://www.sidewayscoding.com/2010/02/lift-textmate-bundle-now-with-primitive.html NB: It's nowhere near as good as what I've seen in intelliJ (haven't tried netbeans or eclipse) but that doesn't mean it isn't helpful :) If you want to help out, please fork me on github http://github.com/mads379 -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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 . -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Textmate bundle with codecompletion (beta)
Heavens! Need to give this a shot. On 22/02/10 4:55 PM, Mads Hartmann wrote: Hello everyone, I've been working a bit on a TextMate bundle for Lift projects that has codecompletion. It's still very beta but I'm sure someone would find it helpfull :) If you're interested you can read a bit more about it here: http://www.sidewayscoding.com/2010/02/lift-textmate-bundle-now-with-primitive.html NB: It's nowhere near as good as what I've seen in intelliJ (haven't tried netbeans or eclipse) but that doesn't mean it isn't helpful :) If you want to help out, please fork me on github http://github.com/mads379 -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Comet issue for Lift-2.0-scala280-SNAPSHOT
Understood, just wanted to ensure.
Cheers, Indrajit
On 22/02/10 4:25 PM, tbje wrote:
Hi Indrajit,
I was a little bit lazy and updated an old pom by hand.
Just pushed a new pom.xml using the following mvn
archetype:generate :
mvn archetype:generate -U -DarchetypeGroupId=net.liftweb -
DarchetypeArtifactId=lift-archetype-blank -DarchetypeVersion=2.0-
scala280-SNAPSHOT -DarchetypeRepository=http://scala-tools.org/repo-
snapshots -DremoteRepositories=http://scala-tools.org/repo-snapshots
Didn't solve the problem :(
Best regards
Trond
On 19 Feb, 16:32, Indrajit Raychaudhuri wrote:
Trond,
From cursory glance it appears that some old form of archetype (pre
Lift 2.0) had been used to generate the project. What command line
option did you use in "mvn archetype:generate" to create the project?
This is just a request for qualification.
Cheers, Indrajit
On 19/02/10 8:22 PM, tbje wrote:
Thank you for rapid replies and a great framework. I opened ticket
#357 for this issue.
Best regards
Trond
On 19 Feb, 15:22, Mariuswrote:
Yeah AFAIK Scala 2.8 integration is not 100% done and fully tested.
Br's,
Marius
On Feb 19, 3:52 pm, tbjewrote:
Hi Marius,
I discovered the issue while porting a working application from 2.7.7
to lift 2.0-scala280-SNAPSHOT and scala 2.8.0.Beta1.
In the example application I provided it's possible to change the
pom.xml by replacing
2.8.0.Beta1
2.0-scala280-SNAPSHOT
with
2.7.7
2.0-SNAPSHOT
and the application is working as I'd like it to :)
I therefor believe it's a lift 2.0-scala280 issue.
Best regards
Trond
On 19 Feb, 14:12, Mariuswrote:
Can you also try with Scala 2.7.7 ?
On Feb 19, 2:26 pm, tbjewrote:
Hi,
I've been testing out the Lift-2.0-scala280-SNAPSHOT a little bit and
found a issue with Comet actor, setHtml and ajaxInvoke.
When trying to invoke the following partial update nothing seems to
happen:
partialUpdate(SetHtml("field",JsRaw("alert('hi')"))._2} value="Say hi" /
))
This works as expected however:
partialUpdate(SetHtml("field", a(() =>JsRaw("alert('hi')"),
Link)))
I've created a example app to illustrate the problem if someone is
interested:
git://github.com/tbje/Lift-2.0-scala280-SNAPSHOT-issue.git
Best regards
Trond
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@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] Textmate bundle with codecompletion (beta)
Hello everyone, I've been working a bit on a TextMate bundle for Lift projects that has codecompletion. It's still very beta but I'm sure someone would find it helpfull :) If you're interested you can read a bit more about it here: http://www.sidewayscoding.com/2010/02/lift-textmate-bundle-now-with-primitive.html NB: It's nowhere near as good as what I've seen in intelliJ (haven't tried netbeans or eclipse) but that doesn't mean it isn't helpful :) If you want to help out, please fork me on github http://github.com/mads379 -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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: Comet issue for Lift-2.0-scala280-SNAPSHOT
Hi Indrajit,
I was a little bit lazy and updated an old pom by hand.
Just pushed a new pom.xml using the following mvn
archetype:generate :
mvn archetype:generate -U -DarchetypeGroupId=net.liftweb -
DarchetypeArtifactId=lift-archetype-blank -DarchetypeVersion=2.0-
scala280-SNAPSHOT -DarchetypeRepository=http://scala-tools.org/repo-
snapshots -DremoteRepositories=http://scala-tools.org/repo-snapshots
Didn't solve the problem :(
Best regards
Trond
On 19 Feb, 16:32, Indrajit Raychaudhuri wrote:
> Trond,
>
> From cursory glance it appears that some old form of archetype (pre
> Lift 2.0) had been used to generate the project. What command line
> option did you use in "mvn archetype:generate" to create the project?
>
> This is just a request for qualification.
>
> Cheers, Indrajit
>
> On 19/02/10 8:22 PM, tbje wrote:
>
>
>
> > Thank you for rapid replies and a great framework. I opened ticket
> > #357 for this issue.
>
> > Best regards
> > Trond
>
> > On 19 Feb, 15:22, Marius wrote:
> >> Yeah AFAIK Scala 2.8 integration is not 100% done and fully tested.
>
> >> Br's,
> >> Marius
>
> >> On Feb 19, 3:52 pm, tbje wrote:
>
> >>> Hi Marius,
> >>> I discovered the issue while porting a working application from 2.7.7
> >>> to lift 2.0-scala280-SNAPSHOT and scala 2.8.0.Beta1.
>
> >>> In the example application I provided it's possible to change the
> >>> pom.xml by replacing
> >>> 2.8.0.Beta1
> >>> 2.0-scala280-SNAPSHOT
> >>> with
> >>> 2.7.7
> >>> 2.0-SNAPSHOT
> >>> and the application is working as I'd like it to :)
>
> >>> I therefor believe it's a lift 2.0-scala280 issue.
>
> >>> Best regards
> >>> Trond
>
> >>> On 19 Feb, 14:12, Marius wrote:
>
> Can you also try with Scala 2.7.7 ?
>
> On Feb 19, 2:26 pm, tbje wrote:
>
> > Hi,
> > I've been testing out the Lift-2.0-scala280-SNAPSHOT a little bit and
> > found a issue with Comet actor, setHtml and ajaxInvoke.
>
> > When trying to invoke the following partial update nothing seems to
> > happen:
> > partialUpdate(SetHtml("field", > onclick={ajaxInvoke(() => JsRaw("alert('hi')"))._2} value="Say hi" /
>
> >> ))
>
> > This works as expected however:
> > partialUpdate(SetHtml("field", a(() => JsRaw("alert('hi')"),
> > Link)))
>
> > I've created a example app to illustrate the problem if someone is
> > interested:
>
> > git://github.com/tbje/Lift-2.0-scala280-SNAPSHOT-issue.git
>
> > Best regards
> > Trond
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
On 22 February 2010 10:52, Indrajit Raychaudhuri wrote:
> Given that setting initParams is the usual webapp idiom, should we not
> consider that at all? That would have served the purpose for Petr.
>
> customRunMode or context.initParam("run.mode") or
> Box.!!(System.getProperty("run.mode"))
>
> with provision for having customRunMode customized heartily.
>
Looks good!
Heiko
Work: weiglewilczek.com
Blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: scalamodules.org
Lift, the simply functional web framework: liftweb.net
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
Given that setting initParams is the usual webapp idiom, should we not
consider that at all? That would have served the purpose for Petr.
So the calcRunMode could roughly have something like:
customRunMode or context.initParam("run.mode") or
Box.!!(System.getProperty("run.mode"))
with provision for having customRunMode customized heartily.
Cheers, Indrajit
On 22/02/10 1:50 PM, Jeppe Nejsum Madsen wrote:
On Mon, Feb 22, 2010 at 8:48 AM, Heiko Seeberger
wrote:
Folks,
I really do not understand the value of setting the run mode statically via
code in LiftRules. The run mode should be set externally, right? In order to
use the same artifact (WAR) on a dev or a prod server.
Heiko
Agreed. This was more so that people could change how "externally" is
defined, ie in a hosted env you can't change system properties.
The default would still be the current lookup in system properties,
but you could change this to look at servlet params, hostname, day of
month etc :-)
/Jeppe
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@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: What is the current working pattern for storing timestamps?
Hi Hannes, Jonathan's suggestion of MappedDateTime is a good one and one that I have used. However, I haven't been super happy about how time is handled by, in my case, MappedDateTime + java.util.Date + MySQL Datetime. I played around a little with making a MappedField that holds a ScalaTime (ie JodaTime) object that would be persisted in a database as a millisecond UTC timestamp but didn't get very far with it. I believe if you look through this mailing list you'll find someone else (sorry, I forget who!) talking about basically doing just this and sharing some code. Anyway, just another possible approach... Peter On Feb 21, 10:59 am, Jonathan Hoffman wrote: > Does MappedDateTime do what you want? > > Also look at MappedEnum for the status > > On Feb 21, 2010, at 6:07 AM, Hannes wrote: > > > > > Hi Lifters, > > > I'm using Mapper with Lift 1.1-M7 and I need to have some information about > > time. > > > Especially I wanna store a time-stamp for a status field that can have > > three values: NEW; OPEN; CLOSED; > > > So, what I thought about was defining two new fields open_time and > > close_time that I'd use to filter/sort items. > > > thanks for any ideas! > > > -- > > You received this message because you are subscribed to the Google Groups > > "Lift" group. > > To post to this group, send email to lift...@googlegroups.com. > > To unsubscribe from this group, send email to > > liftweb+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
On 22 February 2010 09:20, Jeppe Nejsum Madsen wrote: > > The default would still be the current lookup in system properties, > but you could change this to look at servlet params, hostname, day of > month etc :-) > Ah, OK. I agree if and only you will also enable setting the run mode depending on the beer-level of the deployer ;-) Heiko Work: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
Re: [Lift] Re: Setting run mode for Lift applications
On Mon, Feb 22, 2010 at 8:48 AM, Heiko Seeberger wrote: > Folks, > I really do not understand the value of setting the run mode statically via > code in LiftRules. The run mode should be set externally, right? In order to > use the same artifact (WAR) on a dev or a prod server. > Heiko Agreed. This was more so that people could change how "externally" is defined, ie in a hosted env you can't change system properties. The default would still be the current lookup in system properties, but you could change this to look at servlet params, hostname, day of month etc :-) /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
