[Lift] Re: [Lift committers] Re: Meeting

2009-04-17 Thread Jonas Bonér
2009/4/16 David Pollak feeder.of.the.be...@gmail.com: Taking the discussion to the main list On Thu, Apr 16, 2009 at 10:23 AM, Jonas Bonér jo...@jonasboner.com wrote: 2009/4/16 David Pollak feeder.of.the.be...@gmail.com: On Thu, Apr 16, 2009 at 7:08 AM, Jonas Bonér jo...@jonasboner.com

[Lift] Re: [Lift committers] Re: Meeting

2009-04-17 Thread Lee Mighdoll
I'm currently giving AOP a try herehttp://github.com/mighdoll/aspecting/tree/master(not in lift). I was looking for a cleaner way to create objects with observable properties. I like that an aspect allows for observable objects that are idiomatic to use and write, and don't require any extra

[Lift] Re: [Lift committers] Re: Meeting

2009-04-17 Thread David Pollak
Lee, The reason that Lift has the richer MappedField and Field objects in Mapper and Record is to programmatically add this kind of functionality to fields. No, it's not PoJos, but it's as syntactically clean and a lot easier to understand/debug. Thanks, David On Fri, Apr 17, 2009 at 9:47 AM,

[Lift] Re: [Lift committers] Re: Meeting

2009-04-16 Thread Josh Suereth
I am firmly against anything that re-writes byte-code after the compilation phase for production code. Once the Scala-Maven plugin supports compiler plugins, then there's a lot of stuff that can be done at compile-time. The scala-maven plugin already supports compiler plugins. Feel