> Use explicitly imports, thus avoiding these problems:
But the problem is knowing what to import :-) When there's no IDE
support, all one
has are the scaladocs... And *none* of the lift examples I found
uses explicit imports,
so you're on your own...
Job
--
You received this message becau
Okay, I wrote an implicit + operator combo that scraps most of the boilerplate.
Snippet code:
def howdy(in: NodeSeq): NodeSeq =
bind("foobar", in, "foobaz" -%%> FocusOnLoad())
(input:attrs="" is the magic)
Template code:
Output:
//
Stephan,
I wrote the paypal module... what do you want to know?
Cheers, Tim
On Nov 28, 4:49 pm, stephanos wrote:
> Hi folks,
>
> I'm new to lift and was wondering about all the various modules like
> "lift-paypal" etc. I found in the maven repository.
> Is there an overview/documentation of the
The "Exploring Lift" book aka "The Definitive guide to Lift "
discusses a good portion of those. http://groups.google.com/group/the-lift-book
Br's,
Marius
On Nov 28, 6:49 pm, stephanos wrote:
> Hi folks,
>
> I'm new to lift and was wondering about all the various modules like
> "lift-paypal" etc
Hi folks,
I'm new to lift and was wondering about all the various modules like
"lift-paypal" etc. I found in the maven repository.
Is there an overview/documentation of them somewhere - I couldn't find
one yet.
Cheers,
Stephan
--
You received this message because you are subscribed to the Googl
Use explicitly imports, thus avoiding these problems:
import some.package.{ClassOne, ClassTwo}
Cheers, Tim
On 28 Nov 2009, at 14:56, jhonig wrote:
> I always avoided Eclipse because it usually got into my way, but with
> the
> lift habit of using wildcard imports I lose a lot of time tracing al
Hi Jeppe,
I'm not using a front-end or any other kind of programming
environment.
I always avoided Eclipse because it usually got into my way, but with
the
lift habit of using wildcard imports I lose a lot of time tracing all
kinds of
definitions, so in this case I'm reconsidering...
As for a we
jhonig writes:
> Dear Tim and Heiko,
>
> I tested a few things under mvn jetty:run...:
>
> getRealPath gives me "./src/main/webapp"
> the temp attribute is set to "./target/work"
> and the location is "./target/classes"
>
> While the war contains "classes/work" which is again di
Thanks very much,
I missing the production.default.props file .
Cheers,
Neil
On Nov 28, 9:33 pm, Leo Lännenmäki wrote:
> Hi,
>
> I'm a Lift newbie so I don't know if my way is the "right" way but
> here goes:
>
> I generated my app using the archetype lift-archetype-basic in order
> to g
Thanks very much!
It's in the production mode now.
This snippet's result is "production"
Cheers,
Neil
David Pollak wrote:
> Write a snippet:
>
> import net.liftweb.util.Props
> import scala.xml._
>
> class WhatMode {
> def render = Text(Props.modeName)
> }
>
> On a page:
>
>
>
> And
Write a snippet:
import net.liftweb.util.Props
import scala.xml._
class WhatMode {
def render = Text(Props.modeName)
}
On a page:
And the mode will be listed (or blank for development mode)
On Sat, Nov 28, 2009 at 6:23 AM, Neil.Lv wrote:
>
> I missing the production.default.props file i
Ross Mellgren writes:
> I'm not sure if this addresses your points, but I figured I'd throw
> out what I've been doing in case it helps.
It's always nice to see how others approach a problem!
> I don't use -%>, but I do use something similar along with another
> implicit so I can place the
I missing the production.default.props file in the /src/main/
resources/props folder
I create a file named production.default.props(copy from
default.props) in this folder.
When i enter a invalid URL like:
http://192.168.1.102/fsdf
The browser will show this message:
The Request
Dear Tim and Heiko,
I tested a few things under mvn jetty:run...:
getRealPath gives me "./src/main/webapp"
the temp attribute is set to "./target/work"
and the location is "./target/classes"
While the war contains "classes/work" which is again different... I
didn't manage to
Do a println to output the value of Props.get("db.driver")
On Sat, Nov 28, 2009 at 6:06 AM, Neil.Lv wrote:
>
> It generated by the archetype lift-archetype-basic.
>
> ## in the Boot.scala
> object DBVendor extends ConnectionManager {
> private var pool: List[Connection] = Nil
> private v
It generated by the archetype lift-archetype-basic.
## in the Boot.scala
object DBVendor extends ConnectionManager {
private var pool: List[Connection] = Nil
private var poolSize = 0
private val maxPoolSize = 4
private def createOne: Box[Connection] = try {
val driverName: Str
Hi,
I'm a Lift newbie so I don't know if my way is the "right" way but
here goes:
I generated my app using the archetype lift-archetype-basic in order
to get the database configuration stuff to Boot.scala. Then i created
two files src/main/webapp/WEB-INF/classes/props/default.props and
production
Hi,
I'm trying to get my first scala/lift app working and I have a problem:
Schemifier.schemify(...) creates everything, i.e. tables, primary keys,
indices but it does not create the foreign key constraints.
I've seen in Schemifier.scala SQL code for generating foreign key
constraints so I thi
Paste your database connection object? its probably that you copied the one
from lift examples and you are now missing the correct properties file...
Cheers, Tim
On 28 Nov 2009, at 10:26, Neil.Lv wrote:
> Hi all,
>
> I have a silly question about the lift app that deployed on the
> Jetty se
What kind of integration do you want?
Cheers, Tim
On 28 Nov 2009, at 03:20, Xuefeng Wu wrote:
> Did anyone try to integrate with SSO?
>
> On Sat, Nov 28, 2009 at 12:37 AM, Marcin Jurczuk wrote:
> That is amazing :)
>
> Probably I will need to bind to AD in near future, so this module is
> li
Hi all,
I have a silly question about the lift app that deployed on the
Jetty server.
Can't find the jdbc:mysql driver in Production Mode ? It will use
the derby to instead of the mysql.
But it works fine in the Development Mode.
I will craete the derby file in the jetty folder.
/h
Now the lift app runs in the production mode,
###
put the "JAVA_OPTIONS=-Drun.mode=production" on the top, and it can
workd.
###
But it will create the database in the jetty's folder
/home/jetty6/derby.log
/home/jetty6/lift_example
It can's find the jdbc:mysql ? (It the development mod
Now the lift app runs in the production mode,
###
put the "JAVA_OPTIONS=-Drun.mode=production" on the top, and it can
workd.
###
But it will create the database in the jetty's folder
/home/jetty6/derby.log
/home/jetty6/lift_example
It can's find the jdbc:mysql ? (It the development mod
23 matches
Mail list logo
