Heiko,
Please see here: http://is.gd/w5SB
We've talked before on the committers list about renaming sites to
examples or such, so I see no reason why putting any working example you
want in there. POC would probably be a different matter... If its not
working code, host it on your own github
On Sat, May 2, 2009 at 5:09 AM, Timothy Perrett timo...@getintheloop.euwrote:
Heiko,
Please see here: http://is.gd/w5SB
+1
We've talked before on the committers list about renaming sites to
examples or such, so I see no reason why putting any working example you
want in there. POC
Oh dear, sorry didn't realize I was butting in on committers talk.
On Sat, May 2, 2009 at 11:20 PM, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Sat, May 2, 2009 at 5:09 AM, Timothy Perrett
timo...@getintheloop.euwrote:
Heiko,
Please see here: http://is.gd/w5SB
+1
On Sat, May 2, 2009 at 6:51 AM, Timothy Perrett timo...@getintheloop.euwrote:
Your not - dont worry ;-)
Heiko posted this to the main list because committers talk is only
scheduling related stuff. Everything else is out in the open. If folks
think that the examples should go someplace else,
With that being said, we're a very vocal bunch... the
top posters to this list on any given month are committers... so we just
can't shut up :-)
Guilty as charged! lol.
I think thats a real positive thing though - it means lots of
community members get lots of help / talk / general
On Thu, Apr 30, 2009 at 10:48 PM, Andrew Scherpbier
and...@scherpbier.orgwrote:
The Getting Started document got me hooked on Lift. :-)
I guess I'll report my struggles from there. I don't know if what I did
is typical.
After actually running the two examples from the Getting Started
Guys,
I noticed that the internal lift snippets (msgs et al) have been moved
to objects rather than classes - there are obvious benefits
performance wise for this, but what should we be supplying to new-
comers as the de-facto snippet implementation style? I know the answer
is unlikely to be
Question for Derek
my jpa 1.1-SNAPSHOT version seems to have disappeared from the maven
repo to be replaced with 1.1
But at the same time now I've done a maven clean it looks like
RequestVarEM doesn't exist any more. I just got the source from git
and this seems to be the case. So what do I do
My apologies. We had to move RequestVarEM to the lift-jpa module in order to
fix a circular dependency that was preventing Lift 1.1-M1 from going out. If
you're using Lift 1.0 then you should really be using ScalaJPA 1.0.
Otherwise, you need to use the lift-jpa module instead of scalajpa with the
I'm at early stages of a fairly big project at the moment and mainly
working in my domain model. Is M1 safe to use, since I doubt we'll get
onto serious UI stuff for at least a month and production is likely
2-3 months after that.
Tim
--~--~-~--~~~---~--~~
You
Tim,
.m1 is indeed stable to use, go right ahead :)
Cheers, Timothy
On 02/05/2009 16:50, TSP tim.pig...@optrak.co.uk wrote:
I'm at early stages of a fairly big project at the moment and mainly
working in my domain model. Is M1 safe to use, since I doubt we'll get
onto serious UI stuff
Lifted,
i'm putting together a little lift-based testharness in which to evaluate
various solutions to the challenge Martin posted recently regarding scalable
abstractions for a little lambda interpreter. You can get a copy of the app
here http://svn.biosimilarity.com/src/open/rlambda/trunk/.
12 matches
Mail list logo