date:20091023

[Lift] Re: Important Migration guide Scala Actors - Lift Actors

2009-10-23 Thread Heiko Seeberger

One small step for Lift and Akka, one giant leap for Scala!
Thanks, David and Jonas!

Heiko

2009/10/22 Marius marius.dan...@gmail.com


 Just Simple  Beautiful ! ... Nice work Dave and Jonas.

 Br's,
 Marius

 On Oct 22, 9:57 pm, David Pollak feeder.of.the.be...@gmail.com
 wrote:
  Folks,
 
  I wrote a quick blog piece about migrating from Scala Actors to Lift
 Actors
  athttp://blog.lostlake.org/index.php?/archives/96-Migrating-from-Scala-.
 ..
 
  I hope this addresses questions that folks on the list have about the
  affirmative steps they need to take to make the migration.
 
  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
 



-- 
Heiko Seeberger

My job: weiglewilczek.com
My 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 liftweb@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: catch a URL

2009-10-23 Thread Jeppe Nejsum Madsen


Chris Lewis burningodzi...@gmail.com writes:

 Hi list,

 I'm working on an appengine app, and need to store some user 
 information. I authenticate the user with their google account, and I 
 need to create their local entity only if it's their first time 
 logging in.

 When a user logs in via google, they are redirected back to your app, to 
 a URL of your choosing. My thought was to catch the request as it comes 
 back and, if it's their first time logging in, create a User entity. My 
 question then is how can I do this without:

 a) Using a snippet, called from the return landing page and emitting 
 NodeSeq.Empty - hack.

 b) Using custom dispatch and then redirecting. That may work, but it's 
 an unneeded round trip.

 Any thoughts? Thanks!

Not sure if the landing page is static, has parameters etc and what you
want to do afterwards. 

Assume you need to render some template and the landing page is not
static (if it is you could just use a normal Loc) I would probably wrap
the landing page in a RewriteRequest, and when a match is made, do the
user creation/lookup thing and then just render the template.

Tim wrote and article about rewriting
http://blog.getintheloop.eu/2009/5/3/url-rewriting-with-the-lift-framework

Also, I've been using the Locs from CRUDify as an example of how to do
more custom-type Locs with rewriting.

/Jeppe

--~--~-~--~~~---~--~~
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
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: A Critique On Lift

2009-10-23 Thread jlist9


Ross,

 Personally I think that Python is great for small simple things, but
 as soon as you start to scale the lack of statically checked
 guarantees starts to bite you.

What you said about the problems with dynamically typed
scripting language is very true. Python is so powerful but the
code is so fragile. You need to write a lot of tests. This is
exactly why I'm trying to learn Scala.

Thanks for your explanation about operators.

 Regarding () and {} BTW, you can replace a single-argument argument
 list with {}, e.g.

 def myFunction(a: String): Unit = println(a)

 myFunction(foobar)
 myFunction { foobar }

I find the following three lines of code do the same thing.
Thanks for your explanation again. I now understand
why the first and second line are equivalent. (But why
does Scala allow {} here? Isn't () good enough?)

I'm not sure what the {} does in the third line, though.

args.foreach{ arg = greeting += (arg +  ) }
args.foreach( arg = greeting += (arg +  ) )
args.foreach( arg = { greeting += (arg +  ) } )

 The two calls are equivalent. It makes more sense with the latter
 format with multiple argument lists or DSL-like things. I could write
 up an example if you're interested, but it might be somewhat involved
 if you're not familiar with Scala or Lift.

Thanks. Let me finish the tutorials first :-)

 Overall, my suggestion would be to stick with it and ask questions. I
 think it's worth it, and the people here are really helpful.

Yes. I plan to bite the bullet and continue with my learning.
And indeed, this is a very friendly and  helpful list.

jlist9

--~--~-~--~~~---~--~~
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
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: A Critique On Lift

2009-10-23 Thread Ross Mellgren

On Oct 23, 2009, at 2:31 AM, jlist9 wrote:
 Regarding () and {} BTW, you can replace a single-argument argument
 list with {}, e.g.

 def myFunction(a: String): Unit = println(a)

 myFunction(foobar)
 myFunction { foobar }

 I find the following three lines of code do the same thing.
 Thanks for your explanation again. I now understand
 why the first and second line are equivalent. (But why
 does Scala allow {} here? Isn't () good enough?)

I find it's good when you're doing a block-like thing where it really  
expects a single value. Most often I use this with functions that do  
something scoped, e.g. acquire a resource and release it, or set  
some kind of semi-global variable temporarily (RequestVar.doWith,  
ThreadGlobal.doWith, for example).


 I'm not sure what the {} does in the third line, though.

 args.foreach{ arg = greeting += (arg +  ) }
 args.foreach( arg = greeting += (arg +  ) )
 args.foreach( arg = { greeting += (arg +  ) } )

The {}s in this case would allow you to have multiple statements  
there. To contrast:

args.map(arg = println(arg); arg.length)   // won't compile
args.map { arg = println(arg); arg.length }  // compiles
args.map(arg = { println(arg); arg.length }) // compiles

I personally prefer the last form because my editor will happily eat  
it and I get some consistency when there's arguments before the  
function argument. Of course, this is an aesthetic thing, I'm sure  
other people prefer the parenless form.

-Ross


--~--~-~--~~~---~--~~
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
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: A Critique On Lift

2009-10-23 Thread Jonas Bonér


I love the _ operator.

2009/10/22 Timothy Perrett timo...@getintheloop.eu:

 I think this is a bit of a running joke in the scala comunity right
 now - your right, underscore really does have a number of meanings; I
 think this will be changed in some future Scala release.

 Your also forgetting:

 import some.package._

 Cheers, Tim

 On 22 Oct 2009, at 12:57, tiro wrote:

 underscore. At least four different uses:
 - it for defining anonymous functions like above
 - default value
 - matching placeholder whose value is ignored
 - use for constructing setter method names boolean functions (empty_?)


 




-- 
Jonas Bonér

twitter: @jboner
blog:http://jonasboner.com
work:   http://scalablesolutions.se
code:   http://github.com/jboner
code:   http://akkasource.org
also:http://letitcrash.com

--~--~-~--~~~---~--~~
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
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: A Critique On Lift

2009-10-23 Thread Joni Freeman

I love it too. While it is used in many different places it always
means stuff that I do not care to name.

BTW. high priest of the lambda calculus loves it too :) It has its
roots in Haskell...

http://channel9.msdn.com/shows/Going+Deep/C9-Lectures-Dr-Erik-Meijer-Functional-Programming-Fundamentals-Chapter-4-of-13/

Cheers Joni

On 23 loka, 09:48, Jonas Bonér jbo...@gmail.com wrote:
I love the _ operator.

2009/10/22 Timothy Perrett timo...@getintheloop.eu:

I think this is a bit of a running joke in the scala comunity right
now - your right, underscore really does have a number of meanings; I
think this will be changed in some future Scala release.

Your also forgetting:

import some.package._

Cheers, Tim

On 22 Oct 2009, at 12:57, tiro wrote:

underscore. At least four different uses:
- it for defining anonymous functions like above
- default value
- matching placeholder whose value is ignored
- use for constructing setter method names boolean functions (empty_?)

--
Jonas Bonér

twitter: @jboner
blog: http://jonasboner.com
work: http://scalablesolutions.se
code: http://github.com/jboner
code: http://akkasource.org
also: http://letitcrash.com
--~--~-~--~~~---~--~~
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
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
-~--~~~~--~~--~--~---

61 matches

Mail list logo