Just looking back over the list - where are we too with the current
Record implementation?
I want to factor out some localization functionality into a
ProtoTranslation style system, but for Record rather than mapper; i'm
not sure Record is sufficiently mature however?
Cheers, Tim
On Sun, Apr 5, 2009 at 3:31 AM, Timothy Perrett timo...@getintheloop.euwrote:
Just looking back over the list - where are we too with the current
Record implementation?
I want to factor out some localization functionality into a
ProtoTranslation style system, but for Record rather than
Also, it would be great it Lift1.1 included all of the
necessary .js, .css and class files for the new MenuWidget
I have not had the chance to actually work with lift yet and have been doing
a lot of reading, but I have not read how lift currently handles script and
css resources? Does it
I have been reading up on OSGi with some discipline it could allow
Erlang like live upgrades (also nice to not have to shutdown a JVM, so
+1.
I'm curious on the Portlet support - is that embedding portlets in
snippets and/or creating portlets (rather than servlets)?
Marc
On 02/04/2009, at
Have you looked at Windmill?
http://www.getwindmill.com/
From what I've heard it's pretty cool.
Chas.
David Pollak wrote:
On Thu, Apr 2, 2009 at 10:09 AM, Bill Venners b...@artima.com
mailto:b...@artima.com wrote:
Hi David,
On Thu, Apr 2, 2009 at 9:28 PM, David Pollak
On Fri, Apr 3, 2009 at 12:35 AM, Marc Boschma
marc+lift...@boschma.cxmarc%2blift...@boschma.cx
wrote:
I have been reading up on OSGi with some discipline it could allow Erlang
like live upgrades (also nice to not have to shutdown a JVM, so +1.
I'm curious on the Portlet support - is that
Also, it would be great it Lift1.1 included all of the
necessary .js, .css and class files for the new MenuWidget
On Apr 3, 3:42 am, Charles F. Munat c...@munat.com wrote:
Have you looked at Windmill?
http://www.getwindmill.com/
From what I've heard it's pretty cool.
Chas.
David Pollak
Hi David,
On Thu, Apr 2, 2009 at 12:11 AM, David Pollak
feeder.of.the.be...@gmail.com wrote:
Folks,
Improved testing framework and better testing support when running in test
mode.
Can you elaborate on what your plans are for this?
Thanks.
Bill
On Thu, Apr 2, 2009 at 2:30 AM, Bill Venners b...@artima.com wrote:
Hi David,
On Thu, Apr 2, 2009 at 12:11 AM, David Pollak
feeder.of.the.be...@gmail.com wrote:
Folks,
Improved testing framework and better testing support when running in
test
mode.
Can you elaborate on what your
My resources are pretty limited, but I'd love to at least contribute what I
can to the OSGi support. I'd love to see a plugin system for lift apps
that's sensible!
Speaking of which, perhaps a plugin system that's sensible should be part of
the list? I know grails does some neat stuff there
Just my two pence, but right now I understand these things are
possible with ViewDispatchPF and SnippetDispatchPF etc etc and all the
other tools we have in lift for creating modular view and logic code.
However, the one thing I would say is that a lot of people appear to
struggle with the
Tim,
It's on my backlog. Right now I'm working on a preso for a class I'm
teaching today at Cal Berkeley. Tomorrow is tax day and next week is a
family vacation. I'll try to get something to you.
Thanks,
David
On Apr 2, 2009 9:07 AM, Timothy Perrett timo...@getintheloop.eu wrote:
Just my
Hi David,
On Thu, Apr 2, 2009 at 9:28 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
On Thu, Apr 2, 2009 at 2:30 AM, Bill Venners b...@artima.com wrote:
Hi David,
On Thu, Apr 2, 2009 at 12:11 AM, David Pollak
feeder.of.the.be...@gmail.com wrote:
Folks,
Improved testing
Ok no worries - personally, I dont have any burning need for it right
this moment but I could certainly make serious use of it within the
next month.
Cheers, Tim
On Apr 2, 7:10 pm, David Pollak feeder.of.the.be...@gmail.com wrote:
Tim,
It's on my backlog. Right now I'm working on a preso for
+10 for documentation effort. Speaking from the noob perspective, the
documentation is the biggest barrier to entry for Lift. Currently
there are 3 places to get lift documentation:
-Get Started Tutorial
-Lift Book
-Lift Wiki
The first two sources are excellent, but the last one is bit
I gotta be honest, with April Fools, I was scared to click on
goatrodeo.org...
On Apr 1, 12:11 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Folks,
I think we've got our Lift 1.1 list. If anyone has anything to add, please
speak up now.
- Improved documentation: better
On Wed, Apr 1, 2009 at 9:37 AM, TylerWeir tyler.w...@gmail.com wrote:
I gotta be honest, with April Fools, I was scared to click on
goatrodeo.org...
:-)
On Apr 1, 12:11 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Folks,
I think we've got our Lift 1.1 list. If anyone
Sounds great.
One other feature I'd like (and I think would be widely useful):
* Partitioned service cluster support for a/b testing: redirect some users
to a different server, e.g. to test the new version
And possibly:
* Backing store support for Voldemort (or does that come through goat
On Wed, Apr 1, 2009 at 7:16 PM, Lee Mighdoll leemighd...@gmail.com wrote:
Sounds great.
One other feature I'd like (and I think would be widely useful):
* Partitioned service cluster support for a/b testing: redirect some users
to a different server, e.g. to test the new version
Just do a
Hahaha.
David, would improved client-side JavaScript support and better
JavaScript abstractions cover my autocomplete customization
question?
Also, could I make a request to add JS and CSS minification in
production mode that can be controlled by a request parameter
variable. So,
I propose we migrate to Joda Time for 1.1.
In particular, I propose that Record ditch Java Date/Time entirely in favor
of Joda Time. Since migrating from Mapper to Record will involve a port
anyway, what's one more breaking change among friends?
Lift's other uses of Date/Time should be
I also propose we start thinking seriously about 2.8.
In particular, 2.8 will probably add support for named and default
arguments. This places extra burdens on library and framework designers, as
method -argument- names will be just as much a part of a library/framework's
API as class, method,
I think your right Jorge... 2.8 brings some important changes that
could quite possibly have some pretty significant breaking changes in
the Lift API.
I also agree with the JodaTime in record/field, sounds like perfect
sense.
Cheers, Tim
--~--~-~--~~~---~--~~
You
+1 Anything to get away from that damn Java Date/Calendar crap.
Agreed on need to review API.
Chas.
Timothy Perrett wrote:
I think your right Jorge... 2.8 brings some important changes that
could quite possibly have some pretty significant breaking changes in
the Lift API.
I also agree
24 matches
Mail list logo
