[Lift] Re: About _root_

Thanks guys! ...Extremely ugly _root_ ! it is at least a weird assumption of the scala compiler to consider the import paths relative and not have a better way of expressing absolute path but with _root_. Br's, Marius On Sep 25, 12:20 am, "Jorge Ortiz" <[EMAIL PROTECTED]> wrote: > Indeed.

[Lift] Re: About _root_

That proposal works for imports, but not for other expressions. For example, how would you express what is currently expressed as: import scala.collections._ val f = mutable.Map.empty With the proposed syntax it would be: import scala.collections._ val f = _.mutable.Map.empty But now th

[Lift] Re: About _root_

Seems like itshould be the other way around ... assume absolute paths and if anyone want relative ones just use import _.foo.ert (as it was suggested by someone). Much more expressive IMHO. But not much accomplishment if we talk about this on this list :) On Sep 25, 8:13 am, Marius <[EMAIL PROTE

[Lift] Re: lift:surround and multiple templates

Charles F. Munat wrote: > All I did was make a copy of my default.html and call it admin.html. > > Then I changed the calling tag attribute in the calling template from > with="default" to with="admin". > > It works when the surround template is called default, and doesn't when > it is called a

[Lift] Re: lift:surround and multiple templates

Charles, The "admin" template was conflicting with the /admin/ directory. Change the name of the template to admin2.html rather than admin.html and change your 'with="admin"' to 'with="admin2"' and it'll work. Thanks, David Charles F. Munat wrote: > I changed the calling template to (exactl

[Lift] Re: ExtLink not working

On Wed, Sep 24, 2008 at 10:50 AM, Charles F. Munat <[EMAIL PROTECTED]> wrote: > > Sorry, I should have mentioned that I'm using the new group function. > When I use builder, it works fine. I notice that the new group function > ignores Hidden and doesn't work with ExtLink links. I'm slowly working

[Lift] Re: lift:surround and multiple templates

Can you mail the whole project to me off-list and I'll take a look at it? (please remove the "target" directory before ziping/tarring) On Wed, Sep 24, 2008 at 4:13 PM, Charles F. Munat <[EMAIL PROTECTED]> wrote: > > I changed the calling template to (exactly): > > > > I changed admin.html to (ex

[Lift] Re: lift:surround and multiple templates

I changed the calling template to (exactly): I changed admin.html to (exactly): I did mvn clean and mvn jetty:run -U. I get the same error: Exception occured while processing / Message: java.lang.IllegalArgumentException: line 6 does not exist scala.io.Source.getLine(Source.scala:

[Lift] Re: lift:surround and multiple templates

Will do. David Pollak wrote: > > > Charles F. Munat wrote: >> All I did was make a copy of my default.html and call it admin.html. >> >> Then I changed the calling tag attribute in the calling template from >> with="default" to with="admin". >> >> It works when the surround template is called

[Lift] Re: lift:surround and multiple templates

Sorry, Jorge, I should've put the closing tag in my post. I assumed it would be clear that there is more after the opening tag -- a bad assumption on my part. It's not an empty element in my template. Jorge Ortiz wrote: > Your file is not valid xml. > > Replace with: > > > > (Note the tra

[Lift] Re: lift:surround and multiple templates

All I did was make a copy of my default.html and call it admin.html. Then I changed the calling tag attribute in the calling template from with="default" to with="admin". It works when the surround template is called default, and doesn't when it is called admin. I've searched through the temp

[Lift] Re: lift:surround and multiple templates

Your file is not valid xml. Replace with: (Note the trailing slash) --j On Wed, Sep 24, 2008 at 2:58 PM, Charles F. Munat <[EMAIL PROTECTED]> wrote: > > I want to change the surrounding template depending on where in the site > I am (and whether I'm logged in or not). > > I tried this: > >

[Lift] Re: lift:surround and multiple templates

There's an XML error in your admin template. Charles F. Munat wrote: > I want to change the surrounding template depending on where in the site > I am (and whether I'm logged in or not). > > I tried this: > > In templates-hidden I created a slightly different template from my > default.html tem

[Lift] lift:surround and multiple templates

I want to change the surrounding template depending on where in the site I am (and whether I'm logged in or not). I tried this: In templates-hidden I created a slightly different template from my default.html template and named it admin.html. In one of my pages I replaced with When I re

[Lift] Re: About _root_

Indeed. For compatibility with the upcoming version of Specs (the one we'll need for Scala 2.7.2 compatibility), and more importantly, to plug potential security vulnerabilities, I've _root_'ed most imports and references in Lift's code. I definitely got all the imports, I think, but I may have mis

[Lift] Re: [ANN] Compiling Lift with Scala 2.7.2.RC2 and Eclipse Plugin

Jorge Ortiz wrote: > Nothing is this e-mail is meant to imply that any future > public version of Lift will compile with Scala 2.7.2. > At the moment, all future public versions of Lift will compile with > Scala 2.7.1 until DavidP says otherwise. Lift will be 2.7.2 on the mai

[Lift] [ANN] Compiling Lift with Scala 2.7.2.RC2 and Eclipse Plugin

Nothing is this e-mail is meant to imply that any future public version of Lift will compile with Scala 2.7.2. At the moment, all future public versions of Lift will compile with Scala 2.7.1 until DavidP says otherwise. Here are the instructions for compiling Lift under Scala 2.7.2.RC2 and (opti

[Lift] Re: About _root_

I believe this is the genesis: http://www.nabble.com/Unfortunate-package-path-conflict-(security-vulnerability-)-tc19618678.html On Sep 24, 4:13 pm, Marius <[EMAIL PROTECTED]> wrote: > Hi, > > I understand from SLS what _root_ does ... but I'm wondering what is > the reason behind it in lift. Wha

[Lift] About _root_

Hi, I understand from SLS what _root_ does ... but I'm wondering what is the reason behind it in lift. What was the problem? Br's, Marius --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this

[Lift] Re: HTTP Client?

This reminds me -- in Lift, I've frequently seen the pattern of utilizing a companion object's apply() methods as factories. Perhaps it's just me, but this seems a little less intuitive than having an explicitly named constructor method that is in some way descriptive of the state in which the rel

[Lift] Re: ExtLink not working

Sorry, I should have mentioned that I'm using the new group function. When I use builder, it works fine. I notice that the new group function ignores Hidden and doesn't work with ExtLink links. I'm slowly working through it to figure out why, but you probably already know why. Chas. David Pol

[Lift] Re: ExtLink not working

And how did you convert the Loc to an URL? Marius wrote: > Looks to me like a bug. I mean it appears to render the random string > generated instead of what createLink returns. > > > Br's, > Marius > > On Sep 24, 12:15 pm, "Charles F. Munat" <[EMAIL PROTECTED]> wrote: > >> When I create an exte

[Lift] Re: HTTP Client?

Kris Nuttycombe wrote: > If you're going to take that approach, why not just make the > constructor or factory method ensure that the object is in a valid > state to begin with? When I write immutable objects, they usually > don't have any setters for that very reason. It doesn't make sense to >

[Lift] Re: HTTP Client?

Also, when writing immutable objects, constructors suck since they do not encourage object sharing... On Wed, Sep 24, 2008 at 4:36 PM, Kris Nuttycombe <[EMAIL PROTECTED]>wrote: > > If you're going to take that approach, why not just make the > constructor or factory method ensure that the object

[Lift] Re: HTTP Client?

If you're going to take that approach, why not just make the constructor or factory method ensure that the object is in a valid state to begin with? When I write immutable objects, they usually don't have any setters for that very reason. It doesn't make sense to me that one would construct a PayP

[Lift] Re: not binding

Charles F. Munat wrote: > Damn. Sometimes I'm a bit dense. I just realized that I created my own > Menu snippet, overriding the default one. A simple copy and paste fixed > things. > > Just so I'm clear, the XML error is because the tag > appeared in the output, and the tag appeared in the ou

[Lift] Passing data with JsonHandler?

Hi, I was looking over the JsonHandler stuff and it looks pretty interesting. I thought I'd try it out for a member add page on my latest project, but I can't figure out how to pass state through the snippet. Basically, I have a "Team" object that I want to add coaches (Member objects) to. I wa

[Lift] Re: ExtLink not working

Looks to me like a bug. I mean it appears to render the random string generated instead of what createLink returns. Br's, Marius On Sep 24, 12:15 pm, "Charles F. Munat" <[EMAIL PROTECTED]> wrote: > When I create an external link in the SiteMap thus: > > Menu(Loc("google", ExtLink("http://google

[Lift] Re: Making Record a reality [was: Validations, Server side controls etc]

Hey Chas, No worries, I re-read too and understood the tone of your reply. I'm playing devils advocate on validation to try to get a flexible framework for everyone to use. Ol On 24/09/2008, at 4:07 PM, Charles F. Munat wrote: > > Charles F. Munat wrote: >>> Running Ajax calls between fields fo

[Lift] ExtLink not working

When I create an external link in the SiteMap thus: Menu(Loc("google", ExtLink("http://google.com/";), "Google")) I get an anchor like this: Google But when I click on this, I get a: HTTP ERROR: 404 NOT_FOUND RequestURI=/JQWGEJZP2BM5JTZ030LH I presume this is meant to obscure the external