Thomas,
You can package Lift apps with OneJar and use the Winstone servlet container
(http://winstone.sourceforge.net/ ) That'll put everything in 1 JAR file
and it should allow single-click launch on a Windows machine.
Thanks,
David
On Fri, Jan 30, 2009 at 1:09 PM, Thomas Santana wrote:
>
>
Tim,
Thanks for your note. i was largely referring to the possibility of sucking
on the data model (mainly from the db schema side, as the parsing would be
easier) to generate appropriate Model code.
Best wishes,
--greg
On Mon, Feb 2, 2009 at 1:04 PM, Tim Perrett wrote:
>
>
> Hey Greg,
>
> I
On Mon, Feb 2, 2009 at 1:04 PM, Tim Perrett wrote:
>
>
> Hey Greg,
>
> I have taken great pleasure in porting several "leaking like a rusty
> bucket"
> rails applications... Whilst there is no direct migration, once you
> understand exactly how lift works, it becomes simple.
>
> When you say "db
Hey Greg,
I have taken great pleasure in porting several "leaking like a rusty bucket"
rails applications... Whilst there is no direct migration, once you
understand exactly how lift works, it becomes simple.
When you say "db stuff squirted out from ActiveRecord?" - what exactly do
you mean? Qu
Ilya,
This is a very helpful observation.
I'm cc'ing the Lift list and perhaps one of the Maven mavens will provide
you with a good answer.
Thanks,
David
On Mon, Feb 2, 2009 at 10:41 AM, Ilya Sergey wrote:
> Hello, David.
>
> Trying to import new liftweb application project into IntelliJ ID
Lifted,
Suppose one were to engage in porting a RoR app to a Lift app. Are there any
tools in the Scala+Lift arsenal that ease that migration? For example, is
there a nice path that allows to preserve the db stuff squirted out from
ActiveRecord? Is the are way to auto-generate some basic Model cod
I followed the tutorial here on this page:
http://scala-blogs.org/2007/12/dynamic-web-applications-with-lift-and.html
And was pleased to see the application come out so quickly. However I have a
question. As I save the file on Eclipse they don't get picked up by Jetty. I
need to do a mvn install
Did a little more digging into how Loc and MenuItem work together. It
looks like the 'kids' of a menu item are not exposed until you click
on it.
I am looking to see if we can have behavior which exposes the 'kids'
of a MenuItem before clicking on it.
Dan
On Feb 1, 8:28 pm, Dano wrote:
> Mor
Does anyone have time to find and mentor a student to do Lift work either
through the Jane st or Google Summer of Code programs?
On Feb 2, 2009 10:23 AM, "Jorge Ortiz" wrote:
If you're a student, Jane Street Capital can give you money to work on
functional programming for a summer...
--j
-
There were no errors on the console. And the state was persisted when i was
using Marius's example. So it looks like a bug to me.
Thanks,
Sergey
On Mon, Feb 2, 2009 at 6:09 PM, Tim Perrett wrote:
>
>
> Lift will still indeed notify you of an error invoking a snippet.
>
> On 02/02/2009 15:01, "De
If you're a student, Jane Street Capital can give you money to work on
functional programming for a summer...
--j
-- Forwarded message --
From: James Iry
Date: Mon, Feb 2, 2009 at 9:36 AM
Subject: [scala] Jane Street Summer Program
To: Scala list
This caught my eye and might b
I've used Lift quite a bit as REST back end for a Flex/Flash front
end. It is straightforward. Check out Steve Jenson's wiki page on
this: http://liftweb.net/index.php/HowTo_do_Web_Services if you
haven't seen it already. Scala's XML support makes it super easy to
create XML on the server, and E4X
Lift will still indeed notify you of an error invoking a snippet.
On 02/02/2009 15:01, "Derek Chen-Becker" wrote:
> Also, if the class for the snippet couldn't be found, Lift should have output
> a message to that effect on the console. If it didn't, then that's a bug.
>
> Derek
--~--~
For the first error I think you need to import net.liftweb.js.JE._ to get
the implicit String => Str (JsExp) conversion into scope. On the second
error, your code seems to indicate that you're still using the "-->"
operator (I think it's deprecated) instead of "->" (one less dash). Please
fix that
Also, if the class for the snippet couldn't be found, Lift should have
output a message to that effect on the console. If it didn't, then
*that's*a bug.
Derek
On Mon, Feb 2, 2009 at 8:00 AM, Derek Chen-Becker wrote:
> I think the convention is to either properly capitalize the snippet tag to
> m
I think the convention is to either properly capitalize the snippet tag to
match the class name, as you've done, or to use underscores to indicate
camel case, a la
show_market
I don't think that Lift handles "mixed" camel case, but it's been a while
since I've looked at that part of the code.
De
Hi David and Rickard,
If you replace property(...) by Prop.forAll(...), the warnings should
disappear.
On the other hand I don't know why forAll(...) only doesn't work.
Cheers,
Eric.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
It seems strange that forAll complains about getting a String => Boolean
function. It works fine in the interpreter. The only reason I can see for
that error message is that Scala somehow thinks that forAll is given two
parameter lists. There exists an overloaded version of forAll of type
[T](Gen[
18 matches
Mail list logo
