Quite so, go for M8. M6 was recommended when M8 hadn't come out. Cheers, Indrajit
On 29/12/09 11:44 PM, Ross Mellgren wrote: > M8 is pretty stable, yes. M7 was not, and so M6 was recommended before > that. I haven't heard of any reason to recommend M6 over M8, but maybe > dpp has some reasons. > > -Ross > > On Dec 29, 2009, at 1:11 PM, Alex Black wrote: > >> Is M8 pretty stable? A little while back DavidP recommended M6 as >> being the most stable of the milestones. >> >> On Tue, Dec 29, 2009 at 1:07 PM, Ross Mellgren <dri...@gmail.com >> <mailto:dri...@gmail.com>> wrote: >> >> Switch to 1.1-M8, if you can. >> >> -Ross >> >> On Dec 29, 2009, at 1:04 PM, Alex Black wrote: >> >> > >> >> To be clear, RewriteResponse is a LiftResponse, and therefore, >> valid. >> > >> > I had tried it, and got a compile error, keep in mind I'm still on >> > 1.0: >> > >> > >> >> http://scala-tools.org/scaladocs/liftweb/1.0/net/liftweb/http/RewriteResponse.html >> > >> >> If you want to display the contents of your 404.html, checkout >> >> NodeResponse... just load up your template using the template >> >> helpers (this will give you NodeSeq) and then you can present that >> >> back to the user. Job done. >> > >> > I'll take a look, that sounds promising, thx. What are the template >> > helpers? This sounds similar to using S.render, but I wasn't able to >> > use that since I'm still on 1.0, it looks like it was added >> later. (I >> > am considering moving to 1.1-M6). >> > >> > - Alex >> > >> >> >> >> Cheers, Tim >> >> >> >> On 29 Dec 2009, at 15:23, Alex Black wrote: >> >> >> >>> But of course RewriteResponse is not a LiftResponse. Whats the >> best >> >>> way to do this? Basically I've got a template called 404.html >> which >> >>> I'd like to display whenever there is a 404. >> >> >> >>> I Just thought of something, perhaps I could add a RewriteRule >> that >> >>> matches everything? >> > >> > -- >> > >> > You received this message because you are subscribed to the Google >> > Groups "Lift" group. >> > To post to this group, send email to liftweb@googlegroups.com >> <mailto:liftweb@googlegroups.com>. >> > To unsubscribe from this group, send email to >> liftweb+unsubscr...@googlegroups.com >> <mailto:liftweb%2bunsubscr...@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 liftweb@googlegroups.com >> <mailto:liftweb@googlegroups.com>. >> To unsubscribe from this group, send email to >> liftweb+unsubscr...@googlegroups.com >> <mailto:liftweb%2bunsubscr...@googlegroups.com>. >> For more options, visit this group at >> http://groups.google.com/group/liftweb?hl=en. >> >> >> >> >> >> -- >> http://blog.alexblack.ca <http://blog.alexblack.ca/> >> http://twitter.com/waterlooalex >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups "Lift" group. >> To post to this group, send email to liftweb@googlegroups.com >> <mailto:liftweb@googlegroups.com>. >> To unsubscribe from this group, send email to >> liftweb+unsubscr...@googlegroups.com >> <mailto: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.
